<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Robert Collins <<a href="mailto:robertc@robertcollins.net">robertc@robertcollins.net</a>><br>
<span style="font-weight:bold">Reply-To: </span>"OpenStack Development Mailing List (not for usage questions)" <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, July 16, 2015 at 6:48 PM<br>
<span style="font-weight:bold">To: </span>OpenStack Development Mailing List <<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [openstack-dev] [kolla] image bloat<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div>
<p dir="ltr"><br>
On 17 Jul 2015 12:30, "Steven Dake (stdake)" <<a href="mailto:stdake@cisco.com">stdake@cisco.com</a>> wrote:<br>
><br>
> Hey folks,<br>
><br>
> <br>
> The bloat on the from-source comes from the C toolchain. The bloat on the binary images comes from our common dependency layer. We can probably just get rid of all the Python dependency installs that occur in the common layer and make things a whole lot
faster when deploying at large node scales although it may negatively impact build speed.</p>
<p dir="ltr">I very much hope plain pip would be faster not slower:)</p>
<p dir="ltr">Rob</p>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>Rob,</div>
<div><br>
</div>
<div>We don’t use pip during deployment as it results in an uncontrolled deployment mechanism. Instead we pre-build containers and rely on an atomic deployment (either the container deploys or doesn’t, vs using pip during deployment, where some could fail
and some could succeed). Pre-building is more deterministic, but images must be build.</div>
<div><br>
</div>
<div>Using pip is slower then yum when installing packages. Most of this has to do with invocation of the c compiler for various modules (lxml is an example that takes awhile).</div>
<div><br>
</div>
<div>What I actually proposed in the above email was getting rid of our common dependency layer where yum is only used one time during the build. This would be replaced by using yum for each container (* 40 or so containers *100 or so dependencies). We
already do this for from-source, but not from-binary container building.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</div>
<div><br>
</div>
</body>
</html>