-
Notifications
You must be signed in to change notification settings - Fork 367
Fun with Deployments and Zero Downtime (ZDT)
Elena Sharma edited this page Jun 7, 2018
·
25 revisions
Background concepts:
-
To deploy ZDT:
upload_capi_release && ~/workspace/capi-release/scripts/deploy -o ~/workspace/capi-ci/cf-deployment-operations/temporary/add-deployment-updater.ymlProcess 'cc_deployment_updater' running . -- lives on the scheduler vm -
It's invoked from
/var/vcap/jobs/cc_deployment_updater/bin/cc_deployment_updaterby runningrake deployment_updater:startand this starts a loop that sleeps forcc.deployment_updater.update_frequency_in_seconds(default 5) and then runs one orchestration step on all active deployments (e.g. ones in stateDEPLOYING).
-
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