Cleanup 'direct' VNIC semantics, preparing for offloads
Bug #1766925 reported by
Jan Gutter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R4.1 |
Fix Committed
|
High
|
Jan Gutter | |||
R5.0 |
Fix Committed
|
Undecided
|
Jan Gutter | |||
Trunk |
Fix Committed
|
Undecided
|
Jan Gutter | |||
OpenContrail |
New
|
Undecided
|
Unassigned |
Bug Description
The 'direct' VNIC type was closely associated with the hw_veb VIF type. Upstream OpenStack moved towards using the VNIC type to indicate offloading for the 'ovs' VIF type. It's therefore possible to specify that the combination of 'vrouter' VIF type, 'direct' VNIC type and no specified provider network should indicate that an offloaded VM port is requested.
tags: | added: vrouter |
To post a comment you must log in.
Review in progress for https:/ /review. opencontrail. org/42478
Submitter: Jan Gutter (<email address hidden>)