[Blueprint servercloud-s-cloud-init] Cloud Init & Cloud Image Development for Saucy

[Scott Moser]

Blueprint changed by Scott Moser:

Whiteboard changed:
  [USER STORIES]
+ Cloud Vender A has some information they want to make available to instances running inside their guest. This includes local mirrors or useful packages to install. They want to be able to put this data into some standard location and have images adapt to it.
+ 
+ Developer Joe wants to work on a cloud-init datasource. He wants to
+ modify the cloud-image from a "black box" perspective and insert his
+ datasource in, and have cloud-init use it as if it were already inside
+ the image.
+ 
+ Vendor A wants to use the ubuntu cloud images to deliver their
+ customized solution, and wants to do as little as possible to take
+ advantage of the regular updates created. They want to provide cloud-
+ init with some data that lives on a volume, and register an image with
+ the attached volume. Then, cloud-init will read the cloud-config from
+ that source in addition to the user's user-data.
+ 
  [ASSUMPTIONS]
  [RISKS]
+ Frankenstein cloud-init datasource / config is complex and unwieldy.
+ openstack does not accept vendor-data.
+ 
  [IN SCOPE]
  [OUT OF SCOPE]
  [USER ACCEPTANCE]
  [RELEASE NOTE/BLOG]
+ Ubuntu cloud images can now use openstack's "vendor-data", allowing generic images to be taylored to a local cloud.
  
- [NOTES]
- vUDS Notes at: http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-init
+ [UDS NOTES]
+  * also relevant is blueprint servercloud-s-cloud-vagrant
+  * vUDS 1305: http://pad.ubuntu.com/uds-1305-servercloud-s-cloud-init
+  * vUDS 1308: http://pad.ubuntu.com/uds-1308-servercloud-s-cloudinit

-- 
Cloud Init & Cloud Image Development for Saucy
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-cloud-init