summaryrefslogtreecommitdiffstats
path: root/playbooks/openstack/sample-inventory/inventory.py
Commit message (Collapse)AuthorAgeFilesLines
* Move the OpenStack dynamic inventory from sampleTomas Sedovic2018-01-161-119/+0
| | | | | | | | | | Keeping the dynamic inventory in the `sample-inventory` alongside the `group_vars` poses a problem: when we update the inventory, our users won't get the latest version. The dynamic inventory should be independent of the OpenShift or OpenStack configuration and the users should be able to either pass it explicitly or create a symlink if they want.
* Allow using server names in openstack dynamic invTomas Sedovic2018-01-101-2/+4
| | | | | | | | When deploying on OpenStack with internal DNS configured, this will set `openshift_hostname` to the Nova server name instead of its IP address. Without those two matching, the OpenStack cloud provider configuration will fail and the OpenShift nodes will not start.
* Merge pull request #6580 from tomassedovic/openstack-fixesOpenShift Merge Robot2018-01-081-0/+5
|\ | | | | | | | | | | | | | | | | Automatic merge from submit-queue. Openstack fixes This includes a few fixes for the OpenStack provider. It should fix #6555 and possibly also #6560.
| * Return a openshift_node_labels as a dictTomas Sedovic2018-01-021-0/+5
| | | | | | | | | | | | | | | | The OpenStack dynamic inventory was setting the `openshift_node_labels` value as a string which causes a failure with the `lib_utils_oo_dict_to_keqv_list` filter. Fixes #6555
* | OpenStack provisioning -- support cns.Jiri Mencak2018-01-021-1/+8
|/
* Update the doc textTomas Sedovic2017-11-291-0/+1
|
* Use IP addresses for OpenStack nodesTomas Sedovic2017-11-281-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 thereTomas Sedovic2017-11-071-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 playbooksTomas Sedovic2017-11-071-0/+88
We move them from `playbooks/provisioning/openstack` to `playbooks/openstack` to mirror `playbooks/aws`.