Files
8a7b586848ad41eb94633d8bd4614a77202ed1d5
openstack-ansible-os_trove /tasks /main.yml

117 lines
3.8 KiB
YAML
Raw Normal View History

2016年08月25日 14:54:34 +02:00
---
# Copyright 2016 Internet Solutions (Pty) Ltd
2016年08月25日 14:54:34 +02:00
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
2016年08月25日 14:54:34 +02:00
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# (c) 2016 Donovan Francesco <donovan.francesco@is.co.za>
# (c) 2016 Paul Stevens <paul.stevens@is.co.za>
2016年08月25日 14:54:34 +02:00
- name:Gather variables for each operating system
include_vars:"{{ item }}"
with_first_found:
- "{{ ansible_distribution | lower }}-{{ ansible_distribution_version | lower }}.yml"
- "{{ ansible_distribution | lower }}-{{ ansible_distribution_major_version | lower }}.yml"
- "{{ ansible_os_family | lower }}-{{ ansible_distribution_major_version | lower }}.yml"
- "{{ ansible_distribution | lower }}.yml"
- "{{ ansible_os_family | lower }}.yml"
tags:
- always
- name:Fail if our required secrets are not present
fail:
msg:"Please set the {{ item }} variable prior to applying this role."
when:(item is undefined) or (item is none)
with_items:"{{ trove_required_secrets }}"
tags:
- always
- include_tasks:trove_pre_install.yml
2016年08月25日 14:54:34 +02:00
tags:
- trove-install
- include_tasks:trove_install.yml
2016年08月25日 14:54:34 +02:00
tags:
- trove-install
- include_tasks:trove_service_network.yml
tags:
- trove-install
- trove-config
- include_tasks:trove_post_install.yml
2016年08月25日 14:54:34 +02:00
tags:
- trove-install
- trove-config
- name:Run the systemd service role
include_role:
name:systemd_service
vars:
systemd_user_name:"{{ trove_system_user_name }}"
systemd_group_name:"{{ trove_system_group_name }}"
systemd_tempd_prefix:openstack
systemd_slice_name:trove
systemd_lock_path:/var/lock/trove
systemd_CPUAccounting:true
systemd_BlockIOAccounting:true
systemd_MemoryAccounting:true
systemd_TasksAccounting:true
systemd_services:
- service_name:"{{ service_var.service_name }}"
enabled:yes
state:started
execstarts:"{{ service_var.execstarts }}"
execreloads:"{{ service_var.execreloads | default([]) }}"
config_overrides:"{{ service_var.init_config_overrides }}"
with_items:"{{ trove_services.values() | list }}"
loop_control:
loop_var:service_var
2016年08月25日 14:54:34 +02:00
tags:
- trove-config
- systemd-service
2016年08月25日 14:54:34 +02:00
- include_tasks:trove_service_setup.yml
when:inventory_hostname == groups['trove_api'][0]
2016年08月25日 14:54:34 +02:00
tags:
- trove-install
Allow tags to be used for MQ tasks The use of 'include_tasks' and a loop of variables creates a situation where a user is unable to use tags to scope the inclusion of only the MQ tasks when running the playbooks. The use-case this is important for is when the rabbitmq containers are destroyed and rebuilt in order to resolve an issue with them, and the user wishes to quickly recreate all the vhosts/users. Ansible's 'include_tasks' is a dynamic inclusion, and dynamic inclusions are not included when using tags. The nice thing about dynamic inclusions is that they completely skip all tasks when the condition does not apply, cutting down deploy time. However, given the use-case, we should rather take on the extra deployment time. This patch changes the dynamic inclusion to a static one, adds a 'common-mq' tag to cover all MQ implementations, and re-implements the 'common-rabbitmq' tag for the tasks that relate to RabbitMQ specifically. It also implements conditionals for each task set so that the rpc/notify tasks can be skipped if a vhost/user is not required for that purpose (eg: swift does not use RPC, and most roles will not use notifications by default). Depends-On: https://review.openstack.org/588191 Change-Id: I320ae83839869ee89fa5db3bf5c55d245f3b17db
2018年08月07日 15:06:11 +01:00
- import_tasks:mq_setup.yml
Move MQ vhost/user creation into role There is no record for why we implement the MQ vhost/user creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement two new variables: - trove_oslomsg_rpc_setup_host - trove_oslomsg_notify_setup_host These are used in the role to allow delegation of the MQ vhost/user setup for each type to any host, but they default to using the first member of the applicable oslomsg host group. We also adjust some of the defaults to automatically inherit existing vars set in group_vars form the integrated build so that we do not need to do the wiring in the integrated build's group vars. We still default them in the role too for independent role usage. Change-Id: I88514f00c4b4c0452b573d765bb895cb562f952e
2018年07月17日 22:10:22 +01:00
when:
- "trove_services['trove-api']['group'] in group_names"
- "inventory_hostname == ((groups[trove_services['trove-api']['group']]| intersect(ansible_play_hosts)) | list)[0]"
Allow tags to be used for MQ tasks The use of 'include_tasks' and a loop of variables creates a situation where a user is unable to use tags to scope the inclusion of only the MQ tasks when running the playbooks. The use-case this is important for is when the rabbitmq containers are destroyed and rebuilt in order to resolve an issue with them, and the user wishes to quickly recreate all the vhosts/users. Ansible's 'include_tasks' is a dynamic inclusion, and dynamic inclusions are not included when using tags. The nice thing about dynamic inclusions is that they completely skip all tasks when the condition does not apply, cutting down deploy time. However, given the use-case, we should rather take on the extra deployment time. This patch changes the dynamic inclusion to a static one, adds a 'common-mq' tag to cover all MQ implementations, and re-implements the 'common-rabbitmq' tag for the tasks that relate to RabbitMQ specifically. It also implements conditionals for each task set so that the rpc/notify tasks can be skipped if a vhost/user is not required for that purpose (eg: swift does not use RPC, and most roles will not use notifications by default). Depends-On: https://review.openstack.org/588191 Change-Id: I320ae83839869ee89fa5db3bf5c55d245f3b17db
2018年08月07日 15:06:11 +01:00
vars:
_oslomsg_rpc_setup_host:"{{ trove_oslomsg_rpc_setup_host }}"
_oslomsg_rpc_userid:"{{ trove_oslomsg_rpc_userid }}"
_oslomsg_rpc_password:"{{ trove_oslomsg_rpc_password }}"
_oslomsg_rpc_vhost:"{{ trove_oslomsg_rpc_vhost }}"
_oslomsg_rpc_transport:"{{ trove_oslomsg_rpc_transport }}"
_oslomsg_notify_setup_host:"{{ trove_oslomsg_notify_setup_host }}"
_oslomsg_notify_userid:"{{ trove_oslomsg_notify_userid }}"
_oslomsg_notify_password:"{{ trove_oslomsg_notify_password }}"
_oslomsg_notify_vhost:"{{ trove_oslomsg_notify_vhost }}"
_oslomsg_notify_transport:"{{ trove_oslomsg_notify_transport }}"
Move MQ vhost/user creation into role There is no record for why we implement the MQ vhost/user creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement two new variables: - trove_oslomsg_rpc_setup_host - trove_oslomsg_notify_setup_host These are used in the role to allow delegation of the MQ vhost/user setup for each type to any host, but they default to using the first member of the applicable oslomsg host group. We also adjust some of the defaults to automatically inherit existing vars set in group_vars form the integrated build so that we do not need to do the wiring in the integrated build's group vars. We still default them in the role too for independent role usage. Change-Id: I88514f00c4b4c0452b573d765bb895cb562f952e
2018年07月17日 22:10:22 +01:00
tags:
Allow tags to be used for MQ tasks The use of 'include_tasks' and a loop of variables creates a situation where a user is unable to use tags to scope the inclusion of only the MQ tasks when running the playbooks. The use-case this is important for is when the rabbitmq containers are destroyed and rebuilt in order to resolve an issue with them, and the user wishes to quickly recreate all the vhosts/users. Ansible's 'include_tasks' is a dynamic inclusion, and dynamic inclusions are not included when using tags. The nice thing about dynamic inclusions is that they completely skip all tasks when the condition does not apply, cutting down deploy time. However, given the use-case, we should rather take on the extra deployment time. This patch changes the dynamic inclusion to a static one, adds a 'common-mq' tag to cover all MQ implementations, and re-implements the 'common-rabbitmq' tag for the tasks that relate to RabbitMQ specifically. It also implements conditionals for each task set so that the rpc/notify tasks can be skipped if a vhost/user is not required for that purpose (eg: swift does not use RPC, and most roles will not use notifications by default). Depends-On: https://review.openstack.org/588191 Change-Id: I320ae83839869ee89fa5db3bf5c55d245f3b17db
2018年08月07日 15:06:11 +01:00
- common-mq
Move MQ vhost/user creation into role There is no record for why we implement the MQ vhost/user creation outside of the role in the playbook, when we could do it inside the role. Implementing it inside the role allows us to reduce the quantity of group_vars duplicated from the role, and allows us to better document the required variables in the role. The delegation can still be done as it is done in the playbook too. In this patch we implement two new variables: - trove_oslomsg_rpc_setup_host - trove_oslomsg_notify_setup_host These are used in the role to allow delegation of the MQ vhost/user setup for each type to any host, but they default to using the first member of the applicable oslomsg host group. We also adjust some of the defaults to automatically inherit existing vars set in group_vars form the integrated build so that we do not need to do the wiring in the integrated build's group vars. We still default them in the role too for independent role usage. Change-Id: I88514f00c4b4c0452b573d765bb895cb562f952e
2018年07月17日 22:10:22 +01:00
- trove-config
- include_tasks:trove_db_setup.yml
when:inventory_hostname == groups['trove_conductor'][0]
2016年08月25日 14:54:34 +02:00
tags:
- trove-install
- include_tasks:trove_apache.yml
2016年08月25日 14:54:34 +02:00
when:trove_use_mod_wsgi | bool
tags:
- trove-install
- trove-config