Unbind DPDK nics for modified network config during deployment update

[Saravanan KR]

During the initial deployment, network config is configured as below:
- nic1: dpdk
- nic2: non-dpdk
- nic3: non-dpdk

During an deployment update, the network config is modified as below:
- nic1: non-dpdk
- nic2: non-dpdk
- nic3: dpdk

In this a case, the DPDK bound nic1 has to be unbound before performing ifup/down operations.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/373680

[Alex Schultz (alex-schultz)]

Is this bug still in progress? The patch has been sitting for about 8 months.

[OpenStack Infra (hudson-openstack)]

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/373680
Reason: Per policy documented here: http://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandomment.html - we decided to abandon this patch. If you want to work on it again, feel free to restore it. Any question about that can be asked on #tripleo.

[Juan Antonio Osorio Robles (juan-osorio-robles)]

Is this still needed?

[Saravanan KR (skramaja)]

It is not of priority as we dont recommend update with nic config changes. I will close it.