Bring consistency to tags

We apply here our practices to have role_name-(config|install).

Change-Id: Ie8792d271efc6f023c2cf006b99ff89f83890774
This commit is contained in:
Jean-Philippe Evrard 2017-01-06 14:12:29 +00:00
parent 8fb5aff353
commit 41d71da4d9
2 changed files with 7 additions and 8 deletions

View File

@ -33,9 +33,10 @@ To use this role, define the following variables:
Tags
~~~~
This role supports two tags: ``openrc-install`` and ``openrc-config``.
The ``openrc-install`` tag can be used to install and upgrade. The
``openrc-config`` tag can be used to manage configuration.
This role supports two tags: ``openstack_openrc-install`` and
``openstack_openrc-config``. The ``openstack_openrc-install`` tag is only
used to setup the appropriate folders. The ``openstack_openrc-config`` tag
can be used to manage configuration.
Example playbook

View File

@ -21,8 +21,7 @@
group: "{{ openrc_file_group }}"
mode: "0600"
tags:
- openrc-install
- openrc-config
- openstack_openrc-config
- name: Create OpenStack client configuration directory
file:
@ -32,7 +31,7 @@
mode: "0600"
state: directory
tags:
- openrc-install
- openstack_openrc-install
- name: Create clouds.yaml file
template:
@ -42,5 +41,4 @@
group: "{{ openrc_clouds_yml_file_group }}"
mode: "0600"
tags:
- openrc-install
- openrc-config
- openstack_openrc-config