oVirt 3.5 TestDay
- 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.5 features.
What I should do
- If you already have the hardware, verify if it meets the hardware requirement, refer to information detail section below.
- Write down the configuration you used (HW, console, etc) and what you’ve tested in the third test day report etherpad (previous is first test day report etherpad; [second test day report etherpad](http://etherpad.ovirt.org/p/3.5-testday-2)).
- Go ahead and install ovirt.
- 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.
- Running into any issues?
- Make sure you have one of the following distributions installed on your machine:
- Fedora 19
- Fedora 20
- CentOS 6.5
- Red Hat Enterprise Linux 6.5
- Any other distribution based on Red Hat Enterprise Linux 6.5
- Follow installation instructions provided within oVirt 3.5 Release Notes
- Fedora 19 hosts: you’ll need libvirt >= 1.0.1 to use cluster level 3.5 . This is provided in the virt-preview repo, enabled automatically by installing the ovirt-release35.rpm as explained in the oVirt 3.5 Release Notes
- DWH/Reports setup is currently broken.
- You can’t refresh iso file list after adding a host, see https://bugzilla.redhat.com/1114499 for a workaround.
- The beta RPM packages are not signed. Either use ‘yum –nogpgcheck’ or set ‘gpgcheck=0’ in the repo file.
- CentOS hosts don’t report RNG devices sources. Please uncheck ‘/dev/random’ checkbox in Cluster Options for default cluster before adding any CentOS host to it.
oVirt 3.5 New Features - Test Status Table
Please report test results on the third test day report etherpad (previous is first test day report etherpad; second test day report etherpad).or on the table below.
Following tests should be performed on all supported distributions.
|Functional team||Feature||Owner||Dev - Status||Test page||Tested By/ Distro||BZs||remarks|
|General||oVirt Live 3.5 (testing)|
|General||upgrade from 3.4 (testing)||Sandro Bonazzola F19||works|
|General||All in One setup (testing)||Sandro Bonazzola F19,F20,EL6||works|
|Network||Network Custom Properties (bridge_opts, ethtool_opts, custom)||lvernia||Done||Features/Network Custom Properties||1080984, 1080987|
|Network||NIC errors in event log||alkaplan||Done||1079719|
|Network||Arbitrary VLAN-tagged network name||alkaplan||Done||1091863||works (gshereme)|
|Network||Warning upon display network changes||yzaspits||Done||1078836|
|Network||Allow big MAC pool ranges||mmucha||Done||1063064|
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||Sandro Bonazzola F19,F20,EL6||works|
|Create virtual machines and assign them to users|
|Migrate Virtual Machines between the hypervisors|
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|
- Important Note: Known Fedora 19 bug: If the ovirtmgmt bridge is not successfully installed during initial host-setup, manually click on the host, setup networks, and add the ovirtmgmt bridge.
- Base config - single NIC, bridge on top, VMs attached to NIC
- Advanced configurations:
Make sure each of the configs can:
- Survive a reboot
- Test network at both host and VM level
- Ping and transfer large amounts of data (2Gb size files should be enough)
- Remain operational over time (1hr of uptime should be sufficient for the basic testing)
- Basic operations on iso-uploader:
- Advanced operations on iso-uploader: try different arguments, see full list with
- Basic operations on log-collector:
- Advanced operations on log-collector : try different arguments, see full list with
- Basic operation on image-uploader
- Advanced operations on image-uploader: try different arguments, see full list with
Features from previous releases
New to v3.1:
New to v3.2:
New to v3.3:
New to v3.4:
Opta planner integration
HE on iscsi
Scheduling policies rest-api
- ovirt - https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt
- Spice - https://bugs.freedesktop.org/ under Spice product
- VDSM - https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt&product=vdsm
Tracker bug for the release