My goals were/are/(may continue to be, haha) the following:
1. Add in enough abstraction so that you can look at how each component is
installed/uninstalled/started/stopped by looking at a single file (maybe 2
files)
2. Have the ability to start/stop in different manners (not always screen)
3. Have the ability to have pkg/pip installation (and definition separate
from the main code, already starting to be done), in more than 1 distro.
* This allows others to easily know what versions of packages work for a
given openstack release for more than one distro (yes that's right, more than
ubuntu)
4. Increase the level of documentation (probably not going to be in the end,
inline like what is in devstack, since that just doesn't seem maintainable in
the long-term)
* This may mean having documentation created similar to nova, glance, as
a separate documentation document/page....
Still be simple "enough" to run and use so that the non-python dev can install
from trunk without having to understand what is going on.
-Josh
On 1/17/12 11:01 AM, "Joshua Harlow" <[email protected]> wrote:
Thx,
Yes we haven't been 100% doing the style stuff yet (which is ok I think for
now).
My idea for not using an underlying fabric was just to keep it as simple as
possible (but not to simple). Not always an easy choice :-)
On 1/17/12 10:56 AM, "Andy Smith" <[email protected]> wrote:
Looks cool :)
I've been trying to plant the seed of switching devstack to python (heavily
utilizing fabric and cuisine) in my team's head for a while now.
We are heavily dependent on devstack for our development and testing workflows
so it would be a pretty big decision for us to switch tools, and we'd be doing
very active development on whatever new tool we switched to.
The general flow and goals of the tool seem appropriate, and it looks like it
could be a good starting place for work in this direction.
The style of the code is pretty far from most of the common openstack style
guides, but that's pretty easily solvable, as are the other small things to get
the project looking more openstack-y.
I'd still be interested in using fabric and cuisine as the underlying layer
because of having a well-tested, built-in way of dealing with remote servers
allows for some more versatility.
--andy
On Tue, Jan 17, 2012 at 10:20 AM, Joshua Harlow <[email protected]> wrote:
Hi all,
I would just like to propose a new devstack (v2?) that we have been starting to
work on that uses python throughout as well as has componentized installs (for
glance, nova...) and a nice object oriented design and the like (including
having a json format for defining package and pip dependencies that allows
simple comments so people can know what the pkgs are). We are currently trying
to get equivalence going for ubuntu (and at the same time rhel6.x) and I would
like it if we could get peoples initial thoughts on this.
I know the current devstack shell script is starting to explode (LOC wise) and
it seems like it is a good time to stop that from exploding by creating
something a little more flexible (and maintainable imho).
Please check it out @ https://github.com/yahoo/Openstack-Devstack2
Comments welcome!
We are working on getting as much equivalence as we can (while still
maintaining a "clean" design).
Thx,
Josh
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
