496904d650
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. In the case of the register.yml and bootstrap.yml includes, all of the tasks in the included file use run_once: True. The run_once flag improves performance at scale drastically, so importing these tasks unconditionally will have a lower overhead than a conditional include task. It therefore makes sense to switch to use import_tasks there. See [1] for benchmarks of run_once. [1] https://github.com/stackhpc/ansible-scaling/blob/master/doc/run-once.md Change-Id: Ic67631ca3ea3fb2081a6f8978e85b1522522d40d Partially-Implements: blueprint performance-improvements
15 lines
235 B
YAML
15 lines
235 B
YAML
---
|
|
- import_tasks: register.yml
|
|
|
|
- import_tasks: config.yml
|
|
|
|
- include_tasks: clone.yml
|
|
when: designate_dev_mode | bool
|
|
|
|
- import_tasks: bootstrap.yml
|
|
|
|
- name: Flush handlers
|
|
meta: flush_handlers
|
|
|
|
- import_tasks: update_pools.yml
|