[pve-devel] question/idea : managing big proxmox cluster (100nodes), get rid of corosync ?

Alexandre DERUMIER aderumier at odiso.com
Tue Sep 20 07:43:33 CEST 2016


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).

Like this, it could be possible migration vm across cluster (offline, or maybe even online),
and also share storage across cluster.

It could be great for ceph too, if you want to share a pool between differents cluster.
(we can create multiple pool in ceph, but with too many pool, this increase the number of pg, which is bad for ceph)



----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "dietmar" <dietmar at proxmox.com>
Cc: "pve-devel" <pve-devel at pve.proxmox.com>
Envoyé: Lundi 19 Septembre 2016 08:56:36
Objet: Re: [pve-devel] question/idea : managing big proxmox cluster (100nodes), get rid of corosync ?

> It's become to be difficult to manage, as we can't easily migrate vm across 
> clusters 

>>But this is difficult because there is no shared storage in that case? 

I have local dc storage, but shared across dc. (mainly do live migration, then storage migration). 

But In the future (>3-5year), I'm looking to implemented ceph across 3 dc. 

----- Mail original ----- 
De: "dietmar" <dietmar at proxmox.com> 
À: "aderumier" <aderumier at odiso.com>, "pve-devel" <pve-devel at pve.proxmox.com> 
Envoyé: Lundi 19 Septembre 2016 06:23:58 
Objet: Re: [pve-devel] question/idea : managing big proxmox cluster (100nodes), get rid of corosync ? 

> It's become to be difficult to manage, as we can't easily migrate vm across 
> clusters 

But this is difficult because there is no shared storage in that case? 

_______________________________________________ 
pve-devel mailing list 
pve-devel at pve.proxmox.com 
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 



More information about the pve-devel mailing list