Bug 1292329

Summary: configure mariadb-galera cluster and rabbitmq cluster on separate set of node from the controller via Director
Product: Red Hat OpenStack Reporter: Pratik Pravin Bandarkar <pbandark>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED DUPLICATE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.0 (Kilo)CC: jschluet, markmc, mburns, srevivo
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: 8.0 (Liberty)   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-13 16:50:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Pratik Pravin Bandarkar 2015-12-17 04:42:42 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 2 Mike Burns 2017-01-13 16:50:45 UTC 

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