Alex Schultz 4ec57c60f3 Add facter cache for container configurations ... Rather than running all the facts for every invocation of container-puppet.py, let's cache the facts for the entire container config step. This is similar to what used to happen when we ran puppet in a single instance for a given step. This improves the time it takes puppet tp execute within the containers. When systems have large number of interfaces, the fact generation for puppet can come to a crawl given that puppet is not supposed to be invoked multiple times in parallel. By pre-caching the facts, we eliminate the need for puppet to do the network (and other fact) related lookups when running container configuration generation. Closes-Bug: #1835959 Change-Id: I6ee3849ff380304a184638493f33882b813bfdff		2019-07-17 13:39:03 +00:00
..
services	Introduce scale_tasks	2019-04-24 11:07:53 -04:00
container-puppet.py	Add facter cache for container configurations	2019-07-17 13:39:03 +00:00
deploy-steps-tasks.yaml	Add facter cache for container configurations	2019-07-17 13:39:03 +00:00
deploy-steps.j2	Merge "Use template for NetworkConfig script"	2019-07-15 19:03:38 +00:00
post.j2.yaml	Consolidate puppet/docker deployments with one deploy steps workflow	2017-08-11 17:25:02 +00:00