Hi Tim,
The DNS needs to still be there because the master server uses those host
names to communicate with the nodes in the cluster. For example I
discovered that in the UI when you look at the logs or the terminal, the
master api server opens up a connection to the node in question via the DNS
OK, so I tried setting `openstack_use_bastion: True`. Servers were
provisioned OK. Public IP addresses were only applied to the infra and
dns nodes (not master).
But the inventory/hosts file that gets auto-generated by this process
still contains the "public" hostnames that can't be reached,
Hi Tim,
Yes, I only discovered what the basion setting did by looking at the heat
template, as I was going to try and remove the need for the bastion by
myself.
I found this line in the heat template:
Joel,
Thanks for that.
I had seen this but didn't really understand what it meant.
Having read through it again I still don't!
I'll give it a try tomorrow and see what happens.
As for the warning about scaling up/down then yes, that is a big
concern. That's the whole point of getting
I had exactly the same concern and I discovered that inside the heat
template there is a bastion mode, which once enabled it doesn’t use
floating ip’s any more.
Have a look at
I hope this is the right place to ask questions about the
openshift/openshift-ansible-contrib GitHub repo, and specifically the
playbooks for installing OpenShift on OpenStack:
https://github.com/openshift/openshift-ansible-contrib/tree/master/playbooks/provisioning/openstack
If not then please
