Sam, Agreed this matches my experience. Building one by one though will result in massive image size sprawl.
Regards -steve From: Sam Yaple <sam...@yaple.net> Reply-To: "s...@yaple.net" <s...@yaple.net>, "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Thursday, October 19, 2017 at 10:37 PM To: Gabriele Cerami <gcer...@redhat.com> Cc: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [TripleO][Kolla] Concerns about containers images in DockerHub On Thu, Oct 19, 2017 at 11:23 PM, Gabriele Cerami <gcer...@redhat.com<mailto:gcer...@redhat.com>> wrote: On 19 Oct, Sam Yaple wrote: > So it seems tripleo is building *all* images and then pushing them. > Reworking your number leads me to believe you will be consuming 10-15GB in > total on Dockerhub. Kolla images are only the size that you posted when > built as seperate services. Just keep building all the images at the same > time and you wont get anywhere near the numbers you posted. Makes sense, so considering the shared layers - a size of 10-15GB per build. - 4-6 builds rotated per release - 3-4 releases - a size of 1-2GB per build - 4-6 builds rotated per release - 3-4 releases At worst you are looking at 48GB not 360GB. Dont worry so much there! total size will be approximately be 360GB in the worst case, and 120GB in the best case, which seems a bit more reasonable. Thanks for he clarifications
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
