doc changes

Author: rpattcorner

README.md

@@ -1,2 +1,9 @@
 geocloud-ecap
 =============
+This repository contains a range of Boundless open source geospatial services and the GeoShape/Rogue deployment of Geonode.  All have  been modified for use in the eCAP automated provisioning system.  
+
+Generic Requirements
+--------------------
+- eCAP server at least tag r0.1.2 or newer
+
+See README.md in applications directory and subdirectories for deployment documentation

applications/README.md

@@ -1,8 +1,4 @@
-This repository contains a range of Boundless open source geospatial services and the GeoShape/Rogue deployment of Geonode.  All have  been modified for use in the eCAP automated provisioning system.  
-
-Requirements
-==============
-- eCAP server at least tag r0.1.2 or newer
+This is the eCAP Deploymenet Descriptor directory
 
 Common Capabilities and BOK (Baskets of Kittens/Deployment Descriptors)
 =======================================================================
@@ -15,16 +11,6 @@ Common Capabilities and BOK (Baskets of Kittens/Deployment Descriptors)
 
 Operational Deployments
 ==================
-This repository is under active development and contains deployments that may not be currently operational.  See README.md in individual deployments for details of operational deployments.
-
-geoshape_geonode Directory
---------------------------
-geoshape_geonode contains the operational descriptors for GeoShape deployment.  See README.md in that directory for status, limitations and usage
-
-VPC Directory
--------------
-The vpc directory defines BOKs to create VPC's for deployment models that target and reuse existing VPCs
-
-Other Directories
-------------------
-Stubs, not operational at this time
+This repository is under active development and contains deployments that may not be currently operational.  See README.md in individual deployments for details of operational deployments.  Currently operational deployments are:
+- VPC - utility for creating standalone VPCs to hold other deployments
+- geoshape_geonode - working GeoShape deployment 

applications/geoshape_geonode/README.md

@@ -11,11 +11,13 @@ Chef community cookbook requirements are met through CAP repository and this rep
 GeoShape uses Chef Vault for credentials.  The eCAP server must have a vault called geoshape_geonode present before deployment with two items ... geoshape_os and unison_os that hold account credentials.  Create them on a one-time basis like this:
 
 `knife vault create geoshape_geonode geoshape_os '{"username": "unison", "password": "somepass"}'`
+
 `knife vault create geoshape_geonode unison_os '{"username": "unison", "password": "somepass"}'`
 
 If you need to add an existing node to the vault later try this:
 
 `knife vault update geoshape_geonode unison_os --search name:GEOSHAPE-DEV-2014121418-ZI-GEONODE-IG5`
+
 `knife vault update geoshape_geonode geoshape_os --search name:GEOSHAPE-DEV-2014121418-ZI-GEONODE-IG5`
 
 Where the name is the CAP-ID/Nodename of the desired node
@@ -65,9 +67,11 @@ Usage
 -----
 #### Carry out a master deployment that creates a VPC and deploys into it
 Expected time 34 minutes
+
 `cap-deploy  /opt/ecap/geocloud-ecap/applications/geoshape_geonode/master.json`
 
 Same, but exclude zone us-east-1a -- needed in some older accounts with AZs that do not support VPC subnets:
+
 `cap-deploy  /opt/ecap/geocloud-ecap/applications/geoshape_geonode/master.json -p azskip=us-east-1a`
 #### Deploy into an existing dev VPC
 The target VPC has the CAPID of INFSTR-DEV-2014121521-CR:

applications/vpc/README.md

@@ -8,4 +8,5 @@ These BOKs are used to create standalone VPC containers that can be used to cont
 Usage
 -----
 Create a dev style VPC for future deployments:
+
 `cap-deploy -n /opt/ecap/geocloud-ecap/applications/vpc/dev_only.json -p azskip=us-east-1a`