Improvements for cloud-init (uec/ec2 cloud initialization/configuration)
The cloud-init package was added in lucid. It introduced some new mechanisms for configuring (cloud-config) and hooking into (boothooks) initialization of a cloud instance. We would like to continue to expand on this, making cloud-images friendly and powerful to their users. This includes looking at existing function from other sources (such as Turnkey Linux Images) and also new function to be defined.
Blueprint information
- Status:
- Complete
- Approver:
- Jos Boumans
- Priority:
- High
- Drafter:
- Scott Moser
- Direction:
- Approved
- Assignee:
- Scott Moser
- Definition:
- Approved
- Series goal:
- Accepted for maverick
- Implementation:
-
Implemented
- Milestone target:
-
maverick-alpha-2
- Started by
- Scott Moser
- Completed by
- Scott Moser
Whiteboard
Status:
Started
Work items for maverick-alpha-2:
(1)ext4 root filesystem: DONE
*(1)(cloud-
*(1)add uec support to ebsmount: DONE
(1)get ebsmount packaging to state for review/universe inclusion: DONE
(1)get ebsmount into universe: DONE
*(1)write an ebsmount.conf on package installation with sane defaults: DONE
*(1)fix ebsmount (udev/upstart changes/
(1)(cloud-init) make cloud-config hooks plugable by added files: DONE
(1)(cloud-init) wiki document on cloud-init/
(1)(cloud-init) better logging (use python logging): DONE
(1)(cloud-init) better error handling: DONE
*(2)(cloud-init) add turnkey style inithooks behavior: DONE
(2)(cloud-init) cloud-config ssh-import-lp-id: DONE
(2)(cloud-init) cloud-config byobu: DONE
(2)(cloud-init) cloud-config set-selections: DONE
Targets of opportunity:
(3)(cloud-init) user controllable run-once-per: DONE
(3)(cloud-init) blog entries on cloud-init syntax: TODO
(3)(cloud-init) #include from ebs volume: TODO
*: alonswartz will work with smoser on turnkey related items
ttx review / 20100526:
* Missing work items :)
* Since those are mostly unrelated new features, could you split them between prio 1/2/3 (must-do/
* Must-do: current order up to better error handling
* should-do: current order up to cloud-config-
* could-do: remainder
* Suggested assignees: smoser / ?
* Estimated complexity: 4 + 3
* Suggested priority: 1/High for prio1-2 features, 2/Medium for prio2-3 ones
* Suggested Subcycle: Iteration 1 (Alpha2) for prio1-2 and Iteration 2 (Alpha3) for prio2-3
jib review 20100526:
* Agreed with ttx; as this is a collection of items, please split out in prio 1/2/3
Comments:
* [2010-05-24]: smoser : time estimate of 2-3 weeks
