<div dir="ltr">+1<div><br></div><div>We've also been looking into stackstorm for day-to-day operational tasks. It's an awesome tool with an awesome team.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 26, 2015 at 1:13 PM, John Dewey <span dir="ltr"><<a href="mailto:john@dewey.ws" target="_blank">john@dewey.ws</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
We are also in the process of looking at stackstorm[1] as a means to operate openstack. The ability limit playbook execution based on a users role, perform auditing, and automatic remediation are intriguing.
</div><div><br></div><div>[1] <a href="http://stackstorm.com" target="_blank">http://stackstorm.com</a></div><div class="HOEnZb"><div class="h5">
<div></div>
<p style="color:#a0a0a8">On Thursday, March 26, 2015 at 11:42 AM, John Dewey wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span><div><div>
<div>
We use ansible to orchestrate puppet. Why? We already were using puppet, and the eventual convergence is a pain. Also, we are able to piecemeal out puppet for ansible as we move forward.
</div><div><br></div><div>John</div>
<p style="color:#a0a0a8">On Thursday, March 26, 2015 at 10:22 AM, Jesse Keating wrote:</p><blockquote type="cite"><div>
<span><div><div><div dir="ltr">We are using Ansible. We need the orchestration capability that Ansible provides, particularly for upgrades where pieces have to move in a very coordinated order.<div><br></div><div><a href="https://github.com/blueboxgroup/ursula" target="_blank">https://github.com/blueboxgroup/ursula</a><br></div></div><div><br clear="all"><div><div><div dir="ltr"><div><div dir="ltr">- jlk</div></div></div></div></div>
<br><div>On Thu, Mar 26, 2015 at 9:40 AM, Forrest Flagg <span dir="ltr"><<a href="mailto:fostro.flagg@gmail.com" target="_blank">fostro.flagg@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div><div dir="ltr">Hi all,<div><br></div><div>Getting ready to install a Juno or Kilo cloud and was wondering what people are using for configuration management to deploy openstack. Are you using Puppet, Chef, something else? What was the decision process for making your choice?<div><br></div><div>Thanks,</div><div><br></div><div>Forrest</div></div></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></div></blockquote></div><br></div>
</div><div><div>_______________________________________________</div><div>OpenStack-operators mailing list</div><div><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a></div><div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div></div></div></span>
</div></blockquote><div>
<br>
</div>
</div></div></span>
</blockquote>
<div>
<br>
</div>
</div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div>