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. 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 :| __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
