GitHub user dcontiveros-nf closed a discussion: Utilizing NetworkManager as the 
only networking solution

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:

```
Configure Network ...         [Failed]
Missing bridge/device network configuration, need to add your network 
configuration into /etc/sysconfig/network-scripts at first
Try to restore your system:
```

I saw that the agent setup was attempting to setup `cloudbr[01]` as intended. I 
then looked at the code here and saw that for bridges it always disables 
NetworkManager:

https://github.com/apache/cloudstack/blob/97c96a55ba9128ae9f50516574745da30cd5c1b7/python/lib/cloudutils/serviceConfig.py#L272

I am trying to accomplish the concurrent use of NetworkManager and OpenVSwitch. 
The documentation I have read seems to use `ifcfg` files to specify the 
information for each bridge. Here is an example:

https://docs.cloudstack.apache.org/en/4.20.0.0/installguide/hypervisor/kvm.html#configure-rhel-centos-for-advanced-networks

However, I am trying to avoid the use of `ifcfg` files per the following post:

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:

https://github.com/apache/cloudstack/issues/5443

I was under the impression if I had setup similar configs within NetworkManager 
that I could get past this, but the `serviceConfig.py`  seems to have a 
stop/disable operation here:

https://github.com/apache/cloudstack/blob/97c96a55ba9128ae9f50516574745da30cd5c1b7/python/lib/cloudutils/serviceConfig.py#L311

If I misread please let me know. I would like to use NetworkManager 
exclusively. Thanks.

GitHub link: https://github.com/apache/cloudstack/discussions/10903

----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org

Reply via email to