Thanks a lot Matthew and Amit, the document can now be publicly accessed/commented. Guillaume.

Hi all, I will not be able to attend the CAB meeting tomorrow, but I have added my notes to the agenda doc. MEGA has been/will be working on a bunch of exciting things, and I welcome

We're happy to see it. Thanks a lot, Warren. Warren Fernandes wrote ----- I'm not a ... noburou taniguchi -- View this message in context:

Hi all, Ramon, Fabien, are you both working on the same problem or is Fabien's response to Daniel separate from Ramon's original question? I couldn't understand Fabien's response. Did Daniel's help

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

Hello All, I have a resource pool , let say small_z1 - name: small_z1 network: cf1 stemcell: stemcell-xyz cloud_properties: instance_type: m1.small

Hi Michael, What do you consider "large"? In principle, nothing is stopping you from deploying a large cf deployment to your own OpenStack environment. When you say "seeing a large install version

Hey all, The router already has some health check behaviour -- you can naively register routes with it and it's smart about knowing whether to actually route traffic or not. I'd like to understand

The mysql and riak services register routes with this guy: https://github.com/cloudfoundry-incubator/route-registrar. At a glance, the option to run a healthcheck script to determine whether the

Curious whether there is any word on a possible time frame of seeing a large install version of CF on OpenStack. I saw in the comments section of a blog post

Hello cf-dev, *TL;DR*: The Cloud Foundry Buildpacks team is discussing whether, and how, to continue support for HHVM support in the php-buildpack. *Actions*: If you're a PHP developer, please fill

i think it's a great idea, but I would wait until the routing api goes live (waiting on consul stability) and use that tooling to create something re-usable. I think the job for that could have some

The GemFire service registers HA routes to our dashboard(s). For this to work correctly and have the gorouter honor session stickiness I submitted this pull request to

Hi all, Several components within cf-release, as well as many jobs in different releases, register a route with the gorouter: - *doppler* registers the "doppler" and "loggregator" routes - the

Hi all, The CF OSS Release Integration team (casually referred to as the "MEGA team") is trying to solve a lot of tightly interrelated problems, and make many of said problems less interrelated. It

juan i don't understand what you are trying to do. your node app should listen to the $PORT environment variable with a plain http connection. the load balancer you use for cloud foundry (HAProxy or

Hi James, I have just tested and I received this message: "502 Bad Gateway: Registered endpoint failed to handle the

The LAMB team added a chore to discuss how we can better manage a dropsonde_incoming_port on the metron_agent over here https://www.pivotaltracker.com/story/show/102935222 We'll update this thread

Final reminder for the CAB call tomorrow. See you at Pivotal SF and talk to you all then. Best, dr.max ibm cloud labs silicon valley, ca Sent from my iPhone

Ben, I guess I am working under the assumption that the current upstream schema is not going to see a terrible amount of change. The StatsD protocol has been very stable for over four years, so I