{"action":"created","issue":{"url":"https://api.github.com/repos/kinow/cylc-docker/issues/2","repository_url":"https://api.github.com/repos/kinow/cylc-docker","labels_url":"https://api.github.com/repos/kinow/cylc-docker/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/kinow/cylc-docker/issues/2/comments","events_url":"https://api.github.com/repos/kinow/cylc-docker/issues/2/events","html_url":"https://github.com/kinow/cylc-docker/issues/2","id":347806716,"node_id":"MDU6SXNzdWUzNDc4MDY3MTY=","number":2,"title":"Cylc as a containerized service","user":{"login":"hjoliver","id":2362137,"node_id":"MDQ6VXNlcjIzNjIxMzc=","avatar_url":"https://avatars0.githubusercontent.com/u/2362137?v=4","gravatar_id":"","url":"https://api.github.com/users/hjoliver","html_url":"https://github.com/hjoliver","followers_url":"https://api.github.com/users/hjoliver/followers","following_url":"https://api.github.com/users/hjoliver/following{/other_user}","gists_url":"https://api.github.com/users/hjoliver/gists{/gist_id}","starred_url":"https://api.github.com/users/hjoliver/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hjoliver/subscriptions","organizations_url":"https://api.github.com/users/hjoliver/orgs","repos_url":"https://api.github.com/users/hjoliver/repos","events_url":"https://api.github.com/users/hjoliver/events{/privacy}","received_events_url":"https://api.github.com/users/hjoliver/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-08-06T07:20:03Z","updated_at":"2018-08-06T09:29:56Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"@kinow - your excellent \"distributed\" example is great for testing cylc in various ways (remote hosts with configurable network latency - brilliant!) but I'm wondering how a containerized cylc might work transparently for users. \r\n\r\nCurrently we expect multiple cylc versions to be installed side by side on suite and job hosts, and we have a built-in way to ensure that suite jobs invoke the same cylc version (if available) as their parent suite.  But of course Python etc. must be compatible on the systems, and cylc has no control over that.\r\n\r\nI wonder if we could have containerized suite server programs (so the containers, like the suite server programs themselves, would live for the duration of the suite run) which would submit jobs that invoke similarly containerized cylc versions for task message commands etc.?\r\n"},"comment":{"url":"https://api.github.com/repos/kinow/cylc-docker/issues/comments/410646944","html_url":"https://github.com/kinow/cylc-docker/issues/2#issuecomment-410646944","issue_url":"https://api.github.com/repos/kinow/cylc-docker/issues/2","id":410646944,"node_id":"MDEyOklzc3VlQ29tbWVudDQxMDY0Njk0NA==","user":{"login":"kinow","id":304786,"node_id":"MDQ6VXNlcjMwNDc4Ng==","avatar_url":"https://avatars1.githubusercontent.com/u/304786?v=4","gravatar_id":"","url":"https://api.github.com/users/kinow","html_url":"https://github.com/kinow","followers_url":"https://api.github.com/users/kinow/followers","following_url":"https://api.github.com/users/kinow/following{/other_user}","gists_url":"https://api.github.com/users/kinow/gists{/gist_id}","starred_url":"https://api.github.com/users/kinow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kinow/subscriptions","organizations_url":"https://api.github.com/users/kinow/orgs","repos_url":"https://api.github.com/users/kinow/repos","events_url":"https://api.github.com/users/kinow/events{/privacy}","received_events_url":"https://api.github.com/users/kinow/received_events","type":"User","site_admin":false},"created_at":"2018-08-06T09:29:56Z","updated_at":"2018-08-06T09:29:56Z","author_association":"OWNER","body":"That's normal. I believe you skipped most of the hype phase. It's getting less hype-y, and easier to keep up with the changes.\r\n\r\nBesides re-using the operating system's kernel, initially I believe they also used the same networking layer. But from what I recall, they decided to completely rewrite the network layer. There were also breaking changes between versions, regressions.\r\n\r\nSo now we have better docs, larger community, and more use cases to use as basis :-)"}}
{"actor":{"display_login":"kinow"}}