openstack team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Hmmm, I'm not sure I agree with that.
The "its just a shell script" argument only works when its pretty simple, setting up all these components is not simple. I think you are dumbing down your sysops to much :-)
I think that having a well documented python script can be just as easy to follow, if not easier (since the rest of openstack is in python). In the end the complexity of the system setup should really not rely on a documented piece of code, but should actually follow what the rest of openstack is doing (with a real set of documentation, ie a http://docs.openstack.org/ guide) imho. Having a shell script act as a run book seems pretty wrong in the end.

On 2/6/12 11:06 AM, "Chmouel Boudjnah" <chmouel@xxxxxxxxxxxxx> wrote:

On Mon, Feb 6, 2012 at 7:40 PM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
Interesting, what is the non-developer use case or the one u see as existing?

This is my own personal opinion and not as commiter of devstack.sh,

I found very valuable to  point sysops to devstack.sh with the argument "it's just a shell script" and you'll learn how openstack components are getting plugged together. The argument being is that no matter they are using automated deployment  like puppet/chef rpm/deb reading that well documented shell script would actually make them understand how it works under the hood and how to investigate problems if needed.

This argument can have less weight with that sort of audience when there is a ''proper'' programming language involved which can maybe scared them away.

Chnmouel.