"Don't use SSH in a `for` loop!" We know we should be better than that, yet many Chef shops still rely on SSH to orchestrate their environments.
Are you using "knife ssh", but aren't happy with the security profile?
Are you using chef-solo, but wish you could use "knife ssh"?
Are you trying to invoke Chef from your other applications, and integrating with SSH feels wrong?
Solve these problems and more with MCollective, a CM-agnostic orchestration framework built on Ruby and message queues. This session shows how to deploy MCollective with Chef, integrate the two systems in various ways, use it as an ad-hoc tool, build multi-node orchestration workflows, and invoke Chef from other applications.
This session will introduce some new work. While it will include some demonstrations, this session is not a tutorial - it examines the capabilities and limitations of this approach to building orchestration, and hopes to provoke further discussion and development.
Download the PDF (1.1 MB)
Zachary (@zts) maintains the mcollective cookbook for Chef, and has previously written about it on his blog.