The cf-release v211 was released on June 4th, 2015 - IMPORTANT: This release removes lucid64 stack, please ensure apps are migrated prior to upgrade - IMPORTANT: If using the postgres included within

Yes, I do recall that the feature did not work on bosh-lite but that was when kernel logging was disabled on the trusty stemcell. Michael, could you send the json for the application security group yo

Link to the chat room for the CAB call: http://webconf.soaphub.org/conf/room/CF-CAB-OpenForum

Hi Pablo, Ops Metrics is a PCF product and questions about that should be directed to Pivotal customer support. Regarding your second question, about the difference between crashed indices and crashed

Thanks Phil! As always, a great write up.

For now, we recommend using a different system domain and app domain so that the overlap does not occur. For example, system.example.com for the system domain and apps.example.com as the apps domain.

Apologies for the delayed release notes. Currently travelling in the UK. So sunny! ----- The cf-release v212 was released on June 22nd, 2015 - IMPORTANT: Database migrations have been moved into their

I think with the CLI we could add clarifying messaging when using ssh what the current policy around recycling is. Eric, what do you think about calling it the "recycling" policy, enabled by default?

Hi Mike, I think I understand your use case. Currently route services are specced out such that they must, at minimum, function like a proxy. I think you're proposing that a route service could be a s

Yes, nginx is required. -Dieu

Hi Peter, Actually `cf restage` does cause down time. It will stop existing instances, stage the new app bits with the buildpack, and start new instances. It's possible that your app may start quickly

Yes, we think that with the initial scope of work for the v3 cc api that we'll have the primitives to be able to orchestrate a rolling deploy. In v3, we've already separated out the staging step so th

Hi All, cf-release 213 was committed to the master branch, but has some issues during deploy and should be avoided. There is a backwards incompatible ccdb migration that will cause cloud controller's

This repo is not officially maintained by the cloud foundry foundation. Due to that, it is not as actively updated to stay in synch with the cloud controller api as the cf cli. We do want the api to b

That's odd. I've fixed the link so it should be readable/commentable again. -Dieu CF CAPI PM

Very cool!

-1 indicates that the state of the instances is unknown. The CLI is purposefully converting the -1 to a ? to indicate that the state is unknown. wrote:

There are a few different approaches to this and different concerns that are possible. The requests I've seen have been around wanting to be able to subscribe to and filter the various events that cc

Hi All, I'm glad to see the interest in this feature. I think this feature is a cross cutting concern across a few teams. I can take this and work on framing the `what` and `why` of the problem and se

It is available in cf-release 212. There is a bug being worked on related to session stickiness [1] but if you are not using session stickiness 212 should be fine to use to take advantage of this feat