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.
Reviewed: https:/ /review. opendev. org/669011 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=4ec57c60f30 f994d8bf36021ff 12670e6c8c77b5
Committed: https:/
Submitter: Zuul
Branch: master
commit 4ec57c60f30f994 d8bf36021ff1267 0e6c8c77b5
Author: Alex Schultz <email address hidden>
Date: Wed Jul 3 19:02:20 2019 -0600
Add facter cache for container configurations
Rather than running all the facts for every invocation of puppet. py, let's cache the facts for the entire container
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 4a184638493f338 82b813bfdff
Change-Id: I6ee3849ff38030