{"action":"created","issue":{"url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/114","repository_url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws","labels_url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/114/labels{/name}","comments_url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/114/comments","events_url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/114/events","html_url":"https://github.com/buildkite/elastic-ci-stack-for-aws/pull/114","id":170801800,"number":114,"title":"Basic support for paravirtualized images","user":{"login":"Vektah","id":2247982,"avatar_url":"https://avatars.githubusercontent.com/u/2247982?v=3","gravatar_id":"","url":"https://api.github.com/users/Vektah","html_url":"https://github.com/Vektah","followers_url":"https://api.github.com/users/Vektah/followers","following_url":"https://api.github.com/users/Vektah/following{/other_user}","gists_url":"https://api.github.com/users/Vektah/gists{/gist_id}","starred_url":"https://api.github.com/users/Vektah/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Vektah/subscriptions","organizations_url":"https://api.github.com/users/Vektah/orgs","repos_url":"https://api.github.com/users/Vektah/repos","events_url":"https://api.github.com/users/Vektah/events{/privacy}","received_events_url":"https://api.github.com/users/Vektah/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-08-12T05:32:11Z","updated_at":"2016-08-15T01:09:20Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/pulls/114","html_url":"https://github.com/buildkite/elastic-ci-stack-for-aws/pull/114","diff_url":"https://github.com/buildkite/elastic-ci-stack-for-aws/pull/114.diff","patch_url":"https://github.com/buildkite/elastic-ci-stack-for-aws/pull/114.patch"},"body":"This is by no means complete, but I wanted to see if anyone else is interested using the older paravirtualized instance types?\r\n\r\nspot pricing for the c4.large instances is going crazy:\r\n![image](https://cloud.githubusercontent.com/assets/2247982/17613490/4eda2d56-60a1-11e6-97f7-73ac4a753b4c.png)\r\n\r\nThese huge price spikes cause instance terminations regardless of lifecycled which look like this in a job:\r\n```\r\n$ docker-compose -f .buildkite/docker-compose.yml -p buildkite135479143c984704a4046342d74118a4 kill\r\nERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?\r\n \r\nIf it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.\r\n$ docker-compose -f .buildkite/docker-compose.yml -p buildkite135479143c984704a4046342d74118a4 rm --force --all -v\r\nERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?\r\n \r\nIf it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.\r\n$ docker-compose -f .buildkite/docker-compose.yml -p buildkite135479143c984704a4046342d74118a4 down\r\nERROR: Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?\r\n \r\nIf it's at a non-standard location, specify the URL with the DOCKER_HOST environment variable.\r\n```\r\n\r\n\r\n\r\nOlder instance types seem to have much more capacity, and lower more stable prices:\r\n![image](https://cloud.githubusercontent.com/assets/2247982/17613500/73116324-60a1-11e6-9647-e71b762a8f95.png)\r\n\r\nThese are the bare minimum changes required to use the PV instances like m1.large, if there is interest perhaps the mappings should support these instance types automatically?"},"comment":{"url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/comments/239711276","html_url":"https://github.com/buildkite/elastic-ci-stack-for-aws/pull/114#issuecomment-239711276","issue_url":"https://api.github.com/repos/buildkite/elastic-ci-stack-for-aws/issues/114","id":239711276,"user":{"login":"toolmantim","id":153,"avatar_url":"https://avatars.githubusercontent.com/u/153?v=3","gravatar_id":"","url":"https://api.github.com/users/toolmantim","html_url":"https://github.com/toolmantim","followers_url":"https://api.github.com/users/toolmantim/followers","following_url":"https://api.github.com/users/toolmantim/following{/other_user}","gists_url":"https://api.github.com/users/toolmantim/gists{/gist_id}","starred_url":"https://api.github.com/users/toolmantim/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolmantim/subscriptions","organizations_url":"https://api.github.com/users/toolmantim/orgs","repos_url":"https://api.github.com/users/toolmantim/repos","events_url":"https://api.github.com/users/toolmantim/events{/privacy}","received_events_url":"https://api.github.com/users/toolmantim/received_events","type":"User","site_admin":false},"created_at":"2016-08-15T01:09:20Z","updated_at":"2016-08-15T01:09:20Z","body":"So for spot instances, we're going add some kind of signal support to say \"I'm shutting down, so cancel this job but feel free to retry\" and a pipeline step can say `retryable` or something similar, and it'll just reschedule it to run again.\r\n\r\nAs for PV support, it'd be great to add support for this with some kind of mapping. Assuming it's not massive overhead?"}}
{"actor":{"display_login":"toolmantim"}}