This message was deleted.
# harvester
a
This message was deleted.
w
There's a nice architecture diagram at https://docs.harvesterhci.io/v1.0/ but unfortunately the inter-node network isn't labelled though because it's in blue you're left wondering if it's the management network.
My management network is my home network and I've set default VLAN 1 so I can attach VMs to same network.
m
Alright, so the blue management network is what I in my terms would call the backplane. And can I add this network to two interfaces, and set up the iptables or whatever harvester runs, so that I can say that traffic that isn't to the LAN is going to traverse these links? Say something like: node1: eth0.management: 192.168.0.111 eth0.vlan1: 192.168.0.221/24 eth1.management: 10.0.0.0/31 node2: eth0.management: 192.168.0.112/24 eth0.vlan1: 192.168.0.222/24 eth1.management: 10.0.0.1/31 where eth0 is connected to the LAN, and eth1 is the point to point link.
w
I don't think you can define two management networks, even on different interfaces (though both interfaces could be bonded). Instead you'd have to name the backplane one as backplane (for example). I also think you'll have to use a /30 subnet as /31 might work for Cisco but not here.
m
Well, if the major hurdle is the interface name and netmask I should be fine 😊 And yeah, as I mentioned, I'm a networking guy, we like our /31's for point to point 😛