Utilizing NetworkManager as the only networking solution #10903
-
Hello all, Quick rundown of what I am trying to accomplish Objective: To connect a KVM hypervisor node to my management server. I am receiving this error:
I saw that the agent setup was attempting to setup I am trying to accomplish the concurrent use of NetworkManager and OpenVSwitch. The documentation I have read seems to use However, I am trying to avoid the use of https://www.redhat.com/en/blog/rhel-9-networking-say-goodbye-ifcfg-files-and-hello-keyfiles Is there a way to completely utilize NetworkManager? I am attempting something similar to this: I was under the impression if I had setup similar configs within NetworkManager that I could get past this, but the If I misread please let me know. I would like to use NetworkManager exclusively. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You are right @dcontiveros-nf , NetworkManager is forcefully stopped by cloudstack (as per the serviceConfig.py code you pointed at) I think it is only the setup script and ACS only cares about the interfaces being there. (cc @weizhouapache agree?) |
Beta Was this translation helpful? Give feedback.
-
I would suggest users configure the host network manually, before adding it to cloudstack |
Beta Was this translation helpful? Give feedback.
I would suggest users configure the host network manually, before adding it to cloudstack
users can use different tools (netplan, networkmanager, network scripts, etc), and support more complication network configurations as they want (e;g. use bond, alternative network interface name, etc).
the script
serviceConfig.py
only support simple network configurations. If the linux bridges have been pre-configured, the script will skip the network configurations.