Hi Thomas,There already is one for HA, the
migrateshutdown-policy. And yes, once set it will be used as better selection for target nodes.
For non-HA it's planned but needs much more extra work (especially if you consider more than one narrow use-case with everything shared already, which could just use HA anyway), once the mechanism is there the new CRS stuff can be used there too, but as said, it's "just" the selection, not the underlying mechanism to handle such stuff - that's done by the HA stack that got all the required information already.
Unless something has changed, the current HA does not provide what we need. It migrates workloads when the node goes down and then brings them back when the node comes us. That's fine if the node crashes or something, but not if we want to do maintenance on the node. We need a way to manually tell the HA to migrate the VMs to other nodes and not migrate them back until we say so. We want to be able to drain a node, do some work on it, test that everything is working properly, then tell the HA it can migrate VMs back. Draining a device is a pretty standard requirement for any infrastructure and has been raised here many many many times before.