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:     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 CF.
      + `VARIABLES-YAML` is the name of the variables YAML file you used when you deployed CF.
  
      For example:
      <pre class="terminal">$ bosh -e my-env -d cf deploy cf.yml -v deployment-vars.yml \
  
negative.code: * [SMB volume release repository](https://github.com/cloudfoundry/smb-volume-release)
  * [EFS volume release repository](https://github.com/cloudfoundry-incubator/efs-volume-release)
  
  <p class="note"><strong>Note:</strong> If you are running a single Diego Cell Cloud Foundry deployment, you can deploy a local volume release in a 
    test environment. Do not deploy local volume releases in production deployments. For information about 
    local volume releases, see <a href="https://github.com/cloudfoundry/local-volume-release.git">local-volume-release</a> in GitHub.
  </p>
  
  ### <a id='contact'></a> Contact
  
  If you have any questions, you can contact the team that develops volume services
  for Cloud Foundry on the **#persi** channel in the [Cloud Foundry (Open Source)](https://cloudfoundry.slack.com)
  Slack organization.
  
  ## <a id="example"></a> Deploy NFS Volume Service to Cloud Foundry
  
  This section provides an example of how to deploy the NFS broker and
  corresponding driver to an existing Cloud Foundry deployment.
  
  To deploy the NFS broker and driver to an existing Cloud Foundry deployment, do the following:
  
  1. [Redeploy Cloud Foundry with NFS Enabled](#redeploy)
  1. [Grant Access to the NFS Service](#broker)
  1. [(Optional) Enable LDAP Support](#ldap)
  1. [(Optional) Deploy Test Servers](#server)
  
  ### <a id="pre"></a> Prerequisites
  
  Before you deploy the NFS volume service to a Cloud Foundry deployment, you must have the following:
  
  * A current version of Cloud Foundry deployed.
  See [Overview of Deploying Cloud Foundry](/deploying/index.html).
  