anchor.diff:  owner: Diego Persistence
   ---
   
  -This topic describes how Cloud Foundry (CF) operators can deploy volume services.
  +This topic describes how Cloud Foundry operators can deploy volume services.
   
   
   ## <a id="overview"></a> Overview
   
   A volume service gives apps access to a remote filesystem, such as NFS.
  -To provide a volume service for CF developers to use with their apps,
  +To provide a volume service for Cloud Foundry developers to use with their apps,
   you must deploy a driver and broker pair.
   
  -For current versions of CF that have been been deployed with cf-deployment,
  -you can deploy brokers and drivers using ops files.
  -For an example, see [Example: Deploy NFS Volume Service to CF](#example) and
  -[Example 2: Deploy SMB Volume Service to CF](#smb-example) below.
  +For current versions of Cloud Foundry that have been been deployed with cf-deployment,
  +you can deploy brokers and drivers using ops files. 
  +
  +For examples of deploying brokers and drivers using ops files, see [Deploy NFS Volume Service to Cloud Foundry](#example) and [Deploy SMB Volume Service to Cloud Foundry](#smb-example) below.
   
   ### <a id='additional-info'></a> Additional Information
   
  -For more information about volume services and the drivers and brokers available to CF, see the following:
  +For more information about volume services and the drivers and brokers available to Cloud Foundry, see the following:
   
   * [Volume Services Google Doc](https://docs.google.com/document/d/1YtPMY9EjxlgJPa4SVVwIinfid_fshCF48xRhzyoZhrQ/edit?usp=sharing)
   * [Volume Services Troubleshooting Guide](https://github.com/cloudfoundry/volman/blob/master/TROUBLESHOOTING.md)
  
positive.code:   For example:
    <pre class="terminal">$ bosh -e my-env -d cf run-errand smbbrokerpush</pre>
  
  Your CF deployment now has a running service broker and volume drivers and
  is ready to mount existing SMB shares.
  
  #### <a id="smb-server"></a> Deploy the SMB Test Server
  
  To deploy the SMB test server, include the `enable-smb-test-server.yml` ops file
  in your deployment with the `-o` flag. To view this file,
  see [cf-deployment](https://github.com/cloudfoundry/cf-deployment/blob/master/operations/test/enable-smb-test-server.yml)
  in GitHub.
  
  The `enable-smb-test-server.yml` ops file creates a separate VM with
  SMB shares you can use to experiment with volume mounts.
  
  <p class="note"><strong>Note:</strong> By default, the SMB test server expects that your
    CF deployment is deployed to a <code>10.x.x.x </code>subnet.
    If you are deploying to a subnet that is not <code>10.x.x.x</code>,
    you must override the <code>export_cidr</code> property.<br><br>
   To override the <code>export_cidr</code> property, edit the ops file and
   add in the properties section <code>export_cidr: YOUR-SUBNET</code>,
   where <code> YOUR-SUBNET</code> is the subnet you are deploying CF to.
  </p>
  
  ###<a id="smb-broker"></a> Grant Access to the SMB Broker
  
  Grant access to the services of the broker by running the following command:
  
  <pre class="terminal">$ cf enable-service-access smb</pre>
  
  CF app developers can now create an SMB service and bind instances to their apps.
  For more information, see
  [Using an External File System (Volume Services)](../devguide/services/using-vol-services.html).
  
negative.code:     Where:
      + `MY-ENV` is the name of the BOSH Director.
      + `MY-DEPLOYMENT` is the name of your deployment.
      + `MANIFEST-YAML` is the name of the manifest YAML file you used when you deployed Cloud Foundry.
      + `VARIABLES-YAML` is the name of the variables YAML file you used when you deployed Cloud Foundry.
  
      For example:
      <pre class="terminal">$ bosh -e my-env -d cf deploy cf.yml -v deployment-vars.yml \
  