summaryrefslogtreecommitdiffstats
path: root/roles/openshift_openstack
Commit message (Collapse)AuthorAgeFilesLines
* dist.iteritems() no longer exists in Python 3.Jan Pazdziora2017-11-271-2/+2
|
* Fix toxTomas Sedovic2017-11-072-3/+3
|
* Namespace the OpenStack varsTomas Sedovic2017-11-0711-312/+314
| | | | | This makes sure that all the variables used in the `openshift_openstack` role are prefixed with `openshift_openstack_` as is the convention.
* Use `null` instead of `False` where it makes senseTomas Sedovic2017-11-071-2/+2
| | | | | The `openstack_*_network_name` vars are strings, not booleans, so the absense shouldn't really be marked by `False`.
* Simplify the template paths for the storage setupTomas Sedovic2017-11-071-3/+3
| | | | | | Because the templates are present in a role, the `template` module is able to look them up directly, without having to use `{{ role_path }}/templates`.
* Use the default `item` loop variable for checksTomas Sedovic2017-11-073-14/+11
|
* Move the selinux check upTomas Sedovic2017-11-071-5/+5
|
* Add the DNS updates and rename the openstack varsTomas Sedovic2017-11-078-305/+238
| | | | | Most of the vars in `roles/openshift_openstack/defaults/main.yml` are now prefixed with `openstack_`.
* Remove the subnet_update_dns_servers task listTomas Sedovic2017-11-071-9/+0
| | | | It's no longer being used.
* Move the vars/main.yml to defaultsTomas Sedovic2017-11-072-49/+53
| | | | | | | | The contents of roles/openshift_openstack/vars/main.yml were moved to the defaults/main.yml file instead. There are now duplication warnings we need to address, but the deployment does still work.
* Add a stub of the dns record update code inTomas Sedovic2017-11-072-0/+173
| | | | This will mostly not work but it's a starting point.
* Add openshift_openstack role and move tasks thereTomas Sedovic2017-11-0722-0/+1672
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.