{"id":1296,"date":"2010-02-18T18:39:35","date_gmt":"2010-02-18T17:39:35","guid":{"rendered":"http:\/\/www.devco.net\/?p=1296"},"modified":"2010-08-17T12:15:44","modified_gmt":"2010-08-17T11:15:44","slug":"custom_deployer_using_mcollective","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2010\/02\/18\/custom_deployer_using_mcollective.php","title":{"rendered":"Custom deployer using MCollective"},"content":{"rendered":"
One of the goals of building the SimpleRPC framework<\/a> and the overall speed of MCollective<\/a> is to create interactive tools to manage your infrastructure in a way that it all just seems like a single point of entry with one machine. I’ve blogged a bit about this before with how I manage Exim clusters<\/a>.<\/p>\n I’ve recently built a deployer for a client that does some very specific things with their FastCGI, packages and monitoring in a way that is safe for developers to use. I’ve made a sanitized demo of it that you can see below. It’s sanitized in that the hostnames are replaced with hashes and some monitoring details removed but you’ll get the idea.<\/p>\n As usual it’s best to just look at the video on youtube<\/a> in it’s HD mode.<\/p>\n