Merge lp:~tellis/ubuntu-on-ec2/attach-volume into lp:~ubuntu-on-ec2/ubuntu-on-ec2/cloud-utils
Proposed by
Tom Ellis
Status: | Merged |
---|---|
Merged at revision: | 86 |
Proposed branch: | lp:~tellis/ubuntu-on-ec2/attach-volume |
Merge into: | lp:~ubuntu-on-ec2/ubuntu-on-ec2/cloud-utils |
Diff against target: |
71 lines (+40/-0) 1 file modified
uec-run-instances (+40/-0) |
To merge this branch: | bzr merge lp:~tellis/ubuntu-on-ec2/attach-volume |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Tom Ellis (community) | Needs Resubmitting | ||
Scott Moser | Pending | ||
Review via email: mp+49576@code.launchpad.net |
Description of the change
Attach volume on boot of system. This work is based on the associate ip and wait_for=ssh work, as volumes can only be attached successfully when instance status = running.
Tested on UEC, might need some tweaking for volume device on ec2.
My first foray into python so be gentle :-)
To post a comment you must log in.
Thanks for doing this. I have two suggestions: volume- dev). Its fine to use /dev/sdb by default as on ec2, people would probably use --block- device- mapping.
- make default dev (/dev/sdb) configurable via command line options (maybe '--attach-
- support attaching a snapshot. I think with the end goal of EBS root, this is more reasonable. Ie, if the target of --attach-volume starts with SNAP- or 'snap-' the, create a volume from that SNAP, wait for it to become available, and then start the instances.