[Blueprint servercloud-p-pushing-cloud] Pushing Ubuntu to the Cloud

2012-04-17 Thread Ben Howard
Blueprint changed by Ben Howard:

Whiteboard changed:
  Work Items:
  [utlemming] Stand-up a public glance server: POSTPONED
  [utlemming] Write new Query format in JSON: INPROGRESS
- [utlemming] Alter build scripts to publish to glance server: INPROGRESS
- [utlemming] Write ubuntu-cloud-images-sync script: INPROGRESS
+ [utlemming] Alter build scripts to publish to glance server: DONE
+ [utlemming] Write ubuntu-cloud-images-sync script: DONE
  [utlemming] Document how to consume public glance server: POSTPONED
  [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance 
server: POSTPONED
  [heckj] Change Dashboard to support multiple glance registry servers: TODO
  [heckj] 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
- [utlemming] Upstream changes to live-build: TODO
- [smoser] Stand-up a public glance server: TODO
+ [utlemming] Eucalytpus sync script: DEFERRED
+ [utlemming] Upstream changes to live-build: DEFERRED
+ [utlemming] Stand-up a public glance server: DEFERRED
  
  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
  
  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-pushing-cloud

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Blueprint servercloud-p-pushing-cloud] Pushing Ubuntu to the Cloud

2012-04-17 Thread Chris Johnston
Blueprint changed by Chris Johnston:

Whiteboard changed:
  Work Items:
  [utlemming] Stand-up a public glance server: POSTPONED
  [utlemming] Write new Query format in JSON: INPROGRESS
  [utlemming] Alter build scripts to publish to glance server: DONE
  [utlemming] Write ubuntu-cloud-images-sync script: DONE
  [utlemming] Document how to consume public glance server: POSTPONED
  [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance 
server: POSTPONED
  [heckj] Change Dashboard to support multiple glance registry servers: TODO
  [heckj] Add GPG support for image authenticity: TODO
  [smoser] cloud-init should look for archive.local and support apt-proxy: TODO
- [utlemming] Eucalytpus sync script: DEFERRED
- [utlemming] Upstream changes to live-build: DEFERRED
- [utlemming] Stand-up a public glance server: DEFERRED
+ [utlemming] Eucalytpus sync script: POSTPONED
+ [utlemming] Upstream changes to live-build: POSTPONED
+ [utlemming] Stand-up a public glance server: POSTPONED
  
  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
  
  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-pushing-cloud

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Blueprint servercloud-p-pushing-cloud] Pushing Ubuntu to the Cloud

2012-02-02 Thread Ben Howard
Blueprint changed by Ben Howard:

Whiteboard changed:
  Work Items:
- [utlemming] 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
+ [utlemming] Stand-up a public glance server: DEFERED
+ [utlemming] Write new Query format in JSON: IN-PROGRESS
+ [utlemming] Alter build scripts to publish to glance server: IN-PROGRESS
+ [utlemming] Write ubuntu-cloud-images-sync script: IN-PROGRESS
+ [utlemming] Document how to consume public glance server: DEFERRED
+ [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance 
server: DEFERRED
  [heckj] Change Dashboard to support multiple glance registry servers: TODO
  [heckj] 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
  [utlemming] Upstream changes to live-build: TODO
  [smoser] Stand-up a public glance server: 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
  
  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-pushing-cloud

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Blueprint servercloud-p-pushing-cloud] Pushing Ubuntu to the Cloud

2012-02-02 Thread Chris Johnston
Blueprint changed by Chris Johnston:

Whiteboard changed:
  Work Items:
- [utlemming] Stand-up a public glance server: DEFERED
- [utlemming] Write new Query format in JSON: IN-PROGRESS
- [utlemming] Alter build scripts to publish to glance server: IN-PROGRESS
- [utlemming] Write ubuntu-cloud-images-sync script: IN-PROGRESS
- [utlemming] Document how to consume public glance server: DEFERRED
- [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance 
server: DEFERRED
+ [utlemming] Stand-up a public glance server: POSTPONED
+ [utlemming] Write new Query format in JSON: INPROGRESS
+ [utlemming] Alter build scripts to publish to glance server: INPROGRESS
+ [utlemming] Write ubuntu-cloud-images-sync script: INPROGRESS
+ [utlemming] Document how to consume public glance server: POSTPONED
+ [utlemming] Modify Ubuntu openstack packaging to include Ubuntu glance 
server: POSTPONED
  [heckj] Change Dashboard to support multiple glance registry servers: TODO
  [heckj] 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
  [utlemming] Upstream changes to live-build: TODO
  [smoser] Stand-up a public glance server: 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
  
  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-pushing-cloud

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs