<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi, <div>I thought in the first place it would make sense to gather all the troubleshooting in the same place, but it turns out that when you are working on a specific operations around networking, referring to the documentation, it makes sense to me to have the troubleshooting around.</div><div>Also for the docs writers, knowing the net. troubleshooting is just under would likely to help producing the content for that part I think.</div><div><br></div><div><br></div><div>Razique</div><div><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Lucida Grande'; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; color: rgb(0, 0, 0); "><span class="Apple-style-span" style="font-family: Helvetica; "><span class="Apple-style-span" style="font-family: Helvetica; "><b style="color: rgb(19, 112, 138); ">Nuage & Co - Razique Mahroua</b></span><span class="Apple-style-span" style="color: rgb(19, 112, 138); font-family: Helvetica; "><b> </b></span><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; 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-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "><font class="Apple-style-span" color="#13708a"><a href="mailto:razique.mahroua@gmail.com">razique.mahroua@gmail.com</a></font></div></span><br class="Apple-interchange-newline"><span></span><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-weight: normal; font-style: normal; "></span><span style="color: rgb(0, 0, 0); font-weight: normal; "></span></span><span><img height="125" width="125" id="e8a58f93-f591-4426-90cf-296162e65574" apple-width="yes" apple-height="yes" src="cid:00E07450-433E-43E6-9005-48B8FD5C669F@la.fabrique"></span>
</span></span></span></div>
<br><div><div>Le 12 juil. 2012 à 19:58, Tom Fifield a écrit :</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>For reference, I'm fine with either, provided it's thought through or even better ... consistent :)<br><br>Assisting troubleshooting is an important role, and an "anemic" chapter is a sad, sad thing :)<br><br>Of course, with our excellent re-use-loving structuring of chapters, it should be possible to even do both if needed or swap in the future ...<br><br>Regards,<br><br>Tom<br><br>(this email is sent at 4am local time, and may contain Australian lingo or not make sense)<br><br>On 13/07/12 01:08, Anne Gentle wrote:<br><blockquote type="cite">I like troubleshooting info very close to the topic it addresses. It's<br></blockquote><blockquote type="cite">also good to pull common errors into one place.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Anne Gentle<br></blockquote><blockquote type="cite">Content Stacker<br></blockquote><blockquote type="cite"><a href="mailto:anne@openstack.org">anne@openstack.org</a> <<a href="mailto:anne@openstack.org">mailto:anne@openstack.org</a>><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">On Jul 12, 2012, at 9:45 AM, Lorin Hochstein <<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a><br></blockquote><blockquote type="cite"><<a href="mailto:lorin@nimbisservices.com">mailto:lorin@nimbisservices.com</a>>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><blockquote type="cite">(crossposting to doc-core in case not everyone there has moved over to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">openstack-docs yet).<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">A question came up on this merge proposal:<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="https://review.openstack.org/9494">https://review.openstack.org/9494</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">In that proposal, I had created a "troubleshooting" section in the<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Networking chapter in the Compute Admin guide. Tom pointed out that we<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">already have a whole Troubleshooting chapter and asked whether it made<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">sense to just keep it in one place or split it across sections. I<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">wanted to bring it up to the list to see what people thought.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">I liked having it by section to have the Networking troubleshooting<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">docs closer to the rest of the networking content. But I can imagine<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">troubleshooting issues where it would deal with issues across multiple<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">sections (e.g., some interaction between scheduling and VMs, for<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">example), in which case that would make it harder to find the right<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">content, since a reader might miss the troubleshooting section that<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">solves their problem.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Also, right now the OpenStack Compute Troubleshooting chapter is<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">pretty anemic<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><<a href="http://docs.openstack.org/essex/openstack-compute/admin/content/common-errors-and-fixes-for-openstack-compute.html">http://docs.openstack.org/essex/openstack-compute/admin/content/common-errors-and-fixes-for-openstack-compute.html</a>>.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Whatever we do, we should probably start populating that with fixes to<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">common issues in better detail.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Take care,<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Lorin<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Lorin Hochstein<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Lead Architect - Cloud Services<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Nimbis Services, Inc.<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><a href="http://www.nimbisservices.com">www.nimbisservices.com</a> <<a href="https://www.nimbisservices.com/">https://www.nimbisservices.com/</a>><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">--<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Mailing list: <a href="https://launchpad.net/~openstack-doc-core">https://launchpad.net/~openstack-doc-core</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Post to : <a href="mailto:openstack-doc-core@lists.launchpad.net">openstack-doc-core@lists.launchpad.net</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><<a href="mailto:openstack-doc-core@lists.launchpad.net">mailto:openstack-doc-core@lists.launchpad.net</a>><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">Unsubscribe : <a href="https://launchpad.net/~openstack-doc-core">https://launchpad.net/~openstack-doc-core</a><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><br><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></div></blockquote></div><br></div></body></html>