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 <[email protected]> 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 > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
