See salt issues #48309 #51925

Linux bridges are automatically set UP when
any parent interface is UP.

But for OVS bridges it doesn't work.

For dpdk and non-dpdk bridges, always create a
config file in /etc/network/interfaces.u/ and
bring the bridge interface up after it is configured,
even if it doesn't have IP address.

Change-Id: I92888ce0d373e412dfb7ed2e2398c0d4d008e301
Closes-Bug: https://mirantis.jira.com/browse/PROD-24343

Previous implementation was not able to add port 'dpdk0' to bridge
'br-dpdk0' since both matches 'grep' condition. To fix this we need to
look for port in a particular bridge

Change-Id: Ie83cebc3ab73c45a48f68fae2d6f474743215908

Change-Id: Ia8690d3968aa6c8491ec62b73f78afd6b2361c60

Wait for dpdk bond interfaces to come up.

linux.network.dpdk state fails to update a port within for loop
when this port does not exist yet.
Dependency will require interfaces to be added before

Prod-Related: PROD-19696
Closes-Bug: PROD-19696

Change-Id: Ia83218a76dd6e86664e7f9498a76341717eb5b80

Change-Id: I016a0737e700162e41a39cf5643d5ee3c42c2cc5
Prod-Related: PROD-20467

Issue: First time you configure dpdk ovs switch it would stuck on
       answering salt-minion because kernel options, such as
       intel_iommu,iommu,isolcpus, are not set and ovs would
       exhaust all hugepages and fail to apply options on the fly.

Fix:   Configure ovs switch without waiting for an answer and
       reboot the node afterall as we do this all the time before
       starting automated pipeline.

Change-Id: Ica27a6cc47312bcc0762cddde049a0abf771f9fb

Change-Id: Icd1745d401ec275687a007e6683175a13569f2b4

Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

By default, the alternative installed by `openvswitch-switch`
packages shadows (higher prio) `openvswitch-switch-dpdk` version,
e.g. for UCA Pike packages:

$ update-alternatives --query ovs-vswitchd
Alternative: /usr/lib/openvswitch-switch-dpdk/ovs-vswitchd-dpdk
Priority: 50
Alternative: /usr/lib/openvswitch-switch/ovs-vswitchd
Priority: 100

To avoid confusion, when DPDK is enabled and ovs-vswitchd-dpdk
should be used, remove the alternative for classic ovs-vswitchd
(which can easily be re-eneabled later if needed).

Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>

iteritems() was dropped in recent Python3 releases and items() is compatible
with Python 2.7.

Bring in "tag" option for dpdk/ovs bridges
to support vlan-tagged vxlan mode.

Change-Id: I7f1f88233694f2c8b968a6cf55584f32879ec042

Currently when OVS-DPDK is enabled, instances fail to spawn
due to permissions mismatch, see nova bug for details:
https://bugs.launchpad.net/nova/+bug/1670950

This patch configures OVS to use a separate dir, created by
nova formula [1].

[1] https://gerrit.mcp.mirantis.net/11213

Related-PROD: PROD-14413

Change-Id: Ia86658b0967b4d35f063c7f6f53e26e78a1fbd39

Current logic does not apply n_rxq, pmd_rxq_affinity and mtu
for a dpdk port in case it is attached directly to a bridge
(not bonded).
This patch makes formula apply parameters in both cases.

Change-Id: I5b19999b1ac8a80d1e31b266fede7dad0d7fd0d4

Change-Id: Iec857e4ac374b7787892144c772063796be87c4b

This enables a more fine tuned dpdk for better performance.
More details on pmd-rxq-affinity config:
http://docs.openvswitch.org/en/latest/howto/dpdk/

Change-Id: I630c6af94ff733619fb175f522fc515984862ff6

Add possiblity to add ip address and mtu on dpdk ovs bridge to
be able use VXLAN as tenant segmentation.

Change-Id: I1394d30c5d9935218841b17ff7651dac7b4abefa
Epic: PROD-8957

Introduce dpdk support for linux OVS configuration.
It configures dpdk interface bind, ovs dpdk ports, bonding,
parameters for dpdk cpu pmd and set multique queues for specific
ovs dpdk interfaces.

Change-Id: I3f38660bab8db0c2b38f03ed8c94eb10b6b3beb9
Epic: PROD-8957
Epic: PROD-8958