Goals and future of cloud-live project

Registered by Ante Karamatić on 2011-10-19

Cloud-live project delivers usable and bootable cloud infrastructure. Purpose of this blueprint is to set and define goals for the future of the project.

Blueprint information

Status:
Not started
Approver:
Dave Walker
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
Ante Karamatić
Definition:
Approved
Series goal:
Accepted for precise
Implementation:
Deferred
Milestone target:
milestone icon ubuntu-12.04

Related branches

Sprints

Whiteboard

Work Items
[ivoks] Glance storage on remaining space on USB drive: TODO
[ivoks] Use LXC by default: TODO
[ivoks] Need a cloud-image (in addtion to ttylinux): TODO
[ivoks] wifi vs wired network as "live" interface (workout remaning issues): TODO
[ivoks] integrate dashboard, identity, swift (maybe?): TODO
[ivoks] persistent for /etc/nova/nova.conf: TODO
[kirkland] orchestra-live image: TODO

Questions/Comments:
Do you think this require further work, that isn't yet captured? -- Daviey

= STATUS =
http://cloud.ubuntu.com/2011/10/ubuntu-cloud-live-11-10-is-available/

= GOALS/IDEAS =
 * Use remaining space on the stick for glance storage
 * Juju on a stick (some simple charms to run on the cloud-live... ) Not sure its possible with ttylinux
 * Need a cloud-image (in addtion to ttylinux [http://launchpad.net/cirros])
   - smoser asks to please replace with cirros
 * Differentiate/discuss devstack
 * Installer (similar in purpose to devstack)?
    Pretty much thumbs downed by all.
 * Live session on a Server install CD
 * which services can we reasonably provide: compute, image service, object service, identity, horizons, etc...
 * default to LXC (and run a full ubuntu)
  * Exercises LXC
  *
 * Two avail zones: kvm, lxc (wishlist)

cloud-live exposes people to Ubuntu Cloud Infrastructure. (Pull it out and use it periodically/experiment.) What does a cloud infrastructure "feel like".

Instead of GettingStarted, have "Go" and a "gettingstarted"

Target a 4G RAM as a testing case (min) and preferably more. 16 GB disk...
Use existing disk space? (loopback, external disk, etc. Cleanup afterwards.) From a kvm/virtual machine launch, it is typical

A sibling project of juju-live. Juju is very network intensive. bzr repo and lots of apt-get.

orchestra-live-provisioning (with real world installs as remnants.) Probably drop rsyslog, etc. With sufficient squid cache to make the install more or less run without outside network.

cobbler dev system (smoser can explain).

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.