Configuration Validation
- Thread starter zahmad
- Start date
I will answer here since this is the original thread. Please avoid creating duplicate threads for the same topic.
Q1
The described configuration looks good and should be fine for production.
If you haven't already,ensure to check the wiki Migrate to Proxmox VE [0].
Q2
LVM on top of iSCSI storage is supported setup, see details on [0]. Note that the snapshot-as-volume-chain at the moment still marked as a technology preview [7].
Q3
Correct. Since Proxmox VE 9 there's no needed for changes in lvm.conf, see [1] and more details on [2].
Q4 and Q5
Proxmox uses the Corosync Cluster Engine for reliable group communication, it is sensitive to latency and any increase of latency could result in a loss of connectivity and cluster fences (reboot) in case HA service is enabled [3]. Proxmox recommend to have a stable connection bellow 5ms, see section 5.7.1. Network Requirements [4]. Therefore you need to ensure that corosync have its own separate link and its also advised to configure a secondary separate link for corosync redundancy [5].
Also note that by default Proxmox VE uses the MGMT network (the one linked to your nodes IP in /etc/hosts) for migration traffic. Recommendation is to configure the migration network on a different interface from the Corosync interface. You can do this by:
Datacenter → Options → Migration Settings. Make sure to read section 5.14.2. Migration Network for more details [6].
[0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=4997
[2] https://lore.proxmox.com/pve-devel/580530151.9411.1751012041645@192.168.2.153/T/
[3] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_fencing
[4] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_cluster_network_requirements
[5] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_redundancy
[6] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_migration_network
[7] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvesm_lvm_config
Q1
The described configuration looks good and should be fine for production.
If you haven't already,ensure to check the wiki Migrate to Proxmox VE [0].
Q2
LVM on top of iSCSI storage is supported setup, see details on [0]. Note that the snapshot-as-volume-chain at the moment still marked as a technology preview [7].
Q3
Correct. Since Proxmox VE 9 there's no needed for changes in lvm.conf, see [1] and more details on [2].
Q4 and Q5
Proxmox uses the Corosync Cluster Engine for reliable group communication, it is sensitive to latency and any increase of latency could result in a loss of connectivity and cluster fences (reboot) in case HA service is enabled [3]. Proxmox recommend to have a stable connection bellow 5ms, see section 5.7.1. Network Requirements [4]. Therefore you need to ensure that corosync have its own separate link and its also advised to configure a secondary separate link for corosync redundancy [5].
Also note that by default Proxmox VE uses the MGMT network (the one linked to your nodes IP in /etc/hosts) for migration traffic. Recommendation is to configure the migration network on a different interface from the Corosync interface. You can do this by:
Datacenter → Options → Migration Settings. Make sure to read section 5.14.2. Migration Network for more details [6].
[0] https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE
[1] https://bugzilla.proxmox.com/show_bug.cgi?id=4997
[2] https://lore.proxmox.com/pve-devel/580530151.9411.1751012041645@192.168.2.153/T/
[3] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_fencing
[4] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_cluster_network_requirements
[5] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_redundancy
[6] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvecm_migration_network
[7] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#pvesm_lvm_config
