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:

For the cached package of the buildpacks, I thought it would refuse to provide a runtime version that's not cached. Yesterday I was playing with the node.js buildpack and found it actually will

Hi, Sebastien Yes, the url with protocol specified works. Thanks a lot for your great help! Regards, Maggie Sent: 2015年11月7日 8:12 To: Discussions about Cloud Foundry projects and the system

William and all, Sorry for an off-topic post. http://cloudfoundryjp.github.io/ is totally old and shouldn't be referred as a reliable source of information. I had asked a member of the owning

Good morning, I understood your app scenario: + Your app has to interact with CF API but your question is about where you can store your configuration. I think that it is very normal to use a

Thanks for getting started on this requirement. Yes, We were looking into webhooks kind of model, where a registered endpoint could be invoked when a (or more than one) criteria is met. A few

Hi, Interesting proposition, wondering if it make sense to hook into Diego or CF. Diego is connected to CF by the CC-Bridge (big picture) why not create a CC-Bridge for other scheduling system

Hi all, Earlier today I added a build and a few scripts to our set of Travis CI builds [1] to continuously push our Abacus services and apps to CF. I'm hoping that will partially address some of our

Great! What you've described here looks like a good start to me. I've included a few comments and questions below: it as seen here: and one more, created from Github #161 by the CF

I've begun to work on supporting notifications in abacus. We already have a github issue and pivotal tracker story associated with it as seen

Hi folks, I would like to start a discussion thread and get community thoughts regarding availability of Pluggable Resource Scheduling within CF/Diego. Just like Kubernetes does, wouldn’t it be nice

CF 170 does not have application security groups, so that is not the issue. However, CF 170 is quite old now - we would be in a better position to assist if you are running a more recent version of