On Mon, Jun 18, 2012 at 02:21:48PM -0700, Joshua Harlow wrote:
Hi all netcf peoples,
Me and others are looking at integrating this library as one of the
components in a project called OpenStack that eventually needs to write
network configuration in a distribution agnostic manner (ie the incoming
format should not be tied to say debian or fedora). It seems like this is
the library to go for that and I had some questions.
1. How actively maintained is this project, just incase.
It is a core dependency of libvirt, so it is actively maintained
2. Does netcf over-write configurations or does it have the
capability
to also merge configs (incase of user provided additions/configuration
extras that we don’t want to over-write).
The answer depends on the driver you are using. For the Linux drivers
at least (Debian, Suse & Fedora/RHEL), netcf uses augeas to update
the configs. When setting the config of an interface, any previous
config for that interface will normally be discarded. So if there
are config elements not currently supported by augeas/netcf that
are required for correct operation, support should be added to
netcf for them.
From an OpenStack POV, I think I'd actually encourage use of the
libvirt virNetworkPtr APIs rather than netcf directly. The use of
netcf is only really applicable to the Xen, UML, KVM/QEMU or LXC
drivers in libvirt. If using something else like libvirt's drivers
for VMWare, HyperV, VirtualBox, etc then netcf would be a wrong
choice. By using libvirt, the applicable network device management
driver would be correctly chosen to match the hypervisor driver.
Regards,
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|