Bug 1292330 - configure mariadb-galera cluster and rabbitmq cluster on separate set of node from the controller via Director
Summary: configure mariadb-galera cluster and rabbitmq cluster on separate set of node...
Keywords:
Status: CLOSED DUPLICATE of bug 1337778
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: 8.0 (Liberty)
Assignee: RHOS Maint
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-17 04:43 UTC by Pratik Pravin Bandarkar
Modified: 2019-12-16 05:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-13 16:51:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pratik Pravin Bandarkar 2015-12-17 04:43:44 UTC
1. Proposed title of this feature request  
       configure mariadb-galera cluster and rabbitmq cluster on separate set of node from the controller via Director
      

    3. What is the nature and description of the request? 
The use case is that in a large scale deployment, running mariadb-galera cluster + rabbitmq-cluster + all API, glance, cinder, other management services etc. on 3 controllers will be causing performance challenges on these controller nodes.
Also, due to large scale - if controller nodes need to be scaled up to handle higher number of API requests + glance and so on, we cannot scale up only controller services without additional database / rabbitmq [as these services are currently tied up with the controller node role / profile]

To avoid such a situation and to be able to scale controller services independently of database / rabbitmq, I want to know the method to do so via director.

Comment 4 Felipe Alfaro Solana 2016-04-27 09:48:54 UTC
We, from Telefonica, are extremely interested in this feature.

Comment 6 Mike Burns 2017-01-13 16:51:14 UTC

*** This bug has been marked as a duplicate of bug 1337778 ***


Note You need to log in before you can comment on or make changes to this bug.