diff options
author | Jenkins <jenkins@review.openstack.org> | 2017-04-13 17:29:59 +0000 |
---|---|---|
committer | Gerrit Code Review <review@openstack.org> | 2017-04-13 17:29:59 +0000 |
commit | 05440b00079628d31aaa8c08a797fe33af4d2889 (patch) | |
tree | 7e7af00a23844902c06eb61e8c76febf3912f96c /releasenotes/notes | |
parent | 837deb91b2173720dc15d5ec33d78b2192f7511d (diff) | |
parent | be274f1f49a15aad118a92107b7d04a57a037092 (diff) |
Merge "Add tags to roles"
Diffstat (limited to 'releasenotes/notes')
-rw-r--r-- | releasenotes/notes/role-tags-16ac2e9e8fcab218.yaml | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/releasenotes/notes/role-tags-16ac2e9e8fcab218.yaml b/releasenotes/notes/role-tags-16ac2e9e8fcab218.yaml new file mode 100644 index 00000000..dadbfa4b --- /dev/null +++ b/releasenotes/notes/role-tags-16ac2e9e8fcab218.yaml @@ -0,0 +1,18 @@ +--- +features: + - | + Adds tags to roles that allow an operator to specify custom tags to use + when trying to find functionality available from a role. Currently a role + with both the 'primary' and 'controller' tag is consider to be the primary + role. Historically the role named 'Controller' was the 'primary' role and + this primary designation is used to determine items like memcache ip + addresses. If no roles have the both the 'primary' and 'controller' tags, + the first role specified in the roles_data.yaml is used as the primary + role. +upgrade: + - | + If using custom roles data, the logic was changed to leverage the first + role listed in the roles_data.yaml file to be the primary role. This can + be worked around by adding the 'primary' and 'controller' tags to the + custom controller role in your roles_data.yaml to ensure that the defined + custom controller role is still considered the primary role. |