{"push_id":1248073192,"size":5,"distinct_size":1,"ref":"refs/heads/master","head":"caea193b37b59d831afe158bf9ee33535173e034","before":"c346e8839eaee385d2a2e260428dbd6256bec3a2","commits":[{"sha":"68d4f9123517a1956de0a99c64c69730a323081c","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Add options for configuring workflow polling\n\nmax timeout and poll interval are now configurable.","distinct":false,"url":"https://api.github.com/repos/emccode/docker-machine-rackhd/commits/68d4f9123517a1956de0a99c64c69730a323081c"},{"sha":"cf06d593ee8a31d6ead78c2359a3ea899a53c484","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Clean up help output of default values\n\nWhen \"Value:\" is passed to a mcnflag entry, it is displayed as the\ndefault value in the --help output. No need to also list it out\nin the help string. That leads to mismatched values.","distinct":false,"url":"https://api.github.com/repos/emccode/docker-machine-rackhd/commits/cf06d593ee8a31d6ead78c2359a3ea899a53c484"},{"sha":"3b8a62b964006ee4e4e4d41a5d7d8f637615ce6a","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Remove setting rackhd transport based on SSH port\n\nThe SSH port setting has no bearing on whether RackHD API is on\nhttp or https. I think this got confounded with --rackhd-endpoint.\nIf the endpoint were set to \"localhost:443\", then it would be\nreasonable to switch transport to \"https\", but that's not what the\ncode was doing.","distinct":false,"url":"https://api.github.com/repos/emccode/docker-machine-rackhd/commits/3b8a62b964006ee4e4e4d41a5d7d8f637615ce6a"},{"sha":"fad520068a6145476f676c5771e01cfe843654b2","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Add initial SSH connect attempt retries\n\nAfter we get an IP address for the node, we check to see if we can\nreach the node on the IP:port for SSH. However in some cases the\nnode will not be ready yet. A specific example is the current state\nof installing CoreOS. The workflow is finished as soon as the install\nis finished and starts a reboot. Our logic would see that then attempt\nto connect, which of course would fail because the node is rebooting.\n\nOther OS installs have a \"validate SSH\" task in the workflows, which\ndoesn't show the workflow as finished until SSH into the node is\nsuccessful, but that isn't in place yet for CoreOS.\n\nSo, we add retries and sleep in between. I initially put the sleep\nin net.DialTimeout(), but that is problematic because when the OS\nfirst is coming up, there is a period where the TCP connection is\nrefused (instead of timing out). This is the period between when\nthe OS gets its networking up and when the SSH daemon starts. If\nwe don't sleep separately from net.DialTimeout(), we just go into a\ntight loop with net.DialTimeout() returning immediately each time and\nexhausting all our retries, instead of the desired effect of \"connect\ndidn't work, wait then try again\".","distinct":false,"url":"https://api.github.com/repos/emccode/docker-machine-rackhd/commits/fad520068a6145476f676c5771e01cfe843654b2"},{"sha":"caea193b37b59d831afe158bf9ee33535173e034","author":{"name":"Travis Rhoden","email":"7cdbaf04b8eeaf9fd3ef3382968eb3df2950f2fd@gmail.com"},"message":"Merge pull request #16 from emccode/add_timeouts\n\nAdd some adjustable timeouts","distinct":true,"url":"https://api.github.com/repos/emccode/docker-machine-rackhd/commits/caea193b37b59d831afe158bf9ee33535173e034"}]}
{"actor":{"display_login":"codenrhoden"}}