Re: [openstack-dev] How should we go about removing legacy VIF types in Queens?

2017-07-19 Thread Kevin Benton
Yeah, if one clearly belongs to a single vendor moving is definitely the way to go. OVS itself is a good example of one that is used by lots of drivers. Since it's in os-vif maybe we should do the same for any others without a clear association (e.g. vif_type='tap' is about as vendor agnostic as

Re: [openstack-dev] How should we go about removing legacy VIF types in Queens?

2017-07-19 Thread Stephen Finucane
On Thu, 2017-07-13 at 07:54 -0600, Kevin Benton wrote: > On Thu, Jul 13, 2017 at 7:26 AM, Stephen Finucane wrote: > > > 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 > >

Re: [openstack-dev] How should we go about removing legacy VIF types in Queens?

2017-07-13 Thread Kevin Benton
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