Add some basic ansible stuff and also some thoughts about organization

for the 101 section.  Good start, like this idea.

config_management.rst

@@ -1,6 +1,9 @@
 Configuration Management 101
 ****************************
 
+The Case for Configuration Management
+=====================================
+
 Idempotency
 ===========
 
@@ -10,6 +13,8 @@ Convergent and Congruent systems
 Direct and Indirect systems: ansible, capistrano
 ================================================
 
+(mpdehaan: Are we talking about deployment here?  Then let's start a deployment section.  What does direct/indirect mean? How about not addressing tools in 101 and talking about concepts, so as to make a better tools section? Ansible operates in both push and pull topologies, so I'm guessing that is not what is meant about direct/indirect?)
+
 Chef
 ====
 
@@ -22,6 +27,15 @@ today like Perl was for a lot of us in the 90's)
 Configuration Management 201
 ****************************
 
+Ansible
+=======
+
+`Ansible <http://ansible.cc>`_ is a configuration management, deployment, and remote execution tool that uses SSH to address remote machines (though it offers other connection types, including 0mq).  It requires no server software nor any remote programs, and works by shipping small modules to remote machines that provide idempotent resource management.  While implemented in Python, Ansible uses a basic YAML data language to describe how to orchestrate operations on remote systems.  
+
+Ansible can be extended by writing modules in any language you want, though there is some accelerated module writing ability that makes it easier to do them in Python.
+
+To prevent documentation drift, see `Ansible documentation site <http://ansible.cc/docs>`_.
+
 Puppet
 ======