<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 19, 2016 at 2:27 AM, Shuu Mutou <span dir="ltr"><<a href="mailto:shu-mutou@rf.jp.nec.com" target="_blank">shu-mutou@rf.jp.nec.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> AFAIK, the API WG adopted Swagger (OpenAPI) as common tool for API<br>
> docs.<br>
> Anne, has not the adoption been changed? Otherwise, do we need to<br>
> maintain much RST files also?<br>
><br>
><br>
><br>
> It does say either/or in the API WG guideline:<br>
> <a href="http://specs.openstack.org/openstack/api-wg/guidelines/api-docs.html" rel="noreferrer" target="_blank">http://specs.openstack.org/<wbr>openstack/api-wg/guidelines/<wbr>api-docs.html</a><br>
<br>
</span>Yes. Also Ken'ichi Omichi said.<br>
<span class=""><br>
<br>
> This isn't about a contest between projects for the best approach. This<br>
> is about serving end-users the best information we can.<br>
<br>
</span>Yes. Correct information is the best information. The Accuracy is more important than web experience. When I was a user (and SIer), the document accuracy had not been kept. So we had to read source code at last. And now, as a developer (mainly UI plugins), I don't want maintain overlapped content several times (API source code, API reference, helps in client, helps in WebUI, etc). So I spend efforts to the spec auto-generation.<br>
<span class=""><br>
<br>
> I'm reporting what I'm seeing from a broader viewpoint than a single project.<br>
> I don't have a solution other than RST/YAML for common navigation, and I'm<br>
> asking you to provide ideas for that integration point.<br>
><br>
> My vision is that even if you choose to publish with OpenAPI, you would<br>
> find a way to make this web experience better. We can do better than this<br>
> scattered approach. I'm asking you to find a way to unify and consider the<br>
> web experience of a consumer of OpenStack services. Can you generate HTML<br>
> that can plug into the openstackdocstheme we are providing as a common tool?<br>
<br>
</span>I need to know about the "common tools". Please, let me know what is difference between HTMLs built by Lars's patch and by common tools? Or can fairy-slipper do that from OpenAPI file?<br>
<br></blockquote><div><br></div><div>Sure, sounds like there's some info missing that I can clarify. </div><div><br></div><div>All HTML built for OpenStack sites are copied via FTP. There's no difference except for the CSS and JavaScript provided by openstackdocstheme and built by os-api-ref. </div><div><br></div><div>Fairy-slipper is no longer being worked on as a common solution to serving all OpenStack API information. It was used for migration purposes.</div><div><br></div><div>Lars's patch could find a way to use the CSS and JS to create a seamless experience for end-users. </div><div><br></div><div>Anne</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<span class="">Shu<br>
<br>
<br>
> -----Original Message-----<br>
> From: Anne Gentle [mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a>]<br>
</span><span class="">> Sent: Wednesday, August 17, 2016 11:55 AM<br>
> To: Mutou Shuu(武藤 周) <<a href="mailto:shu-mutou@rf.jp.nec.com">shu-mutou@rf.jp.nec.com</a>><br>
> Cc: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a>; <a href="mailto:msm@redhat.com">msm@redhat.com</a>; Katou Haruhiko(加<br>
> 藤 治彦) <<a href="mailto:har-katou@ts.jp.nec.com">har-katou@ts.jp.nec.com</a>>; <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a>;<br>
> <a href="mailto:Kenichi.Omichi@necam.com">Kenichi.Omichi@necam.com</a><br>
> Subject: Re: [OpenStack-docs] [openstack-dev] [Magnum] Using common<br>
> tooling for API docs<br>
><br>
><br>
><br>
</span><span class="">> On Tue, Aug 16, 2016 at 1:05 AM, Shuu Mutou <<a href="mailto:shu-mutou@rf.jp.nec.com">shu-mutou@rf.jp.nec.com</a><br>
</span><div><div class="h5">> <mailto:<a href="mailto:shu-mutou@rf.jp.nec.com">shu-mutou@rf.jp.nec.<wbr>com</a>> > wrote:<br>
><br>
><br>
> Hi Anne,<br>
><br>
> AFAIK, the API WG adopted Swagger (OpenAPI) as common tool for API<br>
> docs.<br>
> Anne, has not the adoption been changed? Otherwise, do we need to<br>
> maintain much RST files also?<br>
><br>
><br>
><br>
> It does say either/or in the API WG guideline:<br>
> <a href="http://specs.openstack.org/openstack/api-wg/guidelines/api-docs.html" rel="noreferrer" target="_blank">http://specs.openstack.org/<wbr>openstack/api-wg/guidelines/<wbr>api-docs.html</a><br>
><br>
><br>
><br>
> IMO, for that the reference and the source code doesn't have<br>
> conflict, these should be near each other as possible as follow. And it<br>
> decreases maintainance costs for documents, and increases document<br>
> reliability. So I believe our approach is more ideal.<br>
><br>
><br>
><br>
><br>
> This isn't about a contest between projects for the best approach. This<br>
> is about serving end-users the best information we can.<br>
><br>
><br>
> The Best: the references generated from source code.<br>
><br>
><br>
><br>
> I don't want to argue, but anything generated from the source code suffers<br>
> if the source code changes in a way that reviewers don't catch as a<br>
> backwards-incompatible change you can break your contract.<br>
><br>
><br>
> Better: the references written in docstring.<br>
><br>
> We know some projects abandoned these approach, and then they uses<br>
> RST + YAML.<br>
> But we hope decreasing maintainance cost for the documents. So we<br>
> should not create so much RST files, I think.<br>
><br>
><br>
><br>
><br>
> I think you'll see the evolution of our discussions over the years has<br>
> brought us to this point in time. Yes, there are trade-offs in these<br>
> decisions.<br>
><br>
><br>
><br>
> I'm proceeding auto-generation of swagger spec from magnum source<br>
> code using pecan-swagger [1], and improving pecan-swagger with Michael<br>
> McCune [2].<br>
> These will generate almost Magnum API specs automatically in<br>
> OpenAPI format.<br>
> Also, these approach can be adopted by other APIs that uses pecan<br>
> and WSME.<br>
> Please check this also.<br>
><br>
><br>
><br>
> I ask you to consider the experience of someone consuming the API documents<br>
> OpenStack provides. There are 26 REST API services under an OpenStack<br>
> umbrella. Twelve of them will be included in an unified side-bar navigation<br>
</div></div>> on <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a>> due to<br>
<div><div class="h5">> using Sphinx tooling provided as a common web experience. Six of them don't<br>
> have redirects yet from the "old way" to do API reference docs. Seven of<br>
> them are not collected under a single landing page or common sidebar or<br>
> navigation. Three of them have no API docs published to a website.<br>
><br>
> I'm reporting what I'm seeing from a broader viewpoint than a single project.<br>
> I don't have a solution other than RST/YAML for common navigation, and I'm<br>
> asking you to provide ideas for that integration point.<br>
><br>
> My vision is that even if you choose to publish with OpenAPI, you would<br>
> find a way to make this web experience better. We can do better than this<br>
> scattered approach. I'm asking you to find a way to unify and consider the<br>
> web experience of a consumer of OpenStack services. Can you generate HTML<br>
> that can plug into the openstackdocstheme we are providing as a common tool?<br>
> Thanks,<br>
> Anne<br>
><br>
><br>
><br>
> [1] <a href="https://review.openstack.org/#/c/303235/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/303235/</a><br>
> <<a href="https://review.openstack.org/#/c/303235/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/303235/</a>><br>
> [2] <a href="https://github.com/elmiko/pecan-swagger/" rel="noreferrer" target="_blank">https://github.com/elmiko/<wbr>pecan-swagger/</a><br>
> <<a href="https://github.com/elmiko/pecan-swagger/" rel="noreferrer" target="_blank">https://github.com/elmiko/<wbr>pecan-swagger/</a>><br>
><br>
> Regards,<br>
> Shu<br>
><br>
><br>
> > -----Original Message-----<br>
> > From: Anne Gentle [mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a><br>
> <mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a>> ]<br>
> > Sent: Monday, August 15, 2016 11:00 AM<br>
> > To: Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a><br>
</div></div>> <mailto:<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>> ><br>
> > Cc: <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.<wbr>org</a><br>
> <mailto:<a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.<wbr>openstack.org</a>> ; <a href="http://enstack.org" rel="noreferrer" target="_blank">enstack.org</a><br>
> <<a href="http://enstack.org" rel="noreferrer" target="_blank">http://enstack.org</a>><br>
> > <<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a><br>
> <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a>> ><br>
<div><div class="h5">> > Subject: Re: [openstack-dev] [OpenStack-docs] [Magnum] Using<br>
> common<br>
> > tooling for API docs<br>
> ><br>
> > Hi Hongbin,<br>
> ><br>
> > Thanks for asking. I'd like for teams to look for ways to innovate<br>
> and<br>
> > integrate with the navigation as a good entry point for OpenAPI<br>
> to become<br>
> > a standard for OpenStack to use. That said, we have to move forward<br>
> and<br>
> > make progress.<br>
> ><br>
> > Is Lars or anyone on the Magnum team interested in the web<br>
> development work<br>
> > to integrate with the sidebar? See the work at<br>
> > <a href="https://review.openstack.org/#/c/329508" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/329508</a><br>
> <<a href="https://review.openstack.org/#/c/329508" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/329508</a>> and my comments on<br>
> > <a href="https://review.openstack.org/#/c/351800/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/351800/</a><br>
> <<a href="https://review.openstack.org/#/c/351800/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/351800/</a>> saying that I would like<br>
> teams<br>
> > to integrate first to provide the best web experience for people<br>
> consuming<br>
> > the docs.<br>
> ><br>
> > Anne<br>
> ><br>
> > On Fri, Aug 12, 2016 at 4:43 PM, Hongbin Lu <<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a><br>
> <mailto:<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>><br>
</div></div>> > <mailto:<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a> <mailto:<a href="mailto:hongbin.lu@huawei.com">hongbin.lu@huawei.com</a>> ><br>
<div><div class="h5">> > wrote:<br>
> ><br>
> ><br>
> > Hi team,<br>
> ><br>
> ><br>
> ><br>
> > As mentioned in the email below, Magnum are not using common<br>
> tooling<br>
> > for generating API docs, so we are excluded from the common<br>
> navigation of<br>
> > OpenStack API. I think we need to prioritize the work to fix it.<br>
> BTW, I<br>
> > notice there is a WIP patch [1] for generating API docs by using<br>
> Swagger.<br>
> > However, I am not sure if Swagger belongs to “common tooling”<br>
> (docs team,<br>
> > please confirm).<br>
> ><br>
> ><br>
> ><br>
> > [1] <a href="https://review.openstack.org/#/c/317368/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/317368/</a><br>
> <<a href="https://review.openstack.org/#/c/317368/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/317368/</a>><br>
> > <<a href="https://review.openstack.org/#/c/317368/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/317368/</a><br>
> <<a href="https://review.openstack.org/#/c/317368/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/317368/</a>> ><br>
> ><br>
> ><br>
> ><br>
> > Best regards,<br>
> ><br>
> > Hongbin<br>
> ><br>
> ><br>
> ><br>
> > From: Anne Gentle [mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a><br>
> <mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a>><br>
> > <mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a><br>
> <mailto:<a href="mailto:annegentle@justwriteclick.com">annegentle@<wbr>justwriteclick.com</a>> > ]<br>
> > Sent: August-10-16 3:50 PM<br>
> > To: OpenStack Development Mailing List;<br>
> > <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a><br>
> <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a>><br>
</div></div>> > <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a><br>
<span class="">> <mailto:<a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.<wbr>openstack.org</a>> ><br>
> > Subject: [openstack-dev] [api] [doc] API status report<br>
> ><br>
> ><br>
> ><br>
> > Hi all,<br>
> ><br>
> > I wanted to report on status and answer any questions you<br>
> all have<br>
> > about the API reference and guide publishing process.<br>
> ><br>
> ><br>
> ><br>
> > The expectation is that we provide all OpenStack API<br>
> information<br>
> > on <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a>><br>
</span>> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a>> > . In<br>
<div><div class="h5">> order to<br>
> > meet that goal, it's simplest for now to have all projects use<br>
> the<br>
> > RST+YAML+openstackdocstheme+<wbr>os-api-ref extension tooling so<br>
> that users<br>
> > see available OpenStack APIs in a sidebar navigation drop-down<br>
> list.<br>
> ><br>
> ><br>
> ><br>
> > --Migration--<br>
> ><br>
> > The current status for migration is that all WADL content<br>
> is<br>
> > migrated except for trove. There is a patch in progress and I'm<br>
> in contact<br>
> > with the team to assist in any way.<br>
> > <a href="https://review.openstack.org/#/c/316381/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/316381/</a><br>
> <<a href="https://review.openstack.org/#/c/316381/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/316381/</a>><br>
> > <<a href="https://review.openstack.org/#/c/316381/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/316381/</a><br>
> <<a href="https://review.openstack.org/#/c/316381/" rel="noreferrer" target="_blank">https://review.openstack.org/<wbr>#/c/316381/</a>> ><br>
> ><br>
> ><br>
> ><br>
> > --Theme, extension, release requirements--<br>
> ><br>
> > The current status for the theme, navigation, and Sphinx<br>
> extension<br>
> > tooling is contained in the latest post from Graham proposing<br>
> a solution<br>
> > for the release number switchover and offers to help teams as<br>
> needed:<br>
> ><br>
> <a href="http://lists.openstack.org/pipermail/openstack-dev/2016-August/101112" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/2016-<wbr>August/101112</a><br>
</div></div>> <<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-August/101112" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/2016-<wbr>August/101112</a><br>
> > .<br>
> > html<br>
> ><br>
> <<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-August/101112" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/2016-<wbr>August/101112</a><br>
<div><div class="h5">> <<a href="http://lists.openstack.org/pipermail/openstack-dev/2016-August/101112" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>pipermail/openstack-dev/2016-<wbr>August/101112</a><br>
> ><br>
> > .html> I hope to meet the requirements deadline to get those<br>
> changes landed.<br>
><br>
> > Requirements freeze is Aug 29.<br>
> ><br>
> ><br>
> ><br>
> > --Project coverage--<br>
> ><br>
> > The current status for project coverage is that these<br>
> projects are<br>
> > now using the RST+YAML in-tree workflow and tools and publishing<br>
> to<br>
> > <a href="http://developer.openstack.org/api-ref/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/</a><br>
> <<a href="http://developer.openstack.org/api-ref/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/</a><br>
> <<a href="http://developer.openstack.org/api-ref/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/</a>> > <servicename> so they will be<br>
> > included in the upcoming API navigation sidebar intended to span<br>
> all<br>
> > OpenStack APIs:<br>
> ><br>
> ><br>
> ><br>
> > designate <a href="http://developer.openstack.org/api-ref/dns/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/dns/</a><br>
> <<a href="http://developer.openstack.org/api-ref/dns/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/dns/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/dns/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/dns/</a><br>
> <<a href="http://developer.openstack.org/api-ref/dns/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/dns/</a>> ><br>
> ><br>
> > glance <a href="http://developer.openstack.org/api-ref/image/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/image/</a><br>
> <<a href="http://developer.openstack.org/api-ref/image/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/image/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/image/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/image/</a><br>
> <<a href="http://developer.openstack.org/api-ref/image/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/image/</a>> ><br>
> > heat<br>
> <a href="http://developer.openstack.org/api-ref/orchestration/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/orchestration/</a><br>
> <<a href="http://developer.openstack.org/api-ref/orchestration/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/orchestration/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/orchestration/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/orchestration/</a><br>
> <<a href="http://developer.openstack.org/api-ref/orchestration/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/orchestration/</a>> ><br>
> > ironic<br>
> <a href="http://developer.openstack.org/api-ref/baremetal/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/baremetal/</a><br>
> <<a href="http://developer.openstack.org/api-ref/baremetal/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/baremetal/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/baremetal/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/baremetal/</a><br>
> <<a href="http://developer.openstack.org/api-ref/baremetal/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/baremetal/</a>> ><br>
> > keystone<br>
> <a href="http://developer.openstack.org/api-ref/identity/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/identity/</a><br>
> <<a href="http://developer.openstack.org/api-ref/identity/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/identity/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/identity/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/identity/</a><br>
> <<a href="http://developer.openstack.org/api-ref/identity/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/identity/</a>> ><br>
> > manila<br>
> > <a href="http://developer.openstack.org/api-ref/shared-file-systems/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/shared-file-<wbr>systems/</a><br>
> <<a href="http://developer.openstack.org/api-ref/shared-file-systems/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/shared-file-<wbr>systems/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/shared-file-systems/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/shared-file-<wbr>systems/</a><br>
> <<a href="http://developer.openstack.org/api-ref/shared-file-systems/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/shared-file-<wbr>systems/</a>> ><br>
> > neutron-lib<br>
> <a href="http://developer.openstack.org/api-ref/networking/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/networking/</a><br>
> <<a href="http://developer.openstack.org/api-ref/networking/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/networking/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/networking/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/networking/</a><br>
> <<a href="http://developer.openstack.org/api-ref/networking/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/networking/</a>> ><br>
> > nova <a href="http://developer.openstack.org/api-ref/compute/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/compute/</a><br>
> <<a href="http://developer.openstack.org/api-ref/compute/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/compute/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/compute/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/compute/</a><br>
> <<a href="http://developer.openstack.org/api-ref/compute/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/compute/</a>> ><br>
> > sahara<br>
> <a href="http://developer.openstack.org/api-ref/data-processing/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/data-processing/</a><br>
> <<a href="http://developer.openstack.org/api-ref/data-processing/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/data-processing/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/data-processing/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/data-processing/</a><br>
> <<a href="http://developer.openstack.org/api-ref/data-processing/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/data-processing/</a>> ><br>
> > senlin<br>
> <a href="http://developer.openstack.org/api-ref/clustering/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/clustering/</a><br>
> <<a href="http://developer.openstack.org/api-ref/clustering/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/clustering/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/clustering/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/clustering/</a><br>
> <<a href="http://developer.openstack.org/api-ref/clustering/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/clustering/</a>> ><br>
> > swift<br>
> <a href="http://developer.openstack.org/api-ref/object-storage/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/object-storage/</a><br>
> <<a href="http://developer.openstack.org/api-ref/object-storage/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/object-storage/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/object-storage/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/object-storage/</a><br>
> <<a href="http://developer.openstack.org/api-ref/object-storage/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/object-storage/</a>> ><br>
> > zaqar <a href="http://developer.openstack.org/api-ref/messaging/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/messaging/</a><br>
> <<a href="http://developer.openstack.org/api-ref/messaging/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/messaging/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/messaging/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/messaging/</a><br>
> <<a href="http://developer.openstack.org/api-ref/messaging/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/messaging/</a>> ><br>
> ><br>
> ><br>
> ><br>
> > These projects are using the in-tree workflow and common<br>
> tools,<br>
> > but do not have a publish job in project-config in the<br>
> > jenkins/jobs/projects.yaml file.<br>
> ><br>
> ><br>
> ><br>
> > ceilometer<br>
> ><br>
> ><br>
> ><br>
> > --Projects not using common tooling--<br>
> ><br>
> > These projects have API docs but are not yet using the<br>
> common tooling,<br>
> > as far as I can tell. Because of the user experience, I'm making<br>
> a judgement<br>
> > call that these cannot be included in the common navigation. I<br>
> have patched<br>
> > the projects.yaml file in the governance repo with the URLs I<br>
> could<br>
> > screen-scrape, but if I'm incorrect please do patch the<br>
> projects.yaml in<br>
> > the governance repo.<br>
> ><br>
> ><br>
> ><br>
> > astara<br>
> ><br>
> > cloudkitty<br>
> ><br>
> > congress<br>
> ><br>
> > magnum<br>
> ><br>
> > mistral<br>
> ><br>
> > monasca<br>
> ><br>
> > solum<br>
> ><br>
> > tacker<br>
> ><br>
> > trove<br>
> ><br>
> ><br>
> ><br>
> > Please reach out if you have questions or need assistance<br>
> getting<br>
> > started with the new common tooling, documented here:<br>
> > <a href="http://docs.openstack.org/contributor-guide/api-guides.html" rel="noreferrer" target="_blank">http://docs.openstack.org/<wbr>contributor-guide/api-guides.<wbr>html</a><br>
> <<a href="http://docs.openstack.org/contributor-guide/api-guides.html" rel="noreferrer" target="_blank">http://docs.openstack.org/<wbr>contributor-guide/api-guides.<wbr>html</a>><br>
><br>
> > <<a href="http://docs.openstack.org/contributor-guide/api-guides.html" rel="noreferrer" target="_blank">http://docs.openstack.org/<wbr>contributor-guide/api-guides.<wbr>html</a><br>
> <<a href="http://docs.openstack.org/contributor-guide/api-guides.html" rel="noreferrer" target="_blank">http://docs.openstack.org/<wbr>contributor-guide/api-guides.<wbr>html</a>> > .<br>
> ><br>
> ><br>
> ><br>
> > For searchlight, looking at<br>
> > <a href="http://developer.openstack.org/api-ref/search/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/search/</a><br>
> <<a href="http://developer.openstack.org/api-ref/search/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/search/</a>><br>
> > <<a href="http://developer.openstack.org/api-ref/search/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/search/</a><br>
> <<a href="http://developer.openstack.org/api-ref/search/" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org/api-ref/search/</a>> > they have the build<br>
> > job, but the info is not complete yet.<br>
> ><br>
> ><br>
> ><br>
> > One additional project I'm not sure what to do with is<br>
> > networking-nfc, since I'm not sure it is considered a neutron<br>
> API. Can I<br>
> > get help to sort that question out?<br>
> ><br>
> ><br>
> > --Redirects from old pages--<br>
> ><br>
> > We have been adding .htaccess redirects from the old<br>
> > api-ref-servicename.html on <a href="http://developer.openstack.org" rel="noreferrer" target="_blank">developer.openstack.org</a><br>
> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a>><br>
</div></div>> > <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a><br>
<div><div class="h5">> <<a href="http://developer.openstack.org" rel="noreferrer" target="_blank">http://developer.openstack.<wbr>org</a>> > as teams are comfortable with the<br>
> > accuracy of information and build stability. Please help out by<br>
> patching<br>
> > the api-site repository's .htaccess file when you are ready to<br>
> redirect.<br>
> > These projects could be ready for redirects but do not have them:<br>
> ><br>
> ><br>
> ><br>
> > designate<br>
> ><br>
> > glance<br>
> ><br>
> > heat<br>
> ><br>
> > sahara<br>
> ><br>
> > senlin<br>
> ><br>
> > swift<br>
> ><br>
> ><br>
> ><br>
> > I'm available for questions so please reach out as needed.<br>
> I hope<br>
> > this covers our current status.<br>
> ><br>
> ><br>
> ><br>
> > A million thank yous to everyone who got us this far! Great<br>
> teamwork,<br>
> > great docs work, great UI work, and great API work everyone.<br>
> ><br>
> > Anne<br>
> ><br>
> ><br>
> ><br>
> > --<br>
> ><br>
> > Anne Gentle<br>
> ><br>
> > <a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > OpenStack-docs mailing list<br>
> > <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a><br>
> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a>><br>
</div></div>> > <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a><br>
<div class="HOEnZb"><div class="h5">> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a>> ><br>
> ><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-</a><br>
> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-</a>><br>
> > docs<br>
> ><br>
> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-docs</a><br>
> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-docs</a>> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> ><br>
> > Anne Gentle<br>
> > <a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> OpenStack-docs mailing list<br>
> <a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a><br>
> <mailto:<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.<wbr>openstack.org</a>><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-</a><br>
> docs<br>
> <<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-docs</a>><br>
><br>
><br>
><br>
><br>
><br>
> --<br>
><br>
> Anne Gentle<br>
> <a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">www.justwriteclick.com</a> <<a href="http://www.justwriteclick.com" rel="noreferrer" target="_blank">http://www.justwriteclick.com</a><wbr>><br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Anne Gentle</div><div><a href="http://www.justwriteclick.com" style="font-size:12.8px" target="_blank">www.justwriteclick.com</a><br></div></div></div></div></div>
</div></div>