Hi, We have not moved over to DIEGO yet. In the DEA execution world, is there anyway to segment Apps such that certain apps go to a particular set of DEA agents and certain other apps go to another

Hi, I want to use external s3 compatible blobstore with bosh-init deployment - for that I provided the required configuration in bosh-init.yml manifest file (mentioned blobstore config below) -

Can you clarify what you think is an internal site? Both the links Dan sent; http://apidocs.cloudfoundry.org/234/apps/get_detailed_stats_for_a_started_app.html and

Oops, replied too quickly. Looks like that's an internal site. Is there any external-facing documentation equivalence?

Thanks Dan!

Hi Don, The stats endpoint <http://apidocs.cloudfoundry.org/234/apps/get_detailed_stats_for_a_started_app.html> gives statistics about each instance individually. In the returned JSON object, each

Someone recently asked me about the data returned from /v2/apps/<APPLICATION_GUID>/stats, regarding whether the stats returned were a total across all instances of the application. I assume that they

Auto-migration does happen, but at some point we end support for certain versions. Upgrading to 211 will automigrate your Postgres to 9.4.2. Upgrading to 230 will automigrate that to 9.4.6.

Hi, Amit Thank you for you explanation. I will try this process out. However I would suggest to take auto migration as consideration for next time upgrading any CF component. Regards, Maggie Sent:

Another possible solution is to enhance platform logging by adding a unique event id such as a UUID to each message. This likely helps auditing efforts by being able to specify an exact message and

We used heroku-buildpack-multi to deploy OpenProject (NodeJS and Ruby). https://github.com/Stackato-Apps/openproject The manifest.yml in that repo has some Stackato-isms, but you get the idea.

Great thought, Jesse. It was a nested /node_modules directory that was the bulk of the size. I added that to .cfignore. Thanks.

Thanks for pointing that out, Mike! From the executor commit history, seems to have been the path of least resistance when Diego switched to the newer dropsonde API circa Dec 2014. Also looks to me

I added Eric's comments to the spike <https://www.pivotaltracker.com/story/show/117583365>. -- Jim Campbell | Product Manager | Cloud Foundry | Pivotal.io | 303.618.0963

Yup, makes sense. I'm sure there is some valid reason for Diego not to use log_sender.ScanLogStream today. When that get's sorted out then the event demarcation and this replacement will all be in

The cf CLI also respects a .cfignore file in the top level of your repo, if there's stuff you'd like to explicitly exclude from push.

It's the cf cli that does this. It looks through your JAR / WAR or push path for files and then uses the resource matching endpoint to ask the server what it needs to upload. Then it uploads just

Thanks, Mike, don't be too hard on yourself. :) I think that's a valid point that if there is processing to translate a byte-stream from process stdout/stderr to loggregator log events, it would be

Guillaume, We just realized that you can remove any PII, personally identifiable information, from tokens without us having to add new features You just configure jwt: token: claims:

It does help -- thanks guys. I looks like Heroku has a buildpack that does this also (https://github.com/heroku/heroku-buildpack-java). The question I am coming up with is this: How does cloud