12-10-2019, 05:11 AM
@deanhills
Thanks for the background story! So, it was five OpenVZ(6) to KVM migrations, each one with its own context and outcome (5 different locations/nodes.)
The disk size issue is expected given that it's easier to advertise a virtual 100GB SSD on OpenVZ than with KVM. Thus (I presume) on the nodes where storage is scarce, they didn't reserve it in bulk but rather on demand.
Thanks for the background story! So, it was five OpenVZ(6) to KVM migrations, each one with its own context and outcome (5 different locations/nodes.)
The disk size issue is expected given that it's easier to advertise a virtual 100GB SSD on OpenVZ than with KVM. Thus (I presume) on the nodes where storage is scarce, they didn't reserve it in bulk but rather on demand.
(12-09-2019, 08:05 PM)Hidden Refuge Wrote: (...)Glad to have read this @Hidden_Refuge, that was the goal :-) I'm sure you'll find the time and the motivation going forward.
Anyway. On the subject I've read some stuff about SELinux recently after working on these cases and reading your replies. It's not bad but you have to be prepared to learn and be aware that simple things turn into a task that requires more work and time. And most important maybe is that you need knowledge and proper management skills. Also (with my job and etc I don't have much of it).
(...)