Fix 3node deployment
The keystone role needs to be on the same node as the mysql/haproxy node due to a TLS requirement that the haproxy be on the 'primary' tagged node. Since the keystone bootstrap stuff only runs on the primary node as well, they need to be tied together. Change-Id: Ifa7ed93993082466a2a6ddff56bee58b074be512 Closes-Bug: #1768142
This commit is contained in:
parent
5b1a2301bf
commit
0ef3058459
@ -26,7 +26,6 @@
|
||||
- OS::TripleO::Services::CinderScheduler
|
||||
- OS::TripleO::Services::Docker
|
||||
- OS::TripleO::Services::Kernel
|
||||
- OS::TripleO::Services::Keystone
|
||||
- OS::TripleO::Services::GlanceApi
|
||||
- OS::TripleO::Services::NeutronDhcpAgent
|
||||
- OS::TripleO::Services::NeutronL3Agent
|
||||
@ -74,6 +73,7 @@
|
||||
- OS::TripleO::Services::OsloMessagingNotify
|
||||
- OS::TripleO::Services::HAproxy
|
||||
- OS::TripleO::Services::Keepalived
|
||||
- OS::TripleO::Services::Keystone
|
||||
- OS::TripleO::Services::Memcached
|
||||
- OS::TripleO::Services::Pacemaker
|
||||
- OS::TripleO::Services::Ntp
|
||||
|
Loading…
x
Reference in New Issue
Block a user