Accelerate Your Path to Full-Stack Monitoring and Alerting
Register for this live webinar featuring Zenoss and VictorOps today!
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
Ceph is a distributed object store and file system.
This ZenPack monitors the Ceph storage clustering system.
We support two APIs for connecting to Ceph: Calamari and SSH.
Ceph features include:
Objects are automatically discovered via Calamari API. The ZenPack class structure can be visualized in the following Diagram:
Ceph ZP Class Structure
Recall that we have two types of API connectivity to Ceph: Calamari and SSH.
The Calamari API is outlined here.
Calamari/Graphite setup is covered here. You must have access to both the Calamari and Graphite APIs which are bundled into the Calamari packages. Calamari has other dependencies that must be installed on the Ceph cluster.
Installation consists of the following steps:
You can also add your devices in batch for convenience and automation.
Attach to the Zope container:
serviced service attach zope
Create a text file (filename: /tmp/ceph.txt) as follows:
ceph zCephCalamariUrl='http://calamari.fqdn/api/v2', \
Now run the zenbatchload command:
The Ceph device should be modeled automatically
For SSH access you must enable an SSH account on each Ceph cluster server. Make sure all your Ceph cluster servers have the Zenoss ssh key install as per the SSH section of Prepare Remote Device Document. We recommend setting up a dedicated user with restricted access.
Ssh authentication can take two forms:
SSH setup on your Ceph servers is beyond the scope of this document. Please reference this document for more information.
We do recommend that you setup sudo your Ceph servers so that the following commands can be used by your ssh user:
Installation is easiest and simplest with zenbatchload as follows:
serviced service attach zope
ceph.ssh zCommandUsername='username', \
Note: if you are using SSH key-pair authentication, you may not need zCommandUsername and zCommandPassword as above.
Ensure to include ALL your ceph servers in the zCephHosts list.
Run the zenbatchload command:
If you have set zCephDiscoverHosts to true, then the first time you visit the Hosts components, each host listed there will be created as a device of type zCephHostDeviceClass.
These hosts will not be modeled until you provide the appropriate zProperties in each host so that the modeler can have proper access.
If your hosts already exist, they should have the same hostname that Ceph believes them to be, either from Ceph's DNS servers for from /etc/hosts files. To avoid having multiple versions of the hosts, you should first remove the hosts from Zenoss prior to installing your first Ceph cluster.
We recommend against manually configuring Linux host devices!
Linux Host device names should use the same FQDN hostname that Ceph ZenPack is expecting whenever possible. Choosing different device names will complicate this process. Therefore it is highly recommended that you do not manually pre-configure those Linux devices, but rather allow the Ceph ZenPack to automatically discover and configure those devices at model time.
If this is not possible, you may have to re-name and re-configure those hosts and place them into the desired device classes manually.
Installing this ZenPack will add the following items to your Zenoss system:
The zProperties and example format settings for the Ceph are as follows:
Under the Calamari/Graphite API:
Under the SSH API:
For all API:
This ZenPack provides additional support for Zenoss Analytics. Perform the following steps to install extra reporting resources into Zenoss Analytics after installing the ZenPack.
Choose Repository from the View menu at the top of the page.Expand Public in the list of folders.Right-click on Ceph_ZenPack folder and choose Delete.Confirm deletion by clicking OK.
Choose Server Settings from the ''Manage' menu at the top of the page.Choose Import in the left page.Remove checks from all check boxes.Click Choose File to import a data file.Choose the analytics-bundle.zip file copied from your Zenoss server.Click Import.
You can now navigate back to the Ceph_ZenPack folder in the repository to see the following resources added by the bundle.
Domains can be used to create ad hoc views using the following steps.
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact and root cause analysis capabilities for Ceph. The service impact relationships shown in the diagram (right) and described below are automatically added and maintained. These will be included in any services that contain one or more of the explicitly mentioned components.
The following Ceph objects types would typically be added to Impact services.
Impact Relationship Diagram
Impact Relationships between Ceph Components
The Ceph ZenPack has support for OpenStack integration of RBD images to OpenStack volumes and snapshots.
OpenStack Integration requires:
Once integration is achieved, you should expect to see corresponding volume links in the respective component details relating Ceph RBDs to OpenStack volumes and snapshots.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.