On 10/02/17 12:24 AM, Nirendra Awasthi wrote: > Overview: > * HyperScale pollsters are required to collect and monitor HyperScale > storage statistics. > * Collected statistics can be visualized in HyperScale dashboard. > * Pollsters are deployed on all the managed computes, HyperScale data > plane and HyperScale control plane. > * Pollsters are driven by a separate HyperScale service > > Pollsters: > HyperScale pollsters are divided into following categories: > - Compute plane pollsters > - Data plane pollsters > - Tenant pollsters > - Cloud pollsters i assume this is a vendor specific solution. we don't/prefer not to store drivers in Ceilometer. you can take a look at how powervm does this[1]. they basically extend the existing interfaces we provide[2]. i suspect you want to do something similar. if there's an interface missing, feel free to propose it. for everything else, we detect pollsters to load via entry_points[3][4]. i imagine you want to leverage that and add your own pollster in same namespace for Ceilometer to pickup. lastly, the polling control is handled by polling.yaml and not the pipeline.yaml[5] you're welcome to post your solution to ceilometer repo. just know, all the driver specific code will be probably pushed outside the repo. [1] https://github.com/openstack/ceilometer-powervm [2] https://github.com/openstack/ceilometer/blob/master/ceilometer/compute/virt/inspector.py [3] https://github.com/openstack/ceilometer/blob/master/setup.cfg#L80 [4] https://github.com/openstack/ceilometer/blob/master/setup.cfg#L143 [5] https://github.com/openstack/ceilometer/blob/master/etc/ceilometer/polling.yaml cheers, -- gord