Hi all, Operating multiple Cloud Foundry instances can be a hassle, so I made cf-plex: https://github.com/EngineerBetter/cf-plex It's a shim that manages a list of Cloud Controllers, and runs the

We've migrated once from one vsphere to another one. We created a new bosh with the same network config on the target vsphere and created a new manifest for this bosh with an instance count of zero

Oops! My bad! I hope all CF Summit attendees who travelled from far have recovered better than I have. For those who couldn't attend, I assume recorded presentations will be available soon, but while

Hi Takeda-san, all Attached our slides presented at the CF Summit. Regards, Dies Koper -- Dies KÖPER Manager Cloud Solutions Fujitsu Australia Software Technology Proprietary Limited T +61 2 9452

If I deleted all deployments, I can see "30G ./ephemeral_bind_mounts_dir" is released, but "21G ./disks" is still there. And after deploying new cf/diego on it, the "disks" size keep increasing after

What I did on this VM is just delete/create APPs and services.

Hello, all I am having a bosh lite VM for testing purpose, and it's running out of space after several days. And comparing to a new build, I can see the disk is used by "warden_cpi" the clean

Just an idea... Is there a feature in Tracker to always cc someone/some email address? For non security and non confidential stories we can Cc this email address automatically which will post to a

Dear Dan, dear Lisa, dear Chip, dear community, sorry for digging out this old issue again and again. If you are just tuning in, here is the situation · I like Pivotal Tracker as a

You should not copy any of the etcd data (neither Diego's etcd cluster, nor the etcd cluster used by Loggregator and Routing components). It's not only unnecessary since CF is designed to seamlessly

We're just starting a project to migrate a CF deployment onto a different cloud platform, including moving a new blobstore cluster (Swift to Swift), and wanted to see if there are any tips on the best

Hi Guillaume, This request is more about making sticky app and sticky session (instance) 2 separate things. I'd assume that sticking instance would always go to a specific instance of an app (by

[Retrying with less typing errors, sorry] +1 for app stickyness when a route is mapped to multiple apps, and sticky sessions are requested (currently through jsessionid cookie). I'd even suggest

+1 for app stickyness when a route us mapped to multiple apps, and sticky sessions are requested (currently through j session is cookie) I'd even suggest that app stickyness is the default when

Yes, thanks for the clarification Mike. Shannon Coen Product Manager, Cloud Foundry Pivotal, Inc.

Hi Shannon, Good question. I haven't really considered an app initiating this but I think that could work. The ultimate use case for this, in my mind, is to eventually support transitioning http

Hello Mike, I thought I'd put this on the list in case others have similar use cases. At summit you mentioned an interest in a variant of sticky session behavior, and I wonder if you could provide

Jim, First of all, thank you for the opportunity to talk doing the summit! As promised, here is a brief recap of those two pieces of feedback I shared, plus one additional note that we came up with

Hi Marco, I think as long as you consider Docker and thinks like Compose, Kubernetes to fit production environments, you should be fine. What we’re doing is repackaging the releases in a different

Thanks Vlad, just a quick question helpful for my forecasts. We are evaluating CF for our production environment and we need it in a few months. Do you think that this solution will fit a production