summaryrefslogtreecommitdiffstats
path: root/roles/openshift_excluder
diff options
context:
space:
mode:
authorTomas Sedovic <tomas@sedovic.cz>2017-11-28 08:40:23 +0100
committerTomas Sedovic <tomas@sedovic.cz>2017-11-28 11:45:10 +0100
commit949897fd410ba74600fd44d2e81cef638b6f5a6c (patch)
tree4d6aef7372519d53d81a7b9123bdeb73eb311b94 /roles/openshift_excluder
parente429fdb4a819d2c401baac917ec4917a8c37be62 (diff)
downloadopenshift-949897fd410ba74600fd44d2e81cef638b6f5a6c.tar.gz
openshift-949897fd410ba74600fd44d2e81cef638b6f5a6c.tar.bz2
openshift-949897fd410ba74600fd44d2e81cef638b6f5a6c.tar.xz
openshift-949897fd410ba74600fd44d2e81cef638b6f5a6c.zip
Use IP addresses for OpenStack nodes
Unlike other cloud providers, OpenStack VMs are not able to resolve each other by their names. If you try to run the playbooks against nodes without a pre-created /etc/hosts or a DNS that provides the hostname/ip resolution, it will fail. By setting the `openshift_hostname` variable to each node's IP address, we're able to deploy a functional cluster without running a custom DNS. It is still possible to provide an external server with nsupdate keys and have it be populated, but that is no longer a hard requirement.
Diffstat (limited to 'roles/openshift_excluder')
0 files changed, 0 insertions, 0 deletions