<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thank you Jesse for your valuable input (here and at the summit) as
well as intent to clarify the discussion.<br>
<br>
Just trying to ensure people are aware about the EXPERIMENTAL nature
of the v3 API and reasons behind it. Please find my responses
in-line. However, I do want to ensure you all, that we will strive
hard to move away from the EXPERIMENTAL nature and go with a rock
solid implementation as and when interest grows in the code-base
(that helps stabilize it).<br>
<br>
<div class="moz-cite-prefix">On 5/26/15 12:57 PM, Jesse Cook wrote:<br>
</div>
<blockquote cite="mid:D18A0DC5.301D7%25jesse.cook@rackspace.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div>
<div>
<div><br>
</div>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div>
<div>On 5/22/15, 4:28 PM, "Nikhil Komawar" <<a
moz-do-not-send="true" href="mailto:nik.komawar@gmail.com">nik.komawar@gmail.com</a>>
wrote:</div>
</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>
<div bgcolor="#FFFFFF" text="#000000">Hi all,<br>
<br>
tl;dr; Artifacts IS staying in Glance.<br>
<br>
<ol>
<li>We had a nice discussion at the contributors'
meet-up at the Vancouver summit this morning. After
weighing in many possibilities and evolution of the
Glance program, we have decided to go ahead with the
Artifacts implementation within Glance program under
the EXPERIMENTAL v3 API.</li>
</ol>
</div>
</div>
</blockquote>
</span>
<div>Want to clarify a bit here. My understanding is:
s/Artifacts/v3 API/g. That is to say, Artifacts is the technical
implementation of the v3 API. This also means the v3 API is an
objects API vs just an images API.</div>
<div><br>
</div>
</blockquote>
Generic "data assets'" API would be a nice term along the lines of
the mission statement. Artifacts seemed fitting as that was the
focus of discussion at various sessions.<br>
<blockquote cite="mid:D18A0DC5.301D7%25jesse.cook@rackspace.com"
type="cite">
<div>
</div>
<div>We also had some hallway talk about putting the v1 and v2
APIs on top of the v3 API. This forces faster adoption, verifies
supportability via v1 and v2 tests, increases supportability of
v1 and v2 APIs, and pushes out the need to kill v1 API.</div>
</blockquote>
Let's discuss more as time and development progresses on that
possibility. v3 API should stay EXPERIMENTAL for now as that would
help us understand use-cases across programs as it gets adopted by
various code-bases. Putting v1/v2 on top of v3 would be tricky for
now as we may have breaking changes with code being relatively-less
stable due to narrow review domain.<br>
<blockquote cite="mid:D18A0DC5.301D7%25jesse.cook@rackspace.com"
type="cite">
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
0 0 5;">
<div>
<div bgcolor="#FFFFFF" text="#000000">
<ol>
<li><br>
</li>
<li>The effort would primarily be conducted as a
sub-team-like structure within the program and the
co-coordinators and drivers of the necessary Artifacts
features would be given core-reviewer status
temporarily with an informal agreement to merge code
that is only related to Artifacts. <br>
</li>
<li>The entire Glance team would give reviews as time
and priorities permit. The approval (+A/+WorkFlow) of
any code within the program would need to come from
core-reviewers who are not temporarily authorized. The
list of such individuals and updated time-line would
be documented in phases during the course of Liberty
cycle. </li>
<li>We will continue to evaluate & update the
governance, maturity of the code and future plans for
the v1, v2 and v3 Glance APIs as time progresses.
However, for now we are aiming to integrate all of
Glance (specifically Images) as Artifacts in the v3
API.</li>
</ol>
</div>
</div>
</blockquote>
</span>
<div><br>
</div>
<div>As I understand it, that is to say that v3 requests in the
first “micro-version” that specify the object type as image
would get a not implemented or similar error. The next next
“micro-version” would likely contain the support for images
along with possibly implementing the v1 and v2 APIs on top of
v3.</div>
</blockquote>
As we will have EXPERIMENTAL v3 API, we should try to avoid
micro-versions. However, we should soon consider this as a
possibility once things seem to stabilize.<br>
<blockquote cite="mid:D18A0DC5.301D7%25jesse.cook@rackspace.com"
type="cite">
<span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE"
style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0
0 0 5;">
<div>
<div bgcolor="#FFFFFF" text="#000000">
<ol>
<li><br>
</li>
</ol>
<p>Special thanks to Flavio for providing DefCore and TC
perspective as well as initializing this discussion.
Also, thanks to Stuart McLaren and Brian Rosmaita for
giving us thoughtful veteran feedback. The entire team
did a great job at putting all their questions and
concerns amicably on the table and came to a good
understanding of the plan and level of commitment.<br>
</p>
<p>All the best to the Project SearchLight team who have
decided to start ElasticSearch based development for
search functionality in OpenStack as a separate program
and would be porting respective code out of Glance.
Glance team would help co-ordinate this porting effort
in order to avoid destabilizing Images and MetaDefs
code-bases.<br>
</p>
<p>This also means we will re-evaluate some of the
existing spec proposals and most likely not ask people
for radical changes in their approach. This first phase
of the Liberty cycle would focus on seeing the
Experimental Artifacts API through. We will also focus
on stability aspects of the Images (v1 & v2) related
features. The second phase priorities would be decided
at the mid-cycle meet-up (details to come out soon).<br>
</p>
<p>Feel free to ask me questions on IRC or via email.<br>
</p>
<p>Cheers,<br>
Nikhil<br>
</p>
</div>
</div>
</blockquote>
</span>
<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>
Cheers,<br>
Nikhil<br>
</body>
</html>