Bug 1628811 - [RFE] NIC Partitioning - OVS-DPDK setup on a VF
Summary: [RFE] NIC Partitioning - OVS-DPDK setup on a VF
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: os-net-config
Version: 16.1 (Train)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: z2
: 16.1 (Train on RHEL 8.2)
Assignee: Karthik Sundaravel
QA Contact: Miguel Angel Nieto
URL:
Whiteboard:
Depends On:
Blocks: 1883318
TreeView+ depends on / blocked
 
Reported: 2018-09-14 05:20 UTC by Karthik Sundaravel
Modified: 2020-10-27 18:34 UTC (History)
22 users (show)

Fixed In Version: os-net-config-8.5.1-2.el7ost
Doc Type: Enhancement
Doc Text:
This update adds NIC partitioning support on Intel and Mellanox NICs.
Clone Of:
: 1883318 (view as bug list)
Environment:
Last Closed: 2020-10-13 10:53:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Karthik Sundaravel 2018-09-14 05:20:57 UTC 
Description of problem:
os-net-config shall 
1. bind a VF, specified by vf id to DPDK driver
2. Generate the ifcfgs and VF configurations for the dpdk port and ovs user bridge


Steps to Reproduce:
1. Deploy a cluster with NIC partitioning
2. One of the VF shall be configured for DPDK/OvsUserBridge
3. Create 2 guests on the DPDK network on 2 different nodes and check if they are reachable


Expected result:
Should be able to use a VF for ovs user bridge and guests shall be able to use the network.
i.e ping test between 2 guests created on 2 different nodes shall be done.
Comment 3 Bob Fournier 2018-09-25 21:20:32 UTC 
Hi Karthik, its not clear from this bug - are you working on a fix for this and is it planned for a release?
Comment 4 Karthik Sundaravel 2018-09-26 04:24:28 UTC 
Hi Bob,

Yes, I am trying to identify the root cause of this and its targeted for OSP15.
Comment 5 Bob Fournier 2018-09-26 13:37:55 UTC 
Thanks Karthik.
Comment 7 Franck Baudin 2018-10-03 06:48:43 UTC 
Reassigned to DFG:NFV, as managed by Karthic from day1.
Comment 27 Miguel Angel Nieto 2020-10-13 07:19:49 UTC 
Verified using nic and mellanox cards. Created a vm on top of dpdk network and checked that there is ping. Used puddle RHOS-16.1-RHEL-8-20200930.n.0

              - type: ovs_user_bridge
                name: br-link0
                use_dhcp: false
                mtu: 9000
                ovs_extra:
                  - str_replace:
                      template: set port br-link0 tag=_VLAN_TAG_
                      params:
                        _VLAN_TAG_:
                           get_param: TenantNetworkVlanID
                addresses:
                  - ip_netmask:
                      get_param: TenantIpSubnet
                members:
                  - type: ovs_dpdk_bond
                    name: dpdkbond0
                    mtu: 9000
                    rx_queue: 1
                    ovs_extra:
                      - set port dpdkbond0 bond_mode=active-backup
                    members:
                      - type: ovs_dpdk_port
                        driver: mlx5_core (only for mellanox cards)
                        name: dpdk0
                        members:
                          - type: sriov_vf
                            device: nic11
                            vfid: 2
                      - type: ovs_dpdk_port
                        driver: mlx5_core (only for mellanox cards)
                        name: dpdk1
                        members:
                          - type: sriov_vf
                            device: nic12
                            vfid: 2
Comment 28 Lon Hohberger 2020-10-13 10:53:11 UTC 
According to our records, this should be resolved by os-net-config-11.3.2-0.20200521033427.b34a730.el8ost.  This build is available now.
Note You need to log in before you can comment on or make changes to this bug.