[openstack-dev] [Nova] Liberty Priorties for Nova

Daniel P. Berrange berrange at redhat.com
Wed Jun 10 08:42:32 UTC 2015

On Wed, Jun 10, 2015 at 08:48:36AM +0200, Andreas Scheuring wrote:
> Daniel, 
> if I got it right, the vif script blueprint only is about plug/unplug
> operations and not about generating new xml representations for vif
> types. What if for a new vif type it's sufficient to have the
> get_config_* method updated? In this case plug/unplug would be handled
> by libvirt (like with many other existing vif types). The plug/unplug
> methods would just contain a "pass".
> Would you tend to be supportive in such cases?

Probably, but it depends if there is any overlap with existing VIF
drivers in terms of libvirt config generated.

|: 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 :|

More information about the OpenStack-dev mailing list