Deprecation: Handle RabbitMQ management_metrics_collection

Summary

The management_metrics_collection feature used by RabbitMQ is now deprecated and triggers warnings in OpenStack components such as Cinder, Nova, Neutron, Designate, Barbican, Ceilometer and Octavia. This affects environments where RabbitMQ management metrics are enabled. The deprecation warning suggests disabling the feature, or can we avoid using the rabbitmq_management plugin?

Use cases

• As an operator, I want to suppress or resolve deprecation warnings related to RabbitMQ management_metrics_collection so that system logs remain clean and compatible with future RabbitMQ versions.

• As a developer, I want to ensure Yaook Operator configurations align with the latest RabbitMQ feature set and avoid reliance on deprecated management features.

Proposal

To be discussed.

Potential approaches include:

Updating RabbitMQ configuration in the Yaook Operator to disable deprecated metrics collection by default:

deprecated_features.permit.management_metrics_collection = true

Or can we avoid using the rabbitmq_management plugin?

Useful references:

• https://www.rabbitmq.com/docs/deprecated-features#configuring-deprecated-features-behavior
• https://www.rabbitmq.com/docs/management#disable-stats

Specification

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this issue are to be interpreted in the spirit of RFC 2119, even though we're not technically doing protocol design.