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

Hi Hristo, Correct me if I'm wrong but it sounds like you are calling purge multiple times. Am I misunderstanding the work flow you are describing? Purge should only be called only one time EVER on

Indeed I scripted a couple of « bosh create release » / « bosh upload release » and then bosh-workspace is happy with it. It worked like a charm. Buildpacks just end up being there, automatically

I did cd cf-release git fetch origin git checkout develop git pull --ff-only ./scripts/update bosh create release --with-tarball And also cd src/buildpacks/binary-buildpack-release/ git fetch

And btw Amit, it looks like the java-buildpack v3.6 is here with its

No no no, these are not SHAs of cf-release, but those of all the buildpack-releases indeed. Looks like no blobs of these releases are actually available online, are they? I'm running the standard

Sorry for the late response. I didn't get a chance to try again until today. It turned out by setting require_https to false will let me run "cf login". Properties uaa + require_https:

At the time of the email, the java buildpack hadn't been extracted into a separate release yet. I believe it has now, and that will be reflected in CF v232. What command did you run? What SHA of

Amit, just for me to be sure, why didn’t you list the java-buildpack? Also, have the blobs properly been uploaded? I copy below the BOSH errors I get: With binary-buildpack: Uploading

Hi Ning, 1) I think you'd better open another terminal and run `cf logs (appname)` while pushing your app. 2) If you know something about buildpacks (especially about the 3 major steps -- detect,

Yes, it's one way but it's not flexible, and scale app need to restart the app as well. As I said I may have some heavy operations which will definitely need more than 2G. In my opinion the ideal way

Thanks for the answer Marco! (I realize I'm much influenced by the Percona vision, because they are active here in Paris dev communities.) I finally upgraded to v26 and well.. Congratulations for the