# new LVM module "lvol" **URL:** \ **Category:** Ansible Project\ **Created:** [March 2, 2013, 5:04am UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445 "2013-03-02T05:04:48Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [March 2, 2013, 5:04am UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/1 "2013-03-02T05:04:48Z")
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 ---
**Author:** ![Lorin\_Hochstein1](https://avatars.discourse-cdn.com/v4/letter/l/ce73a5/32.png) [@Lorin\_Hochstein1](https://forum.ansible.com/u/Lorin_Hochstein1)\ **Post date:** [March 4, 2013, 1:48am UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/2 "2013-03-04T01:48:12Z")
Nice. This will make configuring OpenStack Block Storage (cinder) easier. ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [March 4, 2013, 4:22am UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/3 "2013-03-04T04:22:16Z")
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 ---
**Author:** ![Jim\_Richardson](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@Jim\_Richardson](https://forum.ansible.com/u/Jim_Richardson)\ **Post date:** [March 4, 2013, 4:32am UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/4 "2013-03-04T04:32:13Z")
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. ---
**Author:** ![Lorin\_Hochstein1](https://avatars.discourse-cdn.com/v4/letter/l/ce73a5/32.png) [@Lorin\_Hochstein1](https://forum.ansible.com/u/Lorin_Hochstein1)\ **Post date:** [March 4, 2013, 6:49pm UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/5 "2013-03-04T18:49:47Z")
> 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 ---
**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\ **Post date:** [March 4, 2013, 6:57pm UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/6 "2013-03-04T18:57:10Z")
\ Have you seen packstack? [https://github.com/fedora-openstack/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 ---
**Author:** ![Jimmy\_Tang](https://avatars.discourse-cdn.com/v4/letter/j/ac91a4/32.png) [@Jimmy\_Tang](https://forum.ansible.com/u/Jimmy_Tang)\ **Post date:** [March 4, 2013, 7:01pm UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/7 "2013-03-04T19:01:27Z")
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. ---
**Author:** ![Seth\_Vidal](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@Seth\_Vidal](https://forum.ansible.com/u/Seth_Vidal)\ **Post date:** [March 4, 2013, 7:58pm UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/8 "2013-03-04T19:58:27Z")
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 ---
**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\ **Post date:** [March 4, 2013, 8:28pm UTC](https://forum.ansible.com/t/new-lvm-module-lvol/12445/9 "2013-03-04T20:28:01Z")
Liking this idea a lot.