libnl should be updated to support SR-IOV

[Dmitry Nikishov]

Environment:
7.0/Ubuntu/KVM/Neutron+VLAN/1 controller/1 compute/Intel 82599 NICs

Steps to reproduce:
1. Configure and deploy environment: add "intel_iommu=on" to kernel parameters
2. Configure SR-IOV according to this guide https://wiki.openstack.org/wiki/SR-IOV-Passthrough-For-Networking
3. Create an SR-IOV Neutron port: neutron port-create net04 --binding:vnic-type=direct
4. Launch an instance: nova boot --image TestVM --flavor m1.small --nic port-id=<uuid of the port> sriov-test-00

Expected result:
Instance has been successfully launched. It may not have network connectivity as TestVM doesn't include ixgbevf driver required for VFs. But that's not a problem.

Actual result:
Instance fails to spawn. Compute log: http://paste.openstack.org/show/475053/

This is fixed by manual upgrade of libnl to 3.2.24-2 (vivid/utopic):
libnl-3-200_3.2.24-2_amd64.deb
libnl-genl-3-200_3.2.24-2_amd64.deb
libnl-route-3-200_3.2.24-2_amd64.deb

MOS should install these versions by default.

[Alexei Sheplyakov (asheplyakov)]

In general updating core OS components is not welcome at all. In particular upgrading libnl might break iproute, iptables, qemu, openvswitch, and other networking software. Also libnl is tightly coupled with in kernel netlink ABI, therefore upgrading only user space part (libnl) might break the whole system.

[Alexei Sheplyakov (asheplyakov)]

> MOS should install these versions by default.

No, it shouldn't (see the comment #1). If you need libnl from vivid, upgrade the whole system to vivid.

[Vitaly Sedelnik (vsedelnik)]

Won't Fix for 7.0-updates - we don't want to update core OS packages in MUs

[Roman Podoliaka (rpodolyaka)]

AFAIU, we are doing this in 8.0-MU1