[qmailtoaster] Chef Deployment
Hey List, Just as a heads up, I have mailed a while ago that I was working on a Chef Cookbook for qmailtoaster. Since I have recently moved to a new root server, here the good news: It worked ;) If others are curious, this is what I did: * Deploy all cookbooks and dependencies on my Hosted Chef account * Bootstrap the target node into my Chef Account * Apply a qmailtoaster role to the node that includes my cookbook * Run chef-client on the Node and wait for qmailtoaster to be installed including spamdyke * Sync data from the old server: * Database Dump and User Information for vpopmail * /home/vpopmail/domains folder * /home/qmail/control folder with changes to hostnames * /home/qmail/users folder to fetch qmail user CDB file And that was all. That move was painless and without issues, actually one of the best ones I had so far. Here some restrictions though: * I am not using any of the fronteds supplied in qmailtoaster (squirrel mail, qmailadmin etc) * The Chef way to install the frontend is prepared but not ready to use * CentOS 6.4 @Eric: If you are curious, I have pushed my Chef files to Github so you (and others) can take a look: https://github.com/TheSerapher/chef-repo This does not include the cookbooks I am using but the qmailtoaster cookbook can be found here: https://github.com/TheSerapher/chef-qmailtoaster Someday qmailtoaster will be in for some changes again, maybe we should consider wrapping it around a Chef way to install it instead of dealing with configuration changes, file adjustments and all that via RPM packages. This could even be accomplished without a Chef Server by using Chef Solo as described in my blog which I posted a while ago too. Just a few ideas, I love qmailtoaster and I will be happy with anything the list comes up with. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Chef Deployment
Well you certainly make it sound easy, but when I tried I failed. I don't understand the cookbook concept and it's not very self explanatory. Glad it worked out, but I'm lost at deploy all the cookbooks. I found the .iso much simpler, however apparently not as modular. On 10/03/2013 11:06 PM, Sebastian Grewe wrote: Hey List, Just as a heads up, I have mailed a while ago that I was working on a Chef Cookbook for qmailtoaster. Since I have recently moved to a new root server, here the good news: It worked ;) If others are curious, this is what I did: * Deploy all cookbooks and dependencies on my Hosted Chef account * Bootstrap the target node into my Chef Account * Apply a qmailtoaster role to the node that includes my cookbook * Run chef-client on the Node and wait for qmailtoaster to be installed including spamdyke * Sync data from the old server: * Database Dump and User Information for vpopmail * /home/vpopmail/domains folder * /home/qmail/control folder with changes to hostnames * /home/qmail/users folder to fetch qmail user CDB file And that was all. That move was painless and without issues, actually one of the best ones I had so far. Here some restrictions though: * I am not using any of the fronteds supplied in qmailtoaster (squirrel mail, qmailadmin etc) * The Chef way to install the frontend is prepared but not ready to use * CentOS 6.4 @Eric: If you are curious, I have pushed my Chef files to Github so you (and others) can take a look: https://github.com/TheSerapher/chef-repo This does not include the cookbooks I am using but the qmailtoaster cookbook can be found here: https://github.com/TheSerapher/chef-qmailtoaster Someday qmailtoaster will be in for some changes again, maybe we should consider wrapping it around a Chef way to install it instead of dealing with configuration changes, file adjustments and all that via RPM packages. This could even be accomplished without a Chef Server by using Chef Solo as described in my blog which I posted a while ago too. Just a few ideas, I love qmailtoaster and I will be happy with anything the list comes up with. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com --
Re: [qmailtoaster] Chef Deployment
Yes, the concept behind Chef is rather hard to grasp at first. Took me a while to get it entirely. Using a pre-setup Chef Solo package is not hard. It's actually harder to prepare it for users than actually using it ;) By no means I am trying to push this. It worked great for me, added a lot of flexibility to my deployment process and automated it completely. Figured I'd share this with others. I am a HUGE fan of qmailtoaster and for that reason alone I have been running CentOS for years now. I can't imagine running anything else anymore ;-) Cheers, Sebastian On Oct 4, 2013, at 8:10 AM, cj yother c...@yother.com wrote: Well you certainly make it sound easy, but when I tried I failed. I don't understand the cookbook concept and it's not very self explanatory. Glad it worked out, but I'm lost at deploy all the cookbooks. I found the .iso much simpler, however apparently not as modular. On 10/03/2013 11:06 PM, Sebastian Grewe wrote: Hey List, Just as a heads up, I have mailed a while ago that I was working on a Chef Cookbook for qmailtoaster. Since I have recently moved to a new root server, here the good news: It worked ;) If others are curious, this is what I did: * Deploy all cookbooks and dependencies on my Hosted Chef account * Bootstrap the target node into my Chef Account * Apply a qmailtoaster role to the node that includes my cookbook * Run chef-client on the Node and wait for qmailtoaster to be installed including spamdyke * Sync data from the old server: * Database Dump and User Information for vpopmail * /home/vpopmail/domains folder * /home/qmail/control folder with changes to hostnames * /home/qmail/users folder to fetch qmail user CDB file And that was all. That move was painless and without issues, actually one of the best ones I had so far. Here some restrictions though: * I am not using any of the fronteds supplied in qmailtoaster (squirrel mail, qmailadmin etc) * The Chef way to install the frontend is prepared but not ready to use * CentOS 6.4 @Eric: If you are curious, I have pushed my Chef files to Github so you (and others) can take a look: https://github.com/TheSerapher/chef-repo This does not include the cookbooks I am using but the qmailtoaster cookbook can be found here: https://github.com/TheSerapher/chef-qmailtoaster Someday qmailtoaster will be in for some changes again, maybe we should consider wrapping it around a Chef way to install it instead of dealing with configuration changes, file adjustments and all that via RPM packages. This could even be accomplished without a Chef Server by using Chef Solo as described in my blog which I posted a while ago too. Just a few ideas, I love qmailtoaster and I will be happy with anything the list comes up with. - To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com -- cj's_sig.png
