<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Mon, Feb 11, 2013 at 2:38 AM, Atul Jha <span dir="ltr"><<a href="mailto:Atul.Jha@csscorp.com" target="_blank">Atul.Jha@csscorp.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Lorin,<br>
<br>
<a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_installing-openstack-compute.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_installing-openstack-compute.html</a> </blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-openstack-compute-basics.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/configuring-openstack-compute-basics.html</a><br>
<br></blockquote><div><br></div><div><div>I didn't even realize there was a chapter on "Installing OpenStack Compute" in the admin guide. Yeah, I'd support migrating this content out of the admin guide and into the install guides.</div>
</div><div><br></div><div style>Take care,</div><div style><br></div><div style>Lorin</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
________________________________________<br>
<br>
From: Lorin Hochstein [<a href="mailto:lorin@nimbisservices.com">lorin@nimbisservices.com</a>]<br>
Sent: Monday, February 11, 2013 3:38 AM<br>
To: Atul Jha<br>
Cc: <a href="mailto:openstack-docs@lists.openstack.org">openstack-docs@lists.openstack.org</a><br>
Subject: Re: [Openstack-docs] Restructuring OpenStack-doc for Grizzly<br>
<br>
Hi Atul:<br>
<div><div class="h5"><br>
<br>
On Wed, Feb 6, 2013 at 2:59 AM, Atul Jha <<a href="mailto:Atul.Jha@csscorp.com">Atul.Jha@csscorp.com</a><mailto:<a href="mailto:Atul.Jha@csscorp.com">Atul.Jha@csscorp.com</a>>> wrote:<br>
Hi All,<br>
<br>
I had a suggestion and wanted to put forward.<br>
<br>
Currently our complete doc structure looks like this<br>
<br>
Installing OS<br>
-- Contains install information on Ubuntu and Fedora<br>
Running OS<br>
-- Contains concepts about OS components and install steps as well for Debian/Suse/Ubunu/Fedora to some extent<br>
Developing OS<br>
OS CLI<br>
OS API<br>
Glossary<br>
<br>
<br>
Will it be good idea to restructure Running OS and Installing OS this way<br>
<br>
Installing OS<br>
-- On Ubuntu<br>
-- Basic<br>
-- Advanced<br>
<br>
-- On Redhat/Centos/Fedora<br>
-- Basic<br>
-- Advanced<br>
-- On Other OS<br>
-- Basic<br>
-- Advance<br>
<br>
Too an extent its already existing, my real concern is with the "Running OS" part which has overlapping contents as in install instructions.<br>
<br>
Keeping Nova/Swift/Quantum guide with conf files and basic concepts behind it and updating it on regular basis will be much better. Lets take compute admin guide for example. I find it like having too much data and to an extent replication of our Install OS components in it.<br>
<br>
Compute administration guide<br>
-- Concept of nova<br>
-- Architecture<br>
-- Hypervisor based config change<br>
-- Available config flags<br>
<br>
<br>
What do you guys think?<br>
<br>
Can you give an example of some content that currently is in the compute admin guide that you think shouldn't be there because of the overlap with the installation manuals?<br>
<br>
I'm not opposed to a refactor on principle, but I also worry about users needing to jump around across many different manuals, because the current task they are trying to perform cuts across multiple doc guides. I think some content overlap might be unavoidable. If you could provide some specific examples about content that you recommend be removed from the admin guide, it would help me understand this better.<br>
<br>
Take care,<br>
<br>
Lorin<br>
<br>
--<br>
Lorin Hochstein<br>
Lead Architect - Cloud Services<br>
Nimbis Services, Inc.<br>
</div></div><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a><<a href="http://www.nimbisservices.com" target="_blank">http://www.nimbisservices.com</a>><br>
<a href="http://www.csscorp.com/common/email-disclaimer.php" target="_blank">http://www.csscorp.com/common/email-disclaimer.php</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Lorin Hochstein<br><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="http://www.nimbisservices.com" target="_blank">www.nimbisservices.com</a></div>
</div>
</div></div>