<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Tom (And list). What we have been finding is that the Dev Docs are a rich source for conceptual discussions of components to be installed. A specific example is the messaging service used in Nova. In the Associate guide, there is an installation task of installing and configuring RabbitMQ. Directly before that configuration task there is a conceptual task of understanding (at a high level) the messaging architecture, and the components that enable its operation. <div><br></div><div>The RPC section of the Nova developer documentation (found here - <a href="http://docs.openstack.org/developer/nova/devref/rpc.html">http://docs.openstack.org/developer/nova/devref/rpc.html</a>) has a very detailed deep dive into this topic. I believe the first section "AMQP and Nova" is appropriate to integrate as the conceptual item for this installation task. In more advanced courses, subsequent sections such as "Broker Load" and "RabbitMQ Gotchas" will be appropriate to include. </div><div><br></div><div>I'd like to also address the subject of improving manuals content within training-manuals by copying vs including external sources. Improving the training-manuals content is an important goal. I however have been a bit of a stickler within Training-Guides on content duplication. I personally don't believe that it is sustainable to maintain two completely separate sources of documentation in a six month release cycle with major changes in structure each release while maintaining forward progress on the advanced courses. I however may be completely off base on this belief and welcome comments and external perspective. </div><div><br></div><div>With that being said, in a perfect wold the Developer Docs would all be in XML that could be included into openstack-manuals content natively. The world we live in has developer content written in ReStructured Text, which is extremely easy for people to update and I doubt will change (or should be changed). The next best thing for me would be for Jenkins to create docbooks XML content on build, or a similar XML content that could be easily included at a granular level into the larger documentation base. </div><div><br></div><div><br></div><div>Regards,</div><div><div apple-content-edited="true"><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; ">Colin</p><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; "><b style="font-family: Calibri, sans-serif; font-size: 15px; "><span style="font-size: 12pt; color: navy; font-family: Arial, sans-serif; ">Colin McNamara</span></b><br></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; "><span style="font-family: Calibri, sans-serif; font-size: 15px; "><span style="font-size: 12pt; color: navy; font-family: Arial, sans-serif; ">People | Process | Technology</span></span></div><div><font color="#000080" face="Arial, sans-serif"><span style="font-size: 16px; ">--------------------------------------------</span></font></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; "><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><b><span style="font-size: 10pt; color: rgb(31, 73, 125); font-family: Arial, sans-serif; ">Mobile</span></b><span style="font-size: 10pt; color: rgb(31, 73, 125); font-family: Arial, sans-serif; ">: <span class="Apple-tab-span" style="white-space: pre; "> </span>858-208-8105</span></div><div style="margin: 0in 0in 0.0001pt; "><font color="#1f497d" face="Arial, sans-serif"><span style="font-size: 13px; "><b>Twitter:<span class="Apple-tab-span" style="white-space: pre; "> </span></b></span></font><a href="http://www.twitter.com/colinmcnamara">@colinmcnamara</a></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><span style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; "><b>Linkedin</b>:<span class="Apple-tab-span" style="white-space: pre; "> </span></span><a href="http://www.linkedin.com/colinmcnamara" style="font-family: Arial, sans-serif; font-size: 13px; ">www.</a><a href="http://www.linkedin.com/colinmcnamara" style="font-family: Arial, sans-serif; font-size: 13px; ">linkedin.com/colinmcnamara</a></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><b style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; ">Blog</b><span style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; ">:<span class="Apple-tab-span" style="white-space: pre; "> </span></span><a href="http://www.colinmcnamara.com/" style="font-family: Arial, sans-serif; font-size: 13px; ">www.colinmcnamara.com</a></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><b style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; ">Email</b><span style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; ">:</span><span class="Apple-tab-span" style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; white-space: pre; "> </span><a href="mailto://colin@2cups.com">colin@2cups.com</a><span class="Apple-tab-span" style="color: rgb(31, 73, 125); font-family: Arial, sans-serif; font-size: 13px; white-space: pre; "> </span></div><div style="font-family: Calibri, sans-serif; font-size: 11pt; margin: 0in 0in 0.0001pt; "><br></div></div></div></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br><div><div>On Oct 9, 2013, at 9:02 PM, Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Oh?<br><br>Can you point out some of the good sections for associates in the devref you're looking at? We should also work on improving the manuals for you if there's stuff missing. In theory the devref is only for dev stuff, which is why I was asking - I didn't think you were up to writing the developer training yet :D<br><br>Regards,<br><br><br>Tom<br><br>On 10/10/13 15:00, Sean Roberts wrote:<br><blockquote type="cite">Good question. The immediate need is for the associate guide that we are<br>working on right now.<br><br><br>Sean Roberts<br>Infrastructure Strategy<br><a href="mailto:seanrob@yahoo-inc.com">seanrob@yahoo-inc.com</a> <<a href="mailto:seanrob@yahoo-inc.com">mailto:seanrob@yahoo-inc.com</a>> (925) 980-4729<br><br>On Oct 9, 2013, at 7:54 PM, Tom Fifield <<a href="mailto:tom@openstack.org">tom@openstack.org</a><br><<a href="mailto:tom@openstack.org">mailto:tom@openstack.org</a>>><br> wrote:<br><br><blockquote type="cite">Hi Sean,<br><br>Just wondering - is this mainly for the "Developer Training Guide" ?<br><br>Regards,<br><br><br>Tom<br><br>On 10/10/13 11:48, Sean Roberts wrote:<br><blockquote type="cite">Sounds great. I'll post my latest code to my repo and share.<br><br>~sean<br><br><blockquote type="cite">On Oct 9, 2013, at 17:00, "David Cramer" <<a href="mailto:david.cramer@rackspace.com">david.cramer@rackspace.com</a><br><<a href="mailto:david.cramer@rackspace.com">mailto:david.cramer@rackspace.com</a>>> wrote:<br><br>Hi Sean,<br>xslt would be well-suited to cleaning up the output of pandoc and<br>converting it to DocBook 5.x. This could be invoked from your python<br>script:<br><br><a href="https://svn.code.sf.net/p/docbook/code/trunk/docbook/relaxng/tools/db4-upgrade.xsl">https://svn.code.sf.net/p/docbook/code/trunk/docbook/relaxng/tools/db4-upgrade.xsl</a><br><br>If you have other cleanup to perform, we could add the necessary logic<br>to the db4-upgrade.xsl.<br><br>I'll be happy to help with the xslt and I think the result would be more<br>robust.<br><br>Regards,<br>David<br><br><blockquote type="cite">On 10/09/2013 06:37 PM, Sean Roberts wrote:<br>The training-manuals team is proposing a blueprint to implement rst to<br>xml conversion script. This code is used to convert devref project rst<br>documentation into xml that the openstack manuals project can use. The<br>Training-manuals sub-project will use xi:include statements so the<br>converted xml becomes part of the training guides during build. The<br>conversion script will live in the ./training-guide/sources sub<br>directory of the training-manuals sub-project. The converted xml gets<br>placed within ./training-guide/sources/<project> directories. The<br>conversion script will be run at the same time as when the<br>openstack-manuals repo updates are pulled. This will allow the training<br>manuals team to find xml content and include it with the training<br>guides. If the source RST has a bug, then the RST source will be<br>patched, and the XML will get the bug fix through the next run of the<br>conversion script.<br><br>Blueprint<br>here<br>https://blueprints.launchpad.net/openstack-manuals/+spec/rst-xml-conversion<br>Wiki details<br>here<br>https://wiki.openstack.org/wiki/Training-manuals#RST-XML_Conversion_automation<br><br>Sean Roberts<br>Infrastructure Strategy<br>seanrob@yahoo-inc.com <mailto:seanrob@yahoo-inc.com> (925) 980-4729<br><br><br><br>_______________________________________________<br>Openstack-docs mailing list<br>Openstack-docs@lists.openstack.org<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br></blockquote><br></blockquote><br>_______________________________________________<br>Openstack-docs mailing list<br><a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br><mailto:Openstack-docs@lists.openstack.org><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br><br></blockquote><br><br>_______________________________________________<br>Openstack-docs mailing list<br><a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br><mailto:Openstack-docs@lists.openstack.org><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br></blockquote><br></blockquote><br><br>_______________________________________________<br>Openstack-docs mailing list<br><a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs<br></blockquote></div><br></div></body></html>