Release branch compatibility?

[charyorde]

I already have an existing bosh-lite director setup based on the warden cf release (v208).
Is cf-release on develop branch(diego) compatible with cf-release in master after executing ./update?

Or should I just setup a brand new bosh-lite running diego?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/95183804.

[emalm]

Hi, @charyorde,

It's not guaranteed that particular commits of cf-release and diego-release will be compatible. For each final version of cf-release, the release notes refer to a corresponding compatible version of diego-release. For example, CF final release v208 is compatible with Diego final release 0.1198.0, and v209 is compatible with Diego final release 0.1209.0.

If you need compatibility for intermediate versions of cf-release, the Diego-CF compatibility repo tracks which versions are successfully promoted through the Diego team's CI pipelines. For the greatest stability, you should take CF/Diego pairs from the rows with 'release_candidate' in the RELEASE_STAGE column, as these also have a definite Diego final release associated to them. For example, as of this writing, Diego final releases 0.1245.0 and 0.1246.0 are compatible with the latest cf-release commit, cloudfoundry-attic/cf-release@211e35e.

You should be perfectly fine to deploy Diego alongside your existing CF bosh-lite deployment, although there may be a few tweaks required to your CF deployment manifest to ensure correct and complete Diego functionality. Please refer to the bosh-lite deployment section of the diego-release README for instructions.

Thanks,
Eric, CF Runtime Diego PM

[charyorde]

wow! This is very very useful. Thank you. Now I have a very good understanding of what's going on in that CF release cycle.