{"action":"created","issue":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/268","labels_url":"https://api.github.com/repos/flux-framework/flux-core/issues/268/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/flux-core/issues/268/comments","events_url":"https://api.github.com/repos/flux-framework/flux-core/issues/268/events","html_url":"https://github.com/flux-framework/flux-core/issues/268","id":94823299,"number":268,"title":"Job submission API","user":{"login":"trws","id":660149,"avatar_url":"https://avatars.githubusercontent.com/u/660149?v=3","gravatar_id":"","url":"https://api.github.com/users/trws","html_url":"https://github.com/trws","followers_url":"https://api.github.com/users/trws/followers","following_url":"https://api.github.com/users/trws/following{/other_user}","gists_url":"https://api.github.com/users/trws/gists{/gist_id}","starred_url":"https://api.github.com/users/trws/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trws/subscriptions","organizations_url":"https://api.github.com/users/trws/orgs","repos_url":"https://api.github.com/users/trws/repos","events_url":"https://api.github.com/users/trws/events{/privacy}","received_events_url":"https://api.github.com/users/trws/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/flux-framework/flux-core/milestones/2","html_url":"https://github.com/flux-framework/flux-core/milestones/Flux%20in-job%20scheduling%20tool%20-%20minimal","labels_url":"https://api.github.com/repos/flux-framework/flux-core/milestones/2/labels","id":1086398,"number":2,"title":"Flux in-job scheduling tool - minimal","description":"This aggregates the issues necessary to get flux to the point that it can be used as a scheduler inside an allocation from an outer resource manager such as SLURM or Torque.  It should be the first published test release for flux as a hierarchical resource manager for a single user on a relatively small scale.","creator":{"login":"trws","id":660149,"avatar_url":"https://avatars.githubusercontent.com/u/660149?v=3","gravatar_id":"","url":"https://api.github.com/users/trws","html_url":"https://github.com/trws","followers_url":"https://api.github.com/users/trws/followers","following_url":"https://api.github.com/users/trws/following{/other_user}","gists_url":"https://api.github.com/users/trws/gists{/gist_id}","starred_url":"https://api.github.com/users/trws/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trws/subscriptions","organizations_url":"https://api.github.com/users/trws/orgs","repos_url":"https://api.github.com/users/trws/repos","events_url":"https://api.github.com/users/trws/events{/privacy}","received_events_url":"https://api.github.com/users/trws/received_events","type":"User","site_admin":false},"open_issues":9,"closed_issues":3,"state":"open","created_at":"2015-04-27T22:59:02Z","updated_at":"2015-07-27T21:54:15Z","due_on":null,"closed_at":null},"comments":4,"created_at":"2015-07-13T22:08:15Z","updated_at":"2015-07-28T16:41:43Z","closed_at":null,"body":"While the tool can be prototyped with the 'flux-submit' tool, to be practical it will require a way to submit jobs directly to the system.  If we need to design this, it seems as though it would be worth designing an interface for job submission, something that different schedulers or perhaps even a core component can implement and provide a common target.\r\n\r\nRequirements:\r\n* An expected response, probably an RPC or request to the scheduler\r\n* A mechanism to create, and populate, a job request"},"comment":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/comments/125674894","html_url":"https://github.com/flux-framework/flux-core/issues/268#issuecomment-125674894","issue_url":"https://api.github.com/repos/flux-framework/flux-core/issues/268","id":125674894,"user":{"login":"trws","id":660149,"avatar_url":"https://avatars.githubusercontent.com/u/660149?v=3","gravatar_id":"","url":"https://api.github.com/users/trws","html_url":"https://github.com/trws","followers_url":"https://api.github.com/users/trws/followers","following_url":"https://api.github.com/users/trws/following{/other_user}","gists_url":"https://api.github.com/users/trws/gists{/gist_id}","starred_url":"https://api.github.com/users/trws/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trws/subscriptions","organizations_url":"https://api.github.com/users/trws/orgs","repos_url":"https://api.github.com/users/trws/repos","events_url":"https://api.github.com/users/trws/events{/privacy}","received_events_url":"https://api.github.com/users/trws/received_events","type":"User","site_admin":false},"created_at":"2015-07-28T16:41:43Z","updated_at":"2015-07-28T16:41:43Z","body":"It also requires the second, to use your numbering scheme.  What I'm looking for is a way to generically submit a job to whatever mechanism is available that should service that request.  At the bare minimum, that may be a blocking queue of length one that simply does a feasibility check, an availability check, and either blocks or fails if the feasibility check passes and the availability check fails.  When the availability check passes, the resources are allocated and the job is run.  This is distinct from a \"run\" service that runs a given set of tasks on a specific set of pre-determined resources."}}