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

Glad to see there’s interest! Yes, you can turn both cf and diego releases (along with garden-linux-release, etcd-release, etc.). We haven’t published the examples yet - we’ll probably create

Nice! Love the alphabetizing. That issue was a long time in coming. :) Mike wrote:

+cf-bosh mailing list it-services(a)marcoristuccia.com> wrote:

Thanks for the presentation yesterday and for posting your slides. Very creative idea on leveraging stacks for "placement pools". We're going to see if this makes sense for some of our use

Hello Vlad, that's a great news! So both cf and diego releases can be turned into docker containers? Could you please be so kind to tell me what where you will publish such examples, so I can keep

Good job. wrote:

I have cloud foundry deployment .I have 3 kafka,3 zookeper and 3- vault/consul instance. kafka/0 10.20.0.174 zookeeper/2 10.20.0.242 vault_consul/0 10.20.0.247 For testing purpose i delete one of

I just saw this tool @ CF Summit. Congrats, really cool thing you just made! 2016-05-25 14:05 GMT-03:00 Vlad Iovanov <viovanov(a)gmail.com>: -- Mis mejores deseos, Best wishes, Meilleurs

Hello Marco, We've just released a tool that can help you deploy Cloud Foundry as Docker containers. It's called fissile - https://github.com/hpcloud/fissile It turns Bosh releases into Docker

Hi all, is there any way to install CF with Diego without using BOSH at all? For example, is there a documented procedure to manually install and configure each CF role on a pre-deployed set of Linux