Re: [openstack-dev] [TripleO] a small experiment with Ansible in TripleO
On 08/04/2014 08:19 AM, Clint Byrum wrote: > I've been fiddling on github. This repo is unfortunately named the same > but is not the same ancestry as yours. Anyway, the branch 'fiddling' has > a working Heat inventory plugin which should give you a hostvar of > 'heat_metadata' per host in the given stack. Cool, Monty and I have that merged now. And, I've got a working Ansible module for nova rebuild: https://github.com/allisonrandal/tripleo-ansible/blob/master/library/cloud/nova_rebuild > Note that in the root there is a 'heat-ansible-inventory.conf' that is > an example config (works w/ devstack) to query a heat stack and turn it > into an ansible inventory. That uses oslo.config so all of the usual > patterns for loading configs in openstack should apply. This is really elegant, I'll follow suit in the example playbook for rebuild. Allison ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] a small experiment with Ansible in TripleO
I've been fiddling on github. This repo is unfortunately named the same but is not the same ancestry as yours. Anyway, the branch 'fiddling' has a working Heat inventory plugin which should give you a hostvar of 'heat_metadata' per host in the given stack. https://github.com/SpamapS/tripleo-ansible/blob/fiddling/plugins/inventory/heat.py Note that in the root there is a 'heat-ansible-inventory.conf' that is an example config (works w/ devstack) to query a heat stack and turn it into an ansible inventory. That uses oslo.config so all of the usual patterns for loading configs in openstack should apply. Excerpts from Allison Randal's message of 2014-08-01 09:07:44 -0700: > A few of us have been independently experimenting with Ansible as a > backend for TripleO, and have just decided to try experimenting > together. I've chatted with Robert, and he says that TripleO was always > intended to have pluggable backends (CM layer), and just never had > anyone interested in working on them. (I see it now, even in the early > docs and talks, I guess I just couldn't see the forest for the trees.) > So, the work is in line with the overall goals of the TripleO project. > > We're starting with a tiny scope, focused only on updating a running > TripleO deployment, so our first work is in: > > - Create an Ansible Dynamic Inventory plugin to extract metadata from Heat > - Improve/extend the Ansible nova_compute Cloud Module (or create a new > one), for Nova rebuild > - Develop a minimal handoff from Heat to Ansible, particularly focused > on the interactions between os-collect-config and Ansible > > We're merging our work in this repo, until we figure out where it should > live: > > https://github.com/allisonrandal/tripleo-ansible > > We've set ourselves one week as the first sanity-check to see whether > this idea is going anywhere, and we may scrap it all at that point. But, > it seems best to be totally transparent about the idea from the start, > so no-one is surprised later. > > Cheers, > Allison > ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] a small experiment with Ansible in TripleO
On 08/01/2014 12:06 PM, Galbraith, Patrick wrote: > I have been working on Ansible nova_compute, a new “nova_facts” > module as well as the nova dynamic inventory plugin, so please do > feel free to collaborate with me on this. Great, are you on #tripleo? I'm 'wendar', and I'm working on this bit. Allison ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [TripleO] a small experiment with Ansible in TripleO
Hi all, I have been working on Ansible nova_compute, a new “nova_facts” module as well as the nova dynamic inventory plugin, so please do feel free to collaborate with me on this. Regards, Patrick On Aug 1, 2014, at 12:07 PM, Allison Randal wrote: > A few of us have been independently experimenting with Ansible as a > backend for TripleO, and have just decided to try experimenting > together. I've chatted with Robert, and he says that TripleO was always > intended to have pluggable backends (CM layer), and just never had > anyone interested in working on them. (I see it now, even in the early > docs and talks, I guess I just couldn't see the forest for the trees.) > So, the work is in line with the overall goals of the TripleO project. > > We're starting with a tiny scope, focused only on updating a running > TripleO deployment, so our first work is in: > > - Create an Ansible Dynamic Inventory plugin to extract metadata from Heat > - Improve/extend the Ansible nova_compute Cloud Module (or create a new > one), for Nova rebuild > - Develop a minimal handoff from Heat to Ansible, particularly focused > on the interactions between os-collect-config and Ansible > > We're merging our work in this repo, until we figure out where it should > live: > > https://github.com/allisonrandal/tripleo-ansible > > We've set ourselves one week as the first sanity-check to see whether > this idea is going anywhere, and we may scrap it all at that point. But, > it seems best to be totally transparent about the idea from the start, > so no-one is surprised later. > > Cheers, > Allison > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev