6:49 a.m.
This is really a situational question.
Short answer is - there's no problem running everything on ovirtmgmt
network - I do it, especially if what your deploying on is essentially
one big network. Its just the VM's bridged into your hosts NIC.
The long answer is, you can create many networks based on a number of
factors i.e. VLAN tagging, different names for different groups,
different things to run over different networks (like migration traffic
and/or host storage traffic etc) this gives you flexibility in the long
run if you need to change things around - more management overhead but
more flexibility.
My home server - being a single node home server - uses a Bond0
interface that the ovirtmgmt bridge is created on. I also have a VLAN
Tagged network on that bond setup in oVirt to some servers, as I run my
server and client device (and IoT device) networks separately.
In terms of your webserver example - you'd ideally have a webproxy VM
that you forward your 80,443 to from your router, and it'd be setup to
talk to any other application/VM internally on their internal IPs - I do
this for a self hosted Nextcloud, Cacti/NMS, Plex, some development
servers etc all behind my NAT router, all on oVirt.
If you have any specific questions or problems - please let me know and
I'll try my best to help.
On 24/1/20 2:38 pm, Richard Nilsson wrote:
High level network advice request :)
I have a self-hosted engine deployed on a node, Ovirt v. 4.3. I am testing, but I
don't understand the big idea of how to set-up Ovirt networking for hosted /
engine-managed virtual servers. I would like to host a few virtual servers for things like
Next/OwnCloud, SuiteCRM, NethServer or others.
For example, I know exactly how set-up a virtual machine with a centos / lamp stack on a
fedora host, I can make a network bridge for the vm with fedora cli, then use haproxy (or
squid) as a reverse-redirect server to allow WAN access to the vm server using FQDNs.
What is a good strategy for Ovirt hosting a webserver? To use the default ovirt
management network for the virtual server machines doesn't seem like a best practice?
Should I make a new logical network for the virtual servers? Do I need to configure
bridges for the machines? It looks like bridges and virtual NICs are automatically
configured when I make the network and virtual machines, is that right?
Is it the usual or typical practice that one ovirt logical network uses only one network
bridge to a one physical NIC? Would all of the kVMs on the logical network share the same
/ single bridge of the particular network? I'm not sure what the big idea should be,
what is a best practice?
I wonder, should I bond several physical NICs, then point the bridge, for a new /
dedicated logical network for webservers, to the the bonded NICs? There is more than a
little new vocabulary for me to onboard for Ovirt / virtual / logical networks...I will
greatly appreciate, and I thank you in advance for any top level / best practice advice!
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/H7GUEYSB77C...