# OpenStack organization & introductions

**URL:** <https://forum.ansible.com/t/openstack-organization-introductions/12473>\
**Category:** Ansible Project\
**Created:** [March 9, 2013, 5:01am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473 "2013-03-09T05:01:09Z")\
**Posts on this page:** 13\
**Page:** 2

<div class="post-metadata">

**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 13, 2013, 3:02am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/21 "2013-03-13T03:02:06Z")

</div>

Hey all:

Finally catching up with this thread (have been in cobbler-land rather than ansible-land for the past few days, doing provisioning stuff…). So, I’m about to do a Folsom deploy of OpenStack internally. I’m looking through this thread, and it wasn’t clear to me whether a concrete plan had formed about what the starting point will be. Are we going to use Jimmy’s jcftang/ansible-openstack repo as the basis for the canonical ansible playbooks? I’m happy to offer mine up as well (lorin/openstack-ansible). I’ve seen lots of references to it, but haven’t gotten much direct feedback on it, so I don’t know how suitable it is outside of the original goal of illustrating an install on Vagrant. I’d like to try to update it for Folsom, although it may become obsolete once the official repo ramps up.

I would really like to see ansible modules like those David has mentioned. It would be great if these eventually used the Python APIs, although shelling out to the command line is a fine start (yes, there are Python APIs for all of the OpenStack command-line tools. They are great, although poorly documented. See [http://docs.openstack.org/developer/language-bindings.html](http://docs.openstack.org/developer/language-bindings.html))

Side note: for OpenStack best practice stuff, take a look at the new OpenStack Operations Guide: [http://docs.openstack.org/ops/](http://docs.openstack.org/ops/)

BTW, Curtis, your Cybera blog post was how I discovered Ansible in the first place.

Take care,

---

<div class="post-metadata">

**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 13, 2013, 3:44am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/22 "2013-03-13T03:44:45Z")

</div>

Lorin -- I'm very much leaning on us taking lead from Packstack (and  
porting it) at the moment. This way we have a pretty well  
evolved/entrenched example.

But I want it to be something everyone can use as a baseline.

Thoughts?

---

<div class="post-metadata">

**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 13, 2013, 7:55am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/23 "2013-03-13T07:55:39Z")

</div>

I was thinking about making my ansible-openstack repo private, I don't  
think it's going to be suitable as a set of examples as I'm beginning  
to customise it for my needs (for a year down the road). I think I was  
a little too eager to just dive right in to get things going and  
sharing it early.

Jimmy

---

<div class="post-metadata">

**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 13, 2013, 3:33pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/24 "2013-03-13T15:33:41Z")

</div>

Let’s do it!

---

<div class="post-metadata">

**Author:** ![Curtis](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@Curtis](https://forum.ansible.com/u/Curtis)\
**Post date:** [March 13, 2013, 5:51pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/25 "2013-03-13T17:51:40Z")

</div>

> Lorin -- I'm very much leaning on us taking lead from Packstack (and  
> porting it) at the moment. This way we have a pretty well  
> evolved/entrenched example.
> 
> But I want it to be something everyone can use as a baseline.

I believe packstack is limited to RedHat/CentOS. Would we just be  
supporting that OS to start with openstack-ansible? Not that it's a big  
deal to me, though most openstack clouds I interact with are based on  
Ubuntu 12.04.

Thanks,  
Curtis.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 13, 2013, 11:22pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/26 "2013-03-13T23:22:32Z")

</div>

Porting packstack is just a starting point, but CentOS gets the first priority.

---

<div class="post-metadata">

**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 14, 2013, 3:22am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/27 "2013-03-14T03:22:53Z")

</div>

We’re an Ubuntu shop, so I can contribute by Ubuntu-izing the CentOS stuff. I think the Fedora folks have their own openstack config tool for doing some of the initial painful setup that isn’t upstream, and they default to Qpid instead of RabbitMQ, but otherwise I think it will be pretty similar.

Lorin

---

<div class="post-metadata">

**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 14, 2013, 7:00pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/28 "2013-03-14T19:00:36Z")

</div>

I'm a fedora person and no, we don't have a special tool for it, afaik.

packstack is what the folks inside rh are working on for this and that  
is all, afaik, being worked on in public.

-sv

---

<div class="post-metadata">

**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 14, 2013, 7:44pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/29 "2013-03-14T19:44:10Z")

</div>

Oh, I didn't mean something private. I was referring to the  
"openstack-config" tool, which I think(?) is bundled with the Fedora  
OpenStack packages, but isn't in the Ubuntu ones. Packstack seems to use it  
here:

[https://github.com/stackforge/packstack/blob/master/packstack/plugins/serverprep\_901.py#L427](https://github.com/stackforge/packstack/blob/master/packstack/plugins/serverprep_901.py#L427)

---

<div class="post-metadata">

**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 28, 2013, 1:20am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/30 "2013-03-28T01:20:30Z")

</div>

Hi Rob:

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [March 28, 2013, 11:06pm UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/31 "2013-03-28T23:06:08Z")

</div>

Should not be too difficult, I'd think.

I would likely use a dynamic host group (group\_by) to segment by OS  
and then have different plays use a mix of common and OS specific  
include files to keep it dead simple -- though even just a few  
conditionals sprinkled here and there would not be too bad.

---

<div class="post-metadata">

**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 31, 2013, 1:55am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/32 "2013-03-31T01:55:03Z")

</div>

Cool!

Lorin

---

<div class="post-metadata">

**Author:** ![Darragh\_O\_Reilly](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@Darragh\_O\_Reilly](https://forum.ansible.com/u/Darragh_O_Reilly)\
**Post date:** [April 15, 2013, 11:32am UTC](https://forum.ansible.com/t/openstack-organization-introductions/12473/33 "2013-04-15T11:32:02Z")

</div>

Hi all,

I have have updated the script for Grizzly and added Cinder block storage. The new dashboard is really good with Quantum and should help newcomers get their heads around it.

[https://github.com/djoreilly/quantum-ansible.git](https://github.com/djoreilly/quantum-ansible.git)

Darragh.

[Previous page](https://forum.ansible.com/t/openstack-organization-introductions/12473.md?page=1)
