Thanks for the answers Since I had different other problems this morning, I destroyed the virtualbox and started from the beginning. And now it magically works No idea what I did differently..

What exactly do you mean by this? Please be specific about where your running this from. If you're not running it from inside a container, it's not an accurate comparison. It's good to know that it

Hello Natalie & Mikhail, FYI, am trying to deploy Cloud Foundry on vSphere. I have shared the Manifest too with this mail. Thanks..

Hi, Tom, Thanks for all the diagnostic data! It looks like the actual size of the btrfs volume (the 'Device allocated: 17.79GiB' line from the btrfs tool output) is quite close to the total size of

CF team is already working on that it's call "isolation groups" (before was placement pool). Maybe Amit, James or Dieu can give you more information about that. Thanks.

To be clear, there are other reasons that error occurs, such as when the stack you requested is not available on any cell. But often it points at a failed deployment.

Hi, Currently, DEA can specified to a "zone", and Cloud Controller can schedule APP instance according to

"found no compatible cell" is the error you will get when all diego Cells have failed to deploy. Start by double checking that the cell is up and running via `bosh vms`. -Ted

Hi, Christian, Thanks for asking. From what you've described, it sounds like Cloud Controller is able to tell Diego to run the app, but the app instance isn't getting placed on a cell. It's probably

Hi, all, If you've tried using the 3126 Warden stemcell for your CF and Diego deployments to BOSH-Lite, you will likely have discovered that Diego doesn't deploy correctly. As it turns out, there is

On the CAB call Dr. Nic asked about support in the routing tier for connection draining. I asked him out-of-band to elaborate, then realized this was a topic the community might be interested in. Nic

Hi all, Here's an update on this topic and the design discussions Assk, Ben and I had in the last few days: I'll start with a description of the problem we're trying to solve here: Abacus currently

Hi, I tried with the lower as well as higher limit, but the instruction is keep hanging and no packets recieved. ubuntu(a)test:~$ ping github.com -M dont -s 1400 PING github.com (192.30.252.131)

Hey Deepak, I found that you provided some more information about your problem on Github: https://github.com/cloudfoundry/cf-release/issues/823 Was there any message from the ping about why packets

Have you checked the control script logs in the `/var/vcap/sys/log/` folder? If the jobs are failing to start that's a good place to start. If you send them to us we can tell you more. Also, what

Hi Daniel, I tried curl -vv https://github.com/cloudfoundry/java-buildpack/ from the instance(on openstack) where CF is installed and that works. Regarding offline buildpacks, CF already has offline

Hi Eric, Thank you. I am responding below with what I have available. Unfortunately, when the problem presents, developers are down so the current resolution is recreate cells. Looking at one below

Yes Will, that summary is essentially correct. But, for even more clarity let me restate the complete story again and reason I want 92085170 to work across stemcell upgrades. :) Today if NATS goes

Hi. I am trying to integrate with application(Java/Spring) authentication with an SSO through Kerberos. Has anyone done this before, I am using tomcat 8, openjdk 7 with java-buildpack version 3.0.

Hi Mike, What I think you're saying is that once the new `prune_on_config_unavailable` property is available in the router, and if it's set to `false`, there's a case when NATs is not reachable from