Running cloud images outside UEC or EC2
The UEC cloud images provide a canned Ubuntu Server instance. It is similar in that sense to the Desktop Live CDs. However, due to cloud-specific pieces, it is not very usable outside of EC2 or UEC. This session will discuss other ways which the cloud images could be run, or uses they might have.
* within testdrive
* within kvm
- Jos Boumans
- Scott Moser
- Scott Moser
- Series goal:
- Accepted for maverick
- Milestone target:
- Started by
- Jos Boumans on 2010-08-17
- Completed by
- Scott Moser on 2013-05-13
Small features needed pre-FF, bulk of the work can be done during the Beta
One remaining item for Andres: FFE will be required to have support for this in Testdrive
Work items for maverick-alpha-3:
Write DataSourceNoCloud to plug into cloudinit, allowing boot without EC2 metadata service: POSTPONED
modify cloud-init init process to boot without network: POSTPONED
get FFE filed for testdrive integration: POSTPONED
Work items for ubuntu-10.10-beta:
PreFF - Write DataSourceNoCloud to plug into cloudinit, allowing boot without EC2 metadata service: DONE
PreFF - modify cloud-init init process to boot without network: DONE
get FFE filed for testdrive integration (bug 619974) : DONE
decide how to package the launching doc (libvirt xml or shell script): DONE
decide how to deliver image file [decided not to deliver separate image]: DONE
write documentation on how to use image in kvm: DONE
[andreserl] add code to testdrive to launch ubuntu server: POSTPONED
Work items for ubuntu-10.10:
[andreserl] add code to testdrive to launch ubuntu server: INPROGRESS
Reviewers: ttx + jib
ttx review / 20100526:
* I'm not entirely convinced by the addition of another (kvm-oriented) deliverable. Would it be possible instead to provide a cloud-utils tool to transform a UEC tar.gz into something that consumed by kvm ?
* [smoser / 2010-05-26] That is somewhat the goal. We will need to do some things in cloud-init to not rely so heavily on presense of the EC2 metadata service. Then, we will provide libvirt xml or a tool that can take the partition image and launch it.
* Suggested assignees: smoser / kirkland
* Estimated complexity: 4-6
* Suggested priority: 3/Low
* Suggested Subcycle: Iteration 1 or 2 (Alpha2 or Alpha3)
jib review / 20100526:
* Complexity is too high as it stands to be sure it makes it into Maverick. Unless we can simplify the
deliverable based on current tools/images, we may have to defer.
* [smoser / 2010-05-26] it really isn't terribly complex. The biggest difficulty is providing a way to easily boot the thing in kvm.
* Jos was commenting on your "2-3 weeks of dedicate effort" evaluation, which translates to 4-6 complexity points, which basically means half of a development iteration, which is a lot -- ttx
* smoser 20100524 - The work in this spec is well understood.
* 2-3 weeks of dedicated effort.