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

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

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

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 |

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

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?

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

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. --

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

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

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

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

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

Thanks for the continued advice. We’ve hit on a key discovery after yet another a soak test this weekend. - When we deploy using Tomcat 8.0.18 we don’t see the issue - When we

Hi, I have posted a sample BOSH deployment manifest to Gist. https://gist.github.com/ozzozz/4c08c37863b703a75afc I could deploy cf-release v207 and diego-release 0.1099.0 to AWS Tokyo region by

fyi. Tomcat 8.0.20 might be consuming more memory than 8.0.18: https://github.com/cloudfoundry/java-buildpack/issues/166#issuecomment-94517568 I think adjusting memory heuristics so that they add up

Not sure if this is what you need, but you can manually sync + delete files from a local filesystem (including NFS mount) to/from S3: http://s3tools.org/s3cmd-sync ... with `—delete-removed`

Hi all Thanks. No I was just curious if there was a way to identify what to remove in the blobstore because I was surprised the size of my blobstore at this point. I will check what's in there (maybe

An option could be to just delete all the resource files on the blobstore. The effect would be that for binaries that would have been matched, they would be uploaded again on the first new push

Hi Ken, How do you generate the manifest file? Thanks Best Regards~! Grissom