Merge lp://qastaging/~ahs3/cloud-live/natty-upgrade into lp://qastaging/cloud-live
| Status: | Merged | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Merged at revision: | 21 | ||||||||||||||||
| Proposed branch: | lp://qastaging/~ahs3/cloud-live/natty-upgrade | ||||||||||||||||
| Merge into: | lp://qastaging/cloud-live | ||||||||||||||||
| Diff against target: | 2274 lines | ||||||||||||||||
| To merge this branch: | bzr merge lp://qastaging/~ahs3/cloud-live/natty-upgrade | ||||||||||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| David Medberry (community) | Approve | ||
|
Review via email:
|
|||
Description of the change
So, there are a lot of changes here. The collection of changes are to:
-- Convert to the standard live-build structure; this means converting from live-helper to live-build, and moving the openstack-live configuration items from chroot_
-- Move the image to being bootable on a USB stick.
-- Convert to using the latest version of Natty (including updates).
-- Convert to using the latest version of Cactus (from the OpenStack PPAs, not Natty).
Note that one change in all of this is to use QEMU for libvirt and not KVM. This should allow the demo to run in more environments without modifying the configuration (e.g., Intel vs AMD processors where the former does not support nested VMs). The downside is a minor loss of speed in the VMs; however, since ttylinux is being used, it is not terribly noticeable. This is also easily changed by the user if speed is an issue. LXC was attempted but ran into trouble with Cactus; this precludes using this version of the demo on ARM, but that's not really an issue until Oneiric which uses OpenStack Diablo anyway, a different version of this demo.
| Al Stone (ahs3) wrote | # |
Looked through (long) diff and saw nothing troubling. Finally figured out that you were including the config ppa (which was confusing me to no end.) Once I grokked that, built and tested. Go for it.
Process check: I selected "Review: Approve" in the web gui. Am I supposed to discuss in email first?