<div>
Although that does bring up a topic I have thought about for quite some time.
</div><div><br></div><div>I personally would love to switch out all the shell script craziness in devstack with ansible. Devstack becomes the reference architecture to deploying openstack. Deploying to a workstation, or multi-node, or production is a matter of swapping out the site.yml.</div><div><br></div>
<div></div>
<p style="color: #A0A0A8;">On Thursday, March 26, 2015 at 12:51 PM, matt wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div dir="ltr">referring to Tim Bell's link =P<br></div><div><br><div>On Thu, Mar 26, 2015 at 3:45 PM, Matthew Kaufman <span dir="ltr"><<a href="mailto:mkfmncom@gmail.com" target="_blank">mkfmncom@gmail.com</a>></span> wrote:<br><blockquote type="cite"><div><div dir="ltr"><div style="font-family:arial,helvetica,sans-serif;font-size:small;color:#000000">hey Matt, nice seeing you last night - who said anything about devstack here?</div></div><div><div><div><br><div>On Thu, Mar 26, 2015 at 3:30 PM, matt <span dir="ltr"><<a href="mailto:matt@nycresistor.com" target="_blank">matt@nycresistor.com</a>></span> wrote:<br><blockquote type="cite"><div><div dir="ltr">Not sure I'd call devstack configuration management.<br></div><div><br><div>On Thu, Mar 26, 2015 at 3:13 PM, John Dewey <span dir="ltr"><<a href="mailto:john@dewey.ws" target="_blank">john@dewey.ws</a>></span> wrote:<br><blockquote type="cite"><div>
<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><div>
<p style="color:#a0a0a8">On Thursday, March 26, 2015 at 11:42 AM, John Dewey wrote:</p><blockquote type="cite"><div>
<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>
</div></blockquote><div>
<br>
</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>
<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></blockquote></div><br></div>
</div></div></span>
</blockquote>
<div>
<br>
</div>