Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Use IP addresses for OpenStack nodes | Tomas Sedovic | 2017-11-28 | 1 | -2/+1 |
| | | | | | | | | | | | | | 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. | ||||
* | Namespace the OpenStack vars | Tomas Sedovic | 2017-11-07 | 1 | -5/+5 |
| | | | | | This makes sure that all the variables used in the `openshift_openstack` role are prefixed with `openshift_openstack_` as is the convention. | ||||
* | Add the DNS updates and rename the openstack vars | Tomas Sedovic | 2017-11-07 | 1 | -2/+2 |
| | | | | | Most of the vars in `roles/openshift_openstack/defaults/main.yml` are now prefixed with `openstack_`. | ||||
* | Move the OpenStack playbooks | Tomas Sedovic | 2017-11-07 | 1 | -0/+59 |
We move them from `playbooks/provisioning/openstack` to `playbooks/openstack` to mirror `playbooks/aws`. |