+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

Saw your talk yesterday...this is a very clever idea and one we will be investigating for sure. Thanks for sharing!

The apiserver, listener, shredder, analyzer all produce standard Go metrics which really don't tell you much as to the "health" of hm9000 other than the processes are up. The metrics that are

Hi Simon, We use OpenStack Swift with Keystone v3 and a non-default domain. I'd just like to confirm you're planning to support that configuration too? Regards, Dies Koper Fujitsu Sent: Wednesday,

The CF CLI team just cut 6.18.1. Binaries and link to release notes are available at: https://github.com/cloudfoundry/cli#downloads I have met some of you at the CF Summit in Santa Clara this week.

Maybe you should contact the pivotal support. https://support.pivotal.io/ wrote:

We're currently in the middle of the CF summit and during our presentation about the 5 years of Cloud Foundry in Rakuten we shared how we (ab)use the stack mechanism to provide application placement

Hi I am deploying Cloudfoundry on vSphere, I am getting some issues configuring PCF autoscalling using DEA. Has anybody encountered this issue ever ? If so can anybody please share ?

Ah, gotcha. +1 to that.

Agree on all counts. We've already suggested vendoring the gems inside the buildpack to ensure they're there on the staging container. I'm now suggesting that the bin scripts just can't find the

It's not an issue of pointing to the gems. The build pack runs (staging) in it's own container. The container is completely isolated from the DEA or Diego Cell where it's running. You can't access

Thanks DHR Team. Yes your correct like the required gem is not available in staging container stack. but these stacks are pre packaged in cf release. Not sure how we can do this Gem.path update for

Thanks a lot DHR team.. Let us try out this approach . Regards Lingesh M