Emilien Macchi ca80ec5c17 tripleo_container_manage: manage systemd services per step vs start_order ... Instead of managing systemd services per start_order per step, we could manage them per step. The start_order was created to be able to create containers which runs some command or do exec; but not really for the ones who are services and managed by systemd. Doing it per step will reduce the number of tasks and therefore the deployment time. Note: it adds dict_to_list() filter; which converts a dict of dicts to a list of dicts. Ansible allows to do it via dict2items | list but in this particular case we don't want key/value when later treating the data to figure out if systemd is needed. Change-Id: Ia38f2ec753dc3c21bcf91f057fe7ff8020d214e6		2020-04-20 16:03:55 +00:00
..
podman	tripleo_container_manage: manage systemd services per step vs start_order	2020-04-20 16:03:55 +00:00
container_running.yml	Rename all roles that have a hyphen	2020-01-21 20:42:40 -06:00
create.yml	tripleo_container_manage: manage systemd services per step vs start_order	2020-04-20 16:03:55 +00:00
delete_orphan.yml	tripleo_container_manage: remove podman/delete.yml and use another role	2020-02-17 10:24:35 -05:00
main.yml	tripleo_container_manage: print message if no container action	2020-04-15 14:56:47 +00:00
puppet_config.yml	Allow to update container startup config with new config hashes	2020-02-17 13:16:34 +00:00
shutdown.yml	Rename all roles that have a hyphen	2020-01-21 20:42:40 -06:00