path: root/roles_data_undercloud.yaml
diff options
authorAlex Schultz <aschultz@redhat.com>2017-03-29 14:43:45 -0600
committerAlex Schultz <aschultz@redhat.com>2017-04-12 06:55:29 -0600
commitbe274f1f49a15aad118a92107b7d04a57a037092 (patch)
tree3549febfae335272bfa67a78ffe0ba56cf2195ed /roles_data_undercloud.yaml
parentae6883323eaed0a925b128dc53301bfa5995f41d (diff)
Add tags to roles
Prior to Ocata, the Controller role was hardcoded for various lookups. When we switched to having the primary role name being dynamically pulled from the roles_data.yaml using the first role as the primary role as part of I36df7fa86c2ff40026d59f02248af529a4a81861, it introduced a regression for folks who had previously been using a custom roles file without the Controller being listed first. Instead of relying on the position of the role in the roles data, this change adds the concepts of tags to the role data that can be used when looking for specific functionality within the deployment process. If no roles are specified with this the tags indicating a 'primary' 'controller', it will fall back to using the first role listed in the roles data as the primary role. Change-Id: Id3377e7d7dcc88ba9a61ca9ef1fb669949714f65 Closes-Bug: #1677374
Diffstat (limited to 'roles_data_undercloud.yaml')
1 files changed, 4 insertions, 1 deletions
diff --git a/roles_data_undercloud.yaml b/roles_data_undercloud.yaml
index 8e83071..df2e196 100644
--- a/roles_data_undercloud.yaml
+++ b/roles_data_undercloud.yaml
@@ -1,6 +1,9 @@
-- name: Undercloud # the 'primary' role goes first
+- name: Undercloud
CountDefault: 1
disable_constraints: True
+ tags:
+ - primary
+ - controller
- OS::TripleO::Services::Ntp
- OS::TripleO::Services::MySQL