© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
In OpenStack we do not expose messaging queues directly to users to allow them to send messages, and we expect a service is in front of messaging queues sending messages. So the limit may need to be implemented in the service layer, not at the library layer. Services should have appropriate user input (and rejection response such as 401).
If we aim to add limit to protect messaging queue from bad design or bug in services, but even in such case we can first try to use an existing mechanism in messaging queue. For example RabbitMQ has max_message_size option. Setting limit at message queue is more robust way instead of implementing it at library layer.
What we can try for a short term is to check the current behavior against the limit within MQ so that we handle the error properly (though this may not be very needed).
As long term we may want to check how user input is injected into message queues by every service but this may be beyond scope of the oslo project, because it requires investigation in individual components.