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

Okay.. Let me try with it.. Thanks..

Subnet ranges on which your other components are provisioned. allow_from_entries: - 192.168.33.0/24 wrote:

Hello Ronak, Actually, previously i have given the values for ALLOW_FROM_ENTRIES, after seeing some mail groups only i changed it to NULL. Could you tell me which IP i need to give

Hi Parthiban, In your manifest , there is a global property block nfs_server: address: 192.168.33.53 allow_from_entries: - null - null share: null allow from entries are

Thanks Amit for your faster reply. FYI, I have shared my deployment manifest too. I got struck in this issue for past couple of weeks. Thanks..

Hi Parthiban, Sorry to hear your deployment is still getting stuck. As Warren points out, based on your log output, it looks like an issue with NFS configuration. I will ask the CAPI team, who are

Hello All, Is there anything i need to change on my CF Deployment Manifest for the deployments or not? Could you please help on this to solve? Thanks. wrote:

Hi Rajesh, Not if you don't make it aware. Only the broker gets registered at the router, then it gets registered at the CC. When containers are created (on request of the CC/broker, by the Docker

+1 having this pluggable scheduling feature ! -- tcnksm 2015年11月14日(土) 6:55 Deepak Vij (A) <deepak.vij(a)huawei.com>:

Hi I installed bosh-lite on my mac according to the docs on https://github.com/cloudfoundry-incubator/diego-release That worked all fine, I can deploy apps without diego enabled and they run as

I have a few questions on the Bosh release for Docker https://github.com/cloudfoundry-community/docker-boshrelease The documentation says: There are 3 deployment scenarios for this BOSH