Comment 2 for bug 1651129

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-powervm (master)

Reviewed: https://review.openstack.org/412458
Committed: https://git.openstack.org/cgit/openstack/networking-powervm/commit/?id=e64928fd16d2f79b46f8e1f9a1649ef41471278a
Submitter: Jenkins
Branch: master

commit e64928fd16d2f79b46f8e1f9a1649ef41471278a
Author: Sridhar Venkat <email address hidden>
Date: Mon Dec 19 08:37:21 2016 -0500

    Physical network not included in vif details

    SR-IOV mechanism driver in networking_powervm/plugins/ml2/drivers/
    mech_pvm_sriov.PvmSRIOVMechanismDriver does not include
    'physical network' in the custom vif details. Method
    customize_vif_details prepares a dictionary like this :
    {'redundancy': 1, 'physical_ports': [u'U78C9.001.WZS05TG-P1-C5-T1'],
    'vlan': '2200', 'port_filter': False, 'capacity': 0.02}
    It does not include physical_network.
    This is not a bug, but SR-IOV vif plug mechanism in
    nova_powervm/virt/powervm/vif.PvmVnicSriovVifDriver.plug can use
    physical_network value to calculate physical ports in migration
    scenario (future work in nova_powervm).

    Above mentioned plug mechanism currently uses get_physical_network method
    in nova/network/model.VIF class. This method expects physical_network in
    custom vif details prepared by mechanism driver.

    This patchset fixes this by adding physical_network to vif details by
    getting it from network segment.

    Unit tests added.

    Change-Id: I379c9deceb72e4d5ea17891120d065230578d59e
    Closes-Bug: #1651129