Dougal, I looked at the source code. Seems like it’s already usable enough. Do you think we need to put a section about Ansible actions into Mistral docs? I’m also thinking if we need to move this code into the mistral repo or leave it on github. Maybe a better time for moving it under Mistral umbrella will be when we finish our actions refactoring activity (when actions are moved into a separate repo, e.g. mistral-extra). Thoughts? Renat Akhmerov @Nokia > On 12 Jan 2017, at 22:27, Dougal Matthews <dougal at redhat.com> wrote: > > Hey all, > > I just wanted to share a quick experiment that I tried out. I had heard there was some interest in native Ansible actions for Mistral. After much dragging my heels I decided to give it a go, and it turns out to be very easy. > > This code is very raw and has only been lightly tested - I just wanted to make sure it was going in the right direction and see what everyone thought. > > I wont duplicate it all again here, but you can see the details on either GitHub or a quick blog post that I put together. > > https://github.com/d0ugal/mistral-ansible-actions <https://github.com/d0ugal/mistral-ansible-actions> > http://www.dougalmatthews.com/2017/Jan/12/calling-ansible-from-mistral-workflows/ <http://www.dougalmatthews.com/2017/Jan/12/calling-ansible-from-mistral-workflows/> > > Cheers, > Dougal > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170117/eba16e64/attachment.html>