<html><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head><body text="#000000" bgcolor="#FFFFFF">Hooray! Thanks Monty :)<br>
<span>
</span><br>
<blockquote style="border: 0px none;"
cite="mid:598cd923-ab58-5e36-8025-c94ad868ba6c@inaugust.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px"> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a moz-do-not-send="true" href="mailto:mordred@inaugust.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Monty Taylor</a></div> <div
style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:
right;"> <font color="#9FA2A5"><span style="padding-left:6px">April
4, 2017 at 5:47 PM</span></font></div> </div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">Hey all,
<br>
<br>As per our discussion in today's TC meeting, I have made a document
format for reporting versions to the project navigator. I stuck it in
the releases repo:
<br>
<br> <a class="moz-txt-link-freetext" href="https://review.openstack.org/453361">https://review.openstack.org/453361</a>
<br>
<br>Because there was already per-release information there, and the
governance repo did not have that structure.
<br>
<br>I've included pseudo-code and a human explanation of how to get from
a
service's version discovery document to the data in this document, but
also how it can be maintained- which is likely to be easier by hand than
by automation - but who knows, maybe we decide we want to make a
devstack job for each service that runs on tag events that submits a
patch to the releases repo. That sounds like WAY more work than once a
cycle someone adding a few lines of json to a repo - but *shrug*.
<br>
<br>Basing it on the version discovery docs show a few things:
<br>
<br>* "As a user, I want to consume an OpenStack Service's Discovery
Document" is a thing people might want to do and want to do consistently
across services.
<br>
<br>* We're not that far off from being able to do that today.
<br>
<br>* Still, like we are in many places, we're randomly different in a
few
minor ways that do not actually matter but make life harder for our
users.
<br>
<br>Thoughts and feedback more than welcome!
<br>Monty
<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></div>
</blockquote>
<br>
</body></html>