diff options
author | 2016-08-17 15:05:41 +0300 | |
---|---|---|
committer | 2016-08-24 15:03:38 +0300 | |
commit | f9dadcafcfa798f20e1ea561c0c75679747bd525 (patch) | |
tree | 6d34a19ccecb6ddc2d9af52475e7240563718c75 /network/config/bond-with-vlans/controller.yaml | |
parent | 1c8b5fa5d7d633d156e761d21ff60188eb43701f (diff) |
Enable usage of FQDNs for the endpoints
The endpoint map has the capability of using the cloud's name for the
endpoint. This is broken, however, since this has the problem that we
only take into account the overcloud's external endpoint name, which
we then cannot use if we have network-isolation enabled, which is
the most common use-case for real deployments.
So this change proposes the following:
* The external endpoint is still CloudName.
* We can now set different (or the same if we want) names for the
different VIPs of the network.
* Using CLOUDNAME for the endpoint map will get a name for the
appropriate network.
bp tls-via-certmonger
Change-Id: I3e7144653f0a1d783d87e6f638304b297f718929
Diffstat (limited to 'network/config/bond-with-vlans/controller.yaml')
0 files changed, 0 insertions, 0 deletions