Hi, I occasionally have found this commit (included in v198 release) recently: https://github.com/cloudfoundry/cloud_controller_ng/commit/57f4c04cb49c67a8d9b128f72906e34d8782f547 The commit message

We are seeing some performance bottlenecks at warden, and at times warden drops all connections under increasing load. We think increasing this network and user pool_size might help. We have tried

So, I certainly like the idea of namespacing Diego specific properties. The job level granularity is excessive though. cf-release is also very old so a lot of its properties could be

we don't use 'saml' as a profile anymore. that is gone. if it exists in documentation we must remove it

change spring_profiles: saml to spring_profiles: default

Hi Filip, Thanks for the links. Here is what I did. Checked out UAA code from git. In resource/uaa.yml file I modified to reflect the use of SAML spring_profiles: saml In login.yml I have populated

Hi Kyle, The fundamental issue with not using Nginx is that all uploads/downloads block the cloud controller instance. A long blocking request to the CC can be a serious issue in any CF environment.

Hi, Mike, Thanks for the feedback! Responses inline below. We intentionally decided to namespace these component properties very early on in the development of diego-release: initially everything

What will be lost by not having nginx? I've had it disabled and haven't seen other problems before this.

I have created and used quite a few BOSH releases and the property namespacing feels very odd to me. I'm very curious to understand the reasoning behind it. I can't reproduce my 2048-bit key problem.

Since you won't be able to upload the blobs to the cf-release bucket, I'd suggest you capture the output of `bosh blobs` in your pull request. That command should enumerate all of the new blobs and

hi Erik any news on this? thx for your help G

hi does anyone faced the same issue ? it seems to be quite important thx ---------- Forwarded message ---------- From: Gianluca Volpe <gvolpe1968(a)gmail.com> Date: 2015-06-23 12:30

excellent. I can create domain to the private proxy that's included cf create-shared-domain apps.<ip of private_haproxy>.xip.io and then push my app to it cf push -d apps.<ip of

There is some IRC channels of freenode. #bosh, #cloudfoundry wrote:

Hi, all. I work on adding support of Power architecture to CF. During the work I needed to update not only cf-release, but existing blobs (postgresql, mysql client and etc.). I wonder how I can make

Hello All, Do we have any slack group for CloudFoundry developer? Best Regards, Pravin Mishra

Thanks Ning, Even we have tried the same approach (deleted unwanted file entries and kept v202 migration related files in schema_migration table) to get back to v202. but after that we were in v202

Thanks for the feedback. I'll let others comment on the bosh aspects other than to say that we are expecting people to use spiff to generate the manifests and that the decision to namespace properties

We will work on improving our documentation, SAML configuration is pretty straight forward. Here is an example of where I have 4 different providers