Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Update the doc text | Tomas Sedovic | 2017-11-29 | 1 | -0/+1 |
| | |||||
* | Use IP addresses for OpenStack nodes | Tomas Sedovic | 2017-11-28 | 1 | -1/+9 |
| | | | | | | | | | | | | | 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. | ||||
* | Add openshift_openstack role and move tasks there | Tomas Sedovic | 2017-11-07 | 1 | -14/+22 |
| | | | | | | | | | All the tasks that were previously in playbooks are now under `roles/openshift_openstack`. The `openshift-cluster` directory now only contains playbooks that include tasks from that role. This makes the structure much closer to that of the AWS provider. | ||||
* | Move the OpenStack playbooks | Tomas Sedovic | 2017-11-07 | 1 | -0/+88 |
We move them from `playbooks/provisioning/openstack` to `playbooks/openstack` to mirror `playbooks/aws`. |