<html><body><p>Yes, we have been aware of the os-vif effort and will try to use it as soon as it is released. The scripts we currently use are to enable the use of the Neutron reference plugins/drivers in the meantime.<br><br>Best,<br><br>Mohammad<br><br><br><img width="16" height="16" src="cid:1__=8FBBF5F0DFF2FEA68f9e8a93df938690918c8FB@" border="0" alt="Inactive hide details for "Daniel P. Berrange" ---02/18/2016 05:36:05 AM---On Thu, Feb 18, 2016 at 09:01:35AM +0000, Liping Mao"><font color="#424282">"Daniel P. Berrange" ---02/18/2016 05:36:05 AM---On Thu, Feb 18, 2016 at 09:01:35AM +0000, Liping Mao (limao) wrote: > Hi Kuryr team,</font><br><br><font size="2" color="#5F5F5F">From: </font><font size="2">"Daniel P. Berrange" <berrange@redhat.com></font><br><font size="2" color="#5F5F5F">To: </font><font size="2">"OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org></font><br><font size="2" color="#5F5F5F">Date: </font><font size="2">02/18/2016 05:36 AM</font><br><font size="2" color="#5F5F5F">Subject: </font><font size="2">Re: [openstack-dev] [Kuryr] will we use os-vif in kuryr</font><br><hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br><br><br><tt>On Thu, Feb 18, 2016 at 09:01:35AM +0000, Liping Mao (limao) wrote:<br>> Hi Kuryr team,<br>> <br>> I see couple of commits to add support for vif plug.<br>> </tt><tt><a href="https://review.openstack.org/#/c/280411/">https://review.openstack.org/#/c/280411/</a></tt><tt><br>> </tt><tt><a href="https://review.openstack.org/#/c/280878/">https://review.openstack.org/#/c/280878/</a></tt><tt><br>> <br>> Do we have plan to use os-vif?<br>> </tt><tt><a href="https://github.com/openstack/os-vif">https://github.com/openstack/os-vif</a></tt><tt><br><br>FYI, we're trying reasonably hard to *not* make any assumptions about<br>what compute or network services are using os-vif. ie, we want os-vif<br>as a framework to be usable from Nova, or any other compute manager,<br>and likewise be usable from Neutron or any other network manager.<br>Obviously the actual implementations may be different, but the general<br>os-vif framework tries to be agnostic.<br><br>Regards,<br>Daniel<br>-- <br>|: </tt><tt><a href="http://berrange.com">http://berrange.com</a></tt><tt> -o- </tt><tt><a href="http://www.flickr.com/photos/dberrange/">http://www.flickr.com/photos/dberrange/</a></tt><tt> :|<br>|: </tt><tt><a href="http://libvirt.org">http://libvirt.org</a></tt><tt> -o- </tt><tt><a href="http://virt-manager.org">http://virt-manager.org</a></tt><tt> :|<br>|: </tt><tt><a href="http://autobuild.org">http://autobuild.org</a></tt><tt> -o- </tt><tt><a href="http://search.cpan.org/~danberr/">http://search.cpan.org/~danberr/</a></tt><tt> :|<br>|: </tt><tt><a href="http://entangle-photo.org">http://entangle-photo.org</a></tt><tt> -o- </tt><tt><a href="http://live.gnome.org/gtk-vnc">http://live.gnome.org/gtk-vnc</a></tt><tt> :|<br><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br></tt><tt><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a></tt><tt><br><br></tt><br><BR>
</body></html>