From Zenoss Wiki
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search
Zenoss, Inc.
GNU General Public License, Version 2, or later
ZenPack name
Git sources (for cloning)

Applications Monitored: 

OVirt ZenPack

Monitoring for oVirt and Red Hat Enterprise Virtualization (RHEV)


The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.


This is an Open Source ZenPack developed by Zenoss, Inc. Enterprise support for this ZenPack is available to commercial customers with an active subscription.


Version 1.2.1- Download
Released on 2016/01/20
Requires PythonCollector ZenPack
Compatible with Zenoss Core 4.2.x, Zenoss Resource Manager 4.1.x, Zenoss Resource Manager 4.2.x


This ZenPack provides the ability to monitor oVirt and by extension, Red Hat Enterprise Virtualization (RHEV). An explanation of what oVirt is can be found on the oVirt and Red Hat Enterprise Virtualization sites.

The oVirt Project is an open virtualization project for anyone who cares about Linux-based KVM virtualization. Providing a feature-rich server virtualization management system with advanced capabilities for hosts and guests, including high availability, live migration, storage management, system scheduler, and more. This ZenPack models, collects events, and collects performance information from an oVirt server for data centers, clusters, hosts and virtual machines.



Once you've successfully added a ovirt system to Zenoss you will begin to see the following metrics available.

  • Host CPU, memory, network utilization
  • VM CPU, memory, network, disk utilization and throughput
  • Counts of hosts, VMs residing in the various containers


oVirt/Rhev has a single event stream containing both events and alerts. The API does not appear to map an opening event to a closing event. For this reason automatic closing of events is not yet supported. Additionally it appears that oVirt may drop events off of its queue very quickly. We are reading events every minute to reduce the chance of a missed event since there is no real time event mechanism in oVirt.


This version of the ZenPack only supports HTTP access to the oVirt server. This version of the ZenPack does not automatically clear events. The oVirt API seems appears to be limited in regards to events. This version of the ZenPack does not automatically detect device models in real time and this can be worked around by manually scheduling zenmodeler to run via cron on a regular basis.

The oVirt controller node is really a Linux device. It might be desirable to set the appropriate modeler plugins and templates to add additional Linux metrics to this organizer. Alternatively, you could use a CNAME for this device and model the real device under a different hostname and organizer.


Installing the ZenPack will add the following items to your Zenoss system.

Device Classes
  • /oVirt
Configuration Properties
  • zOVirtPassword
  • zOVirtUrl
  • zOVirtDomain
  • zOVirtUser
Modeler Plugins
  • zenoss.oVirt
Monitoring Templates
  • oVirtCluster
  • oVirtDataCenter
  • oVirtHost
  • oVirtHostNic
  • oVirtStorageDomain
  • oVirtSystem
  • oVirtVm
  • oVirtVmDisk
  • oVirtVmNic
Event Classes
  • /oVirt

The above Configuration Properties will be automatically set when adding a new oVirt instance.

Bulbgraph.png Note: If the zOVirtUrl changes it would be recommended to rename the ovirt device as well.


Add an oVirt Server

  1. Navigate to the Infrastructure page
  2. Click on the Add Device menu item and select Add oVirt Infrastructure... option.
  3. Fill in the appropriate fields in the dialog box:
    1. URL: URL of the oVirt instance. (i.e. http://ovirt.example.com:8080)
    2. Authentication Domain: Domain in which the user credentials are valid.
    3. Username: User name.
    4. Password: Password for the user.
    5. Collector: Zenoss collector to which the device will be assigned.
  4. Click on the Add button.
    1. Wait for the device to be modeled.
    2. Navigate to the new device.

Add an oVirt Server (zenbatchload)

1. Add an entry like the following to your zenbatchload input file.

/Devices/oVirt loader='oVirt', loader_arg_keys=['url', 'username', 'domain', 'password']
ovirt.zenosslabs.com url='http://ovirt.zenosslabs.com', username='admin', domain='internal', password='zenoss'

2. Run zenbatchload.

zenbatchload inputfile

Add an oVirt Server (zendmd)

  1. Run the following snippet in zendmd.
ovirt_facade = getFacade('oVirt')
ovirt_facade.add_ovirt('http://ovirt.example.com','username', 'domain', 'password')

Change Log

1.2.1 - 2016-01-20
  • Licensing fixes. No functional changes.
1.2.0 - 2013-04-11
  • Support for oVirt 3.2.
  • Introduced dependency on PythonCollector ZenPack.
  • Moved from COMMAND datasources to Python datasources for better performance.
1.1.0 - 2012-08-28
  • Support for RHEV 3.
  • Discovery of oVirt or RHEV product and version information.
  • RHEV and oVirt Icons for all component types.
  • Fix for "No data returned for command" events.
1.0.3 - 2012-08-06
  • First fully-featured release.
  • No longer dependent on Liberator ZenPack.
1.0.1 - 2012-03-21
  • Initial demonstration release.


Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.oVirt-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone git://github.com/zenoss/ZenPacks.zenoss.oVirt.git
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.oVirt
  4. Finally, restart these serivices:
    $ zenoss restart


Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus