anchor.diff:  
   This command may take several minutes, because each Diego cell must drain its contents to the new `cf-deployment` cells.
   
  -## <a id='cleanup'></a> (Optional) Step 6: Clean Up
  -
  +## <a id='cleanup'></a> (Optional) Step 7: Clean Up
   To delete any unused releases and stemcells from your BOSH Director,
   including `cf-release`, run the following command:
   
  
positive.code:   you must also apply the appropriate ops files from the transition repo.
  * The `deployment-vars.yml` file you pass with the `--vars-store` flag must be the variables store file you created above.
  
  ## <a id='delete-diego'></a> Step 5: Delete Old Diego Deployment
  
  Delete your Diego deployment by running the following command:
  
  <pre class="terminal">
  
negative.code:   value: 12
  ```
  
  ## <a id='cloud-config'> Step 4: Write and Upload Cloud Config
  `cf-deployment` requires that a [https://bosh.io/docs/cloud-config.html](https://bosh.io/docs/cloud-config.html)
  providing certain properties be available on the BOSH Director.
  
  You must write such a cloud config,
  drawing its values from your current CF and Diego manifests.
  
  The following properties can be used
  as the basis for your cloud config:
  
  ```yaml
  compilation:
    az: z1
    network: private
    reuse_compilation_vms: true
    vm_extensions:
    - 100GB_ephemeral_disk
    vm_type: c3.large
    workers: 6
  
  disk_types:
  - name: 5GB
    cloud_properties:
      encrypted: true
      type: gp2
    disk_size: 5120
  - name: 10GB
    cloud_properties:
      encrypted: true
      type: gp2
    disk_size: 10240
  - name: 100GB
    cloud_properties:
      encrypted: true
      type: gp2
    disk_size: 102400
  
  vm_types:
  - name: t2.small
    cloud_properties:
      ephemeral_disk:
        size: 10240
        type: gp2
      instance_type: t2.small
  - name: c3.large
    cloud_properties:
      ephemeral_disk:
        size: 10240
        type: gp2
      instance_type: c3.large
  - name: m3.medium
    cloud_properties:
      ephemeral_disk:
        size: 10240
        type: gp2
      instance_type: m3.medium
  - name: m3.large
    cloud_properties:
      ephemeral_disk:
        size: 10240
        type: gp2
      instance_type: m3.large
  - name: r3.xlarge
    cloud_properties:
      ephemeral_disk:
        size: 10240
        type: gp2
      instance_type: r3.xlarge
  
  vm_extensions:
  - name: 50GB_ephemeral_disk
    cloud_properties:
      ephemeral_disk:
        size: 102400
        type: gp2
  - name: 100GB_ephemeral_disk
    cloud_properties:
      ephemeral_disk:
        size: 512000
        type: gp2
  ```
  
  While the above properties are always the same,
  the properties below will need
  to be figured out from your existing manifests.
  (Note that the below continues
  immediately from where the above left off,
  so it starts in the `vm_extensions` section
  of the cloud config.)
  
  ```yaml
  - name: cf-router-network-properties
    cloud_properties:
      elbs:
      - FIGURE-THIS-OUT
      security_groups:
      - FIGURE-THIS-OUT
      - FIGURE-THIS-OUT
  - name: diego-ssh-proxy-network-properties
    cloud_properties:
      elbs:
      - FIGURE-THIS-OUT
      security_groups:
      - FIGURE-THIS-OUT
      - FIGURE-THIS-OUT
  azs:
  - name: z1
    cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  - name: z1
    cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  - name: z3
    cloud_properties: {availability_zone: FIGURE-THIS-OUT}
  
  networks:
  - name: default
    subnets:
    - 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: subnet-635cd92a
      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: subnet-57d8c40f
      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
  ```
  
  Once you've written a suitable cloud config,
  upload it to the BOSH Director:
  
  <pre class="terminal">
  $ bosh update-cloud-config PATH-TO-YOUR-CLOUD-CONFIG
  </pre>
  
  ## <a id='deploy-cf'></a> Step 5: Deploy Cloud Foundry
  Perform the steps in the [Deploying Cloud Foundry](./cf-deployment/deploy-cf.html) topic. Keep in mind the following when deploying Cloud Foundry in [Step 5: Deploy](./cf-deployment/deploy-cf.html#deploy):
  
  * You must apply the ops file for scaling your components that you created in the previous step.
  