If Mesosphere can do it for Kubernetes, CF/Diego is doable too. I am not worried about that, it is a solved problem. The only concern I have is regarding deployment of Garden Container environment in

Hi Sandy, Yes, I'm happy to help work through requirements on these via a github issue in support of PRs to follow through on implementation. -Dieu CF CAPI PM

would drastically reduce the programming complexity and would help to make the data more consistent with the source. That approach would also create another path for these stats (apps proactively

Hi Kevin, collected by abacus-perf. Interesting feature! It'd be good to understand what you're trying to do with that data (I think Assk for asking a similar question) as that'll help us provide

Hello Christopher, thanks for your reply. We are stumbling over the very same test again. Just to confirm, the tests haven't been fixed according to [1], have they? Can I help you in any way with

Thanks JT. Except the Java buildpack though :-) Jack

Hi, I'm not sure what strategies exist either. This same topic came up partially in the context of my resubmitted FIPS proposal, and I was curious - is it worth creating an issue (or even a separate

Jack, This is correct. The online version and the offline version of the buildpack only differ one way. The offline version has the dependencies, defined in the `manifest.yml`, packaged with

What is the purpose of that Shell Script? In my humble opinion, Buildpacks interacts with a unique software artifact in your case in Java. Another approach could be, the development of a Docker

Hi All, I have a java application which is a composition of several jars in the running environment. The main jar is invoked by a shell script. Is it possible to push such application into cloud

> I believe that Assk (@sasrin) has started to document the beginning of that monitoring setup as well in doc/monitor.md [1] Yes...We have started to write down the steps to setup the Hystrix

You can add different scheduling strategy into Diego by implementing a scheduler plugin. But not Mesos, that would be a huge task and another story. The reason Kubernetes can integrate Mesos as

I would like to add one more to the list of possible solutions for further discussion: How about extending abacus-perf to optionally persist collected performance metrics into a database? In my

Hi, One of the thing that I want to do is to persist the metrics performance collected by abacus-perf. What would be the best way to do this? I've been through some solutions, but none of them seems

Thanks Brian for your feedback. Can you elaborate on use-cases for which somes scopes would need to be auto-approved by the platform (i.e. without users providing their consent) ? Do you rather see

I think that would work well too. I guess the main thing between the two approaches is number of docs versus size of a doc. Building a query for either wouldn't be too hard, but putting multiple

I did not mean to replace the whole “Diego” environment itself. What I was thinking was more in terms of plug-ability within Diego itself. This is so that “Auctioneer” component can be turned

Thanks Mike. Is it true that even for the online version (aka when doing "cf push -b https://github.com/cloudfoundry/nodejs-buildpack.git"), users are now limited to use the runtime versions defined

Hi William, Thanks for the links. We don't have support for client side encryption currently. Cloud Controller and Diego's blobstore clients would need to be modified to encrypt and decrypt for

This is a bug in the nodejs-buildpack v1.5.1, which we should have a fix for later today. Github issue is here: https://github.com/cloudfoundry/nodejs-buildpack/issues/35 Tracker story is here: