aboutsummaryrefslogtreecommitdiffstats
path: root/net-config-bond.yaml
diff options
context:
space:
mode:
authorBen Nemec <bnemec@redhat.com>2016-07-27 15:44:58 -0500
committerBen Nemec <bnemec@redhat.com>2016-08-12 10:26:16 -0500
commit8cd7861a26bcf82dfb8d3c744d03007c0b66644f (patch)
treecb186c6c306dfade1a23792cc818bc623e28f866 /net-config-bond.yaml
parent0eb70014a339eddc6be9257a70d6ad0547e31c9a (diff)
Decouple EndpointMap from SSL certificate params
Having the endpoint map in the same environment as the SSL certificate parameters means that every time a service is added to the overcloud, the user must remember to update their copy of enable-tls.yaml to reflect the new service. To avoid this, let's separate the SSL EndpointMap from the SSL certificates so users can simply pass the shipped list of SSL endpoints and only have to customize the certificate env file. As and added bonus, this means they won't have to put the certificates in enable-tls.yaml specifically. The parameters can be set anywhere, and will be used as long as one of the tls-endpoints envs is also specified. inject-trust-anchor.yaml is not changed, but it could already be used in the same fashion. The root certificate param could be set in any env passed after inject-trust-anchor.yaml, and then inject-trust-anchor.yaml would only be responsible for setting the appropriate resource_registry entry. This way there is no need to customize the in-tree inject-trust-anchor.yaml either. Change-Id: I38eabb903b8382e6577ccc97e21fbb9d09c382b3
Diffstat (limited to 'net-config-bond.yaml')
0 files changed, 0 insertions, 0 deletions