Hi,
For those of you out there using configuration management on your servers I have written some puppet modules for sabnzbd, sickbeard, couch potato and headphones.
They are not perfect and I am looking for contributors, particularly if your running a debian environment as I have only tested on centos.
https://github.com/liamjbennett/puppet-sabnzbd
https://github.com/liamjbennett/puppet-sickbeard
https://github.com/liamjbennett/puppet-couchpotato
https://github.com/liamjbennett/puppet-headphones
puppet modules for sab, sb, cp and hp
Re: puppet modules for sab, sb, cp and hp
Cool. I've never used puppet, but I've heard of it, and now is a nice time to see what it can do.
The wikipedia says "puppet is ... an open source configuration management tool.". So it's only about configs? Puppet can't distribute new versions of SAB itself?
And if so, do you use puppet to set the same config in different sabnzbd instances running on different servers?
The wikipedia says "puppet is ... an open source configuration management tool.". So it's only about configs? Puppet can't distribute new versions of SAB itself?
And if so, do you use puppet to set the same config in different sabnzbd instances running on different servers?
Re: puppet modules for sab, sb, cp and hp
Hi,
By "config" it means everything on the system: files, packages, services. Theoretically you can configure and maintain a server without having to ever ssh into the box again.
In terms of the puppet modules, I have written them assuming you would want deploy from source but if we can find a permanent location to store packages then I can also support that method of deployment. I need to find a slightly more elegant solution for managing source updates but this is something i am looking into as we speak.
You should at the moment be able to include these modules in your server config and a have a running setup in less than a few mins.
By "config" it means everything on the system: files, packages, services. Theoretically you can configure and maintain a server without having to ever ssh into the box again.
In terms of the puppet modules, I have written them assuming you would want deploy from source but if we can find a permanent location to store packages then I can also support that method of deployment. I need to find a slightly more elegant solution for managing source updates but this is something i am looking into as we speak.
You should at the moment be able to include these modules in your server config and a have a running setup in less than a few mins.