Features/oVirtEngine 3.1

From FedoraProject

< Features(Difference between revisions)
Jump to: navigation, search
(Scope)
(How To Test)
Line 26: Line 26:
  
 
== How To Test ==
 
== 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>
  
0. 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.
1. 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.
2. 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.
3. 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 ==
 
== User Experience ==

Revision as of 14:02, 18 July 2012

Contents

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

Current status

  • Targeted release: Fedora 18
  • Last updated: 2012-7-18
  • Percentage of completion: 70%

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

Dependencies

Contingency Plan

Documentation

Release Notes

Comments and Discussion