Guest filesystem
Have a filesystem for the guest which includes any extra needed guest tools. The filesystem may be an existing LEB (developer?). We may add packages to the standard LEB.
The filesystem shall be suitable for use with libvirt.
Blueprint information
- Status:
- Complete
- Approver:
- Michael Hope
- Priority:
- Medium
- Drafter:
- Michael Hope
- Direction:
- Needs approval
- Assignee:
- Michael Hope
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Michael Hope
- Completed by
- Michael Hope
Related branches
Sprints
Whiteboard
2012-03-26 michaelh1 sent smoser an email re: tools
2012-03-27 smoser replied. utlemming did the implementation. Daviey said it would be a shame if we had to fork the images and michaelh1 agrees.
Notes on nocloud are at:
http://
nocloud seems fine. You need meta-data and user-data which can be loaded into the images under /var/lib/
~/opt/bin/
Images are built via live-build at:
https:/
with documentation at:
https:/
Notes:
* Openstack prefers a plain EXT4 image so it can resize on creation
* Can resize images but not the FS inside
* Ubuntu supply a UEC image under http://
* armhf-disk1.img is a qcow2 generic image
* armhf_omap-
* armhf.tar.gz is the armhf_omap-
[1] from a 1.0 point of view, the existing nano prebuilt image is fine. It includes the overlay which can be used to pull extra packages at boot.
Work Items
Work items:
Check Ubuntu UEC image for suitability: DONE
Check Linaro nano image for suitability[1]: DONE
Dependency tree
* Blueprints in grey have been implemented.
