Utilities for easier interaction with UEC or EC2

Registered by Scott Moser on 2010-04-26

The lucid cycle introduced 'cloud-utils', a package of tools to make make interaction with uec easier. We would like to continue to expand these tools to easily expose function in the UEC images and make interaction with UEC more user friendly. This would include support for easily re-bundling images.

Blueprint information

Jos Boumans
Scott Moser
Scott Moser
Series goal:
Accepted for maverick
Milestone target:
milestone icon ubuntu-10.10-beta
Started by
Scott Moser on 2010-07-06
Completed by
Scott Moser on 2013-05-13



Spec reduced to one work item and completed.

[ttx] ubuntu-10.10-beta: 1

Roadmap Notes:
Can't do the feature work before Feature Freeze; will be done in a PPA if there is time.

Work items for maverick-alpha-2:
[clint-fewbar] (1)run instance and wait into cloud-utils: DONE
[clint-fewbar] (1)run instance and wait till it is reachable via ssh: DONE
[clint-fewbar] (1)run instance and attach elastic IP address: DONE
[clint-fewbar] (1)run instance and run command, then tear down: DONE

Work items for maverick-alpha-3:
(2)fix bug 556528 ~/.eucarc v. environ: POSTPONED
(2)send mail requesting feedback on rebundle design: POSTPONED
(2)rebundle image (ec2-ubuntu-base) into cloud-utils: POSTPONED
(2)rebundle support for re-bundling an image to EBS: POSTPONED
(2)rebundle support for re-bundling an image to instance store: POSTPONED
(2)rebundle support for "let the user do some things by hand": POSTPONED

Work items for ubuntu-10.10-beta:
[ttx] (2)fix bug 556528 ~/.eucarc v. environ (fix is not worth it): DONE

Targets of opportunity:
(2)send mail requesting feedback on rebundle design: TODO
(2)rebundle image (ec2-ubuntu-base) into cloud-utils in PPA: TODO
(2)rebundle support for re-bundling an image to EBS: TODO
(2)rebundle support for re-bundling an image to instance store: TODO
(2)rebundle support for "let the user do some things by hand": TODO
(3)euca2ools/ec2-api-tools wrapper into cloud-utils: TODO
(3)wrapper name based launching: TODO
(3)published image to tarfile : TODO
(3)uec-cc-setup into cloud-utils: TODO
(3)util for kill all instances: TODO
(3)util for delete instance (by ami or name): TODO
(3)delete all in a bucket (unregistering): TODO

ttx review / 20100526:
 * I'd consider all work items up to "fix bug 556528" to be prio1 and the rest to be prio2
 * Suggested assignees: smoser / ?
 * Estimated complexity: 4-5 for prio1 + 3-4 for prio2
 * Suggested priority: 1/High for prio1 features, 2/Medium for prio2 ones
 * Suggested Subcycle: Iteration 1 (Alpha2) for prio1 and Iteration 2 (Alpha3) for prio2
 * We don't expect there is sufficient dev time to do the prio2 part

jib review 20100526:
  * Given the estimated complexity, this takes up a signifcant part of our development time.
    I'd like to see a distinction between low hanging fruit and time intensive items and prioritize
    the low hanging fruit.
    * [smoser / 2010-05-26] many of the items are simple. realistically, all but the rebundle and and name-based-launching are "low hanging fruit". The rebundle image is something I think would be highly used, and we have a starting point (that was used for creation of DB2 images).

- [2010-05-25/smoser]
  - time estimate: 3-4 weeks


Work Items