openstack team mailing list archive
Mailing list archive
Re: [DEVSTACK] officialize it!
Our team had discussions on python vs. bash at the beginning of devstack.
If we go with python it would be nice to do something similar to
python-novaclient where setting DEBUG lets users see CURL commands
that you can execute to do the same thing.
That said, we are focused on essex until the design summit... We look
forward to reviewing ideas about devstack after essex (including
installing atlas/reddwarf/other-service-here & python - our team uses
fabric to do multi-node devstack deploys and so python would be nice
On Mon, Feb 6, 2012 at 3:40 PM, Monty Taylor <mordred@xxxxxxxxxxxx> wrote:
> On 02/06/2012 10:37 AM, Jesse Andrews wrote:
>> I think having a session on devstack at the summit would be valuable.
>> I'm still torn on it being python vs. bash because I see
>> non-developers using it all the time because they can take snippets of
>> the shell script and use it.
> I'm similarly torn. One of the things Jesse and I have spoke of several
> times is in making sure that we don't let the scope of devstack grow to
> the point where we re-invent chef or puppet or juju. It's not really
> intended as a tool for doing "real" deployments - it's intended to make
> developer's lives easier, and to serve as an easy to follow living
> document of what a base working openstack installation looks like.
> My concern is that if we go and get all software developer on it and
> make it python and "right" and "better" - that it will cease to be an
> easy to follow annotated installation and start to become a
> custom-written multi-purpose deployment software.
>> On Mon, Feb 6, 2012 at 10:29 AM, Joshua Harlow <harlowja@xxxxxxxxxxxxx> wrote:
>>> Hi all,
>>> Over the weekend I was thinking (I know a first, haha).
>>> I was wondering if the community could elevate devstack to a "official"
>>> openstack project, instead of being a "unofficial project". Since it seems
>>> like pretty much every developer (and even CI) is either depending on the
>>> shell script or the python script, so the unofficial wording seems
>>> incorrect. Hopefully we can have that happen and have this "official"
>>> project focus on just a developer setup script (imho the python version,
>>> since it fits in with the whole python model every other component is using
>>> and allows for features the shell script is not doing, multi-distro support,
>>> starting, stopping, uninstalling, object oriented design, to name a few....)
>>> of the openstack components (and not dive into the scripts that are showing
>>> up), ie leave that to 3rd party websites.
>>> What does everyone think?
>>> Maybe this can happen after essex?
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help : https://help.launchpad.net/ListHelp
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp