Recent content by spirit

no, it's local on the node.

at minimum, if you use your arista as exit-node, (advertising the default route from arista) you should remove "exitnodes proxmox1-4,proxmox1-3,proxmox1-1" and peer with your arista router "peers proxmox1ip, proxmox2ip, proxmox3ip, aristaip" snat should be done on your arista too

https://docs.netapp.com/us-en/netapp-solutions-virtualization/proxmox/proxmox-ontap.html#lvm-with-iscsi ?

that's not true, CRM also open/close/update watchdog https://git.proxmox.com/?p=pve-ha-manager.git;a=blob;f=src/PVE/HA/CRM.pm;h=9b80b73f694062f4a82eed59ea601314daa5ad59;hb=HEAD both crm && lrm are connected through the watchdog-muxer

1) on each node : systemctl stop pve-ha-lrm then (when all lrm are down) 2) on each node: systemctl stop pve-ha-crm

proxmoxer is a client lib (a wrapper to proxmox rest api), why do you need to use it on pve node directly ?

don't seem to be a FS, but more an s3 like object storage, it'll not work

It's use for any qcow2 storage, including file storage. (local,nfs,...). External snapshot allow snap/delete snap without interruption. Current internal snapshot freeze the vm when deleting snapshot for example.

(I forgot to say that for snapshot, we use qcow2 sub-allocated cluster (l2_extended=on) with 128k cluster size, so metadatas are 32x smaller than base image (64k cluster without suballocated cluster). around 4MB memory for 1TB image https://www.youtube.com/watch?v=NfgLCdtkRus Also, the memory...

the cache value is a max value, it's only allocated when you need to load specific metadatas (and unused metadatas are flushed after 10min). It's not too much different than zfs btw, where you need memory to handle metadatas too. so , yes, if you read full disk with 8TB datas in less than...

I don't known who as recommend you tu use consumer ssd with zfs or ceph, but performance will be horrible. (because lack of power-loss protection, so the fsync for the zfs/ceph journal can't be cached). pm1643 (or any other enterprise ssd with plp) should works fine.

it should work with bridge-vlan-aware, but don't use 1 in bridge vids. (bridge-vids 1006) . (don't add native vlan in bridge-vids)

this is internal plumbing, ln_ && pr_ are veth interfaces, like a virtual link, between bondv77 && exemple bridge.

rm -rf /var/lib/pve-cluster/* on each node, and "systemctl restart pve-cluster"