summaryrefslogtreecommitdiffstats
path: root/playbooks
diff options
context:
space:
mode:
authorOpenShift Merge Robot <openshift-merge-robot@users.noreply.github.com>2017-12-12 04:07:21 -0800
committerGitHub <noreply@github.com>2017-12-12 04:07:21 -0800
commitd00e5f4e224f281961c3f5975c27381f5e5d972d (patch)
tree82f6fbd17a4f5a10689f9e7698042322600dbbfc /playbooks
parentc86e136cd2e6f30372c77fa2fd4ce13586e88bb9 (diff)
parentcf4ec9c8205e84288bf35f93e7f2f4190d2bf9a4 (diff)
downloadopenshift-d00e5f4e224f281961c3f5975c27381f5e5d972d.tar.gz
openshift-d00e5f4e224f281961c3f5975c27381f5e5d972d.tar.bz2
openshift-d00e5f4e224f281961c3f5975c27381f5e5d972d.tar.xz
openshift-d00e5f4e224f281961c3f5975c27381f5e5d972d.zip
Merge pull request #6381 from bogdando/dns_hostname_prefixes
Automatic merge from submit-queue. Allow 2 sets of hostnames for openstack provider Support private/public hostnames suffixes for DNS records. Real hostnames, Inventory variables, Nova servers and ansible hostnames will ignore the custom suffixes. Those are only for nsupdates sent to external DNS servers. Related change: add openshift_openstack_public_dns_domain to the role defaults to not rely on the group vars example only. Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com> Co-authored-by: Tomas Sedovic <tsedovic@redhat.com>
Diffstat (limited to 'playbooks')
-rw-r--r--playbooks/openstack/advanced-configuration.md21
1 files changed, 16 insertions, 5 deletions
diff --git a/playbooks/openstack/advanced-configuration.md b/playbooks/openstack/advanced-configuration.md
index 403e0e1a7..2c9b70b5f 100644
--- a/playbooks/openstack/advanced-configuration.md
+++ b/playbooks/openstack/advanced-configuration.md
@@ -159,11 +159,22 @@ So the provisioned cluster nodes will start using those natively as
default nameservers. Technically, this allows to deploy OpenShift clusters
without dnsmasq proxies.
-The `openshift_openstack_clusterid` and `openshift_openstack_public_dns_domain` will form the cluster's DNS domain all
-your servers will be under. With the default values, this will be
-`openshift.example.com`. For workloads, the default subdomain is 'apps'.
-That sudomain can be set as well by the `openshift_openstack_app_subdomain` variable in
-the inventory.
+The `openshift_openstack_clusterid` and `openshift_openstack_public_dns_domain`
+will form the cluster's public DNS domain all your servers will be under. With
+the default values, this will be `openshift.example.com`. For workloads, the
+default subdomain is 'apps'. That sudomain can be set as well by the
+`openshift_openstack_app_subdomain` variable in the inventory.
+
+If you want to use a two sets of hostnames for public and private/prefixed DNS
+records for your externally managed public DNS server, you can specify
+`openshift_openstack_public_hostname_suffix` and/or
+`openshift_openstack_private_hostname_suffix`. The suffixes will be added
+to the nsupdate records sent to the external DNS server. Those are empty by default.
+
+**Note** the real hostnames, Nova servers' or ansible hostnames and inventory
+variables will not be updated. The deployment may be done on arbitrary named
+hosts with the hostnames managed by cloud-init. Inventory hostnames will ignore
+the suffixes.
The `openstack_<role name>_hostname` is a set of variables used for customising
public names of Nova servers provisioned with a given role. When such a variable stays commented,