10:50 p.m.
I'm not sure if anyone else has already answered your questions.
Let me try inline.
В петък, 28 август 2020 г., 01:14:42 Гринуич+3, Michael Thomas <wart(a)caltech.edu>
написа:
I have not been able to find answers to a couple of questions in the
self-hosted engine documentation[1].
* When installing a new Enterprise Linux host for ovirt, what are the
network requirements? Specifically, am I supposed to set up the
ovirtmgmt bridge myself on new hosts, or am I supposed to let that be
handled by the engine when I add the new host to the engine?
Just add your Host as a regular linux -> setup the VLAN, IP, mask + gateway and DNS.
ovirtmgmt bridge will be created by the setup.
* In the 'New Host' dialog on the engine management page, does the
Hostname/IP that I enter have to be the host's name on the ovirtmgmt
LAN? If so, then it seems to me that I need to configure the ovirtmgmt
bridge myself on new hosts.
You just define the IP that can be reached from the engine , as it uses ssh to setup the
host.
* Does the engine need to be able to route outside of the cluster (eg to
the WAN), or is it allowed to restrict the engine's routing to the local
cluster?
I'm not sure what WAN has to do here. Engine needs to be able to reach all oVirt nodes
over ssh.
* In the 'New Host' dialog on the engine management page, what is the
meaning of 'Choose hosted engine deployment action'? From the way it is
phrased, it sounds like this will create a second engine in my cluster,
which doesn't make sense. Or does this mean that the new host will be
able to run the Engine VM in a HA manner?
You can define if you wish that host to be able to host regular VMs + HostedEngine or just
only VMs.If you pick the first solution , there will be some extra daemons running on the
system like ovirt-ha-agent and ovirt-ha-broker which take care to restart the HE when
necessary.
In my current test deployment I have 3 subnets in my cluster. Network
WAN is the WAN. Network CLUSTER is for communication between cluster
compute nodes, storage servers, and management servers. Network OVIRT
is for ovirt management and VM migration between hosts.
My first self-hosted engine host is connected to networks CLUSTER and
OVIRT. The engine VM is only connected to network OVIRT through a
bridge on the host, but has a gateway that lets it route traffic to
network CLUSTER (but not network WAN).
Is this an appropriate network setup for ovirt, or should there be no
distinction between the CLUSTER and OVIRT networks?
Usually you need several networks (I am not using the proper terms):
- Storage network if you use Gluster/NFS/anything network based
- VM migration network that will allow you to migrate the VM from one Host to another
- ovirtmgmt which is used by the engine to reach to all Hosts and manage them
Another type of network could be when you use IPMI-based fencing which is done from a Host
to the IPMI of another Host.
Best Regards,
Strahil Nikolov