oVirt 3.6 Test Day

Objective

  • engage project users and stakeholders to a hands-on experiences with oVirt new release.
  • improve the quality of oVirt.
  • Introduce and validate new oVirt 3.6 features.

What I should do

Test Days are an opportunity to exercise a completed, or in-development, Feature planned for an upcoming oVirt release. Each Test Day brings something unique and you’re encouraged to join and share your ideas, tests, and results.

  • If you already have the hardware, verify if it meets the hardware requirements in oVirt 3.6 Release Notes
  • Write down the configuration you used (HW, console, etc) and what you’ve tested in the oVirt 3.6 Beta Test Day etherpad.
  • Follow the documentation to setup your environment, and test drive the new features.
  • Please remember we expect to see some issues, and anything you come up with will save you when you’ll install final release.
  • Remember to try daily tasks you’d usually do in the engine, to see there are no regressions.
  • Accomplish the goals set in objective section , run the tests, update the test matrix.

Bug Reporting

Running into any issues? Try to get help from the community on #ovirt IRC channel or file a bug:

New Features - Test Status Table

Feature Test page Tested By/ Distro BZs remarks
Features/BackupAwareness        
CinderGlance Docker Integration CinderGlance_Docker_Integration#Testing      
Features/Debian support for hosts Features/Debian support for hosts#Testing      
Features/Fedora 22 Support Features/Fedora_22_Support#Testing      
Features/oVirt Live Rebase on CentOS 7 Features/oVirt_Live_Rebase_on_CentOS_7#Testing      
Features/Self Hosted Engine FC Support Features/Self_Hosted_Engine_FC_Support#Testing      
Features/Self Hosted Engine Gluster Support      

Regression testing - Test Status Table

Scenario Tested By/ Distro BZs remarks
Upgrade from 3.5      
All-in-one setup      

General

You need at least two physical servers to install and configure a basic yet complete oVirt environment with shared storage to exercise the following:

Scenario Tested By/ Distro BZs remarks
Setup oVirt engine using either Active Directory or Local IPA, two hosts configured as hypervisors (Fedora / Ovirt-Node / other) with power management (Storage Domains - Data Domain / ISO Domain and Export Domain)      
Basic Network Configuration      
Create virtual machines and assign them to users      
Migrate Virtual Machines between the hypervisors      

Hosted Engine

You need at least two physical servers to install and configure a basic yet complete oVirt environment with shared storage to exercise the following tests. You may need to read the following documents:

Scenario Tested By/ Distro BZs remarks
Setup oVirt Hosted Engine using a NFS storage domain      
Setup oVirt Hosted Engine using a common network interface      
Setup oVirt Hosted Engine using a tagged VLAN interface      
Setup oVirt Hosted Engine using a bonded interface      
Migrate Hosted Engine VM on another host      

Tools

  • Basic operations on iso-uploader:

engine-iso-uploader list **engine-iso-uploader upload `-i` `-v` `-f`**

  • Advanced operations on iso-uploader: try different arguments, see full list with

engine-iso-uploader --help

  • Basic operations on log-collector:

engine-log-collector list engine-log-collector collect

  • Advanced operations on log-collector : try different arguments, see full list with

engine-log-collector --help

  • Basic operation on image-uploader

engine-image-uploader list **engine-image-uploader --name= `-e` `upload` `my.ovf`**

  • Advanced operations on image-uploader: try different arguments, see full list with

engine-image-uploader --help