Yours might make sense to be added on to devstackPY.
We have a concept of a persona (thanks! to dreamhost pep's) that might be what
you want/use for this also:
Features:
Supports more than one distribution
Currently RHEL 6.2 (with epel), Ubuntu 11.10 (12 WIP), Fedora 16 (WIP)
Supports dry-run mode (to see what would happen)
Supports varying installation personas (see conf/personas/devstack.sh.yaml)
A single stack.ini file that shows configuration used/applied
Supports install/uninstall/starting/stopping of OpenStack components.
In various styles (daemonizing via forking, screen, upstart)
Written in python so it matches the style of other OpenStack components.
Extensively documented distribution specifics (see conf/distros/)
Packages and pip (with versions known to work!) dependencies
Any needed distribution specific actions (ie service names...)
Follows standard software development practices (for everyones sanity).
Functions, classes, objects and more (oh my!)
Still readable by someone with limited python knowledge.
The ability to be unit-tested!
-Josh
On 3/20/12 11:01 AM, "Justin Santa Barbara" <jus...@fathomdb.com> wrote:
Hi Thomas,
I think devstack has done a lot for the developer's use-case, but I believe we
should also have a official / semi-official project that does some sort of
packaging to help the production use-case. I've proposed a summit discussion:
http://summit.openstack.org/sessions/view/26
The background: I want a semi-production deployment, but as a developer I still
want to be able to edit the code (which makes packages inconvenient). devstack
is orientated towards e.g. wiping the databases.
I'm hoping that all the various OS packagers can work together, or at least
tell us what sucks. As a community, we should solve these problems once, and
the OpenStack project shouldn't treat them as externalities. I've been doing
some initial coding here:
https://github.com/justinsb/openstack-simple-config
The first use case I'm trying to solve is "single node installation of
OpenStack" that is as easy as possible, but also isn't painting the user into
the corner. Think "apt-get openstack", then the user finds they like it and
grows to a 4 node cluster, all the way up to a 100 node cluster. So it uses
KVM, FlatManager, config drive injection, Postgresql, etc. - I'm afraid it is
still quite "opinionated"! I have Keystone, Glance & Nova installing. I'm
using supervisord to avoid any OS dependencies/flamewars, but I would imagine
that any OS packager could move it to their preferred init.d flavor easily.
Swift is next on my list - I was facing the problem that the number of replicas
isn't changeable, though I have a patch for that now.
If you'd like to work together, I'd love to collaborate (and that holds for
anyone doing packaging). I'm hanging out in #openstack-packaging
Justin
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
