Open Stack

Thank you for asking this! It's really very important and interesting, so
I'm going to explain those things more detailed.

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.

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:
https://docs.google.com/document/d/18Tqad0NUPyFfHUo1KMr6bDDISpQtzacvZtEQIGhNkf4/edit?usp=sharing
Other changes are rather cosmetic. For instance, "queued" image status was
renamed to "drafted".

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.

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.

Best,
Mike Fedosin

On Mon, Jul 10, 2017 at 9:55 PM, Joshua Harlow <harlowja at fastmail.com>
wrote:

> Ed Leafe wrote:
>
>> On Jul 10, 2017, at 5:06 AM, Mikhail Fedosin <mfedosin at gmail.com
>> <mailto:mfedosin at gmail.com>> wrote:
>>
>> Given all the advantages and features of Glare, I believe that it can
>>> become the successful drop-in replacement.
>>>
>>
>> Can you clarify this? Let’s assume I have a decent-sized deployment
>> running Glance. If I were to remove Glance and replace it with Glare,
>> are you saying that nothing would break? Operators, users, scripts,
>> SDKs, etc., would all work unchanged?
>>
>
> Sounds interesting,
>
> Is there some kind of glance-compat API?
>
>
>> -- Ed Leafe
>>
>>
>>
>>
>>
>> ____________________________________________________________
>> ______________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170711/dd807561/attachment.html>