<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Hi Travis,</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Looking at the feature, it touches multiple guides, yep. I don’t think we’d need a blueprint, though, as the blueprint already happened in glance. We would expect to track it with a DocImpact flag on the code commits that landed, then a doc bug is registered
for tracking purposes. Blueprints for docs are for major cross-project updates, this seems like a feature addition.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
Here’s what we’d need to ensure we cover the doc needs for this feature:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
- API Reference information: WADL update in the openstack/api-site repository. You may be able to automate the generation of the WADL for a starting point with this tool:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<a href="https://github.com/stackforge/sphinxcontrib-docbookrestapi/blob/master/sphinxcontrib/docbookrestapi/docbook.py">https://github.com/stackforge/sphinxcontrib-docbookrestapi/blob/master/sphinxcontrib/docbookrestapi/docbook.py</a></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
- CLI Reference information: The python-glanceclient additions may be pulled in with our scripted CLI Reference. </div>
<div><font face="Calibri,sans-serif"> - User Guide information: You should document how users tag their resources in the User Guide at </font><a href="http://docs.openstack.org/user-guide/content/">http://docs.openstack.org/user-guide/content/</a><font face="Calibri,sans-serif">.
That’s done by updating the openstack/openstack-manuals repo. </font></div>
<div><font face="Calibri,sans-serif"> - Admin User Guide or Cloud Admin Guide: If it’s an admin task to tag resources, you may want to write an admin section in the Cloud Admin User Guide, also sourced in the openstack/openstack-manuals repo. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Let us know on IRC or this openstack-docs mailing list if you have any further questions; we’re here to help.</font></div>
<div><font face="Calibri,sans-serif">Thanks!</font></div>
<div><font face="Calibri,sans-serif">Anne</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 14px;">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span><Tripp>, Travis S <<a href="mailto:travis.tripp@hp.com">travis.tripp@hp.com</a>><br>
<span style="font-weight:bold">Date: </span>Wednesday, August 20, 2014 at 12:46 PM<br>
<span style="font-weight:bold">To: </span>Anne Gentle <<a href="mailto:anne.gentle@rackspace.com">anne.gentle@rackspace.com</a>><br>
<span style="font-weight:bold">Cc: </span>"Sundar, Murali (<a href="mailto:murali.sundar@intel.com">murali.sundar@intel.com</a>)" <<a href="mailto:murali.sundar@intel.com">murali.sundar@intel.com</a>>, "Sampath, Lakshmi" <<a href="mailto:lakshmi.sampath@hp.com">lakshmi.sampath@hp.com</a>>,
"Okuma, Wayne" <<a href="mailto:wayne.okuma@hp.com">wayne.okuma@hp.com</a>>, "Chylinski, Arkadiusz (<a href="mailto:arkadiusz.chylinski@intel.com">arkadiusz.chylinski@intel.com</a>)" <<a href="mailto:arkadiusz.chylinski@intel.com">arkadiusz.chylinski@intel.com</a>>,
Mark Washenberger <<a href="mailto:mark.washenberger@markwash.net">mark.washenberger@markwash.net</a>>, Arnaud Legendre <<a href="mailto:arnaudleg@gmail.com">arnaudleg@gmail.com</a>><br>
<span style="font-weight:bold">Subject: </span>Documentation for new Glance Metadata Definition Catalog<br>
</div>
<div><br>
</div>
<div xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal">Hello Anne,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We will be landing a major new feature in Glance in Juno. We would like to ensure that we get the OpenStack manual documentation updated with information about it in the appropriate guides. We can contribute documentation, but we are
not sure if you need a single blueprint for each guide or if we can just register a single blueprint and then update all guides. We hope that it isn’t too late for us to contribute updates.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The feature is this one: <a href="https://github.com/openstack/glance-specs/blob/master/specs/juno/metadata-schema-catalog.rst">
https://github.com/openstack/glance-specs/blob/master/specs/juno/metadata-schema-catalog.rst</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thank you!<o:p></o:p></p>
<p class="MsoNormal">Travis<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</span>
</body>
</html>