Emilien Macchi fa99329115 deploy-steps-tasks/containers: set concurrency to 2 ... After some testing, it seems like podman run/exec/create commands can be run at the same time and decrease the deployment time when 2 commands (maximum) at the same time are run. Example of benchmark done for an Undercloud deployment in my local environment: - With Paunch enabled: 26 min - With Paunch disabled and concurrency set to 1: 32 min - With Paunch disabled and concurrency set to 2: 29 min - With Paunch disabled and concurrency set to 3: 33 min (Above 4, results are worse). Change-Id: Ie7fc754046611a339c743141fe28f801f4e4b331		2019-12-09 02:57:47 +00:00
..
services	Convert firewall rules to use TripleO-Ansible	2019-11-18 15:40:22 -06:00
container_startup_configs_tasks.yaml	Do not log startup config output	2019-11-04 14:39:44 -07:00
container-puppet.py	Use '0' instead of root in container-puppet.py	2019-11-27 23:18:40 +00:00
container-puppet.sh	Drop file test before removal	2019-11-22 10:22:39 -07:00
deploy-steps-tasks-step-0.j2.yaml	Ensure we set proper SELinux label on container-puppet.sh	2019-11-28 17:01:05 +01:00
deploy-steps-tasks-step-1.yaml	Mode 0750 for /var/log/containers	2019-11-04 11:06:44 +01:00
deploy-steps-tasks.yaml	deploy-steps-tasks/containers: set concurrency to 2	2019-12-09 02:57:47 +00:00
deploy-steps.j2	Merge "Re-enable "service_names" hieradata"	2019-12-06 09:04:03 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00