Features/Ovirt Node

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
 
(12 intermediate revisions by 2 users not shown)
Line 9: Line 9:
  
 
== Current status ==
 
== Current status ==
* Targeted release: [[Releases/12|Fedora 12]]
+
* Targeted release: [[Releases/13|Fedora 13]]
* Last updated: 2009-07-20
+
* Last updated: 2009-08-19
* Percentage of completion: 77%
+
* Percentage of completion:
 +
 
 +
Moving to F13 target, the spin did not make it into Fedora 12 due to the current level of blacklisting.
  
 
== Detailed Description ==
 
== Detailed Description ==
Line 28: Line 30:
 
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.
 
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/Testing ==
+
== Scope ==
  
 
Process for building upstream ovirt node packages....
 
Process for building upstream ovirt node packages....
Line 35: Line 37:
  
 
2. Build ovirt-node-image (manual step done by ovirt project)
 
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)
+
1. checkout git repo run make recipe
  3. output checking in to fedora cvs as source for (3)
+
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])
 
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)
+
1. does not include iso image, spin hosted on spin.fedoraproject.org
  3. includes tools for manipulating ovirt-node-image
+
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
 
4. Fedora project builds official spin form ks in ovirt-node-recipe
  1. verify that iso form 2 and 4 match.
 
  
 +
* verify that iso form 2 and 4 match (possibility)
 +
1. edit-livecd to open up the filesystem of spin ISO
 +
2. edit-livecd to open up the filesystem of our ISO
 +
3. diff the two
  
 +
== How To Test ==
  
== User Experience ==
+
0. need at least one machine with full hardware virt capability:
  
1. Download spin and burn to cd: ovirt-node can be run as livecd, or installed from livecd to bare-metal
+
1. Install ovirt-node-recipe.rpm to dev box.
  
2. Install ovirt-node-recipe.rpm
+
  1. pull down ovirt-node-image(spin), use get-ovirt-node-image script
    * pull down ovirt-node-image (spin)
+
2. convert to usb disk or set up pxe environment  
    * convert to usb disk or set up pxe environment  
+
3. run ovirt node on septate machine or as "fake node"
    * run ovirt node
+
 
 +
2. you can now run virtual guests on the node
 +
 
 +
1. log onto guest in standalone mode and start a guest
 +
2. connect machine to ovirt server to manage virtual guests
 +
 
 +
== User Experience ==
 +
 
 +
Once a ovirt node is deployed weather installed to the hosts physical storage, or run as a livecd image off a CD or USB key, the user can manage virtual machine on top of the node either n standalone mode or in conjunction with the oVirt management server, a web-based virtual machine management console. 
  
 
== Dependencies ==
 
== Dependencies ==
** ovirt-node.rpm
+
 
** ovirt-node-repo.rpm
+
* Main deps
 +
** ovirt-node.rpm     - https://bugzilla.redhat.com/show_bug.cgi?id=514221
 +
** ovirt-node-repo.rpm - https://bugzilla.redhat.com/show_bug.cgi?id=514311
 
** ovirt-node-spin.iso - https://fedoraproject.org/wiki/Ovirt_Node_Spin
 
** ovirt-node-spin.iso - https://fedoraproject.org/wiki/Ovirt_Node_Spin
  
*RPM deps
+
* RPM deps
 
** matahari - https://bugzilla.redhat.com/show_bug.cgi?id=511148
 
** matahari - https://bugzilla.redhat.com/show_bug.cgi?id=511148
 
** anyterm  - https://bugzilla.redhat.com/show_bug.cgi?id=491694
 
** anyterm  - https://bugzilla.redhat.com/show_bug.cgi?id=491694
Line 81: Line 99:
 
== Comments and Discussion ==
 
== Comments and Discussion ==
  
* See [[Talk:Ovirt_Node]]   
+
* See [[Talk:Features/Ovirt_Node]]   
 
* #ovirt (freenode)
 
* #ovirt (freenode)
 
* ovirt-devel@redhat.com (public mailing list)
 
* ovirt-devel@redhat.com (public mailing list)
  
 
[[Category:FeaturePageIncomplete]]
 
[[Category:FeaturePageIncomplete]]
[[Category:F12_Virt_Features|ovirt-server]]
 

Latest revision as of 21:51, 19 August 2009

Contents

[edit] ovirt-node

[edit] Summary

oVirt Node is a small scaled down version of Fedora used solely to host virtual machine guests.

[edit] Owner

[edit] Current status

  • Targeted release: Fedora 13
  • Last updated: 2009-08-19
  • Percentage of completion:

Moving to F13 target, the spin did not make it into Fedora 12 due to the current level of blacklisting.

[edit] 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)

http://ovirt.org/

[edit] 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.

[edit] Scope

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 recipe
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

* verify that iso form 2 and 4 match (possibility)
1. edit-livecd to open up the filesystem of spin ISO
2. edit-livecd to open up the filesystem of our ISO
3. diff the two

[edit] How To Test

0. need at least one machine with full hardware virt capability:

1. Install ovirt-node-recipe.rpm to dev box.

1. pull down ovirt-node-image(spin), use get-ovirt-node-image script
2. convert to usb disk or set up pxe environment 
3. run ovirt node on septate machine or as "fake node"

2. you can now run virtual guests on the node

1. log onto guest in standalone mode and start a guest
2. connect machine to ovirt server to manage virtual guests

[edit] User Experience

Once a ovirt node is deployed weather installed to the hosts physical storage, or run as a livecd image off a CD or USB key, the user can manage virtual machine on top of the node either n standalone mode or in conjunction with the oVirt management server, a web-based virtual machine management console.

[edit] Dependencies

[edit] Contingency Plan

  • This is a brand new package, so no contingency plan is required.

[edit] Documentation

[edit] 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.

[edit] Comments and Discussion