Red Hat Bugzilla – Bug 1383199
[DOC] Overcloud domain names can be set per network
Last modified: 2017-05-31 06:33:59 EDT
Description of problem: Overcloud nodes VIP entries in /etc/hosts ignore the domain name set by CloudDomain parameter: Version-Release number of selected component (if applicable): openstack-tripleo-heat-templates-5.0.0-0.20160929150845.4cdc4fc.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1. Deploy overcloud with CloudDomain: redhat.local paremeter 2. Check /etc/hosts entries on overcloud nodes Actual results: # HEAT_HOSTS_END 10.0.1.5 overcloud.storagemgmt.localdomain # FQDN of the storage mgmt VIP 192.168.0.5 overcloud.ctlplane.localdomain # FQDN of the ctlplane VIP 10.0.0.5 overcloud.internalapi.localdomain # FQDN of the internal api VIP 10.0.0.129 overcloud.storage.localdomain # FQDN of the storage VIP 172.16.18.25 overcloud.localdomain # FQDN of the external VIP Expected results: # HEAT_HOSTS_END 10.0.1.5 overcloud.storagemgmt.redhat.local # FQDN of the storage mgmt VIP 192.168.0.5 overcloud.ctlplane.redhat.local # FQDN of the ctlplane VIP 10.0.0.5 overcloud.internalapi.redhat.local # FQDN of the internal api VIP 10.0.0.129 overcloud.storage.redhat.local # FQDN of the storage VIP 172.16.18.25 overcloud.redhat.local # FQDN of the external VIP Additional info: Also I believe they should be inside the HEAT_HOSTS_START - HEAT_HOSTS_END section.
This should be addressed by https://review.openstack.org/#/c/382886/
Testing this bug produce the same problem as describe in bug description: # HEAT_HOSTS_END 172.16.1.22 overcloud.storagemgmt.localdomain # FQDN of the storage mgmt VIP 172.16.1.22 overcloud.ctlplane.localdomain # FQDN of the ctlplane VIP 172.16.1.22 overcloud.internalapi.localdomain # FQDN of the internal api VIP 172.16.1.22 overcloud.storage.localdomain # FQDN of the storage VIP 172.16.1.22 overcloud.localdomain # FQDN of the external VIP
Bob, could you please take a look?
The VIPs actually don't use CloudDomain, they have specific parameters defined in overcloud.j2.yaml CloudName: default: overcloud.localdomain description: The DNS name of this cloud. E.g. ci-overcloud.tripleo.org type: string CloudNameInternal: default: overcloud.internalapi.localdomain description: > The DNS name of this cloud's internal API endpoint. E.g. 'ci-overcloud.internalapi.tripleo.org'. type: string CloudNameStorage: default: overcloud.storage.localdomain description: > The DNS name of this cloud's storage endpoint. E.g. 'ci-overcloud.storage.tripleo.org'. type: string CloudNameStorageManagement: default: overcloud.storagemgmt.localdomain description: > The DNS name of this cloud's storage management endpoint. E.g. 'ci-overcloud.storagemgmt.tripleo.org'. type: string CloudNameCtlplane: default: overcloud.ctlplane.localdomain description: > The DNS name of this cloud's storage management endpoint. E.g. 'ci-overcloud.management.tripleo.org'. As can be seen, these are the values in /etc/hosts 10.0.1.5 overcloud.storagemgmt.localdomain # FQDN of the storage mgmt VIP 192.168.0.5 overcloud.ctlplane.localdomain # FQDN of the ctlplane VIP 10.0.0.5 overcloud.internalapi.localdomain # FQDN of the internal api VIP 10.0.0.129 overcloud.storage.localdomain # FQDN of the storage VIP 172.16.18.25 overcloud.localdomain # FQDN of the external VIP So in order the change the VIP entries in /etc/hosts, these parameters need to be overwritten in a template file. Changing CloudDomain will have no affect on the VIP entries. I recommend closing this and creating an RFE if the desired behavior is to use CloudDomain to replace the value of "localdomain" in all the VIP entries, I believe that may be a significant change.
Ok, converting on an RFE. Thanks for looking into it Bob!
I order to he set the VIP's FQDN you need to add the following to your environment file (example): CloudName: "overcloud.redhat.local" CloudNameInternal: "overcloud.internalapi.redhat.local" CloudNameStorage: "overcloud.storage.redhat.local" CloudNameStorageManagement: "overcloud.storagemgmt.redhat.local" This will configure /etc/hosts on the overcloud nodes like: # HEAT_HOSTS_END 172.16.1.22 overcloud.storagemgmt.redhat.local # FQDN of the storage mgmt VIP 172.16.1.22 overcloud.ctlpane.redhat.local # FQDN of the ctlplane VIP 172.16.1.22 overcloud.internalapi.redhat.local # FQDN of the internal api VIP 172.16.1.22 overcloud.storage.redhat.local # FQDN of the storage VIP 172.16.1.22 overcloud.redhat.local # FQDN of the external VIP In stack update scenario the hosts entries will be added in addition to the existing ones.
A quick update on this one: Juan proposed it this way initially but this approach was rejected - https://review.openstack.org/#/c/357765/1..32/overcloud.yaml Different domain names could be used for the public and the internal networks respectively so it makes sense to be able to pass different domain names per network. I think we can go with a docs bug and document these parameters.
These are now documented as a part of the Core Overcloud Parameters: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/html/overcloud_parameters/core_overcloud_parameters Marius, does this suit what was required with this BZ?
(In reply to Dan Macpherson from comment #13) > These are now documented as a part of the Core Overcloud Parameters: > > https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/11/ > html/overcloud_parameters/core_overcloud_parameters > > Marius, does this suit what was required with this BZ? It looks good. Thank you, Dan!
Thanks, marius!