BOSH Google CPI release
This is a BOSH release for the BOSH Google CPI.
Releases
CPI
| Version |
SHA1 |
Date |
| 22.0.0 |
d39ac2bc02fe5a2287c30e6c728729d2e68b8e1d |
2016-07-19 |
| 23.0.0 |
f4ec50c628af404f60870e933e558bf9b2c36424 |
2016-07-21 |
| 24.0.0 |
e2f77a0a8696b29fdb676cf447cfd9bc6841b648 |
2016-07-22 |
| 24.1.0 |
dda781faa6673430ce77d708ac1c4be3cb763886 |
2016-07-25 |
| [//]: # (new-cpi) |
|
|
Stemcell
| Version |
SHA1 |
Date |
| 3262.2 (Light) |
f46d82a6ae6e89a5635cb3122389f0c8459a82e0 |
2016-07-22 |
| 3262.2 (Heavy) |
f294226d3ade9e27b67e4ef82b8cd5d3b4e23af7 |
2016-07-25 |
| [//]: # (new-stemcell) |
|
|
Usage
If you are not familiar with BOSH and its terminology please take a look at the BOSH documentation.
Complete instructions for deploying a BOSH Director are available in the docs/bosh/README.md file.
Deploy other software
After you have followed the instructions for deploying a BOSH director in docs/bosh/README.md, you may deploy releases like CloudFoundry by following the links below:
Submitting an Issue
We use the GitHub issue tracker to track bugs and features.
Before submitting a bug report or feature request, check to make sure it hasn't already been submitted. You can indicate
support for an existing issue by voting it up. When submitting a bug report, please include a
Gist that includes a stack trace and any details that may be necessary to reproduce the bug,
including your gem version, Ruby version, and operating system. Ideally, a bug report should include a pull request with
failing specs.
Submitting a Pull Request
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Commit and push your changes.
- Submit a pull request.