{"action":"closed","issue":{"url":"https://api.github.com/repos/flux-framework/rfc/issues/25","labels_url":"https://api.github.com/repos/flux-framework/rfc/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/rfc/issues/25/comments","events_url":"https://api.github.com/repos/flux-framework/rfc/issues/25/events","html_url":"https://github.com/flux-framework/rfc/issues/25","id":96614933,"number":25,"title":"Create RFC that specifies the form of a resource request and resource allocation","user":{"login":"lipari","id":740218,"avatar_url":"https://avatars.githubusercontent.com/u/740218?v=3","gravatar_id":"","url":"https://api.github.com/users/lipari","html_url":"https://github.com/lipari","followers_url":"https://api.github.com/users/lipari/followers","following_url":"https://api.github.com/users/lipari/following{/other_user}","gists_url":"https://api.github.com/users/lipari/gists{/gist_id}","starred_url":"https://api.github.com/users/lipari/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lipari/subscriptions","organizations_url":"https://api.github.com/users/lipari/orgs","repos_url":"https://api.github.com/users/lipari/repos","events_url":"https://api.github.com/users/lipari/events{/privacy}","received_events_url":"https://api.github.com/users/lipari/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-22T16:51:35Z","updated_at":"2015-10-06T21:34:01Z","closed_at":"2015-10-06T21:34:01Z","body":"In the simplest sense, when a job is allocated a resource, it is assigned that resource to use for a period of time.  A “job” is a synonym for a Flux program as defined in [RFC 8](https://github.com/flux-framework/rfc/blob/master/spec_8.adoc).\r\n\r\nA scheduler’s role is to search, select, and allocate appropriate resources for each job over the course of time.  To do this, a scheduler implements a mechanism for annotating each resource with the job ID which it has either allocated or reserved to a job.\r\n\r\nSubsequent resource searches for idle resources will thereby have a means to identify which resources that are in use, reserved, or available for new jobs.\r\n\r\nBack in February 2015, we discussed resource allocation ideas on the flux-discuss list under the subject, \"Resource Allocation Considerations\".  A summary of those ideas was generated and this elicited more ideas and suggestions.\r\n\r\nThis issue identifies the need to capture in an RFC the ideas that were proposed in that thread.  [RFC 4](https://github.com/flux-framework/rfc/blob/master/spec_4.adoc) presents and defines the Flux resource model.  This issue identifies the need to build on that work in two ways:\r\n* to specify the form of a request for resources\r\n* to specify the rules for annotating resources with their associated jobs\r\n\r\nBoth of these specifications should avoid implementation details and instead provide guidance to be reflected in all implementations."}}