cf-dev@lists.cloudfoundry.org

Re: What ports will be needed to support hm and loggregator

He also probably listens for udp4 connections. Have you tried to allow udp4 traffic to ports 3456-3457 and check if loggregator collects the logs after it? -- Lev Berman Altoros - Cloud Foundry

By Lev Berman <lev.berman@...> · #339 ·

Runtime PMC - 2015-06-02 notes

Hi, We had a meeting for the Runtime PMC earlier this week. Notes available here: > https://github.com/cloudfoundry/pmc-notes/blob/master/Runtime/2015-06-02-runtime.md -Dieu

By Dieu Cao <dcao@...> · #338 ·

Re: Announcing Experimental support for Asynchronous Service Operations

i'm very happy to see this work delivered as the 60 second limit has come up so often as a pain point in the past. great job to all who contributed! -- Thank you, James Bayer

By James Bayer · #337 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

Finally, it works after I changed the configuration related to memory and disk for dea. < disk_mb: 2048 --- 1025c1029 < memory_overcommit_factor: 3 --- 1028c1032 < staging_disk_limit_mb:

By iamflying · #336 ·

Re: What ports will be needed to support hm and loggregator

We found the loggregator was listening on port 3456 and 3457 with upd6. udp6 0 0 [::]:3457 [::]:* But we can’t use ipv6 in our env. So is there any way to force

By MaggieMeng · #335 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

debug log sample

By Takeshi Morikawa · #334 ·

Re: UAA : Is anyone utilizing the Password Score Feature

On the Password Score feature, I haven't yet received any updates on whether its being used at all. Please let us know if anyone is using the same. Thank you Nick/Steve/Josh for the feedback !! I

By Sree Tummidi · #333 ·

Re: Release Notes for v210

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

By Guillaume Berche · #332 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

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,

By iamflying · #331 ·

Re: getting the cf version from the api

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

By Dieu Cao <dcao@...> · #330 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

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

By iamflying · #329 ·

Re: getting the cf version from the api

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

By Takeshi Morikawa · #328 ·

getting the cf version from the api

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

By Naga Rakesh · #327 ·

Service offering testService not found

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

By Supraja Yasoda <ykmsupraja@...> · #326 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

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

By iamflying · #325 ·

Re: Syslog Drain to Logstash Problems

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

By Josh Ghiloni · #324 ·

Re: Staging error: no available stagers (status code: 400, error code: 170001)

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:

By iamflying · #323 ·

Re: Announcing Experimental support for Asynchronous Service Operations

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

By Onsi Fakhouri <ofakhouri@...> · #322 ·

Re: Announcing Experimental support for Asynchronous Service Operations

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

By Chip Childers <cchilders@...> · #321 ·

Announcing Experimental support for Asynchronous Service Operations

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

By Shannon Coen · #320 ·

Messages