We're running a set of virtual machines for several environments. Unfortunately, sometimes we encounter out-of-memory situations, ofter resulting in termination of kvm/lxc process handling whole machines.
Beside increasing hardware resources, we consider setting up OOM score adjustments, making hypervisor hosts to prefer to terminate dev instances more than production instances.
Our idea consists of a small shell script that integrates with Proxmox API to fetch list of running machines categorised by pools assigned to dev pool and then adjusts oom score for the lxc and kvm processes that are parents of these machines.
In effect, if an out-of-memory situation occurs, development machines would be killed more eager than production instances.
Is this a viable temporary solution? Our Proxmox deployment isn't currently using a subscription but we would like to consider returning to it in future. Would implementing oom_score adjustments scripts interfere with Proxmox or the ability to use a subscription support?
Beside increasing hardware resources, we consider setting up OOM score adjustments, making hypervisor hosts to prefer to terminate dev instances more than production instances.
Our idea consists of a small shell script that integrates with Proxmox API to fetch list of running machines categorised by pools assigned to dev pool and then adjusts oom score for the lxc and kvm processes that are parents of these machines.
In effect, if an out-of-memory situation occurs, development machines would be killed more eager than production instances.
Is this a viable temporary solution? Our Proxmox deployment isn't currently using a subscription but we would like to consider returning to it in future. Would implementing oom_score adjustments scripts interfere with Proxmox or the ability to use a subscription support?
