>>I guess we need more. For example, we can exactly identify >>a VM/CT/Storage/Network by prefixing it with the cluster name: >> >>cluster1/vm/100 >>cluster2/ct/100 >>cluster1/storage/local >>cluster2/network/vmbr >> >>But we need a way to tell if resources are considered >>to be equal (cluster wide). >> >>An easy way to to do that would be to assign UUIDs to VMs, CTs, >>storages and networks?
yes, could be the solution. I think openstack/xenserver already doing this. The vm disks also need to be unique. (they use vmid, so if vmid is unique it's ok) ----- Mail original ----- De: "dietmar" <diet...@proxmox.com> À: "Thomas Lamprecht" <t.lampre...@proxmox.com>, "pve-devel" <pve-devel@pve.proxmox.com> Envoyé: Mardi 20 Septembre 2016 08:38:09 Objet: Re: [pve-devel] question/idea : managing big proxmox cluster (100nodes), get rid of corosync ? > On September 20, 2016 at 8:21 AM Thomas Lamprecht <t.lampre...@proxmox.com> > wrote: > > > > > On 09/20/2016 07:43 AM, Alexandre DERUMIER wrote: > > One thing that I think it could be great, > > > > is to be able to have unique vmid across differents proxmox clusters. > > > > maybe with a letter prefix for example (cluster1: vmid: a100 , cluster2: > > vmid:b100). > > I would use the clustername as a "namespace" for this, as its already > unique in a network. I guess we need more. For example, we can exactly identify a VM/CT/Storage/Network by prefixing it with the cluster name: cluster1/vm/100 cluster2/ct/100 cluster1/storage/local cluster2/network/vmbr But we need a way to tell if resources are considered to be equal (cluster wide). An easy way to to do that would be to assign UUIDs to VMs, CTs, storages and networks? _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel