Hi Donny,
thank you for this precision, but I don't want to manage network from Cockpit, just
view the graphs of network usage in it, and eventually logs (can be interesting !).
That's why I ask about risks to activate NM after configuring the networks in engine
UI : what are the opinions ?
--
Cordialement,
Frank Soyer
Mob. 06 72 28 38 53 - Fix. 05 49 50 52 34
Systea IG
Administration systèmes, réseaux et bases de données
www.systea.net
Membre du réseau Les Professionnels du Numérique
KoGite
Hébergement de proximité
www.kogite.fr
Le Dimanche, Octobre 21, 2018 14:05 CEST, Donny Davis <donny(a)fortnebula.com> a
écrit:
Use the Ovirt engine to manage your networks. VDSM takes over at boot time, and the only
way for this to happen is if you use the engine On Fri, Oct 19, 2018 at 9:26 AM fsoyer
<fsoyer(a)systea.fr> wrote:Hi,
I have installed a 4.2 cluster on CentOS 7 nodes but I have follow an (old) procedure of
mine done with 4.0 : so, I have disabled Network Manager before installing oVirt.
The networks created and validated in the engine UI are :
ovirmgmt on bond0 (2 slaves) failover mode
storagemanager on bond1 (2 slaves), jumbo frames, aggregation mode, serving Gluster.
Today, I installed Cockpit on the node to have the nodes consoles. But it say that it
cannot manage the network without NM.
So my question is : is there any risk to re-enabled NM on the nodes ? Can it broke
anything done by the UI ?
--
Cordialement,
Frank Soyer
Mob. 06 72 28 38 53 - Fix. 05 49 50 52 34
Systea IG
Administration systèmes, réseaux et bases de données
www.systea.net
Membre du réseau Les Professionnels du Numérique
KoGite
Hébergement de proximité
www.kogite.fr
_______________________________________________
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/GOWGDMXIQ2V...