736b1e1bf3
Just setting CloudDomain won't make the domains used consistent. There are a number of CloudName parameters that must be set as well. This change adds a sample environment that includes all of those parameters so it is easy to set everything consistently. Also fixes the description of CloudNameCtlplane to reflect the actual use for that parameter. Change-Id: I56d1c1c5619f83c16c4e8350aa84fccc3d748425
33 lines
1.1 KiB
YAML
33 lines
1.1 KiB
YAML
environments:
|
|
-
|
|
name: predictable-placement/custom-hostnames
|
|
title: Custom Hostnames
|
|
files:
|
|
overcloud.yaml:
|
|
parameters:
|
|
- ControllerHostnameFormat
|
|
- ComputeHostnameFormat
|
|
- BlockStorageHostnameFormat
|
|
- ObjectStorageHostnameFormat
|
|
- CephStorageHostnameFormat
|
|
description: |
|
|
Hostname format for each role
|
|
Note %index% is translated into the index of the node, e.g 0/1/2 etc
|
|
and %stackname% is replaced with OS::stack_name in the template below.
|
|
If you want to use the heat generated names, pass '' (empty string).
|
|
-
|
|
name: predictable-placement/custom-domain
|
|
title: Custom Domain Name
|
|
files:
|
|
overcloud.yaml:
|
|
parameters:
|
|
- CloudDomain
|
|
- CloudName
|
|
- CloudNameInternal
|
|
- CloudNameStorage
|
|
- CloudNameStorageManagement
|
|
- CloudNameCtlplane
|
|
description: |
|
|
This environment contains the parameters that need to be set in order to
|
|
use a custom domain name and have all of the various FQDNs reflect it.
|