kolla-ansible/ansible/roles/mistral/tasks/deploy.yml

---
- import_tasks: register.yml

- import_tasks: config.yml

- import_tasks: check-containers.yml

- include_tasks: clone.yml
  when: mistral_dev_mode | bool

- import_tasks: bootstrap.yml

- name: Flush handlers
  meta: flush_handlers
Allow mistral role to pull images Change-Id: Id5e56f62dff4fc7bc52641a56abab3ee88a25740 Partially-Implements: blueprint pre-pull-images 2016-01-07 16:00:43 +00:00			`---`
Performance: use import_tasks for register and bootstrap 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 2020-07-07 17:14:37 +01:00			`- import_tasks: register.yml`
Allow mistral role to pull images Change-Id: Id5e56f62dff4fc7bc52641a56abab3ee88a25740 Partially-Implements: blueprint pre-pull-images 2016-01-07 16:00:43 +00: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: config.yml`
Allow mistral role to pull images Change-Id: Id5e56f62dff4fc7bc52641a56abab3ee88a25740 Partially-Implements: blueprint pre-pull-images 2016-01-07 16:00:43 +00:00
Performance: optimize genconfig Config plays do not need to check containers. This avoids skipping tasks during the genconfig action. Ironic and Glance rolling upgrades are handled specially. Swift and Bifrost do not use the handlers at all. Partially-Implements: blueprint performance-improvements Change-Id: I140bf71d62e8f0932c96270d1f08940a5ba4542a 2020-07-30 14:36:15 +02:00			`- import_tasks: check-containers.yml`

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: clone.yml`
dev mode: Add support for mistral Provide support for kolla dev mode in mistral. When 'kolla_dev_mode' or 'mistral_dev_mode' variables are enabled, source code of mistral project is cloned and bind mounted. Partially implements: blueprint mount-sources Co-Authored-By: chenqiaomin <chen.qiaomin@99cloud.net> Change-Id: I6e5f9b1a6b35dbb672905987e715cae4bf10af7f 2018-04-13 00:47:35 +08:00			`when: mistral_dev_mode \| bool`

Performance: use import_tasks for register and bootstrap 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 2020-07-07 17:14:37 +01:00			`- import_tasks: bootstrap.yml`
Allow mistral role to pull images Change-Id: Id5e56f62dff4fc7bc52641a56abab3ee88a25740 Partially-Implements: blueprint pre-pull-images 2016-01-07 16:00:43 +00:00
Optimize reconfiguration for mistral Change-Id: Ieec58fe3759c8ce430a187357ca8282b0f81b7eb Partially-implements: blueprint better-reconfigure 2017-01-22 17:05:11 +08:00			`- name: Flush handlers`
			`meta: flush_handlers`