Hello, all By default, there are about 20 VMs will be used in cf/diego installation. I am trying to minimize the VM size. I tried to follow https://github.com/cloudfoundry-community/cf-boshworkspace

Hey cf-dev, Completing the work from CF v231 to extract the buildpacks to a separate release, the java buildpacks have also been extracted as of CF v232. As before, the new release is submoduled

Thanks Nicholas, Please let me know when you have an update on this. Regards, Muhammad Altaf Software Development Engineer Fujitsu Australia Software Technology Pty Ltd 14 Rodborough Road, Frenchs

wrote: Yeah, I acknowledge that it's a significant impact, and I regret that we weren't able to come up with an easier way to do it. However, in order to make a material difference in how difficult

Is there still somebody out there using spiff? Then you might be interested in some good news... End of last year I've started to take a look into the source code. After providing some major fixes

Since November 2015, the [nodejs-buildpack](https://github.com/cloudfoundry/nodejs-buildpack) has been packaging binaries of Node.js® with OpenSSL that are statically linked. With [community

Hi Muhammad, Unfortunately, we don't have an environment using keystone v3. We are passing the configuration to fog as-is. There are several fixes that have been made in later releases of fog, for

Hi Dan Check with the bosh cli options rgd the vms and status check.

Hi, Dan, It may be a regression in the CF CLI: in my check against one of the Diego team environments, that stack field is consistently absent after the initial push with CLI

Great question, Dan. I'm curious to this as well - I just assumed it took some time to report back the status. -- Ed Mikuszewski *| * <http://www.pivotal.io> *|* Mobile: 646-628-2872 *| * Email:

Quick question, when I push an app to CF I get this output at the bottom after the app starts. ``` requested state: started instances: 1/1 usage: 256M x 1 instances urls:

I have further information the to 403 error. internal_error.log states: "2016/03/16 12:05:00 [error] 20579#0: *105 directory index of "/var/vcap/store/shared/" is forbidden, client: 10.10.0.104,

Hello, I am facing some problems with the cloud_connector on cf-release 231. I suspect the problem has something to do with the blobstore configuration, but I can't figure out what's wrong. I want

Hi, Fillip, here's decoded token { doesn't contain scim scope -- Regards, Yitao

Hello Rob, sure...i will post to the other thread. Thank you for your answer.

Hi Raymond, It is possible to use FUSE-based clients to connect to remote filesystems, but only if your Cloud Foundry deployment has enabled privileged containers. We are currently working on adding

Hi Austin, We are not sure which docs you are referring to - can you clarify this? Cloud Foundry is available as a bosh release at https://github.com/cloudfoundry/cf-release - this includes the

Hi Austin, We are not sure which docs you are referring to - can you clarify this? Cloud Foundry is available as a bosh release at https://github.com/cloudfoundry/cf-release - this includes the

Can a cloud foundry application make us of Network Filesystem share? If so, would this scale? Thanks, Raymond

Giovanni, A github issue was opened by others with similar issues at https://github.com/cloudfoundry/cf-release/issues/923. Could you take a look at our suggestions there and, in the interest of