-
Notifications
You must be signed in to change notification settings - Fork 359
So you want a broker with volume mounts?
Tim Hausler edited this page Mar 30, 2017
·
1 revision
- Clone the local volume release repo.
- Build and upload the local-volume-release to your bosh director.
cd ~/workspace/local-volume-release
./scripts/update
bosh -n create release --force && bosh -n upload release
- Enable a local driver in your diego manifest and deploy it. The diego deployment will use the local-volume-release to create a localdriver.
cd ~/workspace/diego-release
export USE_VOLDRIVER=true
./scripts/generate-bosh-lite-manifest
./scripts/deploy
- The broker is a submodule in local-volume-release:
src/code.cloudfoundry.org/localbroker
. Deploy the broker via bosh release:
cd ~/workspace/local-volume-release
./scripts/deploy-bosh-lite.sh
- Start using the broker!
cf create-service-broker localbroker admin admin http://localbroker.bosh-lite.com
cf enable-service-access local-volume
For more information, see the local-volume-release README
-
Pipelines
-
Contributing
- Tips and Tricks
- Cloud Controller API v3 Style Guide
- Playbooks
- Development configuration
- Testing
-
Architectural Details
-
CC Resources
- Apps
- Audit Events
- Deployments
- Labels
- Services
- Sidecars
-
Dependencies
-
Troubleshooting
- Ruby Console Script to Find Fields that Cannot Be Decrypted
- Logging database queries in unit tests
- Inspecting blobstore cc resources and cc packages(webdav)
- How to Use USR1 Trap for Diagnostics
- How to Perf: Finding and Fixing Bottlenecks
- How to get access to mysql database
- How To Get a Ruby Heap Dumps & GC Stats from CC
- How to curl v4 internal endpoints with mtls
- How to access Bosh Director console and restore an outdated Cloud Config
- Analyzing Cloud Controller's NGINX logs using the toplogs script
-
k8s
-
Archive