Latest revision as of 19:04, 3 October 2012

oVirt engine 3.1

Summary

The oVirt engine is the management application of the oVirt virtualization platform. Version 3.1 is the latest version, including the GUI and many important new features.

Owner

Name: Juan Hernández
Email: juan.hernandez@redhat.com

Current status

Targeted release: Fedora 18
Last updated: 3 Oct 2012
Percentage of completion: 100%

Jhernand (talk) The feature is complete now, however we had to use the first alternative of the contingency plan, as GWT is not yet available in Fedora.

Jhernand (talk) 20:37, 9 August 2012 (UTC) - The first Fedora 18 build (after branching) is completed and available here.

Jhernand (talk) 20:09, 9 August 2012 (UTC) - A new rawhide build based in the just released upstream version 3.1.0 is now available here.

Jhernand (talk) 14:52, 7 August 2012 (UTC) - A new rawhide build containing all the new features in upstream 3.1 is now available here. It doesn't contain the GUI applications as GWT is not yet available. We will probably go for the first alternative in the contingency plan.

Jhernand (talk) 20:38, 1 August 2012 (UTC) - The first Koji scratch build based in latest rawhide and in the latest upstream 3.1 branch finished correctly.

Detailed Description

Version 3.0 of the oVirt engine was already included in Fedora 17, but we want to bring the new features provided by version 3.1 and we want also to include the GUI applications (web admin and user portal) that were not included because they require GWT.

Benefit to Fedora

Adding version 3.1 of the oVirt engine and the GUI applications to Fedora will attract users that are currently using the upstream project and will provide a complete and seamless virtualization management solution, with a web interface that can be used from virtually any place.

Scope

The scope of the feature includes the update to upstream version 3.1 and the addition of the GUI applications that were not included in Fedora 17.

How To Test

In order to test the user will need to install the ovirt-engine package in any Fedora supported platform (the packages are noarch):

yum install ovirt-engine

Once the feature is 100% completed this will download and install all the required packages, including the GUI applications.

After the installation the user will need to run the engine-setup command line tool. This tool will ask for the details of the environment (ports, passwords, host names, etc), will take care to do all the required configuration changes and will start the required services.

Once the setup is completed and the services up and running the user will use the GUI applications to add hypervisors (using oVirt node or Fedora itself), configure storage and manage virtual machines.

See the testing section of the oVirt wiki for detailed instructions.

User Experience

Users will have the ability to setup a complete virtualization management environment using GUI tools.

Dependencies

The major dependencies of this feature is GWT 2.4.0 (Google Web Toolkit [1]) and GWT-P (GWT Platform [2]). The rest of the dependencies of oVirt engine where added to Fedora as part of the effort to include version 3.0 of the oVirt engine.

We intend to work closely with the owners of other features that also require GWT.

In addition some of the oVirt engine sub-packages have been converted to standalone packages. These are the review request bugs:

Package	Bug
ovirt-log-collector	RHBZ #831878
ovirt-iso-uploader	RHBZ #831881
ovirt-image-uploader	RHBZ #831883

Contingency Plan

In case we can't complete the feature by freeze date we have two alternatives:

Update to upstream version 3.1 of the oVirt engine, but don't include the GUI. We will need to do this if we are not able to have GWT packaged by freeze date.

Keep the current 3.0 version, as no other package in Fedora depends on the oVirt engine packages at the moment.

The second alternative is extremely unlikely to happen, as we think that the update to upstream 3.1 will be very smooth.

Documentation

Release Notes

The version 3.1 of the oVirt engine includes the web based user interface for administrators and users, and many new features, for example:

Live snapshots
Shared disks
External disks
Disk and network interface hotplug
Quotas
CPU pinning
Jumbo frames
Pre-started virtual machine pools
Clone virtual machine from snapshot
POSIX file system storage
Support for Red Hat directory server and IBM Tivoly Directory Server
Support for remote database
Use of ports 80 and 443 for the web interface
All in one (engine and hypervisor in the same machine)

Comments and Discussion

See Talk:Features/Your_Feature_Name

@@ Line 2: / Line 2: @@
 == Summary ==
-oVirt engine 3.1 is the latest version of the management application of the oVirt virtualization platform.
+The oVirt engine is the management application of the oVirt virtualization platform. Version 3.1 is the latest version, including the GUI and many important new features.
 == Owner ==
@@ Line 10: / Line 10: @@
 == Current status ==
 * Targeted release: [[Releases/18 | Fedora 18]]
