{"action":"created","issue":{"url":"https://api.github.com/repos/dask/dask-jobqueue/issues/68","repository_url":"https://api.github.com/repos/dask/dask-jobqueue","labels_url":"https://api.github.com/repos/dask/dask-jobqueue/issues/68/labels{/name}","comments_url":"https://api.github.com/repos/dask/dask-jobqueue/issues/68/comments","events_url":"https://api.github.com/repos/dask/dask-jobqueue/issues/68/events","html_url":"https://github.com/dask/dask-jobqueue/issues/68","id":330317252,"node_id":"MDU6SXNzdWUzMzAzMTcyNTI=","number":68,"title":"Reorganize the dask-jobqueue config file","user":{"login":"jhamman","id":2443309,"node_id":"MDQ6VXNlcjI0NDMzMDk=","avatar_url":"https://avatars3.githubusercontent.com/u/2443309?v=4","gravatar_id":"","url":"https://api.github.com/users/jhamman","html_url":"https://github.com/jhamman","followers_url":"https://api.github.com/users/jhamman/followers","following_url":"https://api.github.com/users/jhamman/following{/other_user}","gists_url":"https://api.github.com/users/jhamman/gists{/gist_id}","starred_url":"https://api.github.com/users/jhamman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhamman/subscriptions","organizations_url":"https://api.github.com/users/jhamman/orgs","repos_url":"https://api.github.com/users/jhamman/repos","events_url":"https://api.github.com/users/jhamman/events{/privacy}","received_events_url":"https://api.github.com/users/jhamman/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":15,"created_at":"2018-06-07T15:11:36Z","updated_at":"2018-06-13T20:59:41Z","closed_at":null,"author_association":"COLLABORATOR","body":"It is not unheard of to have multiple job queue systems running from the machine. For example, the machine I use the most, Cheyenne, uses both PBS and Slurm. For cases like this, it would be nice if we revamped our config file stricture a bit.\r\n\r\nCurrently we have:\r\n\r\n```yml\r\njobqueue:\r\n  name: dask-worker\r\n  threads: 2\r\n  processes: 4\r\n  memory: 8GB\r\n  interface: null\r\n  death-timeout: 60\r\n  local-directory: null\r\n  extra: \"\"\r\n  env-extra: []\r\n\r\n  queue: null\r\n  project: null\r\n  walltime: '00:30:00'\r\n\r\n  pbs:\r\n    resource-spec: null\r\n    job-extra: []\r\n\r\n  sge:\r\n    resource-spec: null\r\n\r\n  slurm:\r\n    job-cpu: null\r\n    job-mem: null\r\n    job-extra: {}\r\n```\r\n\r\nI'd like to propose that we move some of the jobqueue values into the pbs/sge/slurm catagories:\r\n\r\n```yml\r\njobqueue:\r\n  # dask options\r\n  name: dask-worker\r\n  death-timeout: 60\r\n\r\n  pbs:\r\n    threads: 2\r\n    processes: 4\r\n    memory: 8GB\r\n    interface: null\r\n    local-directory: null\r\n    extra: \"\"\r\n    env-extra: []\r\n    queue: null\r\n    project: null\r\n    walltime: '00:30:00'\r\n    resource-spec: null\r\n    job-extra: []\r\n\r\n  sge:\r\n    threads: 2\r\n    processes: 4\r\n    memory: 8GB\r\n    interface: null\r\n    local-directory: null\r\n    extra: \"\"\r\n    env-extra: []\r\n    queue: null\r\n    project: null\r\n    walltime: '00:30:00'\r\n    resource-spec: null\r\n\r\n  slurm:\r\n    threads: 2\r\n    processes: 4\r\n    memory: 8GB\r\n    interface: null\r\n    local-directory: null\r\n    extra: \"\"\r\n    env-extra: []\r\n    queue: null\r\n    project: null\r\n    walltime: '00:30:00'\r\n\r\n    job-cpu: null\r\n    job-mem: null\r\n    job-extra: {}\r\n```\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/dask/dask-jobqueue/issues/comments/397084914","html_url":"https://github.com/dask/dask-jobqueue/issues/68#issuecomment-397084914","issue_url":"https://api.github.com/repos/dask/dask-jobqueue/issues/68","id":397084914,"node_id":"MDEyOklzc3VlQ29tbWVudDM5NzA4NDkxNA==","user":{"login":"mrocklin","id":306380,"node_id":"MDQ6VXNlcjMwNjM4MA==","avatar_url":"https://avatars3.githubusercontent.com/u/306380?v=4","gravatar_id":"","url":"https://api.github.com/users/mrocklin","html_url":"https://github.com/mrocklin","followers_url":"https://api.github.com/users/mrocklin/followers","following_url":"https://api.github.com/users/mrocklin/following{/other_user}","gists_url":"https://api.github.com/users/mrocklin/gists{/gist_id}","starred_url":"https://api.github.com/users/mrocklin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrocklin/subscriptions","organizations_url":"https://api.github.com/users/mrocklin/orgs","repos_url":"https://api.github.com/users/mrocklin/repos","events_url":"https://api.github.com/users/mrocklin/events{/privacy}","received_events_url":"https://api.github.com/users/mrocklin/received_events","type":"User","site_admin":false},"created_at":"2018-06-13T20:59:41Z","updated_at":"2018-06-13T20:59:41Z","author_association":"MEMBER","body":"> I personnaly have no use of this functionnality, and I believe (but I may be wrong) that this is true for most users. But the current proposed solution is not too intrusive into the scheduler subclass code, and replacing\r\n\r\nRight, so we could also just decide not to make this change.  @jhamman is this a concrete need, or is this more hypothetical?  If the latter then do you have objections to waiting until a user raises this as an issue?"}}
{"actor":{"display_login":"mrocklin"}}