<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body>
Hi Bob,<br>
<br>
Thanks for reaching out!<br>
<br>
We're in the process of finalizing the API and the team is working
hard on getting the code ready; atm with near to complete
functionality WIP patches. Please be mindful of the fact that there
is currently an experimental API in glance and code that will change
completely. As we do not want to document these things, they are
missing from the search results of advanced search engines.<br>
<br>
A good reference document is [1] . This spec has evolved over time
and has input from many a standards so I do not expect drastic
changes unless some security loophole is found during testing
(Probability ~0.1).<br>
<br>
Hope that helps.<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://review.openstack.org/#/c/283136/">https://review.openstack.org/#/c/283136/</a><br>
<br>
<div class="moz-cite-prefix">On 5/4/16 10:08 AM, HADDLETON, Robert W
(Bob) wrote:<br>
</div>
<blockquote
cite="mid:34f28315-7578-b7c4-de99-da97a247c0d5@nokia.com"
type="cite">Hi Nikhil:
<br>
The Tacker project may also be interested in using Glare
during this cycle. Is there any API or other
documentation/examples that we could use to start?
<br>
<br>
Thanks
<br>
<br>
Bob
<br>
<br>
On 5/3/2016 2:40 PM, EXT Nikhil Komawar wrote:
<br>
<blockquote type="cite">Comment inline.
<br>
<br>
On 5/3/16 3:21 PM, Flavio Percoco wrote:
<br>
<blockquote type="cite">On 02/05/16 19:09 -0400, Nikhil Komawar
wrote:
<br>
<br>
<blockquote type="cite">Added a few more tags to the subject
line.
<br>
<br>
<br>
<br>
On 5/2/16 7:05 PM, Nikhil Komawar wrote:
<br>
<br>
<blockquote type="cite">Hello everyone,
<br>
<br>
<br>
<br>
Just wanted to send a brief summary of the discussions at
the summit.
<br>
<br>
This list is not holistic however, it covers the relevant
aspects that
<br>
<br>
various stakeholders need to be aware of.
<br>
<br>
<br>
<br>
* Glare is useful for different use cases in OpenStack
including
<br>
<br>
currently being asked for in Heat, Murano and TOSCA
<br>
<br>
* Heat needs something for usage in Newton
<br>
<br>
* Murano needs the stable API to adapt the changes as
they currently
<br>
<br>
use experimental version
<br>
<br>
* Glance team will continue to make progress on this
effort and plan
<br>
<br>
to have POC after Newton R-16 [1]
<br>
<br>
* The initial plan is to focus on base artifact (no
data asset
<br>
<br>
associated) and then support at least one artifact
type
<br>
<br>
* The first artifact can be Murano application catalogs
or Heat
<br>
<br>
templates depending on either team's priorities when
Glare is ready
<br>
<br>
for consumption
<br>
<br>
* In Newton, we will focus on the adoption of this
service in at least
<br>
<br>
the above mentioned two projects and getting the API
in good shape
<br>
<br>
* Images compatibility is deferred for now
<br>
<br>
* Glare will be a side-priority for Newton meaning most
of the cores
<br>
<br>
are currently not expected to prioritize reviews on
it except for
<br>
<br>
those who want to focus on cross project initiatives
and those
<br>
<br>
involved in its adoption
<br>
<br>
</blockquote>
</blockquote>
<br>
Does this mean there will be some sort of "Fast Track" again?
I'm
<br>
asking because
<br>
</blockquote>
No, we won't have the FastTrack model. But at the same time, we
want to
<br>
iterate over the code once that is consumed by the first service
so that
<br>
the behavioral changes found during that phase can be corrected
before
<br>
m-3. The end goal is to have a good API that can be consumed by
other
<br>
services (and something compliant with OpenStack standards).
<br>
<br>
<blockquote type="cite">I believe this model polarizes the
community a bit as far as picking
<br>
reviews go.
<br>
<br>
We voted to remove it in Mitaka and I was hoping we would
workout a
<br>
way to bring
<br>
<br>
the community together in the Glare reviews.
<br>
</blockquote>
My goal is to have champions for each module that is being
worked on in
<br>
Newton (import, micro-versions, glare, documentation, etc) .
This does
<br>
have a little bit of effect in creating tribal knowledge but we
do have
<br>
that even today. The iterative plan though (yet to be
formalized) is
<br>
that we need some sort of knowledge sharing model. I have been
trying to
<br>
do that using the dedicated Glare meetings but we may need other
models
<br>
of KT (knowledge transfer) here.
<br>
<br>
<blockquote type="cite">
<br>
<br>
Please, don't get me wrong. As far as priorities go, I agree
with what
<br>
you've
<br>
</blockquote>
Thanks for bringing this up. Refines the thought process for
sure.
<br>
<br>
<blockquote type="cite">said in the last point but review wise,
I'm worried this would
<br>
implicitly bring
<br>
<br>
back some kind of fast track model.
<br>
<br>
<br>
</blockquote>
Let's not go with the FastTrack model :-)
<br>
<br>
<blockquote type="cite">Cheers,
<br>
<br>
Flavio
<br>
<br>
<br>
<br>
<br>
<br>
__________________________________________________________________________
<br>
OpenStack Development Mailing List (not for usage questions)
<br>
Unsubscribe:
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
<br>
<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Thanks,
Nikhil</pre>
</body>
</html>