{"action":"created","issue":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/338","labels_url":"https://api.github.com/repos/flux-framework/flux-core/issues/338/labels{/name}","comments_url":"https://api.github.com/repos/flux-framework/flux-core/issues/338/comments","events_url":"https://api.github.com/repos/flux-framework/flux-core/issues/338/events","html_url":"https://github.com/flux-framework/flux-core/issues/338","id":102012189,"number":338,"title":"replace current job module with job submit service","user":{"login":"grondo","id":741970,"avatar_url":"https://avatars.githubusercontent.com/u/741970?v=3","gravatar_id":"","url":"https://api.github.com/users/grondo","html_url":"https://github.com/grondo","followers_url":"https://api.github.com/users/grondo/followers","following_url":"https://api.github.com/users/grondo/following{/other_user}","gists_url":"https://api.github.com/users/grondo/gists{/gist_id}","starred_url":"https://api.github.com/users/grondo/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grondo/subscriptions","organizations_url":"https://api.github.com/users/grondo/orgs","repos_url":"https://api.github.com/users/grondo/repos","events_url":"https://api.github.com/users/grondo/events{/privacy}","received_events_url":"https://api.github.com/users/grondo/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":7,"closed_issues":11,"state":"open","created_at":"2015-04-27T22:59:02Z","updated_at":"2015-09-23T23:42:19Z","due_on":null,"closed_at":null},"comments":8,"created_at":"2015-08-19T22:23:05Z","updated_at":"2015-09-25T22:17:37Z","closed_at":null,"body":"Job module on rank 0 should be replaced by a service implementing a suitable subset of Job Submit API (#268) and Job Feasibility Filter/Checks (#269).\r\n\r\nThe current `job` service should be extended to take a minimum viable job description encoded in JSON and perform a simple job feasibility check. If feasibility fails, a descriptive error is returned to the caller in the response. If job request is feasible, then the new job/submit module shall allocate a new lwj id and populate a job description skeleton in appropriate kvs directory, then respond to caller with success and the newly allocated jobid or kvs path.\r\n\r\nThe key requirements in this issue are the job feasibility check and response that indicates error (job not feasible) or success (a valid job request has been submitted to the queue)\r\n\r\nOPTION: submit service has configurable or registered stack of filters that can reject and/or modify job submission.\r\n"},"comment":{"url":"https://api.github.com/repos/flux-framework/flux-core/issues/comments/143366108","html_url":"https://github.com/flux-framework/flux-core/issues/338#issuecomment-143366108","issue_url":"https://api.github.com/repos/flux-framework/flux-core/issues/338","id":143366108,"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-09-25T22:17:37Z","updated_at":"2015-09-25T22:17:37Z","body":"Not exactly.  Making it possible to run several copies of a scheduler \nthat are more-or-less stand-alone but act against the same pool of \nresources.  The net result would be a distributed scheduler I suppose, \nbut I wasn't thinking of anything quite fancy enough to be worthy of the \nname.  Basically, it's safe to ignore that paragraph as a thought \nexperiment.\n\nOn 25 Sep 2015, at 15:14, Mark Grondona wrote:\n\n> Yes, good idea on the uuid, I was suggesting hash of contents because \n> requesting entity could know a priori what the ID would be, but other \n> than there is no benefit and a UUID is just as good (already used in \n> `cmb.exec` service anyway).\n>\n> I like the idea of user tag, generated by a filter if not supplied. \n> This will make viewing/searching for jobs much more user friendly. \n> We'd also want a way to at least loosely sort uuids, maybe based on a \n> kvs timestamp?\n>\n> @trws, you might have to explain your last comment again -- are you \n> talking about development of a distributed scheduler?\n>\n> ---\n> Reply to this email directly or view it on GitHub:\n> https://github.com/flux-framework/flux-core/issues/338#issuecomment-143365734\n"}}