ZenPack:Xen Virtual Hosts

From Zenoss Wiki
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search

Note: This is a Core ZenPack which can be found in the Core Zenoss RPM, and is fully documented in the Zenoss Extended Monitoring Guide. If you did not install this pack when you installed Zenoss Core, it can be found in $ZENHOME/packs.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.XenMonitor
Link to more docs
View Documentation


Applications Monitored: 



Xen Virtual Hosts ZenPack

The XenMonitor ZenPack allows you to monitor Xen para-virtualized domains with Zenoss.
Note: This ZenPack is deprecated has been superseded by http://wiki.zenoss.org/ZenPack:XenServer

Warning

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.

Support

This ZenPack is part of Zenoss Core. Open Source users receive community support for this ZenPack via our online forums. Enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Background

The ZenPacks.zenoss.XenMonitor ZenPack monitors Xen para-virtualized domains.


With this ZenPack, the zenmodeler can discover guests running on Xen hosts, and Zenoss platform includes screens and templates for collecting and displaying resources allocated to guests.


Prerequisites

Prerequisite Restriction
Product Zenoss platform 4.x
Required ZenPacks ZenPacks.zenoss.XenMonitor ZenPacks.zenoss.ZenossVirtualHostMonitor


Model Hosts and Guest

For each Xen server, follow this procedure:


  1. Optionally, place an SSH key to your Xen server to allow the zenoss user from the Zenoss platform server to log in as root without requiring further credentials.
  2. Create the Xen server in the /Servers/Virtual Hosts/Xen device class. Warning: If you have this server modeled already, remove the server and recreate it under the Xen device class. Do not move it.
  3. Select the Guest menu and ensure that the guest hosts were found during the modeling process.


Daemons

Type Name
Modeler zenmodeler
Performance Collector zencommand


Monitoring with sudo

To configure sudo in order to run the xm on the Virtual Machine Host, you will need to modify a few things.

  • Modify the zCommandPath zProperty to be blank, otherwise this path will be pre-pended to the sudo command.
  • Modify the zCommandUsername and zCommandPassword configuration properties to be a non-root user with sudo access to the xm command.
  • Modify the Xen.py modeler to add the sudo command. The modeler can be found under the $ZENHOME/ZenPacks/ZenPacks.zenoss.ZenossVirtualHostMonitor directory, under the modeler/plugins directory.
  • Modify the performance templates.
    1. Navigate to the /Devices/Server/Virtual Machine Host/Xen device class
    2. From the device class click on the Templates tab
    3. Click on the VirtualMachine performance template
    4. In the Data Sources table, click on the resources Data Source
    5. Edit the command template to add the sudo command to the beginning of the xm command

Installation

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.XenMonitor-*.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/path/to/repo
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.XenMonitor
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

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

blog comments powered by Disqus