[openstack-dev] [Glance][TC][Heat][App-Catalog][Murano][Tacker] Glare as a new Project

Erno Kuvaja ekuvaja at redhat.com
Thu Aug 4 16:03:02 UTC 2016


On Thu, Aug 4, 2016 at 4:46 PM, Alexander Tivelkov
<ativelkov at mirantis.com> wrote:
> I am the one who started the initiative 2.5 years ago, and was always
> advocating the "let's stay in Glance" approach during numerous discussions
> on "where should it belong" for all these years.
> Now I believe that it is time to move forward indeed. Some things remain to
> be defined (first of all the differences and responsibility sharing between
> Images and Artifacts APIs), but I am fully supportive of this move and
> strongly believe it is a step in a right direction. Thanks Mike, Nikhil,
> Flavio, Erno, Stuart, Brian and all others who helped Glare on this rough
> path.
>
>
> On Thu, Aug 4, 2016 at 6:29 PM Mikhail Fedosin <mfedosin at mirantis.com>
> wrote:
>>
>> Hi all,
>> after 6 months of Glare v1 API development we have decided to continue our
>> work in a separate project in the "openstack" namespace with its own core
>> team (me, Kairat Kushaev, Darja Shkhray and the original creator - Alexander
>> Tivelkov). We want to thank Glance community for their support during the
>> incubation period, valuable advice and suggestions - this time was really
>> productive for us. I believe that this step will allow the Glare project to
>> concentrate on feature development and move forward faster. Having the
>> independent service also removes inconsistencies in understanding what
>> Glance project is: it seems that a single project cannot own two different
>> APIs with partially overlapping functionality. So with the separation of
>> Glare into a new project, Glance may continue its work on the OpenStack
>> Images API, while Glare will become the reference implementation of the new
>> OpenStack Artifacts API.
>>
>> Nevertheless, Glare team would like to continue to collaborate with the
>> Glance team in a new - cross-project - format. We still have lots in common,
>> both in code and usage scenarios, so we are looking forward for fruitful
>> work with the rest of the Glance team. Those of you guys who are interested
>> in Glare and the future of Artifacts API are also welcome to join the Glare
>> team: we have a lot of really exciting tasks and will always welcome new
>> members.
>> Meanwhile, despite the fact that my focus will be on the new project, I
>> will continue to be part of the Glance team and for sure I'm going to
>> contribute in Glance, because I am interested in this project and want to
>> help it be successful.
>>
>> We'll have the formal patches pushed to project-config earlier next week,
>> appropriate repositories, wiki and launchpad space will be created soon as
>> well.  Our regular weekly IRC meeting remains intact: it is 17:30 UTC
>> Mondays in #openstack-meeting-alt, it will just become a Glare project
>> meeting instead of a Glare sub-team meeting. Please feel free to join!
>>
>> Best regards,
>> Mikhail Fedosin
>>
>> P.S. For those of you who may be curious on the project name. We'll still
>> be called "Glare", but since we are on our own now this acronym becomes
>> recursive: GLARE now stands for "GLare Artifact REpository" :)
>> __________________________________________________________________________
>> 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
>
> --
> Regards,
> Alexander Tivelkov
>
> __________________________________________________________________________
> 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
>

Glare is dead, Long Live Glare!

It's sad to see the child moving out of the house, but I'm sure this
is the right thing to do to keep the momentum ongoing while she
matures.

- Erno



More information about the OpenStack-dev mailing list