Description of problem: 
TripleO support for Jumbo frames and Multiqueue

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info: 
Blueprint: https://blueprints.launchpad.net/tripleo/+spec/ovs-2-6-dpdk

Blueprint Details below. 
Jumbo Frames:
The feature “Jumbo Frames”[2] can be enabled by configuring the MTU value for the OVS-DPDK interface and OVS-DPDK bond. Already os-net-config supports an option for providing MTU values[1], but for DPDK it has to be set to the OvS DB with below command:
 ovs-vsctl -- set Interface <DPDK device> mtu_request=<frame size>

DPDK port types in os-net-config shall append this to ovs_extra and update to the ifcfg files if MTU value is set on the DPDK interface and bond.

[1] http://docs.openstack.org/developer/tripleo-docs/advanced_deployment/network_isolation.html#configuring-jumbo-frames
[2] https://software.intel.com/en-us/articles/jumbo-frames-in-open-vswitch-with-dpdk

Multi-queue support:
OVS2.6 has support to specify the number of multi-queues per physical interface. The command, “ovs-vsctl set Interface <DPDK interface> options:n_rxq=<integer>”, will set the number of multi-queues in OvS DB, that can be used for this interface. The rx queues are assigned to pmd threads on the same NUMA node in a round-robin fashion.

A new parameter “rx_queues” shall be added to all DPDK interface types to configure the number of queues.

- type: ovs_user_bridge
  name: br-link
  memebers:
    -
      type: ovs_dpdk_port
      name: dpdk0
      rx_queues: 4
      members:
        -
          type: interface
          name: nic2

Note that this value can be provided via ovs_extra of the interface, but having it as separate value provides better usability.