Dear CF Community, Over the next few weeks, the Diego and Buildpacks teams will be working together to extract a new BOSH release for the cflinuxfs2 rootfs/stack out of the Diego BOSH release. The

Great! Any info on the rumored post Summit Bosh event? Mike wrote:

Hi all, Registration is open for the upcoming CF Summit North America, and we have a limited number of free passes for contributors to the project. This code can be used by anyone that is a

Its to support https from CC to DEAs for staging and starting instead of relying on NATs. - Michael

Good question Long, I am wondering the same .. also its creating trouble in resolv.conf Thanks and Regards Amulya Sharma wrote:

Anyone know why consul is running on dea runner machine? it looks like its for a healthcheck

Hi, New to CF. I need to store some large objects in S3 storage. When i bind S3 storage to an app, it gave following binding System ENV. 1. host 2. AccessKey 3. SecretKey AWS

Hi, Stanley, If you're looking to reduce the Diego VM footprint in a dev deployment, you could consider using the 'colocated_vN' (N=1,2,3) jobs in the manifests generated by the spiff-based scripts

Hi Amit I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times. But now, I am getting timeout errors while compiling buildpacks once in rootfs or in buildpack_java or in

Dear Nicholas, if desired, we can also do a PR for allowing the CC to connect to Swift using Keystone v3. A couple of months ago we did the same thing in the OpenStack CPI. We also have some test

after a lot of investigation, we found out, that it was simply a "duplicate domain" problem cause we set system_domain and domain to the same value. so this is solved.

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