{"id":1216,"date":"2009-12-14T23:22:08","date_gmt":"2009-12-14T22:22:08","guid":{"rendered":"http:\/\/www.devco.net\/?p=1216"},"modified":"2010-08-17T12:25:13","modified_gmt":"2010-08-17T11:25:13","slug":"exim_mcollective_and_speed","status":"publish","type":"post","link":"https:\/\/www.devco.net\/archives\/2009\/12\/14\/exim_mcollective_and_speed.php","title":{"rendered":"Exim, MCollective and speed"},"content":{"rendered":"
Usually when I describe mcollective<\/a> to someone they generally think its nice and all but the infrastructure to install is quite a bit and so ssh parallel tools like cap seems a better choice. They like the discovery and stuff but it’s not all that clear. <\/p>\n I have a different end-game in mind than just restarting services, and I’ve made a video to show just how I manage a cluster of Exim servers using mcollective. This video should give you some ideas about the possibilities that the architecture I chose brings to the table and just what it can enable.<\/p>\n While watching the video please note how quick and interactive everything is, then keep in mind the following while you are seeing the dialog driven app:<\/p>\n Here’s the video then, as before I suggest you hit the full screen link and watch it that way to see what’s going on.<\/p>\n\n
\n