[openstack-dev] How should we go about removing legacy VIF types in Queens?
kevin at benton.pub
Thu Jul 13 13:54:38 UTC 2017
Some of the stuff like '802.1qbh' isn't particularly vendor specific so I'm
not sure who will host it and a repo just for that seems like a bit much.
Should we just bite the bullet and convert them in the nova tree or put
them in os-vif?
On Thu, Jul 13, 2017 at 7:26 AM, Stephen Finucane <sfinucan at redhat.com>
> os-vif has been integrated into nova since the newton cycle. With the
> integration of os-vif, the expectation is that all the old, non-os-vif
> plugging/unplugging code found in  will be replaced by code that
> os-vif plugins . This has happened for a few of the VIF types, and newer
> VIFs are being added in this manner . However, there are quite a few
> that are still using the legacy path, and I think it's about time we
> moving things forward. Doing so allows us to continue to progress on
> os-vif objects from neutron and remove the large swathes of legacy code
> found in nova.
> I've opened a bug against networking-bigswitch  for one of these VIF
> IVS, and I'm thinking I'll do the same for a lot of the other VIF types
> where I
> can find definite vendors. Is there anything else we can do though? At some
> point we're going to have to just start deleting code and I'd like to avoid
> leaving operators in the lurch.
>  https://github.com/openstack/nova/blob/6205a3f8c/nova/virt/
>  https://github.com/openstack/nova/blob/6205a3f8c/nova/
>  https://github.com/Juniper/contrail-nova-vif-driver
>  https://bugs.launchpad.net/networking-bigswitch/+bug/1704129
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev