Open Stack

----- Original Message -----
> From: "Joe Topjian" <joe at topjian.net>
> To: "Anne Gentle" <anne at openstack.org>
> Cc: openstack-docs at lists.openstack.org
> Sent: Thursday, February 20, 2014 1:30:43 PM
> Subject: Re: [Openstack-docs] Install Guide
> 
> Hello,
> 
> Seems like the model makes for easier maintenance while also pushing the
> > "learning by doing" aspect of that guide.
> >
> 
> Having just done a hands-on OpenStack workshop today, I agree with this.
> But I do understand that "installation instructions" can be different from
> "training instructions".
> 
> If there is consensus to use a helper tool, I'd like to suggest the use of
> the devstack "iniset" function:
> 
> https://github.com/openstack-dev/devstack/blob/master/functions-common#L81-L116
> 
> By copying and pasting those highlighted lines either directly into the
> user's shell or into a shell script and executing, the user will then have
> a bash function called "iniset" that works the same way that crudini and
> openstack-config work.
> 
> The benefit of iniset is that it will work on all distributions and not
> require a special tool to be installed. I personally use this snippet for
> quick OpenStack installs and testing. The downside of iniset is that it
> requires a user to "enable" it in their current shell session and might
> seem awkward.

What's the upside of using this function over crudini if all the platforms we're building the guide for package the latter? 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).

Thanks,

Steve