Added Chef config skeleton and README

Author: nacx

README.md

@@ -0,0 +1,41 @@
+ApacheCon NA 2016 demo
+======================
+
+The ACNA 2016 demo is an application that deploys nodes to a given cloud provider, and uses 
+[Chef](http://chef.io) for configuration management and service discovery. If you don't have a Chef Server, you can try this demo for free with a [Hosted Chef] account.
+
+## Configuring the Chef Server
+
+First of all, the Chef Server must have the cookbooks and roles that will be used in this example
+application. In order to do that, you need to have the `knife CLI` installed on route machine. If you don't have it, you can download and install Chef from [here](<chef download link>).
+
+Once the Chef CLI is installed, you can upload everything to the Chef Server as follows:
+
+```bash
+gem install Berkshelf    # Cookbook manager used to manage cookbook dependencies
+cd chef
+berks install            # Download the cookbooks and their dependencies
+berks upload -a          # Upload everything to the Chef Server
+```
+
+Once the cookbooks are installed, the roles and environments need to be uploaded:
+
+```bash
+knife environment from file environments/*
+knife role from file roles/*
+```
+
+Now the Chef Server has all it needs for the demo.
+
+## Configuring the connection to the cloud providers
+
+To configure the connection to a cloud provider, create a file in the format `<provider-id>.properties` in the `src/main/resources` directory. The file must contain two keys:
+
+* <provider-id>.identity = <identity used to connect to the provider>
+* <provider-id>.credential = <credential used to connect to the provider>
+
+Values can also be path to files that contain the credential. This makes it easier to provide
+private keys, and avoids exposing the credentials if the file is uploaded to a version control
+system. 
+
+You will also have to change the `chef.properties` file to point to your Chef Server. 

chef/Berksfile

@@ -0,0 +1,8 @@
+source 'https://supermarket.chef.io'
+
+cookbook 'apache2', '~> 3.2.2'
+
+# The HAProxy cookbook does not properly read the ip address of the nodes
+# in some clouds (issue COOK<ref>). This branch containst a temporal patch
+# that can be used until the bug is fixed. 
+cookbook 'haproxy', :git => 'https://github.com/nacx/haproxy

pom.xml

@@ -1,5 +1,6 @@
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
     <modelVersion>4.0.0</modelVersion>
+
     <groupId>org.apache.jclouds</groupId>
     <artifactId>acna2016-demo</artifactId>
     <version>0.0.1-SNAPSHOT</version>
@@ -33,14 +34,16 @@
         </dependency>
         <dependency>
             <groupId>org.apache.jclouds.provider</groupId>
-            <artifactId>aws-ec2</artifactId>
+            <artifactId>digitalocean2</artifactId>
             <version>${jclouds.version}</version>
         </dependency>
+        <!-- Uncomment to have access to all compute providers 
         <dependency>
-            <groupId>org.apache.jclouds.provider</groupId>
-            <artifactId>digitalocean2</artifactId>
+            <groupId>org.apache.jclouds</groupId>
+            <artifactId>jclouds-allcompute</artifactId>
             <version>${jclouds.version}</version>
         </dependency>
+        -->
 
         <!-- Drivers -->
         <dependency>