KVM HA configuration via database: Global Config parameters and enabling HA on uploaded templates

[raniers1]

Hi everyone,

I would like to get some feedback regarding the following Global Configuration parameters related to KVM High Availability in our staging environment running Apache CloudStack.

We know that these settings can be changed via the Web UI, API, or directly in the database. We would like to know if there are any concerns or restrictions regarding changing these parameters directly in the database.

The parameters in question:

Parameter	Value
kvm.ha.recover.failure.threshold	1
kvm.ha.degraded.max.period	300s
kvm.ha.activity.check.failure.ratio	?
kvm.ha.activity.check.max.attempts	5

Some questions:

• Is modifying these settings directly in the database safe, or could it cause cache inconsistencies in the Management Server (ACS 4.21.0.0 )?

Additionally, we have a second concern: we have templates that were uploaded without HA enabled. Once a template is uploaded, the HA option is no longer available through the Web UI. In this case, is it safe to enable HA directly in the database for both the templates and the VMs that were deployed from them?

• Is there any risk in enabling HA directly in the database for existing templates and VMs?

Thanks in advance!

[jgotteswinter]

imho this should be fine, restart the management server afterwards.