Description of problem:
There are some usability issues with the custom roles interfaces, because we don't currently template default mappings for various per-role things in the base overcloud-resource-registry-puppet.yaml file.
It's possible to work around these things by copying files from existing roles and making a bespoke additional environment (or hacking on overcloud-resource-registry-puppet.yaml by copying the relevant lines), but this isn't convenient from a user interface perspective.
Instead we should template as much of this as possible by default, such that just adding a role name and list of services to roles_data.yaml is enough to create a custom role.
Version-Release number of selected component (if applicable):
carlos, please have a look at this one
Carlos and I have pushed a number of patches tracked via https://bugs.launchpad.net/tripleo/+bug/1626976 which resolve this, we should pick these up by rebasing on the TripleO newton GA.
i believe https://review.openstack.org/#/q/I23b84d4ee8c4d0bff4b4e38dc4731924a6272ac5,n,z is the last needed patch to merge
Indeed, now all patches were merged in master (backported to stable/newton)
all patches merged to newton
Currently for deploying custom roles the input in environment files is related to the nic templates/networks which are particular to each deployment, e.g for a role running the Neutron agents:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.