Makes perfect sense. I really like the NoRouter because of its simplicity. I really hope CloudFoundry adopts it and makes it part of its official release so that NoRouter stays in step with GoRouter

The issue was likely the disk. The staging_disk_limit_mb tells the cloud controller how much disk space is needed for staging an app (unless the app asks for more). This is normally much higher than

There is currently no way for users to rotate the cc.db_encryption_key. We're going to schedule some work to look into ways to solve the problem without downtime. Any input would be great, as well as

We are also very interested in pursuing this capability. Cheers, Christopher Ferris IBM Distinguished Engineer, CTO Open Cloud IBM Software Group, Open Technologies email:

There are a lot of Keys in my CF deployment manifest. I'd like to be able to rotate them. Most of the keys I could probably just change in a deployment but would cause some downtime or a service

I believe the full crashed Warden container is kept around for an hour. The DEA keeps the Warden handle to the container. The Warden grace time only applies after all handles have been

Thinking a little more about your question Mohamed. In his presentation Mike might have made reference to people making adhoc changes to F5. In our organization today we have a handfull of engineers

Mike, Thanks for finding that. I've filed a bug <https://www.pivotaltracker.com/story/show/96801752> to get the README fixed. – John Tuley

I don't have an answer, so here are some diagnostic questions to help you debug: Have you set doppler.blacklisted_syslog_ranges to something that includes your destination? (This would be bad.) Do

We had the same problem due to missing templates in our manifest. We initially used the example manifest snippet shown at https://github.com/cloudfoundry/loggregator which mentions only the doppler

Ok. Just a question: When you say "the DEA will keep its container carcass around for an hour", you mean that the DEA does not remove the container files. However, if Warden grace time is configured

Thanks for responding Mohamed. Help me understand what you mean when you refer to opening up the LTM to developers. NoRouter itself must have access to the LTM to update app pool members and such

Interesting. Do you get log output from the application when it's working? I'm curious because you weren't seeing this when it was failing. Trying to understand if the app is not logging properly or

I removed static assets as well as many classes that were not used, I left classes related to jetty, javax (managment, ..), apache commons io, and the package (with all classes) where the main class

Hi Pablo, Ops Metrics is a PCF product and questions about that should be directed to Pivotal customer support. Regarding your second question, about the difference between crashed indices and

Apologize for restarting this thread after a few weeks. That's right Mike. Once the LTM opens up to the developers they might start putting in too much functionality into the Load Balancer like

Interesting. Out of curiosity what did you remove to make it smaller? Static assets? Also have you tried a larger CF install like PWS / BlueMix, just to see if this is an issue specific to

Hi, I had to reduce the size of the jar to ~ 51M to get the simple class that runs jetty to work on bosh-lite!!! Is there any kind of size restriction for executable jars?? Here is the system

daniel.jones(a)engineerbetter.com> wrote: Seems odd. Every time you stage an app, you should get a copy of the latest app bits (i.e. what was pushed up by cf). If you're not getting the latest set

Good morning. Recently, I have been revising metrics emitted by CF components. In order to understand HM9000 metrics, I have been reading the metrics documentation (at