Open Stack

On Thu, Feb 20, 2014 at 1:03 PM, phil hopkins <phil.hopkins at rackspace.com>wrote:

>  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.
>
>
Here's my current line of thought:

- 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.

- The "official" install guide should offer a few different ideas for
installers who want to know what setups still give them "OpenStack" such as:
 ---Compute with nova-network
 ---Compute with neutron
 ---Object Storage, Identity only

- 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.

With these goals in mind is it advantageous to:
- unify on one AMQP broker?
- analyze the maintenance savings by doing a trial non-openstack-config
rewrite on one chapter?

Hope this is helpful -- thanks all for the questions and discussion.

Anne


>  Phil
>
>
> On 02/20/2014 12:53 PM, Joe Topjian wrote:
>
> Hi Steve,
>
>  What's the upside of using this function over crudini if all the
>> platforms we're building the guide for package the latter?
>
>
>  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.
>
>
>> 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).
>>
>
>  Fair, but it can be simplified by just doing a "wget" or something
> similar.
>
>  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.
>
>  Joe
>
>
> _______________________________________________
> Openstack-docs mailing listOpenstack-docs at lists.openstack.orghttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
>
> _______________________________________________
> Openstack-docs mailing list
> Openstack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20140221/53ee869f/attachment.html>