{"action":"created","issue":{"url":"https://api.github.com/repos/blox/blox/issues/67","repository_url":"https://api.github.com/repos/blox/blox","labels_url":"https://api.github.com/repos/blox/blox/issues/67/labels{/name}","comments_url":"https://api.github.com/repos/blox/blox/issues/67/comments","events_url":"https://api.github.com/repos/blox/blox/issues/67/events","html_url":"https://github.com/blox/blox/issues/67","id":192955572,"number":67,"title":"Implement the existing AWS API for all list and describe calls","user":{"login":"jhspaybar","id":1356513,"avatar_url":"https://avatars.githubusercontent.com/u/1356513?v=3","gravatar_id":"","url":"https://api.github.com/users/jhspaybar","html_url":"https://github.com/jhspaybar","followers_url":"https://api.github.com/users/jhspaybar/followers","following_url":"https://api.github.com/users/jhspaybar/following{/other_user}","gists_url":"https://api.github.com/users/jhspaybar/gists{/gist_id}","starred_url":"https://api.github.com/users/jhspaybar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jhspaybar/subscriptions","organizations_url":"https://api.github.com/users/jhspaybar/orgs","repos_url":"https://api.github.com/users/jhspaybar/repos","events_url":"https://api.github.com/users/jhspaybar/events{/privacy}","received_events_url":"https://api.github.com/users/jhspaybar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-12-01T20:36:05Z","updated_at":"2016-12-05T18:41:04Z","closed_at":null,"body":"Rather than a separate client and separate API I'd prefer to just use the existing AWS SDK and command line tools to query my cluster state from this system, just without the risk of throttling that exists when speaking to the hosted API.\r\n\r\nIt'd also be cool if it implemented the various write APIs as well and forwarded them, but that's probably less valuable for me."},"comment":{"url":"https://api.github.com/repos/blox/blox/issues/comments/264938378","html_url":"https://github.com/blox/blox/issues/67#issuecomment-264938378","issue_url":"https://api.github.com/repos/blox/blox/issues/67","id":264938378,"user":{"login":"kiranmeduri","id":4035,"avatar_url":"https://avatars.githubusercontent.com/u/4035?v=3","gravatar_id":"","url":"https://api.github.com/users/kiranmeduri","html_url":"https://github.com/kiranmeduri","followers_url":"https://api.github.com/users/kiranmeduri/followers","following_url":"https://api.github.com/users/kiranmeduri/following{/other_user}","gists_url":"https://api.github.com/users/kiranmeduri/gists{/gist_id}","starred_url":"https://api.github.com/users/kiranmeduri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kiranmeduri/subscriptions","organizations_url":"https://api.github.com/users/kiranmeduri/orgs","repos_url":"https://api.github.com/users/kiranmeduri/repos","events_url":"https://api.github.com/users/kiranmeduri/events{/privacy}","received_events_url":"https://api.github.com/users/kiranmeduri/received_events","type":"User","site_admin":false},"created_at":"2016-12-05T18:41:04Z","updated_at":"2016-12-05T18:41:04Z","body":"I like the idea of @jhspaybar to conform to AWS ECS APIs for the following reasons\r\n\r\n- Leverage AWS SDK across multiple languages as a path to interact with cluster-state-service.\r\n- Scheduler or other client code may not need to change if they already are using AWS ECS APIs for getting cluster-state.\r\n\r\nHowever I have following concerns which need to be addressed\r\n\r\n- Authn/Authz support similar to AWS service (sigv4) (http://docs.aws.amazon.com/general/latest/gr/signature-version-4.html). At first we can ignore the verification, but need to set right expectation.\r\n- Maintaining compatibility of API may become a blocker for experimentation. To solve this we may need to support two flavors of API which can bloat the code-base. \r\n- Richer APIs may not be available via AWS SDK which can be useful for schedulers (e.g. streaming/watch style APIs)\r\n- ECS will have APIs not supported by cluster-state-service which can cause confusion. For e.g. TaskDefinition management APIs. \r\n\r\nRegarding the write APIs I agree that they can pass-through cluster-state-service. This can enable better task lifecycle management. "}}
{"actor":{"display_login":"kiranmeduri"}}