<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 20, 2014 at 1:03 PM, phil hopkins <span dir="ltr"><<a href="mailto:phil.hopkins@rackspace.com" target="_blank">phil.hopkins@rackspace.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">
<div bgcolor="#FFFFFF" text="#000000">
I believe we are missing a key point, which is what is the purpose
of the install guide? If it is just to help folks quickly get
OpenStack or are we also trying to teach them about OpenStack as
they install it to help them become proficient and quickly as
possible? If we decide on the purpose of the book then many of these
other detail will resolve themselves.<span class=""><font color="#888888"><br>
<br></font></span></div></blockquote><div><br></div><div>Here's my current line of thought:</div><div><br></div><div>- The "official" install guide should offer instruction to anyone wanting to set up OpenStack in a non-DevStack environment with a single happy path, even if it's simple.</div>
<div><br></div><div>- The "official" install guide should offer a few different ideas for installers who want to know what setups still give them "OpenStack" such as:</div><div> ---Compute with nova-network</div>
<div> ---Compute with neutron</div><div> ---Object Storage, Identity only <br></div><div><br></div><div>- The "official" install guide should provide enough information for someone to learn from to then create or use a more repeatable method of install/deploy such as Chef, Juju, or Puppet and be able to read or write those recipes with a good understanding of why OpenStack services go together the way they do.</div>
<div><br></div><div>With these goals in mind is it advantageous to:</div><div>- unify on one AMQP broker?</div><div>- analyze the maintenance savings by doing a trial non-openstack-config rewrite on one chapter?</div><div>
<br></div><div><div>Hope this is helpful -- thanks all for the questions and discussion. </div></div><div><br></div><div>Anne</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">
<div bgcolor="#FFFFFF" text="#000000"><span class=""><font color="#888888">
Phil</font></span><div><div class="h5"><br>
<br>
<div>On 02/20/2014 12:53 PM, Joe Topjian
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">Hi Steve,
<div><br>
<div class="gmail_extra">
<div class="gmail_quote">
<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">What's
the upside of using this function over crudini if all
the platforms we're building the guide for package the
latter?</blockquote>
<div><br>
</div>
<div>Admittedly, the only upside is that crudini is not
guaranteed to be easily available on all distributions.
For Ubuntu, it's only available in Ubuntu 14.04, for
example. </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"> I
think awkward is a bit of an understatement here and
suggesting that this isn't a "special tool" that also
needs to be installed/enabled is perhaps stretching
things - in either case it's something the user is going
to have to handle in the prerequisites and ensure they
repeat on each node (and make sure it takes effect for
each session for iniset).<br>
</blockquote>
<div><br>
</div>
<div>Fair, but it can be simplified by just doing a "wget"
or something similar.</div>
<div><br>
</div>
<div>The upside of iniset is that it's portable and is
known to work on all distributions. As soon as a
distribution lacks support, or drops support, for
crudini, the installation instructions are now broke.</div>
<div><br>
</div>
<div>Joe</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><div class=""><pre>_______________________________________________
Openstack-docs mailing list
<a href="mailto:Openstack-docs@lists.openstack.org" target="_blank">Openstack-docs@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a>
</pre>
</div></blockquote>
<br>
</div>
<br>_______________________________________________<br>
Openstack-docs mailing list<br>
<a href="mailto:Openstack-docs@lists.openstack.org">Openstack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br></blockquote></div></div></div>