And the SubstitutedVM Event has an unresolved merge conflict in the example ;)
@HerrSpace I am not attending Fosdem. What's / who's in 5C3 ?
@HerrSpace I'll fix the doc. About your original request wrt. modelling an over-provisionning resource: ShareableResource exhibit how the resources are shared inside a node, so this indicates the node capacity is too low
here, the notion of over-provisioning does not hold, you just state what you observe. Typically, you cannot have a node loaded at 110%
@HerrSpace no pb. I don't guarantee it is perfect but it exists
Is there some way to debug which constraint solving failed on? I'm now looping through lots and lots of fencing constraints and it's taking forever to find the broken ones.
I already set the scheduler verbosity to three but no luck.
I'm close to implement some kind of binary search ^^
@HerrSpace You mean inferring for an unsolvable problem the constraint(s) that led to the situation ?
I did that in the past inside SafePlace but eventually I removed the code.
What I did was delta debugging. Then it is a matter of granularity. For example, delta debugging affinity constraints is fine
but delta-debugging resource oriented constraint was not very informative due to the granularity and the arbitrary splits
Otherwise, it is quite easy to implement as constraints are immutable and express outside the model (add/remove inside Instance objects). I may end up providing that in the future but for my use cases, most of the time, what need to a non-solution is the resource usage
If you use BtrPlace inside your company, it would be great if we can advertise for that. As an open-source project, this matters for visibility and to acknowledge the work done ;)