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 <[email protected] > > (mailto:[email protected])> 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 > > > [email protected] > > > (mailto:[email protected]) > > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > _______________________________________________ > > OpenStack-operators mailing list > > [email protected] > > (mailto:[email protected]) > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > > > >
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
