[netcf-devel] Re: [libvirt] [RFC] why netcf/libvirt lists/dumpxml only unslaved/unsubordinated interfaces?

Daniel P. Berrange

2016-11-15 12:12:48 UTC

It could be useful to dumpxml of slaves/subordinates too to introspect
'Interface eth0 does not exist or is not a toplevel interface'.
Has it some deeper meaning or netcf can be enhanced? (and *libvirt* as well).

The netcf API / libvirt Interface APIs are designed to work against the
concept of logical network connections, which may comprise multiple
physical interfaces. They are explicitly *not* a way to query all
individual physical interfaces - that's what libvirt's node device APIs
are for.

I donno. AFAIU you can start with bridge and unslaved physical interface. They are both
in list and can be dumped. Then you enslave interface to the bridge via netcf's define
and then physical interface can not be reached anymore. If I can not change host interfaces
tree then it would be ok I guess.

That is expected behaviour. You originally had 2 separate logical
connections, and you've changed the system to have a single logical
connection.

Regards,
Daniel

--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
_______________________________________________
netcf-devel mailing list -- netcf-***@lists.fedorahosted.org
To unsubscribe send a