Pull develop branch to update docs.

docs/source/configuration.rst

@@ -361,6 +361,16 @@ If you wish for cfncluster to create a compute subnet, this is the CIDR that. ::
 
     compute_subnet_cidr = 10.0.100.0/24
 
+use_public_ips
+""""""""""""""
+Define whether or not to assign public IP addresses to EC2 instances.
+
+Set to false if operating in a private VPC.
+
+Defaults to true. ::
+
+    use_public_ips = true
+
 .. _ebs_section:
 
 ebs

docs/source/hello_world.rst

@@ -0,0 +1,103 @@
+.. _hello_world:
+
+.. toctree::
+   :maxdepth: 2
+
+####################################
+Running your first job on cfncluster
+####################################
+
+This tutorial will walk you through running your first "Hello World" job on cfncluster.
+
+If you haven't yet, you will need to following the :doc:`getting started <getting_started>` guide to install cfncluster and configure your CLI.
+
+Verifying your installation
+===========================
+
+First, we'll verify that cfncluster is correctly installed and configured. ::
+
+        $ cfncluster version
+
+This should return the running version of cfncluster.  If it gives you a message about configuration, you will need to run the following to configure cfncluster. ::
+
+        $ cfncluster configure
+
+
+Creating your First Cluster
+===========================
+
+Now it's time to create our first cluster.  Because our workload isn't performance intensive, we will use the default instance sizes of t2.micro.  For production workloads, you'll want to choose an instance size which better fits your needs.
+
+We're going to call our cluster "hello-world". ::
+
+        $ cfncluster create hello-world
+
+You'll see some messages on your screen about the cluster creating.  When it's finished, it will provide the following output::
+
+        Starting: hello-world
+        Status: cfncluster-hello-world - CREATE_COMPLETE
+        Output:"MasterPrivateIP"="192.168.x.x"
+        Output:"MasterPublicIP"="54.148.x.x"
+        Output:"GangliaPrivateURL"="http://192.168.x.x/ganglia/"
+        Output:"GangliaPublicURL"="http://54.148.x.x/ganglia/"
+
+The message "CREATE_COMPLETE" shows that the cluster created sucessfully.  It also provided us with the public and private IP addresses of our master node.  We'll need this IP to log in.
+
+Logging into your Master instance
+=================================
+You'll use your OpenSSH pem file and the ec2-user to log into your master instance. ::
+
+        ssh -i /path/to/keyfile.pem ec2-user@54.148.x.x
+
+Once logged in, run the command "qhost" to ensure that your compute nodes are setup and configured. ::
+
+        [ec2-user@ip-192-168-1-86 ~]$ qhost
+        HOSTNAME                ARCH         NCPU NSOC NCOR NTHR  LOAD  MEMTOT  MEMUSE  SWAPTO  SWAPUS
+        ----------------------------------------------------------------------------------------------
+        global                  -               -    -    -    -     -       -       -       -       -
+        ip-192-168-1-125        lx-amd64        2    1    2    2  0.15    3.7G  130.8M 1024.0M     0.0
+        ip-192-168-1-126        lx-amd64        2    1    2    2  0.15    3.7G  130.8M 1024.0M     0.0
+
+As you can see, we have two compute nodes in our cluster, both with 2 threads available to them.
+
+Running your first job
+=====================
+Now we'll create a simple job which sleeps for a little while and then outputs it's own hostname.
+
+Create a file called "hellojob.sh" with the following contents. ::
+
+        #!/bin/bash
+        sleep 30
+        echo "Hello World from $(hostname)"
+
+Next, submit the job using "qsub" and ensure it runs. ::
+
+        $ qsub hellojob.sh
+        Your job 1 ("hellojob.sh") has been submitted
+
+Now, you can vew your queue and check the status of the job. ::
+
+        $ qstat
+        job-ID  prior   name       user         state submit/start at     queue                          slots ja-task-ID
+        -----------------------------------------------------------------------------------------------------------------
+              1 0.55500 hellojob.s ec2-user     r     03/24/2015 22:23:48 all.q@ip-192-168-1-125.us-west     1
+
+The job is currently in a running state.  Wait 30 seconds for the job to finish and run qsub again. ::
+
+        $ qstat
+        $
+
+Now that there are no jobs in the queue, we can check for output in our current directory. ::
+
+        $ ls -l
+        total 8
+        -rw-rw-r-- 1 ec2-user ec2-user 48 Mar 24 22:34 hellojob.sh
+        -rw-r--r-- 1 ec2-user ec2-user  0 Mar 24 22:34 hellojob.sh.e1
+        -rw-r--r-- 1 ec2-user ec2-user 34 Mar 24 22:34 hellojob.sh.o1
+
+Here, we see our job script, an "e1" and "o1" file.  Since the e1 file is empty, there was no output to stderr.  If we view the .o1 file, we can see any output from our job. ::
+
+        $ cat hellojob.sh.o1
+        Hello World from ip-192-168-1-125
+
+We can see that our job sucessfully ran on instance "ip-192-168-1-125".

docs/source/index.rst

@@ -16,6 +16,7 @@ cfncluster is a framework that deploys and maintains High Performance Clusters (
     welcome
     configuration
     functional    
+    tutorials
 
 Getting Started
 ---------------

docs/source/tutorials.rst

@@ -0,0 +1,10 @@
+.. _tutorials
+
+Tutorials
+#########
+
+Here you can find tutorials for best practices guides for getting started with cfncluster.
+
+.. toctree::
+
+    hello_world