Avoid streching a PVE cluster, it isn't that good of an idea.
At the very least you will need to make sure each side have the same amount of votes, and add a QDevice in a third location that helps with quorum. Get ready to deal with nodes with different votes (i.e. when a server is down for any reason). Also, the latency requirements between nodes [1] must be taken into account.
Both sides of the cluster will be out of quorum, given they both now have exactly 50% of votes (4 of 8). If you have HA enabled, both sides will fence the hosts by a reboot and all your VM/CT will go down [2]. A QDevice in a third location can help here, as it will give it's bote to one of the sides randomly if the locations can't reach each other but both can reach the QDevice.
If you just want easier management, use PDM [3].
If you just want to manually recover quorum in case of a disaster, there's always the option to use
pvecm expected
, althoug it comes with it's own requirements (i.e. make 100% sure you use it on one side of the cluster
only and while the other is out of quorum, or risk painful pmxcfs errors when the sides reach each other again).
[1]
https://pve.proxmox.com/wiki/Cluster_Manager#pvecm_cluster_network
[2]
https://pve.proxmox.com/wiki/High_Availability#ha_manager_fencing
[3]
https://pve.proxmox.com/wiki/Proxmox_Datacenter_Manager_Roadmap