I forgot to mention this earlier, but Jeroen Hoekx's very nice "lvol"
module is now part of core as well.
(This means the 1.1 release has so far added *13* new modules)
1.1 is still due for release at the end of this month (give or take).
--Michael
Nice. This will make configuring OpenStack Block Storage (cinder) easier.
Speaking of which, it's about time we had an ansible-openstack repo so
we can all collaborate on this stuff.
I just saw a pull request for a Ceph module, which while a bit
specific for core, would probably fit very well here.
I'm thinking both modules+playbooks.
What releases should we target?
I know you have some good examples of a basic Essex setup, but from
what I seem to be detecting lots of other people have some great stuff
too.
It would be nice if we could have some of the playbooks/module content
all in one place.
--Michael
count me in for wanting (and being willing to contribute to) an
openstack module, we are exploring OpenStack at work, and are already
heavily invested in Ansible.
Speaking of which, it's about time we had an ansible-openstack repo so
we can all collaborate on this stuff.I just saw a pull request for a Ceph module, which while a bit
specific for core, would probably fit very well here.I'm thinking both modules+playbooks.
Yes and yes! The modules part is pretty straightforward, and I can
contribute to that. Doing playbooks will be...interesting, considering how
configurable OpenStack deployments are, and considering that doing a
generic playbook that handles multiple configurations is un-Ansible-y. How
should we handle that?
Do we want to just do example playbooks for one particular type of
configuration? Or do we want to multiple configurations with entirely
separate playbooks? Or do we want to try to do something where we can share
some of the content across the different configuration playbooks?
What releases should we target?
I know you have some good examples of a basic Essex setup, but from
what I seem to be detecting lots of other people have some great stuff
too.
I propose we target Folsom initially, and update for Grizzly when it's
released (which will happen next month).
It would be nice if we could have some of the playbooks/module content
all in one place.
Yep, that would be great.
Lorin
\
Have you seen packstack?
https://github.com/fedora-openstack/packstack
I'd love to see that w/o the puppet-isms.
The way it works SCREAMS out for ansible instead of puppet, imo.
-sv
This looks interesting, I’m game for making something similar to packstack but with ansible, I may be face with this challenge in a ~1years time for the project im working on now, so I may as well hit it early.
Jimmy.
I'm actually suggesting take packstack, fork it on github, rip out the
puppetbits and replace with ansible bits.
packstack is already in python and integrating with the ansible
playbook-api is, of course, trivial.
-sv
Liking this idea a lot.