Mark Goddard 9702d4c3c3 Performance: use import_tasks for check-containers.yml ... 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 check-containers.yml include, the included file only has a single task, so the overhead of skipping this task will not be greater than the overhead of the task import. It therefore makes sense to switch to use import_tasks there. Partially-Implements: blueprint performance-improvements Change-Id: I65d911670649960708b9f6a4c110d1a7df1ad8f7		2020-07-28 12:10:59 +01:00
..
check-containers.yml	Add a job that *only* deploys updated containers	2019-09-26 17:51:14 +01:00
check.yml	introduce playbook to ovs with dpdk	2017-08-09 18:43:06 +00:00
config.yml	Performance: use import_tasks for check-containers.yml	2020-07-28 12:10:59 +01:00
deploy-containers.yml	Add a job that *only* deploys updated containers	2019-09-26 17:51:14 +01:00
deploy.yml	Use include_tasks instead of include	2018-07-25 23:57:22 +08:00
main.yml	Use include_tasks instead of include	2018-07-25 23:57:22 +08:00
precheck.yml	Add Ansible group check to prechecks	2020-02-28 16:23:14 +00:00
pull.yml	Specify 'become' for all tasks that use kolla_docker module	2018-06-08 12:39:24 +00:00
reconfigure.yml	Use include_tasks instead of include	2018-07-25 23:57:22 +08:00
stop.yml	Use "name:" instead of "role:" for *_role modules	2020-03-02 10:01:17 +01:00
upgrade.yml	Use include_tasks instead of include	2018-07-25 23:57:22 +08:00