diff options
| author | Tomas Sedovic <tomas@sedovic.cz> | 2017-11-28 08:40:23 +0100 |
|---|---|---|
| committer | Tomas Sedovic <tomas@sedovic.cz> | 2017-11-28 11:45:10 +0100 |
| commit | 949897fd410ba74600fd44d2e81cef638b6f5a6c (patch) | |
| tree | 4d6aef7372519d53d81a7b9123bdeb73eb311b94 /utils/etc/ansible-quiet.cfg | |
| parent | e429fdb4a819d2c401baac917ec4917a8c37be62 (diff) | |
| download | openshift-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 'utils/etc/ansible-quiet.cfg')
0 files changed, 0 insertions, 0 deletions