{"action":"created","issue":{"url":"https://api.github.com/repos/StackStorm/st2/issues/1360","labels_url":"https://api.github.com/repos/StackStorm/st2/issues/1360/labels{/name}","comments_url":"https://api.github.com/repos/StackStorm/st2/issues/1360/comments","events_url":"https://api.github.com/repos/StackStorm/st2/issues/1360/events","html_url":"https://github.com/StackStorm/st2/pull/1360","id":69975959,"number":1360,"title":"Implement action execution scheduler","user":{"login":"m4dcoder","id":2767408,"avatar_url":"https://avatars.githubusercontent.com/u/2767408?v=3","gravatar_id":"","url":"https://api.github.com/users/m4dcoder","html_url":"https://github.com/m4dcoder","followers_url":"https://api.github.com/users/m4dcoder/followers","following_url":"https://api.github.com/users/m4dcoder/following{/other_user}","gists_url":"https://api.github.com/users/m4dcoder/gists{/gist_id}","starred_url":"https://api.github.com/users/m4dcoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/m4dcoder/subscriptions","organizations_url":"https://api.github.com/users/m4dcoder/orgs","repos_url":"https://api.github.com/users/m4dcoder/repos","events_url":"https://api.github.com/users/m4dcoder/events{/privacy}","received_events_url":"https://api.github.com/users/m4dcoder/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-04-21T23:20:34Z","updated_at":"2015-04-24T06:21:51Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/StackStorm/st2/pulls/1360","html_url":"https://github.com/StackStorm/st2/pull/1360","diff_url":"https://github.com/StackStorm/st2/pull/1360.diff","patch_url":"https://github.com/StackStorm/st2/pull/1360.patch"},"body":"Create a scheduling service that takes the action execution request, performs scheduling logic (placeholder), and dispatch to the action runner(s).  Move the execute_action from the action runner worker to the action service.  Create request, schedule, and execute methods in the action service. Introduced new \"requested\" status."},"comment":{"url":"https://api.github.com/repos/StackStorm/st2/issues/comments/95816214","html_url":"https://github.com/StackStorm/st2/pull/1360#issuecomment-95816214","issue_url":"https://api.github.com/repos/StackStorm/st2/issues/1360","id":95816214,"user":{"login":"manasdk","id":1776099,"avatar_url":"https://avatars.githubusercontent.com/u/1776099?v=3","gravatar_id":"","url":"https://api.github.com/users/manasdk","html_url":"https://github.com/manasdk","followers_url":"https://api.github.com/users/manasdk/followers","following_url":"https://api.github.com/users/manasdk/following{/other_user}","gists_url":"https://api.github.com/users/manasdk/gists{/gist_id}","starred_url":"https://api.github.com/users/manasdk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/manasdk/subscriptions","organizations_url":"https://api.github.com/users/manasdk/orgs","repos_url":"https://api.github.com/users/manasdk/repos","events_url":"https://api.github.com/users/manasdk/events{/privacy}","received_events_url":"https://api.github.com/users/manasdk/received_events","type":"User","site_admin":false},"created_at":"2015-04-24T06:21:51Z","updated_at":"2015-04-24T06:21:51Z","body":"I am a little confused by the change in the publish for liveaction. \r\n\r\nCurrently all objects either publish on create, update or delete. For liveaction there is now publish_schedule. schedule is only a state change therefore it should fall under update at the most rather than its own routing key.\r\n\r\nIn general I am ok to completely changing the publish structure for LiveAction. I would strive to make that internally consistent though,\r\n\r\ne.g. we could go with publish on all state transition of LiveAction so\r\n`publish_schedule`, `publish_requested`,`publish_execute` and `publish_finished`. In this scheme we entirely drop support for `publish_{create/update/delete}`. \r\n\r\nI still believe that update can be used as per the original scheme as that keeps it consistent with other object types and lends to some design predictability."}}