This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
View analytic
Wednesday, May 14 • 3:30pm - 4:10pm
Ceilometer SNMP improvements & code-free meters

Sign up or log in to save this to your schedule and see who's attending!

This session will include the following subject(s):

improve snmp inspector and h/w pollster :

Just like Eoghan Glynn pointed out, there are some improvements we can do about the snmp inspector and potentially the h/w pollster we added in the Icehouse release:

1. It would be nice to have a generic mapping mechanism between the snmp OID and final sample in snmp inspector. The goal would be that new OID-sample mappings could be added to the mix *without* writing any new code(or writing as little code as possible)

2. How to manage the snmp credential

3. Misc
- Support bulkCmd mode in snmp
- Is the inspector data definition too snmp-ish?

(Session proposed by Lianhao Lu)

Avoid writing code while introducing new meters:

Each time a new meter is introduced in Ceilometer, we need to perform a lot of tasks like:
1) Adding a mapping in setup.cfg for the new meter to a Pollster
2) Writing a pollster for the counter
3) Implementing the corresponding method in inspectors to collect data for the meter.

Hypervisors like Vsphere come with a single generic API for querying statistics for any meter. Moreover, it supports over 300 such meters. From the development perspective, it will be very difficult, time-consuming and unnecessary to implement a pollster for each and every such meter.

From a customer perspective too, the following difficulties exist:
1) Though Vsphere supports 300+ meters, all the data is not available via Ceilometer.
2) There is no way for the customers to be able to select the meters for which data should be collected by Ceilometer.
3) Even if the developers put in the efforts to collect data for each and every Vsphere meter, if the customer is interested only in some specific meters, it will be an unnecessary load on Ceilometer to collect data for so many meters.

Hence, we propose to implement a generic solution where:

A configuration file can be provided in Ceilometer, which will have a mapping of Ceilometer's meter to the corresponding Vsphere's (or any such other hypervisor's) counter. Customers can directly add/remove these mappings, so that they can have control over which meters to populate in Ceilometer. The configuration file can have additional parameters like, conversion factor for the meters and/or method in the corresponding inspector to be used to populate the meter, if the methods are not generic enough.

We can publish sample configuration files for all the meters, and for each hypervisor.

(Session proposed by Piyush Masrani)

Wednesday May 14, 2014 3:30pm - 4:10pm

Attendees (38)