> Let's also think of removing puppet-tripleo from the base container.
> It really brings the world-in (and yum updates in CI!) each job and each
> So if we did so, we should then either install puppet-tripleo and co on
> the host and bind-mount it for the docker-puppet deployment task steps
> (bad idea IMO), OR use the magical --volumes-from <a-side-car-container>
> option to mount volumes from some "puppet-config" sidecar container
> inside each of the containers being launched by docker-puppet tooling.
On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås <hjensas at redhat.com>
> We add this to all images:
> https://github.com/openstack/tripleo-common/blob/d35af75b0d8c4683a677660646e535cf972c98ef/container-images/tripleo_kolla_template_overrides.j2#L35 >
> /bin/sh -c yum -y install iproute iscsi-initiator-utils lvm2 python
> socat sudo which openstack-tripleo-common-container-base rsync cronie
> crudini openstack-selinux ansible python-shade puppet-tripleo python2-
> kubernetes && yum clean all && rm -rf /var/cache/yum 276 MB
> Is the additional 276 MB reasonable here?
> openstack-selinux <- This package run relabling, does that kind of
> touching the filesystem impact the size due to docker layers?
> Also: python2-kubernetes is a fairly large package (18007990) do we use
> that in every image? I don't see any tripleo related repos importing
> from that when searching on Hound? The original commit message
> adding it states it is for future convenience.
> On my undercloud we have 101 images, if we are downloading every 18 MB
> per image thats almost 1.8 GB for a package we don't use? (I hope it's
> not like this? With docker layers, we only download that 276 MB
> transaction once? Or?)
>  https://review.openstack.org/527927