<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>Kevin,</div>
<div><br>
</div>
<div>Agree it would be a very useful feature, however, easier said then done. Part of Docker's approach is to "move fast";they schedule releases every 2 months. I'm sure the glare team is quite competent, however, keeping API parity on such a fast moving
project such as the docker registry API is a big objective not to be undertaken lightly. If there isn't complete API parity with the docker rregistry v2 API, the work wouldn't be particularly useful to many in the container communities inside OpenStack as
Hongbin pointed out.</div>
<div><br>
</div>
<div>Regards</div>
<div>-steve</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>"Fox, Kevin M" <<a href="mailto:Kevin.Fox@pnnl.gov">Kevin.Fox@pnnl.gov</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>Friday, August 5, 2016 at 2:29 PM<br>
<span style="font-weight:bold">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">Subject: </span>Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project<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 dir="ltr"><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:"Times New Roman","serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:#1F497D}
@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>
<div ocsi="0" fpstyle="1" lang="EN-CA" link="blue" vlink="purple">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">If glare was docker repo api compatible though, I think it would be quite useful. then each tenant doesn't have to set one up themselves.<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="divRpF168695"><font face="Tahoma" size="2" color="#000000"><b>From:</b> Hongbin Lu [<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>]<br>
<b>Sent:</b> Friday, August 05, 2016 1:29 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project<br>
</font><br>
</div>
<div></div>
<div>
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">Replied inline.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"> </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: 10pt; font-family: Tahoma, sans-serif;" lang="EN-US">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif;" lang="EN-US"> Mikhail Fedosin [<a href="mailto:mfedosin@mirantis.com">mailto:mfedosin@mirantis.com</a>]
<br>
<b>Sent:</b> August-05-16 2:10 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project</span></p>
</div>
</div>
<p class="MsoNormal"> </p>
<div>
<div>
<p class="MsoNormal">Thank you all for your responses!</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">From my side I can add that our separation is a deliberate step. We pre-weighed all pros and cons and our final decision was that moving forward as a new project is the lesser of two evils. Undoubtedly, in the short term it will be painful,
but I believe that in the long run Glare will win.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Also, I want to say, that Glare was designed as an open project and we want to build a good community with members from different companies. Glare suppose to be a backend for Heat (and therefore TripleO), App-Catalog, Tacker and definitely
Nova. In addition we are considering the possibility of storage Docker containers, which may be useful for Magnum.</p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><b><i><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);">[Hongbin Lu] Magnum doesn’t have any plan to store docker images at Glare, because COE (i.e. Kubernetes) is simply incompatible with any API
other than docker registry. Zun might have use cases to store docker images at Glare if Glare is part of Glance, but I am reluctant to set a dependency on Glare if Glare is a totally branch new service.</span></i></b><span style="font-size: 11pt; font-family: Calibri, sans-serif; color: rgb(31, 73, 125);"></span></p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Then, I think that comparison between Image API and Artifact API is not correct. Moreover, in my opinion Image API imposes artificial constraints. Just imagine that your file system can only store images in JPG format (more precisely, it
could store any data, but it is imperative that all files must have the extension ".jpg"). Likewise Glance - I can put there any data, it can be both packages and templates, as well as video from my holiday. And this interface, though not ideal, may not work
for all services. But those artificial limitations that have been created, do Glance uncomfortable even for storing images.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">On the other hand Glare provides unified interface for all possible binary data types. If we take the example with filesystem, in Glare's case it supports all file extensions, folders, history of file changes on your disk, data validation
and conversion, import/export files from different computers and so on. These features are not presented in Glance and I think they never will, because of deficiencies in the architecture. </p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">For this reason I think Glare's adoption is important and it will be a huge step forward for OpenStack and the whole community.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Thanks again! If you want to support us, please vote for our talk on Barcelona summit -
<a href="https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/" target="_blank">
https://www.openstack.org/summit/barcelona-2016/vote-for-speakers/</a> Search "Glare" and there will be our presentation.</p>
</div>
<div>
<p class="MsoNormal"> </p>
</div>
<div>
<p class="MsoNormal">Best,</p>
</div>
<div>
<p class="MsoNormal">Mike </p>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<div>
<p class="MsoNormal">On Fri, Aug 5, 2016 at 5:22 PM, Jonathan D. Proulx <<a href="mailto:jon@csail.mit.edu" target="_blank">jon@csail.mit.edu</a>> wrote:</p>
<p class="MsoNormal"><br>
I don't have a strong opinion on the split vs stay discussion. It<br>
does seem there's been sustained if ineffective attempts to keep this<br>
together so I lean toward supporting the divorce.<br>
<br>
But let's not pretend there are no costs for this.<br>
<br>
On Thu, Aug 04, 2016 at 07:02:48PM -0400, Jay Pipes wrote:<br>
:On 08/04/2016 06:40 PM, Clint Byrum wrote:<br>
<br>
:>But, if I look at this from a user perspective, if I do want to use<br>
:>anything other than images as cloud artifacts, the story is pretty<br>
:>confusing.<br>
:<br>
:Actually, I beg to differ. A unified OpenStack Artifacts API,<br>
:long-term, will be more user-friendly and less confusing since a<br>
:single API can be used for various kinds of similar artifacts --<br>
:images, Heat templates, Tosca flows, Murano app manifests, maybe<br>
:Solum things, maybe eventually Nova flavor-like things, etc.<br>
<br>
The confusion is the current state of two API's, not having a future<br>
integrated API.<br>
<br>
Remember how well that served us with nova-network and neutron (né<br>
quantum).<br>
<br>
I also agree with Tim's point. Yes if a new project is fully<br>
documented and integrated well into packaging and config management<br>
implementing it is trivial, but history again teaches this is a long<br>
road.<br>
<br>
It also means extra dev overhead to create and mange these<br>
supporting structures to hide the complexity from end users. Now if<br>
the two project are sufficiently different this may not be a<br>
significant delta as the new docs and config management code would be<br>
need in the old project if the new service stayed stayed there.<br>
<br>
-Jon</p>
<div>
<div>
<p class="MsoNormal"><br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></p>
</div>
</div>
</div>
<p class="MsoNormal"> </p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</span>
</body>
</html>