Composable roles require all services in Services list

[Steven Hardy]

Currently there's a couple of related issues related to our default definition for e.g ControllerServices and other roles.

1. We "enable" a bunch of services which are really disabled via OS::Heat::None - this will be confusing e.g if a Ux shows the list of "enabled" services.

2. When adding a new service to e.g the Controller role, you need to copy (and rebase forever) the entire ControllerServices list (same problem for all roles).

It'd be nice to use the new heat parameter_merge_strategy option to solve this, as I did in https://review.openstack.org/#/c/384618/1/test-environments/multinode.yaml but this doesn't work because we define the default ControllerServices list in overcloud.yaml (not an environment file).

If we moved the definition of the default *Services list into an environment file, these issues could be resolved via the parameter_merge_strategy method.

[Steven Hardy (shardy)]

Deferring to pike as fixing this will require tripleoclient changes, and the ocata tripleoclient is due for imminent release. We can perhaps backport this fix after it lands in (hopefully) early pike.

[Ben Nemec (bnemec)]

Per Steve's previous comment I'm deferring this to Queens. I believe the client releases for Pike have already happened, so we're in the same situation we were back at the end of Ocata.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE