…nstack blimps Last night I was mistakenly using the image ID when trying to associate instead of the server ID, so this fixes that. OpenStack wants a certain order of operations for associating an IP as well, we must associate only after OpenStack says the machine is ready.
…ing boxes from .blimp files
…mpy.d state files
… to tear down their floating ip
… and associate an IP This is the first half of the story, we need to make sure that the right information is being persisted and then the second half can take place: deassociating and releasing the floating IP
…hosts This has only been tested on Ubuntu 10.04 LTS
…inary Fixes #40
…nvoking `blimpy ssh` This restores the behavior of being able to script blimpy with: % blimpy ssh mycloud "ls /etc"
… port 22 is opened Fixes #11
…or security groups