What is Reddit's opinion of
Chef?
From 3.5 billion Reddit comments
17 reviews of this app found across Reddit:
10 Think "man, this sucked, I should learn about Vagrant and Chef/Puppet"
(or system configuration management and provisioning in general)
As far as automation the two games in town are puppet and chef. Each have their pros and cons but they basically scratch the same itch: getting a system configured properly.
An extremely useful introductory exercise would be to use the tool of your choice to configure your ideal workstation. Templatize your configuration files and have them deployed automatically, have the software installed, configure your network, and do any and all configuration via puppet. Try to never log into the system, except to watch the puppet runs and ensure they're doing everything you expected them to do.
In the situations where the domain specific languages fall short, write scripts to fill in the gaps. ONLY write pure-scripts if you're absolutely certain there's no sanctioned way of doing it though. Scripting is a great skill, but the most important thing to learn is when a tool is the right fix for a given issue or if there are better options.
For this I'd use Puppet: http://puppetlabs.com/
Create a puppet master server and assign it a static IP or good DNS resolvable. Build out your AMI's to start up Puppet which checks in with the master and then builds out however you want it to.
Alternatively, take a look at Chef: http://www.opscode.com/chef/
But basically what you want has already been written.
Puppet (http://docs.puppetlabs.com/) and Chef (http://www.opscode.com/chef/) are configuration management tools that allow you to manage a group of servers based on rules that you create. As an example you can create a Puppet "manifest" describing your Apache server configuration and then configure dozens of them automatically. They make managing large amounts of Unix systems way less resource-intensive, and things will generally be more stable as you'll be able to roll out changes in an automated, staged fashion much easier.
The right way to do this IMHO is to use a config management tool. I suggest you checkout something like puppet or chef. There are other tools out there, but these two are definitly the heavy weights (and what I would recommend to somebody starting out.)
Also, check out vagrant. It's a great way to build-test your puppet/chef code :)
Not to split hairs, but it sounds like your VPS company is provisioning them (VM creation, OS, basic software) - what you seem to be asking about is configuration and package management.
Have you looked into Puppet and/or Chef?
We've recently gone through this architecture debate at my job. We needed to create a scalable platform that could easily handle as much traffic as heroku gets. The system below is what we came up with.
If you want to keep a fully managed hosting system, instead of going with Heroku (recommended), then you'll want to look at some of the newer tools on the market currently. Heroku uses a custom version of Chef with the Knife tool to do there remote management and deploy logic. I'd recommend Chef, unicorn, Nginx, combined with a hosting platform with a great scalabale architecture and api (we use EC2 boxes), combined with a master controller interface for grouping the servers, creating app groups, user management, etc...
Pick up Chef then: http://www.opscode.com/chef/ Or Puppet: http://projects.puppetlabs.com/projects/puppet
If you can grok Puppet, PM me in a couple months and I'll give you a referral to my current employer. They've got a really good track record of working with people with disabilities. They usually offer relocation assistance.
If you're looking to manage config files, I guess you could use git by itself. The real way to do it though would be using system configuration management tools like puppet or chef (and back up the configuration repository using git). There is a bit of a learning curve to overcome to implement them, but in the end you will have a much smoother configuration change management and server deployment.
I learned the hardway that AWS "tiny"/"free" option cant handle chef11 server. You need to do at least 2 Gigs VM or the "Mini" option.
Just a heads up if you want to play with it.
5000 machines? You need a platform for that. Both of these CM tools have good Windows support:
http://www.opscode.com/chef/ http://saltstack.com
More work now, yes. But problems like this will become trivial next time.
At this point, I've got two scripting languages under my belt: bash and powershell. (Working on learning Ruby for Chef - automating our infrastructure piece by piece, Powershell's a big part of the Windows automation side.)
For me at least, I'm not really seeing much of a difference in syntax or structures from bash to powershell. The biggest difference is obviously that powershell works with objects rather than simple data streams. I have to think in a slightly different way when I'm working on one vs the other, but overall I think I prefer the object-orientedness of it.
For instance, I'm writing a script to automate our developers' pushes to QA.
$CurrentRevisionXML = [xml](svn log -r COMMITTED -g --xml)
This takes the xml-based output of the SVN log and I can play around with it as an XML object rather than just a long string. I can pass individual nodes off to different programs - if I wanted to run individual files through a checksum then add the checksum as an additional node property, for instance, it would be a couple of lines of script.
Another example would be adding an announcement to our PBX. Most recordings seem to come in as CD quality (44kHz, 16-bit, stereo). To save storage space and avoid the cpu usage of on-the-fly re-encoding, we convert them down to what they'll be played at. Part of the process has always been done on windows computers, and it was a good time to learn powershell, so the open source 'sox' program came in handy here.
This is a portion of the loop that gets an input file, checks to see if it needs conversion, then converts if necessary. What I'm doing here is assigning values to custom properties of the input file object:
$.Channels=& $SoxExecutable --info -c (join-path $.Directory $.Name) $.SampleRate=& $SoxExecutable --info -r (join-path $.Directory $.Name)
($_ is the current object used in the loop. I think it's analogous to java's 'this.'?)
Chef + PXEBoot = Bootstrapping, IPs, DNS etc.
Forward and reverse DNS for everything - improves diagnostics, helps prevents any emails the system sends you (cron, OMSA, insights, Logwatch, whatever) from getting spammed
For a long while I was quick to say that anyone using the word "cloud" is trying to sell you something you can already get for free, but as I've learned more about the capabilities of OpenStack and Chef I've realized that the idea of a private cloud means that you have a management layer that handles provisioning VM instances almost automatically. So for sysadmins, the difference between a data center and a private cloud is that a data center houses servers that run private cloud software, basically allowing you to run an Amazon EC2-type service on your internal network.