We've found NATS to be unstable under certain conditions, temporary network interruptions or network instability, around the client reconnection logic. We've seen that it could take anywhere from a fe

Hello all, We plan to remove support for v1 service brokers in about 3 months, in a cf-release following 12/31/2015. We are working towards removing CF's dependency on NATS and the v1 service brokers

Yes, we'd only be truncating the table backing /v2/events. This will not affect the tables backing /v2/app_usage_events or /v2/service_usage_events and thus should not affect billing. I'll clarify in

Try this endpoint [1]. I believe we added it at about cf-release v200. [1] http://apidocs.cloudfoundry.org/217/organizations/retrieving_organization_memory_usage.html aleksey.zalesov(a)altoros.com> wr

Shannon, the Product Manager for the Routing team, has this story [1] in the CF Routing tracker project for doing a PR to the CLI to add support for context path routes. Yes, that's correct that the c

Thanks Guillaume!

Yes, there are some differences in the approach from that document. -Dieu

Hi Guillaume, Just to ensure that it will be addressed, could you add it as github issues on the repo? Hoping to do another pass at the remaining open issues later this week. -Dieu

Agree with Zach, that for the CAPI team we would prefer to just wait for the routing-api to be ready before prioritizing work to change the way CC registers its routes. Dieu

Sure. I added a note in the note story to consider that request. -Dieu

Shannon recently pulled the story over into the Routing team's tracker [1] with the intention to submit a PR for it to the CLI team. -Dieu CF CAPI PM [1] https://www.pivotaltracker.com/story/show/9336

To follow up on this, I've been working with Simon Moser on an initial proposal for this and he is now taking lead on it. Simon just completed a PM dojo at the end of August. Dieu

Yes, I was just talking with Onsi and Mark Kropf about this yesterday and plan to submit a talk on this with Mark Kropf for cf summit berlin. I'll take on getting the proposal for isolation groups sha

Thanks Guillaume for the feedback. I've now gathered enough feedback to bring async operations out of the experimental phase and bump the service broker api version. I've added stories to the CAPI bac

Hi All, The CAPI team has created a style guide for v3 of the cloud controller api and would like to share this again with the wider cf community for feedback after initial review within the team. [1]

Hi John, I added a story for the upgrade use case [1]. I believe the use case of needing to move the dashboard_url end point that does not correspond to a service lifecycle event is trickier and is tr

Hi Guillaume, We are looking for a couple more pieces of feedback. All feedback I've received so far has been positive. There was one report recently from Robert Moss about being able to provide the d

I believe you need to enable it via the cli. cf enable-feature-flag diego_docker

Hi All, As we worked on better documenting how app usage events and service usage events work [1] in the cloud controller api, we uncovered that service usage events do not currently expire events. Th

What do you use for your edge load balancer? You could try to set up your edge load balancer to strip x_forwarded_for sent in the request and set it again before forwarding on. In that way, I believe