{"action":"opened","issue":{"url":"https://api.github.com/repos/mesos/chronos/issues/440","labels_url":"https://api.github.com/repos/mesos/chronos/issues/440/labels{/name}","comments_url":"https://api.github.com/repos/mesos/chronos/issues/440/comments","events_url":"https://api.github.com/repos/mesos/chronos/issues/440/events","html_url":"https://github.com/mesos/chronos/issues/440","id":74482975,"number":440,"title":"Job Groups","user":{"login":"WalterDalton","id":1930065,"avatar_url":"https://avatars.githubusercontent.com/u/1930065?v=3","gravatar_id":"","url":"https://api.github.com/users/WalterDalton","html_url":"https://github.com/WalterDalton","followers_url":"https://api.github.com/users/WalterDalton/followers","following_url":"https://api.github.com/users/WalterDalton/following{/other_user}","gists_url":"https://api.github.com/users/WalterDalton/gists{/gist_id}","starred_url":"https://api.github.com/users/WalterDalton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WalterDalton/subscriptions","organizations_url":"https://api.github.com/users/WalterDalton/orgs","repos_url":"https://api.github.com/users/WalterDalton/repos","events_url":"https://api.github.com/users/WalterDalton/events{/privacy}","received_events_url":"https://api.github.com/users/WalterDalton/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-08T20:21:16Z","updated_at":"2015-05-08T20:21:16Z","closed_at":null,"body":"I am getting to know Chronos and there are some awesome features for Mesos clusters in it. One thing I was curious on the communities thoughts with was the concept of job groups.  Individual jobs at our org are broken up into several tasks that have the parent/child relationship.  While in Chronos it appears that everything is a \"job\" even what we'd consider a task. Yes, you can link 5 jobs together, and you could do this with tasks, but from a management standpoint, there is a concept of the success/failure of individual tasks (maybe a ETL job that checks for files, retrieves files, loads to HDFS, parses into managed tables in hive, archives source data) The job may be \"load_trans_data\" and the tasks are all those individual parts.  \r\n\r\nI could just preface each part with load_trans_data_retrieve, then load_trans_data_run_hive  etc\r\nbut there is no grouping of that in the UI which makes it interesting.  \r\n\r\nI'd really be interested in the thoughts of community "}}