b685ac44e0
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
37 lines
1.1 KiB
YAML
37 lines
1.1 KiB
YAML
---
|
|
- name: Creating vitrage database
|
|
become: true
|
|
kolla_toolbox:
|
|
module_name: mysql_db
|
|
module_args:
|
|
login_host: "{{ database_address }}"
|
|
login_port: "{{ database_port }}"
|
|
login_user: "{{ database_user }}"
|
|
login_password: "{{ database_password }}"
|
|
name: "{{ vitrage_database_name }}"
|
|
run_once: True
|
|
delegate_to: "{{ groups['vitrage-api'][0] }}"
|
|
when:
|
|
- not use_preconfigured_databases | bool
|
|
|
|
- name: Creating vitrage database user and setting permissions
|
|
become: true
|
|
kolla_toolbox:
|
|
module_name: mysql_user
|
|
module_args:
|
|
login_host: "{{ database_address }}"
|
|
login_port: "{{ database_port }}"
|
|
login_user: "{{ database_user }}"
|
|
login_password: "{{ database_password }}"
|
|
name: "{{ vitrage_database_user }}"
|
|
password: "{{ vitrage_database_password }}"
|
|
host: "%"
|
|
priv: "{{ vitrage_database_name }}.*:ALL"
|
|
append_privs: "yes"
|
|
run_once: True
|
|
delegate_to: "{{ groups['vitrage-api'][0] }}"
|
|
when:
|
|
- not use_preconfigured_databases | bool
|
|
|
|
- import_tasks: bootstrap_service.yml
|