Oh yeah this release notes looks great thanks !

oups, sorry wrong list, meant to send it to cf-dev@, will repost. Guillaume.

Hi, The service broker api great to provide access to a common catalog (e.g. mysql, cassandra...). I understand private service brokers [3] will enable to extend the marketplace per space or per org

BOSH release and stemcells are in, ToC added. Thanks for the feedback! wrote:

Agree, this new format is great. One request would be to add a TOC and to have only the last 5 inline, and the remainder on an archive page. Just a suggestion, but this is very nice. Chris

The release notes look great! Looking forward to the bosh release and stemcell versions being populated. :) Mike

Currently Director will bring back VMs in the same AZ as configured in the manifest because resource pool is configured to point to that specific AZ. If Director is in the affected zone you will have

Dmitry, Besides the great CPI V1 doc (for which I proposed refinements in [4]), I notice you have planned a future page "Interactions between CPIs and BOSH Agent" in the TOC. I have few questions

Can you include stacktrace from `bosh task 55 --debug`?

Hi all, On Monday, at approximately 7 PM Pacific Time, the Linux Foundation IT team will be performing a mailing list migration to a newer version of Mailman and adding the HyperKitty UI for

Sorry Tom and Mike, "Publish" was hit prematurely on the draft notes, so bosh.io picked the empty notes up. The release notes are still being filled in, you can see them

Hi, Tom and Mike, We're still assembling release notes from the various teams that contribute to cf-release, but I would expect to see the published notes soon. The recommended version of Diego is

In particular I'd like to know bosh version and diego version used. Thanks! Mike

Good Day, Any release notes available for v214? http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=214 The usual lower right is blank. Thanks, Tom

When I run bosh cck and try to recreate a missing VM I get the following error: -------------------------- 1. VM with cloud ID `urn:vcloud:vm:15f25edb-4dc4-4d9b-8a4e-359a0b22dbd3' missing.

To clarify, 213 is fine to use as a fresh deploy. It's not recommended to use it if you desire not to have down time of cloud controller during the update of the cloud controller job due to a

213 have been deprecated and should not be use . https://github.com/cloudfoundry/cf-release/releases "*IMPORTANT*: This release has a backwards incompatible Cloud Controller database migration that

I saw a clients' environment in cf 210/211 having issues with bosh deploy on an existing environment (fresh install always work) Happens to both cloud contoller and cloud controller worker If I

I am attempting the v213 install on Openstack. Initially with cf-boshworkspace, now as a manual install, api_z1/0 is not running after update. -- I did include debian_nfs_server: no_root_squash:

OK, looks like it was added in v171 and I'm on v152. I'll upgrade and try again, but I would be interested to hear if anyone else it using it yet. -- View this message in context: