openstack/kolla-ansible
Code Issues Proposed changes
4a84bac919
kolla-ansible/ansible/roles/prechecks/tasks/main.yml

24 lines
522 B
YAML
Raw Normal View History

Add playbook for hosts pre-deployment checks (ports, files) This playbook runs on hosts before deployment to be sure we don't have any conflicting services running and systems are in expected state. DocImpact Change-Id: If5f288b7fbdf269697ca834da4eb969b61683ca0 Partially-implements: blueprint precheck-tasks
2015-11-11 13:00:02 +03:00
---
Remove haproxy,keepalived groups Haproxy was renamed in [1]. [1] https://review.opendev.org/c/openstack/kolla-ansible/+/770618 Change-Id: Ib2d7f0774fede570a8c4c315d83afd420c31da0b
2021-09-03 16:41:50 +02:00
- import_tasks: inventory_checks.yml
Check supported host OS distributions in prechecks This should help to ensure that users are running tested and supported host OS distributions. Change-Id: I6ee76463d284ad4f3646af1c7ec2b7e50e2f3b15 Partially-Implements: blueprint improve-prechecks
2019-12-17 15:37:04 +00:00
- include_tasks: host_os_checks.yml
when: prechecks_enable_host_os_checks | bool
Add timesync prechecks If not running containerised chrony, we need to check that host has its own means of system clock synchronization. Change-Id: I31b3e9ed625d63a4bf82c674593522268c20ec4c Partial-Bug: #1885689
2020-07-12 10:33:24 +02:00
- include_tasks: timesync_checks.yml
when:
Do not run timesync checks on deployment host Kolla-ansible install python docker library in role/baremetal to group/baremetal, because of this get container facts for timesync checks is failing on deployment host. This patch adding when conditional, so deployment host will be skipped as there is no need to run timesync checks. Closes-Bug: #1933347 Change-Id: Ifefb9c74ee6a80cdbc458992d0196850ddfe7ffa
2021-06-23 15:28:04 +02:00
- inventory_hostname not in groups['deployment']|default([])
Add timesync prechecks If not running containerised chrony, we need to check that host has its own means of system clock synchronization. Change-Id: I31b3e9ed625d63a4bf82c674593522268c20ec4c Partial-Bug: #1885689
2020-07-12 10:33:24 +02:00
Performance: replace unconditional include_tasks with import_tasks Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
2020-06-29 15:06:53 +01:00
- import_tasks: datetime_checks.yml
Introduce /etc/timezone to Debian/Ubuntu containers Some services look for /etc/timezone on Debian/Ubuntu, so we should introduce it to the containers. In addition, added prechecks for /etc/localtime and /etc/timezone. Closes-Bug: #1821592 Change-Id: I9fef14643d1bcc7eee9547eb87fa1fb436d8a6b3
2020-01-26 23:05:13 +03:00
Use include_tasks instead of include include is marked as deprecated since ansible 2.4[0] [0] https://docs.ansible.com/ansible/2.4/include_module.html#deprecated Co-Authored-By: confi-surya <singh.surya64mnnit@gmail.com> Change-Id: Ic9d71e1865d1c728890625aeddf424a5734c0a8a
2018-07-23 12:58:02 +08:00
- include_tasks: port_checks.yml
Do not check api_interface for deployment group Close-Bug: 1732846 Change-Id: I6489599453ae56a60281ecbae9ce85aa59b1162a
2017-11-17 02:54:02 -05:00
when:
Allow the deployment group to be optional This small change prevents the deployment group from being mandatory. Change-Id: I5693fbad0d5677ae341121619b6ec2e8738cffb7
2018-10-25 16:10:26 +01:00
- inventory_hostname not in groups['deployment']|default([])
Add playbook for hosts pre-deployment checks (ports, files) This playbook runs on hosts before deployment to be sure we don't have any conflicting services running and systems are in expected state. DocImpact Change-Id: If5f288b7fbdf269697ca834da4eb969b61683ca0 Partially-implements: blueprint precheck-tasks
2015-11-11 13:00:02 +03:00
Performance: replace unconditional include_tasks with import_tasks Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
2020-06-29 15:06:53 +01:00
- import_tasks: service_checks.yml
Add playbook for hosts pre-deployment checks (ports, files) This playbook runs on hosts before deployment to be sure we don't have any conflicting services running and systems are in expected state. DocImpact Change-Id: If5f288b7fbdf269697ca834da4eb969b61683ca0 Partially-implements: blueprint precheck-tasks
2015-11-11 13:00:02 +03:00
Performance: replace unconditional include_tasks with import_tasks Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
2020-06-29 15:06:53 +01:00
- import_tasks: package_checks.yml
Specify 'become' to necessary tasks (general roles) Add config_owner_user and config_owner_group to group_vars/all, which is user and group of Kolla configuration files in /etc/kolla. Add become to post-deploy playbook. Add become to only neccesary tasks in roles: - certificate - common - destroy - haproxy - mariadb - memcached - rabbitmq Change-Id: I2aba745a6e3928c52642f64551470fd08cbfd058 Partial-Implements: blueprint ansible-specific-task-become
2016-08-23 00:18:36 +07:00
Performance: replace unconditional include_tasks with import_tasks Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
2020-06-29 15:06:53 +01:00
- import_tasks: user_checks.yml
Implement external MariaDB and pre-configured Databases support This change allows the following use cases: 1. Using an already-configured MariaDB / MySQL server / Cluster 2. Using already-created DB users, without requiring root DB access. Update: added external mariadb precheck Change-Id: I78b0d178306d7c5293b0bf53e445f19f18b4b824 Implements: blueprint external-mariadb-support. Closes-Bug: #1603121
2018-01-14 20:16:43 +02:00
Performance: replace unconditional include_tasks with import_tasks Including tasks has a performance penalty when compared with importing tasks. If the include has a condition associated with it, then the overhead of the include may be lower than the overhead of skipping all imported tasks. For unconditionally included tasks, switching to import_tasks provides a clear benefit. Benchmarking of include vs. import is available at [1]. This change switches from include_tasks to import_tasks where there is no condition applied to the include. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/include-and-import.md#task-include-and-import Partially-Implements: blueprint performance-improvements Change-Id: Ia45af4a198e422773d9f009c7f7b2e32ce9e3b97
2020-06-29 15:06:53 +01:00
- import_tasks: database_checks.yml
Copy Permalink