I do not see how SDM helps us here, unless we give one of our SDMs control on our single VM DB. One Vdsm is asked to create VM-A. Another Vdsm is asked to create another VM, which happens to have the same name, but a totally different definition. Who decides which one is created?
As I noted above, you would have a VM "DB" per domain, not one global DB. And of course only one vdsm would control a domain (the SDM)
The point that I try to convey is that having more than one VM DB in a migration domain, is wrong.
One SDM may be asked to define VM-A, with disks on its domain. Another SDM may be asked to define another VM named VM-A. We end up defining both, and cannot run them both on the same host.
A. Why not? B. that's the user's problem. But it wouldn't cause any corruption.
And to our jewish readers: there's one God in heaven; there should be one DB on earth.
Dan. _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel