<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 11, 2017 at 1:43 AM, Monty Taylor <span dir="ltr"><<a href="mailto:mordred@inaugust.com" target="_blank">mordred@inaugust.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-">On 07/10/2017 04:31 PM, Mikhail Fedosin wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Thank you for asking this! It's really very important and interesting, so I'm going to explain those things more detailed.<br>
<br>
First, when we designed Glare, we kept in mind the compatibility with Glance, and I can tell that Glance data from the database can be ported to Glare with a simple script without any loss.<br>
<br>
Second, APIs are very similar and map 1:1. The only one big difference is that user has to perform activation manually after image file is uploaded. I created a small table with the most popular API requests. You may notice how similar both APIs are: <a href="https://docs.google.com/document/d/18Tqad0NUPyFfHUo1KMr6bDDISpQtzacvZtEQIGhNkf4/edit?usp=sharing" rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/18Tqad0NUPyFfHUo1KMr6bDDI<wbr>SpQtzacvZtEQIGhNkf4/edit?usp=s<wbr>haring</a><br>
Other changes are rather cosmetic. For instance, "queued" image status was renamed to "drafted".<br>
<br>
Third, all these changes can be hidden in Glare client. So if we try a little, we can achieve 100% compatibility there, and other projects can use Glare client instead of Glance's without even noticing the differences.<br>
</blockquote>
<br></span>
I think we should definitely not do this... I think instead, if we decide to go down this road, we want to look at adding an endpoint to glare that speaks glance v2 API so that users can have a transition period while libraries and tools get updated to understand the artifacts API.</blockquote><div> </div><div>This is optional and depends on the project developers. For my part, I can only offer the most compatible client, so that the Glance module can be simply copied into the new Glare module.</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span class="gmail-"><br>
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
If projects use Glance without client, it means that some direct API requests will need to be rewritten. But in any case, the number of differences between Glance v1 and Glance v2 was much larger, and we switched pretty smoothly. So I hope everything will be fine here, too.<br>
</blockquote>
<br></span>
v1 vs v2 is still a major headache for end users. I don't think it's ok for us to do that to our users again if we can help it.<br>
<br>
However, as you said, conceptually the calls are very similar so making an API controller that can be registered in the catalog as "image" should be fairly easy to do, no?<br></blockquote><div><div>Indeed, the interfaces are almost identical. And all the differences were made on purpose. </div><div><br></div><div>For example, deactivating an image in Glance looks like <b>POST</b> <font face="monospace, monospace">/v2/images/{image_id}/actions/deactivate</font> with empty body.</div><div>At one time, Chris Dent advised us to avoid such decisions, and simply change the status of the artifact to 'deactivated' using <b>PATCH</b>, which we did.</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Best,<br>
Mike Fedosin<span class="gmail-"><br>
<br>
On Mon, Jul 10, 2017 at 9:55 PM, Joshua Harlow <<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a> <mailto:<a href="mailto:harlowja@fastmail.com" target="_blank">harlowja@fastmail.com</a>><wbr>> wrote:<br>
<br>
Ed Leafe wrote:<br>
<br>
On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin <<a href="mailto:mfedosin@gmail.com" target="_blank">mfedosin@gmail.com</a><br>
<mailto:<a href="mailto:mfedosin@gmail.com" target="_blank">mfedosin@gmail.com</a>><br></span><span class="gmail-">
<mailto:<a href="mailto:mfedosin@gmail.com" target="_blank">mfedosin@gmail.com</a> <mailto:<a href="mailto:mfedosin@gmail.com" target="_blank">mfedosin@gmail.com</a>>>> wrote:<br>
<br>
Given all the advantages and features of Glare, I believe<br>
that it can<br>
become the successful drop-in replacement.<br>
<br>
<br>
Can you clarify this? Let’s assume I have a decent-sized deployment<br>
running Glance. If I were to remove Glance and replace it with<br>
Glare,<br>
are you saying that nothing would break? Operators, users, scripts,<br>
SDKs, etc., would all work unchanged?<br>
<br>
<br>
Sounds interesting,<br>
<br>
Is there some kind of glance-compat API?<br>
<br>
<br>
-- Ed Leafe<br>
<br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><span class="gmail-"><br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br></span>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@<wbr>lists.openstack.org?subject:un<wbr>subscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><span class="gmail-"><br>
<<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cg<wbr>i-bin/mailman/listinfo/opensta<wbr>ck-dev</a>><br>
<br>
<br>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</span></blockquote><div class="gmail-HOEnZb"><div class="gmail-h5">
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div></div>