Perhaps instead of renaming the setting, we can note in its description the
hypervisors it currently pertains to.
> On May 19, 2018, at 7:03 PM, Glen Baars wrote:
>
> Based on the responses, I think it is a worthy feature to be retained. Maybe
> the following changes?
>
> Rename the setting t
Based on the responses, I think it is a worthy feature to be retained. Maybe
the following changes?
Rename the setting to something like kvmxen.snapshot.primaryonly ( I have no
idea of the naming scheme that Cloudstack uses )
Ensure the code for vmware snapshots does not get impacted by the sett
