On 14/08/14 16:02, Joe Abley wrote: > The cool kids are doing system automation and orchestration using > puppet, chef, ansible, salt, etc (choose your poison), with > bare-metal installs managed using tools like cobbler. Many of these > are seeing more active development on linux than FreeBSD, linux being > a more popular vehicle for devops these days, it seems.
If I could configure my Juniper firewall policies with CFEngine I'd be a happy man! NETCONF looks like the way to do it but as I only have two firewalls and the policies don't change very often I don't think it's worth my time trying to hack NETCONF support into CFEngine. > (The ability for developers to manage their own development and test > releases on a dev branch in svn or git and have ops/noc merge those > into trunk in order to push changes to production is also quite > tasty, as is the ability to reverse those changes easily when you > realise the developers are all smoking crack.) I have 'dev' and 'staging' branches set up for developers. When they merge changes into those branches Jenkins will automatically deploy to the 'dev' and 'staging' servers. It means the developers don't need access to the servers, they can deploy to them whenever they want, and, best of all, they don't have to bother me to do it! Alas, deploying to 'production' is still a manual process (although I've scripted the hell out of it) as it's still just a little bit too fragile for me to trust it 100%. Shane.
