Hi, Congratulations for this v26 release! Do you have any documentation for the benefits and trade offs introduced by this new arbitrator, compared to the standard 3-nodes setup? What happens to the "

Hi, I'm no expert but “monit” is a component of BOSH, not Cloud Foundry. Your question would get answered if asked on the “bosh-dev” mailing-list. Cheers

Hi cf-dev, For a fresh new deployment of cf-release <https://github.com/cloudfoundry/cf-release>, I wonder how the default manifests stubs and templates should be modified to remove unnecessary suppor

That's right Amit, but it was just a typo by me. I meant setting instances counts to zero for “runner_z*” and “hm9000_z*”. I saw in a-detailed-transition-timeline that those two properties are also of

I suggest you manually “cf scale -m 2G“ after your app has booted. Type “cf scale --help” for more info.

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

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 'binary-buildpac

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 midd

And btw Amit, it looks like the java-buildpack v3.6 is here with its fellows: https://github.com/cloudfoundry/buildpack-releases/blob/master/java-buildpack-release/releases/java-buildpack-release/java

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 upda

Perfect. Thanks Eric!

When I read "decrease the VM size" I guess you might be using BOSH-lite. Then you could be interested in switching to microPCF which has a smaller memory footprint. /Benjamin

Hi Eric, Facing the pace of cflinuxfs2 updates, I've done and successfully deployed such a BOSH release. It also ships with example manifests. I'll share it with you this afternoon. I've been using a

Ok sorry for the delay, I was listening and chatting with Josh here at Paris Spring Meetup. That was really cool. Anyway, here it is : <https://github.com/bgandon/rootfses-boshrelease <https://github.

And here is the README! https://github.com/bgandon/rootfses-boshrelease/blob/master/README.md <https://github.com/bgandon/rootfses-boshrelease/blob/master/README.md> I took the chance of upgrading to

Very great news! As BOSH doesn't support multiple CPIs, does this mean that people need a separate BoshWin to manage Windows deployments, along with the normal BOSH for classical Linux deployments? /B

Hi, Sorry for the late up, but would this hit bosh-lite too? Because after it has run for a while, I’m experiencing severe similar issues with the 53 garden containers I use in Bosh-Lite. Config : - B

Hi cf devs, I’m running a CF deployment with redundancy, and I just experienced my consul servers not being able to elect any leader. That’s a VERY frustrating situation that keeps the whole CF deploy

Very neat! Thanks a lot Eric.

Actually, doing some further tests, I realize a mere 'join' is definitely not enough. Instead, you need to restore the raft/peers.json on each one of the 3 consul server nodes: monit stop consul_agent