title | expires_at | tags | |
---|---|---|---|
Deploying to CloudFoundry |
never |
|
- Install Cloud Foundry, or start from an existing CF deployment. If you are starting from scratch, the article Overview of Deploying Cloud Foundry provides detailed instructions.
-
You should have it already after deploying Cloud Foundry, but if not clone the cf-deployment repository from git:
$ cd ~/workspace $ git clone https://github.com/cloudfoundry/cf-deployment.git $ cd ~/workspace/cf-deployment
-
Now redeploy your cf-deployment while including the nfs ops file:
$ bosh -e my-env -d cf deploy cf.yml -v deployment-vars.yml -o operations/enable-nfs-volume-service.yml
Note
The above command is an example, but your deployment command should match the one you used to deploy Cloud
Foundry initially, with the addition of a -o operations/enable-nfs-volume-service.yml
option.
Note
If you'd like to run with ldap server, also include -o operations/test/enable-nfs-test-ldapserver.yml
opsfile.
Your CF deployment will now have a running service broker and volume drivers, ready to mount or create NFS volumes.
Unless you have explicitly defined a variable for your broker password, BOSH will generate one for you.
If you do not have an existing NFS Server then you can optionally deploy the test NFS server bundled in this release.
The easiest way to deploy the test server is to include the enable-nfs-test-server.yml
operations file when you deploy
Cloud Foundry:
$ bosh -e my-env -d cf deploy cf.yml -v deployment-vars.yml \
-o operations/enable-nfs-volume-service.yml \
-o operations/test/enable-nfs-test-server.yml
After deploying, test server can be reached at nfstestserver.service.cf.internal
.
Note
If you'd like to add ldap test server, also include -o operations/test/enable-nfs-test-ldapserver.yml
Important
In order for containers to reach nfstestserver, you will also need a CF security-group that will allow containers to reach the server.
-
Deploy and register the broker and grant access to its service with the following command:
$ bosh -e my-env -d cf run-errand nfsbrokerpush $ cf enable-service-access nfs
You can refer to the Cloud Foundry docs for testing and general usage information.
Test instructions are here The nfsbroker uses credhub as a backing store, and as a result, does not require separate scripts for backup and restore, since credhub itself will get backed up by BBR.