-* Last updated: 2012-7-18
+* Last updated: 3 Oct 2012
-* Percentage of completion: 70%
+* Percentage of completion: 100%
+[[User:Jhernand|Jhernand]] ([[User talk:Jhernand|talk]]) The feature is complete now, however we had to use the first alternative of the contingency plan, as GWT is not yet available in Fedora.
+[[User:Jhernand|Jhernand]] ([[User talk:Jhernand|talk]]) 20:37, 9 August 2012 (UTC) - The first Fedora 18 build (after branching) is completed and available [http://koji.fedoraproject.org/koji/buildinfo?buildID=346969 here].
+[[User:Jhernand|Jhernand]] ([[User talk:Jhernand|talk]]) 20:09, 9 August 2012 (UTC) - A new rawhide build based in the just released upstream version 3.1.0 is now available [http://koji.fedoraproject.org/koji/buildinfo?buildID=346967 here].
+[[User:Jhernand|Jhernand]] ([[User talk:Jhernand|talk]]) 14:52, 7 August 2012 (UTC) - A new rawhide build containing all the new features in upstream 3.1 is now available [http://koji.fedoraproject.org/koji/buildinfo?buildID=346519 here]. It doesn't contain the GUI applications as GWT is not yet available. We will probably go for the first alternative in the contingency plan.
+[[User:Jhernand|Jhernand]] ([[User talk:Jhernand|talk]]) 20:38, 1 August 2012 (UTC) - The first [http://koji.fedoraproject.org/koji/taskinfo?taskID=4348891 Koji scratch build] based in latest rawhide and in the latest upstream 3.1 branch finished correctly.
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
+Version 3.0 of the oVirt engine was already included in Fedora 17, but we want to bring the new features provided by version 3.1 and we want also to include the GUI applications (web admin and user portal) that were not included because they require GWT.
 == Benefit to Fedora ==
-<!-- What is the benefit to the platform?  If this is a major capability update, what has changed?  If this is a new feature, what capabilities does it bring? Why will Fedora become a better distribution or project because of this feature?-->
+Adding version 3.1 of the oVirt engine and the GUI applications to Fedora will attract users that are currently using the upstream project and will provide a complete and seamless virtualization management solution, with a web interface that can be used from virtually any place.
 == 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?-->
+The scope of the feature includes the update to upstream version 3.1 and the addition of the GUI applications that were not included in Fedora 17.
 == 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.
+In order to test the user will need to install the ovirt-engine package in any Fedora supported platform (the packages are <code>noarch</code>):
-A good "how to test" should answer these four questions:
+<pre>
+yum install ovirt-engine
+</pre>
-. What special hardware / data / etc. is needed (if any)?
+Once the feature is 100% completed this will download and install all the required packages, including the GUI applications.
-. How do I prepare my system to test this feature? What packages
-need to be installed, config files edited, etc.?
+After the installation the user will need to run the <code>engine-setup</code> command line tool. This tool will ask for the details of the environment (ports, passwords, host names, etc), will take care to do all the required configuration changes and will start the required services.
-. What specific actions do I perform to check that the feature is
-working like it's supposed to?
+Once the setup is completed and the services up and running the user will use the GUI applications to add hypervisors (using [http://wiki.ovirt.org/wiki/Category:Node oVirt node] or Fedora itself), configure storage and manage virtual machines.
-. What are the expected results of those actions?
--->
+See the [http://www.ovirt.org/wiki/Building_Ovirt_Engine#Testing testing] section of the oVirt wiki for detailed instructions.
 == 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. -->
+Users will have the ability to setup a complete virtualization management environment using GUI tools.
 == Dependencies ==
-<!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this feature depends?  In other words, completion of another feature owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel feature)? -->
+The major dependencies of this feature is GWT 2.4.0 (Google Web Toolkit [https://developers.google.com/web-toolkit]) and GWT-P (GWT Platform [http://code.google.com/p/gwt-platform]). The rest of the dependencies of oVirt engine where added to Fedora as part of the effort to include version 3.0 of the oVirt engine.
+We intend to work closely with the owners of other features that also require GWT.
+In addition some of the oVirt engine sub-packages have been converted to standalone packages. These are the review request bugs:
+{|
+!Package
+!Bug
+|-
+| ovirt-log-collector
+|{{bz|831878}}
+|-
+|ovirt-iso-uploader
+|{{bz|831881}}
+|-
+|ovirt-image-uploader
+|{{bz|831883}}
+|}
 == Contingency Plan ==
-<!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "None necessary, revert to previous release behaviour."  Or it might not.  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
+In case we can't complete the feature by freeze date we have two alternatives:
+* Update to upstream version 3.1 of the oVirt engine, but don't include the GUI. We will need to do this if we are not able to have GWT packaged by freeze date.
+* Keep the current 3.0 version, as no other package in Fedora depends on the oVirt engine packages at the moment.
+The second alternative is extremely unlikely to happen, as we think that the update to upstream 3.1 will be very smooth.
 == Documentation ==
-<!-- Is there upstream documentation on this feature, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
-*
+* [http://www.ovirt.org/wiki/Main_Page Wiki main page].
+* [http://www.ovirt.org/wiki/Documentation Technical documentation].
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this feature, indicate them here.  You can also link to upstream documentation if it satisfies this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release. -->
+The version 3.1 of the oVirt engine includes the web based user interface for administrators and users, and many new features, for example:
-*
+* Live snapshots
+* Shared disks
+* External disks
+* Disk and network interface hotplug
+* Quotas
+* CPU pinning
+* Jumbo frames
+* Pre-started virtual machine pools
+* Clone virtual machine from snapshot
+* POSIX file system storage
+* Support for Red Hat directory server and IBM Tivoly Directory Server
+* Support for remote database
+* Use of ports 80 and 443 for the web interface
+* All in one (engine and hypervisor in the same machine)
 == Comments and Discussion ==
@@ Line 59: / Line 115: @@
-[[Category:FeaturePageIncomplete]]
+[[Category:FeatureAcceptedF18]]
 <!-- When your feature page is completed and ready for review -->
 <!-- remove Category:FeaturePageIncomplete and change it to Category:FeatureReadyForWrangler -->
 <!-- After review, the feature wrangler will move your page to Category:FeatureReadyForFesco... if it still needs more work it will move back to Category:FeaturePageIncomplete-->
 <!-- A pretty picture of the page category usage is at: https://fedoraproject.org/wiki/Features/Policy/Process -->

Search

Features/oVirtEngine 3.1: Difference between revisions