anchor.diff:    * `SERVICE`: The name of the volume service that you want to use.
     * `PLAN`: The name of the service plan. Service plans are a way for providers to offer varying levels of resources or features for the same service.
     * `SERVICE-INSTANCE`:  A name you provide for your service instance. Use any series of alpha-numeric characters, hyphens, and underscores. You can rename the instance at any time.
  -  * `SHARE-JSON` (NFS Only): If you create an instance of the NFS volume service, you must supply an extra parameter, `share`, by using the `-c` flag with a JSON string, in-line or in a file. This parameter forwards information to the broker about the NFS server and share required for the service. 
  -  
  -    The following example shows creating an instance of the "Existing" NFS 
  -    service plan, passing an in-line JSON string: 
  +  * `SHARE-JSON` (NFS Only): If you create an instance of the NFS volume service, you must supply an extra parameter, `share`, by using the `-c` flag with a JSON string, in-line or in a file. This parameter forwards information to the broker about the NFS server and share required for the service.
  +
  +    The following example shows creating an instance of the "Existing" NFS
  +    service plan, passing an in-line JSON string:
       <pre class="terminal">$ cf create-service nfs Existing nfs\_service\_instance -c '{"share": "10.10.10.10/export/myshare"}'</pre>
   
   1. Run `cf bind-service YOUR-APP SERVICE-NAME -c GID-AND-UID-JSON MOUNT-PATH READ-ONLY-TRUE` to bind your service instance to an app. Replace the following with the specified values:
  -  * `YOUR-APP`: The name of the <%= vars.product_name %> app for which you want to use the volume service. 
  +  * `YOUR-APP`: The name of the <%= vars.product_name %> app for which you want to use the volume service.
     * `SERVICE-NAME`: The name of the volume service instance you created in the previous step.
     * `GID-AND-UID-JSON` (NFS only): If you bind an instance of the NFS volume service, you must supply two extra parameters, `gid` and `uid`. You can specify these parameters with the `-c` flag and a JSON string, in-line or from a file. This parameter specifies the `gid` and `uid` to use when mounting the share to the app.
     * `MOUNT-PATH` (Optional): To mount the volume to a particular path within your app rather than the default path, you supply the `mount` parameter. Choose a path with a root-level folder that already exists in the container, such as `/home`, `/usr`, or `/var`.
  -  * `READ-ONLY-TRUE` (Optional): When you issue the `cf bind-service` command, Volume Services mounts a read-write file system by default. You can specify a read-only mount by adding `"readonly":true` to the bind configuration JSON string. 
  +  * `READ-ONLY-TRUE` (Optional): When you issue the `cf bind-service` command, Volume Services mounts a read-write file system by default. You can specify a read-only mount by adding `"readonly":true` to the bind configuration JSON string.
   
       The following example shows binding `my-app` to the `nfs_service_instance` and specifying a read-only volume to be mounted to `/var/volume1`,
       passing an in-line JSON string:
  
positive.code: 
  ## <a id='nfs'></a> NFS Volume Service
  
  This section describes how to use the NFS volume service. 
  
  ### <a id='create-nfs'></a> Create an NFS Volume Service
  
  Cloud Foundry offers two plans for the NFS volume service: 
  
  * `Existing`: This volume service is implemented with libfuse. It only supports NFSv3 and has some performance constraints.
  * `nfs-experimental`: This volume service provides better performance:
    * It supports NFSv4 through a `version` parameter that determines which NFS protocol to use.
    * It is using the read-only mounts causing the driver to enable attribute caching for mounts. This results in fewer attribute RPCs and better performance.
    * Omitting 'uid' and 'gid' (or 'username' and 'password') in bind configuration causes the nfsdriver to skip mapfs mounting, resulting in a normal kernel mount of the nfs file system without the overhead associated with FUSE mounts.
  
  To create an NFS volume service, follow the procedure below that corresponds to your use case. 
  
  #### Create with Existing Plan
  
  You can create a NFS volume service with NFSv3 using the `Existing` service plan. Run the following command:
  
  ```
  $ cf create-service nfs Existing SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE"}'   
  ```
  
  Where: 
  
  * `SERVICE-INSTANCE-NAME` is a name you provide for this NFS volume service instance. 
  * `SERVER/SHARE` is the NFS address of your server and share. 
  
  <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  You can run the `cf services` command to confirm that your newly created NFS volume service displays in the output. 
  
  
  #### Create with Experimental Plan:
  
  You can create a NFS volume service with NFSv3 or NFSv4 using the `nfs-experimental` service plan. Run the following command:
  
  ```
  $ cf create-service nfs nfs-experimental SERVICE-INSTANCE-NAME -c '{"share":"SERVER/SHARE", "version":"NFS-PROTOCOL"}'   
  ```
  
  Where: 
  
  * `SERVICE-INSTANCE-NAME` is a name you provide for this NFS volume service instance. 
  * `SERVER/SHARE` is the NFS address of your server and share. 
  * `VERSION` is the NFS protocol you want to use. For example, if you want to use NFSv4, set the version to `4.1`. 
  
  <p class="note"><strong>Note</strong>: Ensure you omit the <code>:</code> that usually follows the server name in the address.</p>
  
  You can run the `cf services` command to confirm that your newly created NFS volume service displays in the output. 
  
  ### <a id='nfs-sample'></a> Deploy and Bind a Sample App
  
  This section includes a procedure for deploying a sample app and binding it to the NFS volume service. 
  
  1. Clone the github repo and push the pora test app:
    1. `cd ~/workspace`
  
negative.code: 
      ```
      $ curl http://pora.YOUR-CF-DOMAIN.com/write
      ```
  
  ### <a id="nfs-additional"></a> Additional Information
  
  This section provides additional information about using the NFS Volume Service.
  
  #### Binding with LDAP Credentials
  
  