Current Series Release Notes

Current Series Release Notes

9.0.0.0rc1-47

New Features

  • A Prometheus scope fetcher has been added in order to dynamically discover scopes from a Prometheus service using a user defined metric and a scope attribute. It can also filter out the response from Prometheus using metadata filters to have a more fine-grained control over scope discovery. It features HTTP basic auth capabilities and HTTPS configuration options similar to Prometheus collector.

  • Added a v2 API endpoint allowing to retrieve the state of several scopes. This endpoint is available via a GET request on /v2/scope and supports filters. Admin privileges are required to use this endpoint.

  • Added a v2 API endpoint allowing to reset the state of several scopes. This endpoint is available via a PUT request on /v2/scope and supports filters. Admin privileges are required to use this endpoint.

  • A v2 API has been bootstrapped. It is compatible with the v2 storage and will be the base for all upcoming API endpoints. It is marked as EXPERIMENTAL for now.

  • It is now possible to force a project_id to retrieve a specific metric from it with the monasca collector.

  • The processor is now able to run several parallel workers. By default, one worker is spawned for each available CPU. Workers can be limited through the max_workers option of the orchestrator section.

Upgrade Notes

  • The v1 API is now marked as CURRENT. The API root is now built with Flask instead of pecan

  • Metrics are now fetched concurrently with eventlet instead of one after another by the orchestrator, leading to a consequent performance improvement. The maximum number of greenthreads to use can be specified through the max_greenthreads option of the orchestrator section.

Security Issues

  • The default policy for the /v1/storage/dataframes endpoint has been changed from unprotected (accessible by any unauthenticated used) to admin_or_owner (accessible only by admins or members of the project).

  • Introduce bandit security checks and fix potential security issues detected by bandit linter. Remove unused option where host_ip was a binding to all interfaces. Using of insecure hash function, switch from sha1 to sha512.

Bug Fixes

  • HashMap module field mapping matching has been fixed: Field mapping values are always stored as strings. However, metadatas to match can be floats or integers (eg vcpus or ram). Given that mappings were matched with == until now, integers or float metadatas did never match.

  • CompileError: Can't resolve label reference for ORDER BY / GROUP BY. errors that were sometimes raised by SQLAlchemy when using the v1 storage backend and grouping on tenant_id and res_type have been fixed.

Creative Commons Attribution 3.0 License

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.