Joseph, Double checking after a good night of sleep, my last check was wrong (reviewing the diff, I had checked for presence of jobs properties, and missed at the bottom of the file for the presence

I got the nats message on 'staging.advertise'. It has the enough resource. but it seems not correct. And it also cannot explain the error - Server error, status code: 400, error code: 170001,

There's not currently a way to determine this exactly. As Takeshi suggests the api version is the closest thing, but it does not get bumped every cf-release. -Dieu CF Runtime PM

From the source code /var/vcap/packages/cloud_controller_ng/cloud_controller_ng/lib/cloud_controller/dea/app_stager_task.rb:26, it seems there is no enough for memory or disk. def

I was just thinking of the same thing. http://cf-api-checker.mybluemix.net/cf/version/ http://cf-api-checker.mybluemix.net/api/version/ I tried to check in the following ways: STEP1: check api

Hello, I wanted to know if there is a way to determine CF versions dynamically/ from API. Thanks, Venkata

Hi, I have deleted service broker by removing service instances. I created again but now I am unable to enable-service-access to Service. I get error "Service offering testService not found". When I

attached the deployment manifest. This is generated by spiff and then I modified it. wrote:

We’ll check that, thanks! Josh Ghiloni Senior Consultant 303.932.2202 o | 303.590.5427 m | 303.565.2794 f jghiloni(a)ecsteam.com<mailto:jghiloni(a)ecsteam.com> ECS Team Technology Solutions

attached the deployment manifest. cf-deployment-single-az.yml <http://cf-dev.70369.x6.nabble.com/file/n290/cf-deployment-single-az.yml> -- View this message in context:

Well done Services API! This is an awesome milestone! wrote:

Awesome news! Long time coming, and it opens up a whole world of additional capabilities for users. Nice work everyone!

On behalf of the Services API team, including Dojo participants from IBM and SAP, I'm pleased to announce experimental availability and published documentation for this much-anticipated feature. As

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."