From Fedora Project Wiki

No edit summary
m (→‎Comments and Discussion: Fix link to talk page)
 
(12 intermediate revisions by 3 users not shown)
Line 14: Line 14:
== Detailed Description ==
== Detailed Description ==


oVirt Node is a small host image that provides libvirt service via KVM to hosts virtual machines.  The Ovirt node can be run in standalone mode or in conjunction with different management servers, 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 live image off a cd or usb key.
oVirt Node is a small host image that provides libvirt service via KVM to hosts virtual machines.  The Ovirt node can be run in standalone mode or in conjunction with different management servers. The ovirt Node Image is a livecd-based image that can be installed to the hosts physical storage, or run as a live image off a cd or usb key.


http://ovirt.org/
http://ovirt.org/
Line 20: Line 20:
== Benefit to Fedora ==
== Benefit to Fedora ==


Easy way for users of Fedora and oVirt to download an oVirt NodeiImage. This lessens the difficulty by not requiring the user to build an ISO image or being distributed in a RPM.
Easy way for users of Fedora and oVirt to download an oVirt Node image. This lessens the difficulty by not requiring the user to build an ISO image or being distributed in a RPM.


https://fedoraproject.org/wiki/Ovirt_Node
https://fedoraproject.org/wiki/Ovirt_Node
Line 27: Line 27:


* upstream: http://git.fedorahosted.org/git/?p=ovirt/node.git;a=summary
* upstream: http://git.fedorahosted.org/git/?p=ovirt/node.git;a=summary
* already made: http://huff.fedorapeople.org/ovirt-node-recipe.ks (temporary)
* already made: http://jboggs.fedorapeople.org/fedora-live-ovirt-node.ks (temporary)
 
Notes about kickstart
part / is set to 1024 for a smaller footprint, disk usage is approximatly 670MB
 
One section in the kickstart is set --nochroot to put version details directly on the iso. This is used for comparision between upgrade scenaros. We can remove this if its just not possible.
 
All previous blacklisting has been removed


== ISO Name / FS Label ==
== ISO Name / FS Label ==


* FS Label: Fedora-16-x86_64-Ovirt-Node
* FS Label: Fedora-$release-$arch-Ovirt-Node
* ISO Name: Fedora-16-x86_64-Ovirt-Node.iso
* ISO Name: Fedora-$release-$arch-Ovirt-Node.iso
 


== Dependencies ==
== Dependencies ==
BZ#
BZ# [https://bugzilla.redhat.com/show_bug.cgi?id=719184 719184]
Updated virt-manager from upstream for a text based ui of vm management
Updated virt-manager from upstream for a text based ui of vm management
== Scope / Testing ==
== Scope / Testing ==


Run basic spin testing
* Run basic spin testing
Test installs from livecd and usb
* oVirt Node can boot boot from CD/pxeboot
Verify system installs and boots correctly
* Can install successfully via gui and autoconfig via kernel arg parameters
After install and reboot, verify configuration interface works (status/network)
* Set authentication, hostname, and iSCSI initiator successfully.
* Set basic network and VLAN network configuration successfully.
* rsyslog functions work.
* Kdump functions work.
* virt-manager-tui runs and can add storage.
* VMs run on oVirt Node successfully.
 
Test Frequency - major builds steps (Alpha/Beta/RC)
 
Initially we will do builds and post them at each cycle. We'd like to get integrated with Fedora's Release Engineering and incorporate it into Koji.


**** UPDATE ****
Once available launch virt-manager-tui to configure and setup vm's/storage
**** UPDATE ****


== Comments and Discussion ==
== Comments and Discussion ==


* See [[Talk:Ovirt_Node_Image]]   
* See [[Talk:Ovirt_Node_Spin]]   
* #ovirt (oftc)
* #ovirt (oftc)
* ovirt-devel@redhat.com (public mailing list)
* ovirt-devel@redhat.com (public mailing list)
Line 57: Line 70:
----
----


[[Category:Spins_in_Development]]
[[Category:Incomplete_Spins]]


<!-- When your spins page is completed and ready for review,
<!-- When your spins page is completed and ready for review,

Latest revision as of 10:08, 8 October 2011

Ovirt Node Spin

Summary

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

Owner(s)

Moving to F16 target, the spin did not make it into Fedora 12 due to the current level of blacklisting.( RPM/file system blacklisting has been removed)

Detailed Description

oVirt Node is a small host image that provides libvirt service via KVM to hosts virtual machines. The Ovirt node can be run in standalone mode or in conjunction with different management servers. The ovirt Node Image is a livecd-based image that can be installed to the hosts physical storage, or run as a live image off a cd or usb key.

http://ovirt.org/

Benefit to Fedora

Easy way for users of Fedora and oVirt to download an oVirt Node image. This lessens the difficulty by not requiring the user to build an ISO image or being distributed in a RPM.

https://fedoraproject.org/wiki/Ovirt_Node

Kickstart File

Notes about kickstart part / is set to 1024 for a smaller footprint, disk usage is approximatly 670MB

One section in the kickstart is set --nochroot to put version details directly on the iso. This is used for comparision between upgrade scenaros. We can remove this if its just not possible.

All previous blacklisting has been removed

ISO Name / FS Label

  • FS Label: Fedora-$release-$arch-Ovirt-Node
  • ISO Name: Fedora-$release-$arch-Ovirt-Node.iso

Dependencies

BZ# 719184 Updated virt-manager from upstream for a text based ui of vm management

Scope / Testing

  • Run basic spin testing
  • oVirt Node can boot boot from CD/pxeboot
  • Can install successfully via gui and autoconfig via kernel arg parameters
  • Set authentication, hostname, and iSCSI initiator successfully.
  • Set basic network and VLAN network configuration successfully.
  • rsyslog functions work.
  • Kdump functions work.
  • virt-manager-tui runs and can add storage.
  • VMs run on oVirt Node successfully.

Test Frequency - major builds steps (Alpha/Beta/RC)

Initially we will do builds and post them at each cycle. We'd like to get integrated with Fedora's Release Engineering and incorporate it into Koji.


Comments and Discussion