Name: csi-local-volume-release
Owner: Cloud Foundry
Description: null
Created: 2017-08-25 17:46:20.0
Updated: 2018-05-01 18:32:19.0
Pushed: 2018-05-01 18:32:17.0
Homepage: null
Size: 3348
Language: Shell
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
CSI local Volume Release for Cloud Foundry that follows protocol specified by Container Storage Interface, it packages a csi-localdriver, a csi-localcontroller and a csi-broker for consumption by a volman-enabled Cloud Foundry deployment.
/workspace/
clone https://github.com/cloudfoundry/cf-deployment.git
f-deployment
-e vbox update-cloud-config ./bosh-lite/cloud-config.yml
-e vbox upload-stemcell https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent
/workspace/
clone https://github.com/cloudfoundry/csi-local-volume-release.git
si-local-volume-release
ripts/update
eate csi-local-volume-release and upload
create-release
-e vbox upload-release
/workspace/cf-deployment
-e vbox -d cf deploy ./cf-deployment.yml \
rs-store ./deployment-vars.yml \
/operations/bosh-lite.yml \
/operations/use-latest-stemcell.yml \
./csi-local-volume-release/operations/enable-csi-local-plugin-bosh-lite.yml \
ystem_domain=bosh-lite.com
/workspace/cf-deployment
assword=`cat deployment-vars.yml |grep cf_admin_password|awk '{print $2}'`
er_password=`cat deployment-vars.yml |grep csi-localbroker-password|awk '{print $2}'`
gin with cf
pi api.bosh-lite.com --skip-ssl-validation
uth admin ${cf_password}
tionaly delete previous broker:
elete-service-broker csilocalfs-broker
eate-service-broker and enable access
reate-service-broker csilocalfs-broker csi-localbroker ${broker_password} http://csi-localbroker.bosh-lite.com
nable-service-access csilocalfs -p free
/workspace/csi-local-volume-release
d ./src/code.cloudfoundry.org/persi-acceptance-tests/
eate a service
reate-org test_org
arget -o test_org
reate-space test_space
arget -s test_space
reate-service csilocalfs free pora-volume-instance \
{"name":"csi-local-storage","volume_capabilities":[{"mount":{}}]}'
sh pora and bind service
ush pora -f ./assets/pora/manifest.yml -p ./assets/pora/ --no-start
ind-service pora pora-volume-instance
tart pora
Bind Parameters
- mount: By default, volumes are mounted into the application container in an arbitrarily named folder under /var/vcap/data. If you prefer to mount your directory to some specific path where your application expects it, you can control the container mount path by specifying the
mount
option. The resulting bind command would look something like
If you have trouble getting this release to operate properly, try consulting the Volume Services Troubleshooting Page