Current Series Release Notes

8.0.0-152

In an effort to minimise the noise, Ceilometer will no longer produce meters which have no measurable data associated with it. Image meter only captures state information which is already captured in events and other meters.

New Features

  • Because of deprecating the collector, the default publishers in pipeline.yaml and event_pipeline.yaml are now changed using database instead of notifier.
  • In the ‘publishers’ section of a meter/event pipeline definition, https:// can now be used in addition to http://. Furthermore, either Basic or client-certificate authentication can be used (obviously, client cert only makes sense in the https case). For Basic authentication, use the form http://username:password@hostname/. For client certificate authentication pass the client certificate’s path (and the key file path, if the key is not in the certificate file) using the parameters ‘clientcert’ and ‘clientkey’, e.g. https://hostname/path?clientcert=/path/to/cert&clientkey=/path/to/key. Any parameters or credentials used for http(s) publishers are removed from the URL before the actual HTTP request is made.
  • A new option named max_parallel_requests is available to control the maximum number of parallel requests that can be executed by the agents. This option also replaces the poolsize option of the HTTP publisher.
  • The tenant (project) discovery code in the polling agent now scans for tenants in all available domains.
  • Support for polling Neutron’s LBaaS v2 API was added as v1 API in Neutron is deprecated. The same metrics are available between v1 and v2.
  • Support loading multiple meter definition files and allow users to add their own meter definitions into several files according to different types of metrics under the directory of /etc/ceilometer/meters.d.
  • Add a new publisher for pushing samples or events to a Zaqar queue.

Known Issues

  • Neutron API is not designed to be polled against. When polling against Neutron is enabled, Ceilometer’s polling agents may generate a significant load against the Neutron API. It is recommended that a dedicated API be enabled for polling while Neutron’s API is improved to handle polling.

Upgrade Notes

  • Add a tool for migrating metrics data from Ceilometer’s native storage to Gnocchi. Since we have deprecated Ceilometer API and the Gnocchi will be the recommended metrics data storage backend.
  • Any existing commands utilising image meter should be switched to image.size meter which will provide equivalent functionality
  • By default, Ceilometer will poll the v2 API. To poll legacy v1 API, add neutron_lbaas_version=v1 option to configuration file.
  • Ceilometer now leverages the latest distribution mechanism provided by the tooz library. Therefore the options coordination.retry_backoff and coordination.max_retry_interval do not exist anymore.

Deprecation Notes

  • Any Archive Policy configuration in Ceilometer is deprecated. Archive Policy Rules system of Gnocchi must be used instead.
  • Collector is no longer supported in this release. The collector introduces lags in pushing data to backend. To optimize the architecture, Ceilometer push data through dispatchers using publishers in notification agent directly.
  • Allow users to add additional exchanges in ceilometer.conf instead of hardcoding exchanges. Now original http_control_exchanges is being deprecated and renamed notification_control_exchanges. Besides, the new option is integrated with other exchanges in default EXCHANGE_OPTS to make it available to extend addtional exchanges.
  • The image meter is dropped in favour of image.size meter.
  • Previously deprecated kwapi meters are not removed.
  • Usage of pipeline.yaml for polling configuration is now deprecated. The dedicated polling.yaml should be used instead.
  • The pipeline dynamic refresh code has been removed. Ceilometer relies on the cotyledon library for a few releases which provides reload functionality by sending the SIGHUP signal to the process. This achieves the same feature while making sure the reload is explicit once the file is correctly and entirely written to the disk, avoiding the failing load of half-written files.

Bug Fixes

  • The transport_url defined in [oslo_messaging_notifications] was never used, which contradicts the oslo_messaging documentation. This is now fixed.

Other Notes

  • Ship YAML files to ceilometer/pipeline/data/ make it convenient to update all the files on upgrade. Users can copy yaml files from /usr/share/ceilometer and customise their own files located in /etc/ceilometer/.

Table Of Contents

Previous topic

Ceilometer Release Notes

Next topic

Ocata Series Release Notes

Project Source

This Page