yahoo-eng-team team mailing list archive

[Boden R <bodenvmw@xxxxxxxxx>]

Based on what I see the change introduced the vif type of 'hostdev_physical'.
This is already documented as a vif type for ports in our API ref, for example [1].
The response parameters show:

---
binding:vif_type
The type of which mechanism is used for the port. An API consumer like nova can use this to determine an appropriate way to attach a device (for example an interface of a virtual server) to the port. Available values currently defined includes ovs, bridge, macvtap, hw_veb, hostdev_physical, vhostuser, distributed and other. There are also special values: unbound and binding_failed. unbound means the port is not bound to a networking back-end. binding_failed means an error that the port failed to be bound to a networking back-end.
---

As seen above, the parameter documentation includes hostdev_physical so
we should be all set for this one.

[1] https://developer.openstack.org/api-ref/network/v2/index.html#show-
port-details

** Changed in: neutron
       Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1538695

Title:
      sriov-mech: Introduce a new VIF type for PF vnic type

Status in neutron:
  Fix Released
Status in openstack-api-site:
  Fix Released

Bug description:
  https://review.openstack.org/262604
  Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
  Your project "openstack/neutron" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

  commit 4a431f75a01fbdd0b802c86e27a93a6daaf70399
  Author: Nikola Dipanov <ndipanov@xxxxxxxxxx>
  Date:   Wed Dec 30 19:48:33 2015 +0000

      sriov-mech: Introduce a new VIF type for PF vnic type
      
      We need to tell Nova to use a specific VIF type for full PF passthrough
      (this is the recently added VNIC_DIRECT_PHYSICAL vnic type).
      
      Make sure that when binding ports with this vnic type, we set the
      appropriate vif type for Nova to be able to provision those ports
      correctly.
      
      Nova change that adds a vif driver for this vif type:
      
      https://review.openstack.org/#/c/262583/
      
      DocImpact: Exposes a new vif type for PF passtrhough vnic type
      
      Change-Id: I895dab98e5e5a9369771539e51ba5c500bfe0045
      Related-blueprint: sriov-pf-passthrough-neutron-port

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1538695/+subscriptions