Will that solve the problem? BOSH will only take one haproxy out of service at a time but those clients that resolved the DNS name to the IP of the haproxy that is taken out of service for upgrade

In your case, 2 HAProxys with DNS configured to point at both.

Is it possible to upgrade cf platform with 100% uptime for apps. Let me give you an scenario of the platform: 1 haproxy 2 instances for gorouter, health manager 3 VMs for dea instances 1 instance

If by "hard dependency" you mean something that has to be up strictly before another thing for a deploy to possibly succeed, I'm not sure if there are any such hard dependencies. PCFDev (formerly

Hi Stanley, No physical memory is actually pre-allocated, it's simply a maximum used to determine if the container needs to be killed when it exceeds it. However, since your VM has some fixed amount

If you changed the app domain in your deployment manifest, it doesn't delete the old shared domain (since other apps might still be using that domain), it actually just adds a new shared app domain.

Hi Nick, Thanks for the clarification! But as a developer I would expect the restart/restage of the application fails if the environment variables is invalid. However, this is not the case always -

Hi everyone, I'm new to learning and understanding the CF architecture, and I realized when I downloaded CF 231, there didn't seem to be any Diego architecture as listed in the documentation online.

This is a proposal to add a new OAuth grant type in UAA to support a stronger authentication model. The proposal lists the two potential implementations for the same grant type. We have chosen to go

Nice work! This looks like an excellent client library. I'm glad it supports v2 and v3 apis. Any thoughts or plans for producing uaa and loggregator/firehose clients as well? Perhaps as separate

As some of you may know, the Cloud Foundry Java Client has gone through various levels of neglect over the past couple of years. Towards the end of last year, my team started working on the project

We heavy over commit our DEAs (like 4x) and we charge the customer the memory they've requested. But we also ensure our DEAs have in total some percentage of free memory on the DEAs just in case.

Hi Given a DEA with 15GB, overcommit factor = 2, total "memory" is 30GB. Ideally we can push up to 30 app instances per host, if each app instance requires 1GB mem allocation. Supposed the

Hi. I am in process of changing the domain name for a service broker. I managed to redeploy CF with updated deployment manifest and all vms which form the deployment are in running state. I can login

Hi Pradma, Sorry for the delayed response. You've accurately characterized the current behavior. One additional item to note is the error message accurately reflects which quota is not allowing new

Hi, Yep - we call purge only once. And that's why we need to disable it afterwards. It feels a bit odd to know there is an endpoint that is there to be called once. I wonder if we can add some

Perfect. Thanks Eric!

Hi, Benjamin, Yes, in addition to setting the runner and hm9000 instance counts to 0 in the CF manifest, those two CC properties should be all you need to change to make your CF+Diego deployment

Good catch. Created issue: https://github.com/cloudfoundry/buildpack-releases/issues/2 wrote:

Hey Mike, I think that sounds like a reasonable approach to the problem. I'm not aware of any other things that would change under that definition. Added Nick, the currently dojo-ing new PM for CAPI