split out of cf for deployment

* define diego1/diego2 networks for our own deployment
* introduce a template for pulling in external services (nats, etcd, cc, loggregator)
* generate_deployment_manifest still depends on cf-release but only uses its
  infrastructure template, which declares its networks and static IPs, etc.
* the cc srv_api_uri is duplicated, which is risky, but the problem goes away
  once we have proper service discovery

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
fix missing $CONF_DIR var in various ctl scripts

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
add etcd job

duped from cf-release, with properties namespaced

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
update templates for triple-AZ split deployment

now shares a stub with cf-release for discovering nats/loggregator/cc

the stub is automatically generated via the cf-release templates, and then fed
into diego's

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
update deploy script

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
explicitly scope cc/nats properties to jobs

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
deploy cf-release

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
deploy etcd serially

only one node should be down at a time during a deploy

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>
Start one etcd with no peers

Signed-off-by: Alex Suraci <asuraci@pivotallabs.com>