Hello, I deployed an application to Diego, found this application often got restarted, there is no error message in the log, just found the following message, what does the status code 255

This issue has been resolved in https://github.com/cloudfoundry-incubator/cf-routing-release/issues/28, the root cause of this issue is that cf cli caches RoutingEndpoint in ~/cf/config.json so do a

Hello, I have a nodejs application, it can be deployed and started in CF if the version nodejs buildpack <v 1.5.9, the version of node and npm in package.json of my nodejs application is as

Hi Am 28.04.2016 um 23:08 schrieb Mike Youngstrom: +1 for that proposal. A 404 also causes issues when crawler remove pages from their index. A 503 has less side effects. I would also prefer a 503

Hi all, Giving everyone heads up about changes in manifest property for 'haproxy' job. We are merging what are now two separate properties for configuration of the router static ips into a single

Hi Eric, forget my preceding messages. I had to add and bind the security groups. Now it seems to work. What if I have a username/password protected registry? (https, self signed certs) Where do I

Hi Stanley, We attempted to reproduce this behavior on bosh-lite and were unable to, which leads me to believe the issue might be in some middleware. Are you using the provided java buildpack or a

Yes, I haven't deployed cf-routing-release, I just deployed cf-routing-release, but meet a new issue, when I run command "cf router-groups", the following error is shown: FAILED This command requires

Hi Eric, thank you for your kind and comprehensive answer! Regarding point 1) I still have problems. Our internal Docker registry is configured with HTTP, a self signed certificate, no user and no

Hi Eric, thank you for the kind and comprehensive answer! Regarding point 1, I still have some difficulties. Our internal Docker repository is configured in HTTPS, self signed certificate, no

they fixed in the community haproxy release see https://github.com/cloudfoundry-community/cf-haproxy-boshrelease/pull/21 it would be nice to implement this as well in the haproxy in cf-release

hey all, v256 bosh version fixed a long present bug with mutation of properties between colocated releases. it was not easily noticeable since most of the time properties are not mutated as part of

Danny, Some additional related use-cases: 1- our corporate CF platform provider is willing to scan content all apps pre staging and post-staging. For instance, in order to black list

Thanks Shannon for your reply and the accurate summary of my proposal. for maintaining routes with no backends in the routing table. I think some use-cases I detailed previously (reproduced and

Here is another minor use case. My users are often confused that a stopped app returns a 404 instead of a 503. So, we implement that functionality for the user using an app mapped to wildcard routes

OpenWhisk may be what you are looking for. Mike Jacobi / Altoros

Hello Guillaume, Thank you for sharing your thoughts on these use cases. I can see how having a route service field requests for an app, whether the app is up on not, could be useful. However,

Hi Sam, To be sure about why the router_z1 VM is failing, you would want to look at the "monit summary" of the processes running on the router VM to see which one is failing. Then, you could look at

This was fixed in [1] CF-234: WebDAV blobstore supports long system domain. Thanks, Nick [1] https://github.com/cloudfoundry/cf-release/releases/tag/v234

Thanks for asking, Marco! Some responses inline below. it-services(a)marcoristuccia.com> wrote: If your internal Docker registry is accessible by IP or DNS from within your CF/Diego deployment, you