Bug 636108 - RFE: interface: provide NetworkManager backend for configuring host interfaces
Summary: RFE: interface: provide NetworkManager backend for configuring host interfaces
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
Depends On:
Blocks: libvirtTodoNetwork
TreeView+ depends on / blocked
Reported: 2010-09-21 14:24 UTC by Daniel Berrangé
Modified: 2019-02-06 23:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2019-02-06 23:47:04 UTC

Attachments (Terms of Use)

Description Daniel Berrangé 2010-09-21 14:24:21 UTC
Description of problem:
The current netcf backend in libvirt requires root privileges to operate. It should be possible to provide an alternative implementation that talks to NetworkManager to perform changes. This will work as root and non-root.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 1 Laine Stump 2010-09-21 17:16:17 UTC
A current blocker is of course that NM doesn't support the configuration of bridge interfaces. AFAIK, the plan to make that happen is still to have NM use netcf, but no resources have been put on that project.

Since NM is written in python, one prerequisite of that is python bindings for netcf.

I'm not sure where upstream NetworkManager's equivalent of bugzilla is located.

Comment 2 Daniel Berrangé 2010-09-21 17:34:33 UTC
Even if NM doesn't yet support bridges, there's still value in letting unprivileged users configure plain eth/wifi interfaces via libvirt, so that NAT based connectivity can be setup. In fact for qemu://session that's pretty much all we want to be able todo via NM. Only changing qemu://system is dependant on bridging/bonding/vlans

Which reminds me that the libvirt/netcf XML/API doesn't have any way to provide wifi keys, or ESSID, channel, etc :-)

Comment 3 Thomas Graf 2011-11-11 17:02:37 UTC
Just a FYI, I'm working on getting both bonding and bridging support into NM and it will be available for RHEL7.0.

Can you elaborate on the interfaces you would need on NM's side?

I'd rather have netcf or a small python script be able to write an ifcfg file unprivleged and have NM pick it.

Comment 4 Cole Robinson 2019-02-06 23:47:04 UTC
This is a nice idea, but since the interface APIs never really took off with applications and netcf has more or less languished, I don't think this will ever be implemented, nor is it worth tracking

Note You need to log in before you can comment on or make changes to this bug.