Thank you, Alex.
I think that makes sense.
I'm a much stronger systems engineer than I am a network engineer, so maybe I need to
go talk to a network engineer about these questions.
I do have a 10Gbps switch (albeit only layer 2) that supports vlan tagging.
And my routers support vlans as well.
If I build a vlan on the router for the public IP space, would I need to use up two public
IP addresses?
1 for the router's WAN interface going to the ISP, and the other for the router's
vlan interface? Or is it possible to use the single gateway IP address of the router as
the vlan interface as well? Or is that router specific that I just need to figure out?
Considering a single, physical connection down from the switch to each of the physical
hosts that run oVirt, I guess that means I shove both the private vlan and the public vlan
on the same physical link. Am I understanding this right?
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, March 8, 2021 5:27 PM, Alex McWhirter <alex(a)triadic.us> wrote:
You can route it to a private address on your router if you want...
We use EVPN/VXLAN (but regular old vlans work too) Just put the
public
space on a vlan, add public as a vlan tagged network in ovirt. Only your
public facing VM's need addresses in the space.
On 2021-03-08 05:53, David White via Users wrote:
> If I have a private network (10.1.0.0/24) that is being used by
the
> cluster for intra-host communication & replication, how do I get a
> block of public IP addresses routed to the virtual cluster?
> For example, let's say I have a public /28, and let's use 1.1.1.0/28
> for example purposes.
> I'll assign 1.1.1.1 to the router.
> How can I then route 1.1.1.2 - 1.1.1.16 down to the virtualized oVirt
> cluster?
> Do I need to assign a public IP address to a 2nd physical NIC on each
> host, and put that network onto a totally different physical switch?
> Or should I instead setup default routes on the 10.1.0.0/24 network?
> I also wanted to follow up on my question below to see if anyone had
> any thoughts on how things would function when a portion of the
> network is lost.
> Sent with ProtonMail [1] Secure Email.
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, March 4, 2021 4:53 AM, David White
> dmwhite823(a)protonmail.com wrote:
>
> > I tested oVirt (4.3? I can't remember) last fall on a
single host
> > (hyperconverged).
> > Now, I'm getting ready to deploy to a 3 physical node (possibly 4)
> > hyperconverged cluster, and I guess I'll go ahead and go with 4.4.
> > Although Red Hat's recent shift of CentOS 8 to the Stream model, as
> > well as the announcement that RHV is going away makes me nervous. I
> > really don't see any other virtualization software doing quite the
> > same stuff as oVirt at the moment.
> > One of my questions is around the back end out-of-band network for
> > data replication.
> > What happens if all 3 servers are healthy and the normal network is
> > fine for serving traffic to the VM consumers, but the switching
> > network for data replication goes down? Is it possible to configure
> > oVirt to "fail over" to the front-end network?
> > I'm also wondering if its possible to do away with a switch all
> > together, and just link the physical hosts together directly (like a
> > cross-over cable) for the data replication.
> > I'm also wondering what would happen in the following scenario:
> >
> > - All 3 servers are healthy
> >
> > - The out-of-band data replication network is healthy
> >
> > - 1 or 2 of the servers suddenly lost network
connectivity on the
> > front-end network
> >
> >
> > What then? Would everything just keep working, and network
traffic
> > be forced to go out the healthy interface(s) on the remaining hosts?
> > Sent with ProtonMail [1] Secure Email.
>
> Links:
>
> -------
>