Although that does bring up a topic I have thought about for quite some time.
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. On Thursday, March 26, 2015 at 12:51 PM, matt wrote: > referring to Tim Bell's link =P > > On Thu, Mar 26, 2015 at 3:45 PM, Matthew Kaufman <mkfmn...@gmail.com > (mailto:mkfmn...@gmail.com)> wrote: > > hey Matt, nice seeing you last night - who said anything about devstack > > here? > > > > On Thu, Mar 26, 2015 at 3:30 PM, matt <m...@nycresistor.com > > (mailto:m...@nycresistor.com)> wrote: > > > Not sure I'd call devstack configuration management. > > > > > > On Thu, Mar 26, 2015 at 3:13 PM, John Dewey <j...@dewey.ws > > > (mailto:j...@dewey.ws)> wrote: > > > > 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. > > > > > > > > [1] http://stackstorm.com > > > > > > > > On Thursday, March 26, 2015 at 11:42 AM, John Dewey wrote: > > > > > > > > > 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. > > > > > > > > > > John > > > > > > > > > > On Thursday, March 26, 2015 at 10:22 AM, Jesse Keating wrote: > > > > > > > > > > > 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. > > > > > > > > > > > > https://github.com/blueboxgroup/ursula > > > > > > > > > > > > - jlk > > > > > > On Thu, Mar 26, 2015 at 9:40 AM, Forrest Flagg > > > > > > <fostro.fl...@gmail.com (mailto:fostro.fl...@gmail.com)> wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > 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? > > > > > > > > > > > > > > Thanks, > > > > > > > > > > > > > > Forrest > > > > > > > _______________________________________________ > > > > > > > OpenStack-operators mailing list > > > > > > > OpenStack-operators@lists.openstack.org > > > > > > > (mailto:OpenStack-operators@lists.openstack.org) > > > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > OpenStack-operators mailing list > > > > > > OpenStack-operators@lists.openstack.org > > > > > > (mailto:OpenStack-operators@lists.openstack.org) > > > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > OpenStack-operators mailing list > > > > OpenStack-operators@lists.openstack.org > > > > (mailto:OpenStack-operators@lists.openstack.org) > > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > > > > > > > _______________________________________________ > > > OpenStack-operators mailing list > > > OpenStack-operators@lists.openstack.org > > > (mailto:OpenStack-operators@lists.openstack.org) > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > >
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
