Hi, I can share my experience on installing Diego on AWS. I followed the instructions for BOSH Lite

Great, thanks a lot for the links. -Dan wrote:

Hi, Are there any examples or docs on installing Diego with bosh/microbosh? Using the bosh-lite as a template, I'm tripping up on various parts. Is this even a valid direction in installing? Either

aaron, i added a page on the cf community wiki with your links: https://github.com/cloudfoundry-community/cf-docs-contrib/wiki/Mailing-Lists wrote: -- Thank you, James Bayer

looks like you already took what was going to be my advice and inquired on the maintainers of the services-contrib repo with an

i believe those files were removed since loggregator gives you access to the files (and you get get the content via syslog). you may be able to adjust the start command to write them out again. --

john, i think the resource files may grow forever right now without intervention. i'm pretty confident that when apps are deleted that their droplets are deleted with them and that proper garbage

How does that jive with offline buildpacks? Would it be a matter of the operator building it with a certain version of the binaries and then uploading them combined?

Ya, it doesn't seem to make a lot of sense to me to bundle the buildpacks with their typical binaries. Take io.js for instance [1]; prolly not required to change the buildpack as often as new

Shannon That's tremendous news. We look forward to working with the Services PMC. See you at CF Summit. Best Duncan -- Duncan Johnston-Watt CEO | Cloudsoft Corporation Twitter |

Hey Dan, You've nailed it. Yes, it makes a ton of sense to handle binaries as separate concerns, and we're heading in that direction. At one point very recently, we started doing some planning

Jack, You're absolutely right, it would be tremendous if it were possible to do this on the BOSH manifest level. I'm sure we'll get there eventually, but there is obviously quite a bit of work to get

Hi Wayne, Thanks for thinking about this problem. wayneeseguin(a)starkandwayne.com> wrote: Which operations did you have in mind? Currently the DEAs download *all* the buildpacks, so it won't save

Hi Team, I’ve been following the instructions to deploy CF found here: http://docs.cloudfoundry.org/deploying/ec2/deploy_aws_cf.html and when doing step 3, it takes a good amount of time. It

For my case, it turned out to be essential to reserve enough memory for "native" in the JBP. For the 2GB total memory, I set the minimum to 330M. With that setting I have been able to get over 2 weeks

Hi Lari et al, Thanks for your help Lari. David and I are pairing on this issue, and we're yet to resolve it. We're in the process of creating a repeatable test case (our most crashy app makes calls

Hi Daniel I found this cf(cli) completion https://github.com/cf-buildpacks/cf_completion bosh cli completion https://github.com/anfernee/bosh-completion Is my answer what you're hoping

Hi DevList, I think it would be extra convenient if there was Cloud Foundry auto-completion script that worked similar to the way git's

https://docs.google.com/document/d/10aOoLF_FPxuHYQfI813VCTF9z2VRC_dIuYDIGND3xbU/edit?usp=sharing Highlights: 1. Two projects were approved for incubation: Brooklyn service broker from Cloudsoft, and

Hi Ronak, We're trying to make sure we understand the question here - * Component logs do not go through loggregator today, only to the rsyslog endpoint designated. * All app logs would be