ok thanks for the extra detail. to confirm, during the load test, the http traffic is being routed through zones 4 and 5 app instances on DEAs in a balanced way. however the dopplers associated with

I am seeing logs from zone 4 and 5 when tailing the logs (*cf logs hello-world | grep App | awk '{ print $2 }'*), I see a relatively even balance between all app instances, yet doppler on zones 1-3

it simply means that there is a Service Broker, and works in conjunction with the "marketplace" so commands like "cf marketplace", "cf create-service", "cf bind-service" and related all work with the

Hi, When I run 'bosh deploy' , I got a error''Error 400007: `uaa_z1/0' is not running after update": *Started preparing configuration > Binding configuration. Done (00:00:04)* *Started updating

CVE-2015-3202 details: http://lists.cloudfoundry.org/pipermail/cf-dev/2015-May/000194.html CVE-2015-1834 details: http://lists.cloudfoundry.org/pipermail/cf-dev/2015-May/000195.html -- Thank

Severity: Medium Vendor: Cloud Foundry Foundation Vulnerable Versions: Cloud Foundry Runtime Releases prior to 208 CVE References: CVE-2015-1834 Description: A path traversal vulnerability was

Severity: High Vendor: Canonical Ubuntu Vulnerable Versions: Canonical Ubuntu 10.04 and 14.04 CVE References: USN-2617-1, CVE-2015-3202 Description: A privilege escalation vulnerability was

please note that this release addresses CVE-2015-3202 and CVE-2015-1834 and we strongly recommend upgrading to this release. more details will be forthcoming after the long united states holiday

john, can you say more about "receiving no load at all"? for example, if you restart one of the app instances in zone 4 or zone 5 do you see logs with "cf logs"? you can target a single app instance

https://github.com/cloudfoundry/cf-release/releases/tag/v209 https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/v209 Best, Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

We map our dea's , dopplers and traffic controllers in 5 logical zones using the various zone properties of doppler, metron_agent and traffic_controller. This aligns to our physical failure domains

This sounds cool. Can't wait to see what you guys come up with here. I've been thinking about the subject a bit, but haven't come up with any great ideas. The first thought that came to mind was a

Hi, all, The Runtime PMC met on Tuesday, 2015-05-19. Permanent notes are available at: > https://github.com/cloudfoundry/pmc-notes/blob/master/Runtime/2015-05-19-runtime.md and are included

the size of cf-release from 5.2gb -> 3.5gb! This is great news, good job buildpack team!

Hi, From the architecture point of view I understand that there are no service explicitly associated with CF. However, the following doc is very

yes, this has affected me -- Thank you, James Bayer

wrote: +1 and +1 Dan

The vcap-dev list used to use a Reply-To header pointing back to the list such that replying to a post would automatically go back to the list. The current mailman configuration for cf-dev does not

Warden explicitly disables access to the container host. If you move up to a more recent level of cf-release, that behavior is configurable with the `allow_host_access` flag. When that flag is true,

As far as I know, it is so by design - in order to setup a connection to the same host you need to explicitly tell Warden to allow external