<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=gb2312">
<style>
<!--
@font-face
{font-family:SimSun}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:SimSun}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
p
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:SimSun}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif"}
span.BalloonTextChar
{font-family:"Tahoma","sans-serif"}
span.EmailStyle20
{font-family:"Calibri","sans-serif";
color:#1F497D}
.MsoChpDefault
{font-size:10.0pt}
@page WordSection1
{margin:72.0pt 72.0pt 72.0pt 72.0pt}
-->
</style><style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
</head>
<body ocsi="0" fpstyle="1" vlink="purple" lang="EN-CA" link="blue">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">If they have a valid CA signed cert for the docker registry, it should 'Just work (TM)' :)<br>
<br>
Self signing is a different issue. Maybe just an additional option in addition to the prefix option to pass a CA to add to the root trust chain?<br>
<br>
Thanks,<br>
Kevin<br>
<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF667174"><font color="#000000" face="Tahoma" size="2"><b>From:</b> Hongbin Lu [hongbin.lu@huawei.com]<br>
<b>Sent:</b> Tuesday, April 19, 2016 11:50 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Magnum]Cache docker images<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Yes, that is an alternative. The complication is how to secure the communication between Magnum bays and the standalone docker registry. I assume we needs
some custom logic to setup the communication channel (i.e. install the TLS credential). One way to support it is to add a configuration hook [1] that allows operators to customize the setup. Pre-built docker images into the glance image is another approach.
I think Magnum can offer both.</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">[1] https://blueprints.launchpad.net/magnum/+spec/allow-user-softwareconfig </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Best regards,</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D">Hongbin</span></p>
<p class="MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri","sans-serif"; color:#1F497D"> </span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"" lang="EN-US">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"" lang="EN-US"> Fox, Kevin M [mailto:Kevin.Fox@pnnl.gov]
<br>
<b>Sent:</b> April-19-16 1:12 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Magnum]Cache docker images</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">why not just allow a prefix to be added to the container name?<br>
<br>
you can then have a container named:<br>
foo/mycontainer<br>
<br>
and the prefix could be set to mylocalserver.org:8080:<br>
mylocalserver.org:8080/foo/mycontainer<br>
<br>
Then if the site needs local only containers, they can set up a local repo. Be it a stand alone docker registry, the docker datacenter product, artifactory with the docker plugin, etc.<br>
<br>
Thanks,<br>
Kevin </span></p>
<div>
<div class="MsoNormal" style="text-align:center" align="center"><span style="font-family:"Times New Roman","serif"; color:black">
<hr align="center" size="2" width="100%">
</span></div>
<div id="divRpF598775">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">From:</span></b><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black">
</span><span style="font-size:10.0pt; color:black" lang="ZH-CN">Íõ»ª</span><span style="font-size:10.0pt; font-family:"Tahoma","sans-serif"; color:black"> [wanghua.humble@gmail.com]<br>
<b>Sent:</b> Monday, April 18, 2016 7:57 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> [openstack-dev] [Magnum]Cache docker images</span><span style="font-family:"Times New Roman","serif"; color:black"></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">Hi all,
</span></p>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black"> </span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">We want to eliminate pulling docker images over the Internet on bay provisioning. There are two problems of this approach:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">1. Pulling docker images over the Internet is slow and fragile.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">2. Some clouds don't have external Internet access.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">It is suggested to build all the required images into the cloud images to resolved the issue.</span></p>
</div>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">Here is a solution:</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">We export the docker images as tar files, and put the tar files into a dir in the image when we build the image. And we add scripts to load the tar files in cloud-init, so
that we don't need to download the docker images.</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">Any advice for this solution or any better solution?</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black"> </span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">Regards,</span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:"Times New Roman","serif"; color:black">Wanghua</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>