Tom Parrott
Tom Parrott
> Thank you for your quick response! Would it be possible to get a patch for the 6.1 series that would give us the option to turn this off? Otherwise...
Chatting with @morphis and he proposes having a new setting: ``` limits.cpu.pin_strategy=[none|auto] ``` Where `none` will disable auto pinning (the new default) and `auto` would be the current default behaviour...
I agree in principle, but have you considered the case where a tpm device is added to a profile that is used with both containers and VMs?
Sounds like a bug to me.
@hamistao is this confirmed as a bug? If so please can you add the Bug label to the issue.
> This is uncomplete, to be done: 1.Handle metric value updates on asynchronous operations 2.Fine tune entity_type assignment 3.Fix GH tests; 4.Manual tests 5.Docs You can convert this to a...
@hamistao as discussed in our 1:1 lets go with storing a "record request result" callback function in the request's context (added by the middleware), that the operation can then detect...
> We can have a quick call to discuss all this if you'd like. Yes we can, as I don't follow this: > but I am afraid this approach still...
> Setting the callback function before the main handler is possible but could run into the problem of being called too early by an operation that is created and completed...
No problem, yes please can you propose a new day/time for our next 1:1