anchor.diff:    - You must be using an external blobstore.
     - You must either create additional databases
       or disable some optional features in `cf-deployment`.
  +* Ensure your deployed network configuration
  +  is compatible with the transition process:
  +  - You must have sufficient available addresses
  +    in your Cloud Foundry network
  +    to fit the scale of your Diego deployment.
  +    Diego jobs will be deployed to your Cloud Foundry network
  +    as part of the transition.
  +  - You must have non-overlapping network IP address ranges
  +    in your existing deployments.
  +    When you deploy `cf-deployment` with your new cloud config,
  +    the BOSH Director will treat the entire range
  +    of any networks declared in your Diego manifest
  +    as fully used.
  +    This creates a problem.
  +    If you previously had networks with
  +    fully overlapping IP address ranges
  +    that had one another's ranges as `reserved`
  +    to avoid conflicts,
  +    the BOSH Director will now be unable to assign IP addresses
  +    in any of those networks.
  +  - To resolve this,
  +    redefine your networks such that they don't overlap,
  +    and deploy those changes
  +    prior to starting the transition process.
   
   ## <a id='configure-cli'></a> Step 1: Configure the BOSH CLI v2
   Perform the following steps:
  
positive.code:   - az: z1
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.16.1
      range: 10.0.16.0/20
      reserved:
      - 10.0.16.2-10.0.16.3
      - 10.0.31.255
      static:
      - 10.0.31.190-10.0.31.254
    - az: z2
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.32.1
      range: 10.0.32.0/20
      reserved:
      - 10.0.32.2-10.0.32.3
      - 10.0.47.255
      static:
      - 10.0.47.190-10.0.47.254
    - az: z3
      cloud_properties:
        security_groups:
        - FIGURE-THIS-OUT
        subnet: FIGURE-THIS-OUT
      gateway: 10.0.48.1
      range: 10.0.48.0/20
      reserved:
      - 10.0.48.2-10.0.48.3
      - 10.0.63.255
      static:
      - 10.0.63.190-10.0.63.254
    type: manual
  ```
  
  Here are some important takeaways from this example:
  
  * You must include compilation configuration.
  * You must include at least the VM types.
    and extensions from the example.
  * You must have a network called `default`.
  * You must configure the Availability Zones
    `z1`, `z2`, and `z3`.
  
  Once you've written a suitable cloud config,
  upload it to the BOSH Director:
  
negative.code:     ephemeral_disk:
        size: 512000
        type: gp2
  - name: cf-router-network-properties
    cloud_properties:
      elbs:
      - ELB-NAME-FROM-ROUTER-RESOURCE-POOL
  - name: diego-ssh-proxy-network-properties
    cloud_properties:
      elbs:
      - ELB-NAME-FROM-DIEGO-MANIFEST-ACCESS-RESOURCE-POOL
  
  azs:
  - name: z1
    cloud_properties:
      availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z1-RESOURCE-POOL
  - name: z1
    cloud_properties:
      availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z2-RESOURCE-POOL
  - name: z3
    cloud_properties:
      availability_zone: AVAILABILITY-ZONE-FROM-LARGE-Z3-RESOURCE-POOL
  
  networks:
  - name: default
  