Closed kukgini closed 6 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/151872704
The labels on this github issue will be updated when the story is started.
Please refer to this code as operation file:
- type: replace
path: /releases/-
value:
name: cephfs
version: "0+dev.1"
- type: replace
path: /instance_groups/name=diego-cell/jobs/-
value:
name: cephdriver
release: cephfs
properties: {}
- type: replace
path: /instance_groups/name=api/jobs/name=cloud_controller_ng/properties/cc/volume_services_enabled?
value: true
- type: replace
path: /instance_groups/name=cc-worker/jobs/name=cloud_controller_worker/properties/cc/volume_services_enabled?
value: true
- type: replace
path: /instance_groups/name=cc-clock/jobs/name=cloud_controller_clock/properties/cc/volume_services_enabled?
value: true
Hi @kukgini
We are actually planning to decommission this bosh release and move it to cloudfoundry-attic, as it has not received a lot of usage, and would require some work in order to make it appropriate for production use. Do you have concrete use cases for this bosh release, or are you just experimenting with it?
Thanks! -Julian
ops files & readme updates added
Manifest v2 and cf-deployment can modify deployment menifest using 'operation' files without modifing release itself. I think this is better then bosh runtime-config because cephdriver only needs on diego-cell. How about consider this to discribe on README.md?