@adramesh are your opened issues fixed ? If so, I can release
Thrilled that you continue to improve an already awesome library.
We currently know of 6 users in production, with a lot more at varying stages of development. I would put the total at somewhere around 20-60 users actually evaluating it or using it in a substantial way, and a lot more that have tried it (hard to know how many more)
@lbradstreet No spread ?
Spread is definitely one that we want to use, but we haven't had the time to expose to our users
You're right that it's probably the most important constraint that we're not using
We've been focused on other things, and haven't given our scheduler some love for a while, so I can't remember the additional constraints that we needed off the top of my head. I'll try to remember
Reduced footprint for large problems
No changes in the API
I will advertise one day, but not now
@apatrida is it disturbing ?
@fhermeni not as-is, but the general concepts. I’m building a planner that manages the internals of a distributed system which has
nodes -> sets -> shards and need to distribute and balance the shards for safety and performance. topology of network, and info such as disk, CPU and stats such as reads/writes are all important. So are migration from one plan to another. so btrplace but focused on this one domain.
currently, looking to see how “initial placement” values are set, because I’m also learning Choco not sure how this is done. If i set a var it can’t be set later? so I shouldn’t set it but I should solve for the lowest differing plan from the original plan instead. which basically favors things staying close to original position?
Well, that's explained while the live demo was out
It's back now
We are trying to porte btrPlace to the SCHIAAS simulator (i.e. we are porting the whole VMPlaceS framework to the SCHIAAS actually)