Re: Issues on Diego Deployment on Openstack
Eric Malm <emalm@...>
Thanks for reporting the problems you've encountered. As Gwenn pointed out,
this has already been reported on GitHub in
https://github.com/cloudfoundry-incubator/diego-release/issues/60, and is
likely a version mismatch between cf-release and the consul service
properties generated in the diego-release deployment manifest. We track the
compatible versions of cf-release and diego-release that pass through our
testing pipelines in the
There's unfortunately not a lot of explanation in the README there at the
moment, but the Diego team has a story coming up soon (
https://www.pivotaltracker.com/story/show/93811624) to provide more
documentation about how to interpret those records.
For now, I recommend the following process to deploy compatible releases:
- If you are deploying a recent final release of CF, the release notes (
https://github.com/cloudfoundry/cf-release/releases) for that version will
contain a link to a compatible final version (0.N.0 for some number N) of
diego-release. You can then check out the git tag 0.N.0, upload the release
YAML file to your BOSH director, and generate your diego deployment
manifest. Make sure to have both the new CF and Diego releases uploaded
before deploying Diego, as the Diego deployment co-locates some jobs from
cf-release (consul-agent, metron-agent) on its VMs.
- If you are deploying a recent development version of CF, search for the
first 8 characters of its commit SHA in the CF_RELEASE_COMMIT_SHA column of
(GitHub conveniently lets you filter for those records via the search bar
at the top of the displayed CSV.) If there is a 'release_candidate' record,
check out and deploy the final version of diego-release listed in the
DIEGO_RELEASE_VERSION column as described above. If there is only a
'development' record for that cf-release SHA, you can check out the
diego-release SHA from the DIEGO_RELEASE_COMMIT_SHA column, generate a dev
release from that, and upload and deploy that to your BOSH. Please note
that those release combinations may not be as stable, though.
- If you are deploying from the tip of diego-release's develop branch,
which you should typically be doing only when doing development on Diego,
you likely want to deploy either the runtime-passed or develop branches of
cf-release, although there are no guarantees about the stability or
compatibility of the releases on those 'edge' branches.
It's important to note that in general the master branch of cf-release and
the master branch of diego-release are not guaranteed to be compatible, as
the Diego team creates minor final versions on a much faster cadence than
cf-release creates its major versions.
We're not currently publishing example manifests for specific
infrastructures, although we would like to as we expand the Diego testing
pipelines to more infrastructures and as we publish more about the
AWS-based environments we currently use in our pipeline.
Eric, CF Runtime Diego PM
On Thu, Jul 9, 2015 at 7:09 PM, Gwenn Etourneau <getourneau(a)pivotal.io>
Missing of documentation really ?