[Blueprint servercloud-p-build-marshall] Pushing Ubuntu to the Cloud

[Ben Howard]

Blueprint changed by Ben Howard:

Whiteboard changed:
- Rationale: There is significant value to both the community and paid
- customers in having Canonical own and maintaining images on major cloud-
- vendors.
+ Work Items:
+ [utlemming/smoser] Stand-up a public glance server (TODO)
+ [utlemming] Alter build scripts to publish to glance server (TODO)
+ [utlemming] Write "ubuntu-cloud-images-sync" script (TODO)
+ [utlemming] Document how to consume public glance server (TODO)
+ [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance server (TODO)
+ [Joe Heck] Change Dashboard to support multiple glance registry servers (TODO)
+ [Joe Heck] Add GPG support for image authenticity (TODO)
+ [smoser] cloud-init should look for archive.local and support apt-proxy (TODO)
+ [utlemming] Eucalytpus sync script (TODO)
+ 
+ 
+ Rationale: There is significant value to both the community and paid customers in having Canonical own and maintaining images on major cloud-vendors.
  
  Assumptions:
-   * There are literally thousands of public Ubuntu public images; each public image is slightly different and is confusing to customers.
-   * Owning our own images will help to reduce vendor customization and make for a consistent experience across different cloud-vendors.
-   * There will be new major cloud-vendors that will want the official images, or on which we want to publish images. 
-   * The current system was design for publishing images to one vendors in multiple regions
-   * Amazon AWS is growing with new services and new regions, which may stress the current system
+   * There are literally thousands of public Ubuntu public images; each public image is slightly different and is confusing to customers.
+   * Owning our own images will help to reduce vendor customization and make for a consistent experience across different cloud-vendors.
+   * There will be new major cloud-vendors that will want the official images, or on which we want to publish images.
+   * The current system was design for publishing images to one vendors in multiple regions
+   * Amazon AWS is growing with new services and new regions, which may stress the current system
  
- 
- [smagoun] This sounds similar to Offspring, which could be easily adapted to produce and deploy images to the cloud. https://launchpad.net/offspring . Linaro have a public Offspring instance here: https://offspring.linaro.org/ . Canonical have an internal Offspring instance as well.
- 
- [utlemming] Thanks Steve for the information about Offspring. The
- problem that we are facing here is a bit different. We have one build
- that needs to be pushed out to N cloud vendors using API's or some sane
- way to do it. If I understand Offspring it is a build wrapper that
- tracks success or failure.
+ UDS Deciusions:
+ To provide multiple ways for different cloud vendors to consume the official Ubuntu images. The four methods decided on are:
+ 1. Push Ubuntu images to all EC2 regions
+ 2. Provide a public glance server for OpenStack Deployments. OpenStack to make changes to support multiple glance registry servers.
+ 3. Provide a sync script for people to pull the latest images for OpenStack
+ 4. Provide a sync script for people to pull the latest images for Eucalpytus
+ To

-- 
Pushing Ubuntu to the Cloud
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-p-build-marshall