We have several use cases - in time event processing for usage, with notification instead of polling we'll be able to keep up better, getting closer to real time for metering, and thus rating and

I don't see anything on Twitter about this. Any objections to tweeting this news? Is there a potential blog post for the CF blog here? Best, Stormy wrote:

Quick update on inception meeting. To accommodate our friends and colleagues from Europe who would like to attend, let's plan to move the meeting to 10a to 12:30p with the option of lunch after at

the way down to app developers increases the cognitive load for folks using the platform. Enabling/disabling it on a per-installation level, and - maybe - a per-space level, might be a decent

Hi Pramod, Still TBD - we're driving hard for a Diego GA first and will then evaluate the various priorities and scope them out. Onsi wrote:

That's still very much open for discussion. Obviously, someone with administrative privileges should be in charge of this particular piece of configuration. Also making this a runtime config (e.g.

Hey Colin, Good stuff. I like to draw a circle around the rootfs, the buildpacks, the generated droplet, the Task/LRP recipes, and the lifecycle binaries that run inside containers to stage and

If not FUSE, what is the timeline/status for support of mounting persistent volumes in Diego natively(remember seeing a talk in cf summit on floating/fixed volumes)? Pramod wrote:

Once - configurable on a per-app, per space, or per deployment basis? -- -- Matt

For me the primary use case to developing management tools on top of the CC API, and being able to intelligently cache information about the state of those resources. Without etags or serial numbers

Hi All, I wrote a couple of articles about droplets and stacks. http://www.cloudcredo.com/a-droplet-of-value/ http://www.cloudcredo.com/stacks-of-problems/ The droplet post is fairly

Hey all, Based on the feedback we got and the relatively low cost to maintain privileged support we'd like to propose making running privileged containers on the platform configurable - we will

Now I see what that means. Each line of a multiline log message could be sent to a different logstash server. Definitely problematic. Especially with the ephemeral nature of the CF logs there needs to

fails, as exp reads 1438228276 most likely your client does not have the access token validity setup correctly. See the test case I posted that validates my

Good. But my apologies. Assume: creation time = 1438184877 access token validity (set by me) = 315360000 exp is expected to be 1753544877 when decoded. Unfortunately, this test fails, as exp reads

For us the main use case is security auditing to keep a long term record of who has done anything. In the case of our Security team rather than use CF events directly they preferred to have events

Thanks Steve. Though I'm no logstash expert I assume this won't work if you have multiple logstash machine's doing filtering like Simon mentioned right? Same is true for us with splunk if you are

when decoded to read exp: 315569260. If this is not, then is it possible to set the token expiry time? It's a little bit different. access_token_validity is how long the token is valid for from the

Thanks again Filip. However, here's what I mean, If I set the access_token_validity to 315569260, I'm expecting the token when decoded to read exp: 315569260. If this is not, then is it possible

Here's a suggested pattern to handle stack traces. http://stackoverflow.com/questions/31657863/logstash-and-multiline-log-entry-from-cloud-foundry?noredirect=1#comment51279061_31657863