Guillaume, We run the pipelines using the Docker image built from cf-release/pipeline-image/Dockerfile, which checks out the spiff repo and builds it, so it should be 1.0.6 since that seems to be

Thanks for letting us know! Long

Hi all, On Thursday, June 4th at ~noon MDT, the Loggregator NOAA[1] Library will introduce a backwards-incompatible change, after feedback from other teams and the community. The NOAA library is used

Steve, Until recently (cf-release v198), binding a syslog service required restarting the app. If you're post-v198, it *should* Just Work. However, one of the things that could be in your way is

Joseph, I just checked, and I indeed still reproduce the issue against the cf-release v210 branch with the submodule properly updated (including loggregator). What other info could be useful to

Hi Joseph, Thanks for your prompt response and the details over the current infrastructures covered by runtime pipelines. Great to hear the nfs template will be merged soon, thanks! I'm indeed using

+1 From: Nicholas Calugar <ncalugar(a)pivotal.io<mailto:ncalugar(a)pivotal.io>> Reply-To: "Discussions about Cloud Foundry projects and the system overall."

In that vein, it would be nice to be able to specify which characters constitute “special” and to have a list of disallowed characters. Josh Ghiloni Senior Consultant 303.932.2202 o |

Hi Sree, Not sure if this is possible, but maybe instead of requireAtLeastOneSpecialCharacter boolean, you could do minSpecialCharacters int (0-n)? This would allow more rigorous password

Hi All, The UAA team is in the process of implementing Password Policy feature <https://www.pivotaltracker.com/story/show/82182984> for users stored in UAA. The following properties around password

Hello, We are having problems draining log messages to Logstash. The drain is setup as a user provided service. cf cups logstash-drain -l syslog://xx.xx.xx.xx:5000 And then bound to the service. cf

Hi, all, Please be aware that the Diego team has recently identified a goroutine and memory leak in the Diego codebase for release 0.1247.0 that eventually affects the performance of Diego's receptor

Hi Guillaume, The metron_agent.deployment default can be found in cf-release/templates/cf-lamb.yml which should get merged automatically if using the generate_deployment_manifest script in

Please check the 'staging.advertise' of nats message https://github.com/cloudfoundry/dea_ng#staging sample command: bundle exec nats-sub

Hi, Thanks for the v210 announcement and the associated release note. It seems that the v209-announced introduction of a new mandatory metron_agent.deployment property did not make it into the

Resend the question. I deployed the cf into openstack successfully. However, I got failure when I tried to push my first php example. Starting app cf-php-demo in org system / space dev as

Regarding a) you could try having your services managed by Apache Brooklyn <http://brooklyn.incubator.apache.org/> it can auto- or manually-scale. I wrote a Service

Hi all, I got failure when I deployed the cf into openstack. Below is my current findings. The DEA and CC have enough resources (4G RAM, 20G disk). Any clues to debug? Attached debug.log.

shannon and team, thanks to all of those that worked on this proposal thus far! so many new workloads will be enabled by adding tcp routing for cf applications. i'm looking forward to the community

My 2 cents: Your database, while it's deployed in CF, it's based on MySQL. Depending on the configuration (YML file) you used for that release, scaling that database is strictly based on whatever