m (moved Ovirt Node to Features/Ovirt Node) |
(several sections need to be completed in accordance with the standard template--see embeded comments) |
||
| Line 23: | Line 23: | ||
http://ovirt.org/ | http://ovirt.org/ | ||
Process for building upstream ovirt node packages.... | Process for building upstream ovirt node packages.... | ||
| Line 48: | Line 42: | ||
== Benefit to Fedora == | |||
Easy way for users of Fedora and Ovirt to download Ovirt Node Image. Will not require and ISO image to be built and distributed in a RPM. | |||
== Scope == | |||
<!-- What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | |||
* '''FIXME''' | |||
== How To Test == | |||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this feature is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | |||
Remember that you are writing this how to for interested testers to use to check out your feature - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your feature. | |||
A good "how to test" should answer these four questions: | |||
0. What special hardware / data / etc. is needed (if any)? | |||
1. How do I prepare my system to test this feature? What packages | |||
need to be installed, config files edited, etc.? | |||
2. What specific actions do I perform to check that the feature is | |||
working like it's supposed to? | |||
3. What are the expected results of those actions? | |||
--> | |||
* '''FIXME''' | |||
== User Experience == | == User Experience == | ||
<!-- If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice. --> | |||
* '''FIXME''' | |||
1. Download spin and burn to cd: ovirt-node can be run as livecd, or installed from livecd to bare-metal | 1. Download spin and burn to cd: ovirt-node can be run as livecd, or installed from livecd to bare-metal | ||
| Line 85: | Line 104: | ||
* ovirt-devel@redhat.com (public mailing list) | * ovirt-devel@redhat.com (public mailing list) | ||
[[Category:FeaturePageIncomplete]] | |||
<!-- When your feature page is completed and ready for review --> | |||
<!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler --> | |||
[[Category:F12_Virt_Features|ovirt-server]] | [[Category:F12_Virt_Features|ovirt-server]] | ||
Revision as of 21:29, 21 July 2009
ovirt-node
Summary
oVirt Node is a small scaled down version of Fedora used solely to host virtual machine guests.
Owner
- Name: David Huff
- email: dhuff@redhat.com
Current status
- Targeted release: Fedora 12
- Last updated: 2009-07-20
- Percentage of completion: 77%
Detailed Description
oVirt Node consists of a small host image and all libraries/utilities to manage virtual machines with libvirt service via KVM as well as interact with the oVirt Server. The oVirt node can be run in standalone mode or in conjunction with the oVirt management server, a web-based virtual machine management console. The oVirt Node Image is a livecd-based image that can be installed to the hosts physical storage, or run as a livecd image off a CD or USB key.
This feature consists of three parts:
- ovirt-node.rpm -> Provides the core oVirt Node functionality required to support running virtual machines and allow to interact with the oVirt Server
- ovirt-node-recipe.rpm -> Package containing client recipe, tools, and documentation for an oVirt Node image
- ovirt-node-spin.iso -> A official fedora spin of the ovirt-node-image (livecd.iso)
Process for building upstream ovirt node packages....
1. Build ovir-node.rpm in koji (everything in fedora)
2. Build ovirt-node-image (manual step done by ovirt project)
1. checkout git repo run make file 2. output = ks file, manifest.tar, ovirt-node.iso (unofficial) 3. output checking in to fedora cvs as source for (3)
3. Build ovirt-node-recipe in koji (requires extra source from step 2, mainfest.tar [includes recipe])
1. does not include iso image, spin hosted on spin.fedoraproject.org 2. recipe/ks and manifest.tar built at image creation time (2) 3. includes tools for manipulating ovirt-node-image
4. Fedora project builds official spin form ks in ovirt-node-recipe
1. verify that iso form 2 and 4 match.
Benefit to Fedora
Easy way for users of Fedora and Ovirt to download Ovirt Node Image. Will not require and ISO image to be built and distributed in a RPM.
Scope
- FIXME
How To Test
- FIXME
User Experience
- FIXME
1. Download spin and burn to cd: ovirt-node can be run as livecd, or installed from livecd to bare-metal
2. Install ovirt-node-recipe.rpm
* pull down ovirt-node-image (spin) * convert to usb disk or set up pxe environment * run ovirt node
Dependencies
- ovirt-node.rpm
- ovirt-node-repo.rpm
- ovirt-node-spin.iso - https://fedoraproject.org/wiki/Ovirt_Node_Spin
- RPM deps
Contingency Plan
- This is a brand new package, so no contingency plan is required.
Documentation
- Upstream web page: http://ovirt.org
Release Notes
oVirt Node consists of a small host image and all libraries/utilities to manage virtual machines with libvirt service via KVM as well as interact with the oVirt Server. The oVirt node can be run in standalone mode or in conjunction with the oVirt management server, a web-based virtual machine management console. The oVirt Node Image is a livecd-based image that can be installed to the hosts physical storage, or run as a livecd image off a CD or USB key.
Comments and Discussion
- See Talk:Ovirt_Node
- #ovirt (freenode)
- ovirt-devel@redhat.com (public mailing list)