Interesting,
On 06/19/2012 10:30 AM, Daniel P. Berrange wrote:
> On Mon, Jun 18, 2012 at 02:21:48PM -0700, Joshua Harlow wrote:
>> 1. How actively maintained is this project, just incase.virInterface, actually :-)
> 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
Another advantage of using libvirt's virInterface API rather than netcf
> 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.
is that libvirt has builtin RPC, while netcf is a local-machine-only
API. Everything supported by calling netcf directly is also supported in
a similar/identical API in libvirt.
_______________________________________________
netcf-devel mailing list
netcf-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/netcf-devel