[openstack-dev] [kolla] Services consuming RabbitMQ
dabarren at gmail.com
Fri Dec 16 13:52:41 UTC 2016
At this moment we have a couple of services that need to consume
connections from a message queue on the client side.
This raised change requests to fix the issue with different approaches.
Those change requests have several implications on Kolla's overall
architecture and security, being said, will need a discussion for message
queue consumers from client side in order to apply the best solution,
avoiding as far we can all risk in the infrastructure.
As far as I know, murano-agent and trove-agent need to connect to RabbitMQ
in order to consume configurations and status tracking from the deployed
services. The agent is installed in the instances.  
Using Murano as example, when a new application is deployed, murano-agent
configuration is injected in the instances through cloud-init with RabbitMQ
connection information (user, URL and password). Once the instance start,
murano-agent communicates with murano-engine through RabbitMQ in order to
get application configurations.
As we have in Kolla at the moment, Murano won't work unless using older
Murano applications on which the application has been previously installed
and configured in the base image.
>From this design I have three different options to fix the issue.
Allow services to use actual RabbitMQ cluster in a different vhost: 
Easy to fix now, there are PS under review at the moment for
Provides some kind of isolation per service as well as more secure
with different user/password.
Expose OpenStack infrastructure RabbitMQ to to end-users.
Risk of DDoS attacks to the whole OpenStack infrastructure,
end-user instances will have access to a shared RabbitMQ
New RabbitMQ instances (per service or shared with other services): 
More secure option, avoid DDoS against the infrastructure and
network access to OpenStack RabbitMQ.
Overload underlay infrastructure with more RabbitMQ instances.
Inability to use standard ports because more than one RabbitMQ can
share the same node.
Complex option to deploy, debug and maintain.
Expose current RabbitMQ to end-user services.
Simple, easy and less resource consuming.
Hell no, this is not an option.
Share OpenStack's RabbitMQ cluster admin password and expose
network access to end-users.
There is a thread which explains the issue and solutions recommended by
other teams. 
Please, share your opinion on this matter.
Regards, Eduardo Gonzalez
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev