[ovirt-users] Re: Understanding Cluster Networking between Hosts
Hi Brad,
What are you using for storage, and are you trying to setup both of your physical servers
into the same cluster?
In my scenario (a hyperconverged environment with Gluster), ideally, you need two
different networks, on separate network interfaces: One for your backend / storage
network, and one for your frontend / VM network.
In my case, I actually have 3 networks:
* Backend Storage
* IPv4 frontend traffic
* IPv6 frontend traffic
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, October 18th, 2021 at 3:44 PM, <admin(a)foundryserver.com> wrote:
Hello everyone. I am looking to setup a ovrit cluster. I am
struggling with the network side of things. I have watched some videos about Ovirt and
kvm/libvirt. I understand the bridge and NAT networks. The part I am struggling with is
the host network. Here is my setup.
I have two bare metal servers, that have one physical nic with a
public IP. There is no private physical network on these boxes virtual or physical.
I want to host an application on a single vm for each customer. the
customer access the application via username.domain.com.
So the question is. I have to have a layer 7 load balancer to route
the url to an IP. This load balancer is haproxy on a separate bare metal box. (it could be
in a vm on one of the hosts) So the load balancer has to be on the same network as all the
vms. I just don't know to setup the networking between the LB on one box and the
vm's on potentially may bare metal hosts.
It really feels like I am missing something really obvious. All the
videos I have watched all assume the host networking is already in place. Any help or
resources I can read/watch would really be helpful.
Brad
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
Attachments:
- signature.asc (application/pgp-signature — 509 bytes)
- publickey-dmwhite823protonmail.com-0x320CD582.asc (application/pgp-keys — 1.8 KB)