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
35 lines
1.0 KiB
YAML
35 lines
1.0 KiB
YAML
---
|
|
- import_tasks: config.yml
|
|
|
|
# NOTE(pbourke): because the images that are used to start Swift containers
|
|
# were refactored for Mitaka, we need to completely remove the existing
|
|
# containers or we get a conflict when attempting to start the new ones.
|
|
- name: "Cleaning out old Swift containers"
|
|
become: true
|
|
kolla_docker:
|
|
name: "{{ item }}"
|
|
action: "stop_container"
|
|
with_items:
|
|
- "swift_rsyncd"
|
|
- "swift_account_server"
|
|
- "swift_account_auditor"
|
|
- "swift_account_replication_server"
|
|
- "swift_account_replicator"
|
|
- "swift_account_reaper"
|
|
- "swift_container_server"
|
|
- "swift_container_auditor"
|
|
- "swift_container_replication_server"
|
|
- "swift_container_replicator"
|
|
- "swift_container_updater"
|
|
- "swift_object_server"
|
|
- "swift_object_auditor"
|
|
- "swift_object_replication_server"
|
|
- "swift_object_replicator"
|
|
- "swift_object_updater"
|
|
- "swift_object_expirer"
|
|
- "swift_proxy_server"
|
|
|
|
- import_tasks: start.yml
|
|
vars:
|
|
run_start_swift_proxy_server: "yes"
|