anchor.diff:  Features (templates) typically require configuration.
   You specify this information in the `properties` block.
   
  +<pre class="terminal">
  +jobs:
  +- name: dummy
  +  templates:
  +  - name: dummy
  +    release: dummy_a
  +  instances: 1
  +  resource_pool: default
  +  persistent_disk: 10240
  +  networks:
  +  - name: default
  +    default: [dns, gateway]
  +</pre>
  +
   ### <a id='properties'></a> The properties block ###
   
   The `properties` block consists of headings which are the names of features (templates) from the `jobs` block.
   Each heading is followed by one or more lines of configuration information.
   
  +<pre class="terminal">
  +properties:
  +
  +  ntp:
  +  - 0.north-america.pool.ntp.org
  +  - 1.north-america.pool.ntp.org
  +  - 2.north-america.pool.ntp.org
  +  - 3.north-america.pool.ntp.org
  +
  +  blobstore:
  +    address: 10.10.0.7
  +    port: 25251
  +    backend_port: 25552
  +    agent:
  +      user: agent
  +      password: ldsjlkadsfjlj
  +    director:
  +      user: director
  +      password: DirectoR
  +
  +...
  +
  +mysql: &bosh_db
  +  adapter: mysql2
  +  user: u1250a5fcd8ade2
  +  password: p2cfca30665aa46f875605ca81845ef4c
  +  host: bosh.cabaz18bo7yr.us-east-1.rds.amazonaws.com
  +  port: 3306
  +  database: bosh
  +
  +...
  +
  +registry:
  +  address: 10.10.0.7
  +  db: *bosh_db
  +  http:
  +    port: 25777
  +    user: awsreg
  +    password: awsreg
  +
  +</pre>
  +
  +
  +
   ## <a id="example"></a> A Basic Example Manifest ##
   
   _insert example and reference other examples?_
  
positive.code:     default: [dns, gateway]
  </pre>
  
  
  ## <a id="anatomy"></a> Anatomy of a Manifest ##
  
  Some of the information in any given BOSH manifest is IaaS-specific.
  The vast majority of manifest content, though, is independent of the cloud infrastructure where you want to deploy.
  This makes it possible to re-use manifests, making minimal changes, even when moving a deployment from one IaaS to another.
  
  A BOSH deployment manifest begins by identifying the deployment as follows:
  
  1. The **name** you give the deployment.
  1. The `director_uuid` _insert text here_ to ensure that you deploy with the correct BOSH.
  1. The **release name** you choose.
  1. The **release version** which _insert description here_.
  
  For example:
  
  
negative.code: * Specifies the number and desired behavior of "canaries."
  
  Before BOSH updates all the instances of a given VM type, it updates one or more "canaries,"
  and monitors the update to determine whether it can run successfully on that VM type.
  
  A "canary" is just an instance of the VM type to be updated.
  
  If the "canary" update fails, or even appears to succeed too quickly, BOSH does not proceed to update the rest of the instances.
  
  <pre class="terminal">
  update:
    canaries: 1
    canary_watch_time: 30000-240000
    update_watch_time: 30000-600000
    max_in_flight: 3
  </pre>
  
  ### <a id='resource_pools'></a> The resource_pools block ###
  
  IaaS-dependent instance type
  
  Resource pools are collections of VMs which are on the same network, are the same kind of VM from the IaaS's perspective, and are built from the same stemcell.
  The `resource_pools` block specifies all of these.
  
  <pre class="terminal">
  resource_pools:
  - name: default
    stemcell:
      name: bosh-aws-xen-ubuntu
      version: latest
    network: default
    size: 1
    cloud_properties:
      instance_type: m1.small
      availability_zone: us-east-1c
  </pre>
  
  ### <a id='networks'></a> The networks block ###
  
  IaaS-dependent -- some have subnet, some have network names, some keys differ
  
  The `networks` block is where you specify network configuration information for the deployment.
  Networks are named, enabling you to specify multiple networks.
  
  <pre class="terminal">
  networks:
  - name: default
    type: manual
    subnets:
    - range: 10.10.0.0/24
      gateway: 10.10.0.1
      static:
      - 10.10.0.7 - 10.10.0.9
      reserved:
      - 10.10.0.2 - 10.10.0.6
      - 10.10.0.10 - 10.10.0.10
      dns:
      - 10.10.0.6
      cloud_properties:
        subnet: subnet-d597b993
  </pre>
  
  ### <a id='jobs'></a> The jobs block ###
  
  IaaS-agnostic
  
  
  The `jobs` block is where you name VM types and specify:
  
  