This bosh release was integrated into the cf-services-contrib-release: https://github.com/cloudfoundry/cf-services-contrib-release and will no longer be maintained under anynines organization. Please use the cf-services-contrib-release for the latest versions of the release.
The cf_swift_service source code is still maintained under the anynines organization: https://github.com/anynines/cf_swift_service .
To create and upload this release to your BOSH:
$ bosh target BOSH_URL
$ git clone git@github.com:anynines/cf_swift_service_release.git
$ cd cf_swift_service_release
$ ./update
$ bosh create release
# blobs are automatically downloaded
# name it 'cassandra-dev' or something unique to your bosh
$ bosh upload release
If you create a final release bosh create release --final, you must immediately create a new development release. Yeah, this is a bug I guess.
[outside vagrant]
$ bosh create release --final
$ bosh create release
[inside vagrant as vcap user]
$ /vagrant/scripts/update examples/default.yml
This BOSH release is configurable during deployment with properties.
Please maintain example scenarios in the examples/ folder.
To switch between example scenarios, run sm bosh-solo update examples/FILE.yml with a different example scenario.
Once you have a BOSH release that you like, you can upload it to BOSH and deploy it.
$ bosh upload release
$ bosh deployment path/to/manifest.yml
$ bosh deploy
Example properties for your manifest.yml can be taken from the examples in examples\