On Mon, Sep 05, 2011 at 01:53:51PM +0300, Dan Kenigsberg wrote:
On Mon, Sep 05, 2011 at 05:59:28AM -0400, Ayal Baron wrote:
It is relevant. For example, we do not want two Vdsms creating different VMs with the same name or vmId. Your suggested scheme, where each Vdsm persists VM metadata on a storage domain that it sees, may lead to that.
We would still have an "SDM" which would prevent such a scenario from occuring. Management would have to choose the SDM. I don't see the problem.
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?
In the standalone case, both VMs can be created (each VDSM is independent). Then, if one instance later tries to migrate a VM over there will be an error. This is not a problem for my usage scenarios.