[pve-devel] Storage::Plugin::deactivate_volume not executed, when VM does shutdown

Dietmar Maurer dietmar at proxmox.com
Sun Dec 11 19:16:28 CET 2016


>  > First, we call deactivate if you migrate a VM to another node.
> OK, I haven't seen this. I will test once my plugin is ready.
> 
>  > For HA, you need to fence the node before you start it on another node,
> If I am using HA. Currently I have two machines and as a first step I plan to
> do a kind of manual "HA". The automatic switch over requires a third machine
> for quorum and I am not sure if I am able to get this running till end of next
> week.
> 
>  > so there is no need to deactivate the volume at VM stop time.
> It seems you insist the behaviour is good as it is, there is another
> mechanism to cover it before migration and you don't want to change it.
> Then it wouldn't make any sense to fix this and provide a patch, when it would
> not be accepted. You are the project leader and you decide.

I simply do not understand why you think the current approach is wrong. It works
with all major storage types, i.e. Ceph, sheepdog, iscsi, NFS, Gluster,
DRBD on LVM in dual primary mode, DRBD9, ...

I do not understand why it does not work with your DRBD driver ...




More information about the pve-devel mailing list