Uploaded image for project: 'netvirt'
  1. netvirt
  2. NETVIRT-1225

QOS bandwidth rule not pushed to ovs dpdk port

    XMLWordPrintable

Details

    • Bug
    • Status: Verified
    • Medium
    • Resolution: Done
    • None
    • Oxygen
    • General

    Description

      1. TROUBLE DESCRIPTION
      1.1. Trouble summary
      QOS bandwidth rule not pushed to ovs dpdk port

      1.2. Detailed trouble description

      QOS bandwidth rule not pushed to ovs dpdk port
      steps:

      • create a bandwidth rule and apply to the port
      • observe bandwidth rule in REST API
        bug: bandwidth rule not pushed to ovs port
        1.3. Frequency of fault
        reproducible

      1.5. System impact
      feature affected

      1.6. Known problem within the ODL/OVS community?
      Not known

      2.2. SW Configuration details

      ODL NAME=BORON

      neutron qos-policy-create qos_policy

      Created a new policy:
      -----------------------------------------------------+

      Field Value

      -----------------------------------------------------+

      created_at 2017-11-09T11:49:27Z
      description  
      id 82040586-3ef8-4052-a4c5-f14251860d4e
      name qos_policy
      project_id c39b07c4896d4275a39a7300510a1127
      revision_number 1
      rules  
      shared False
      tenant_id c39b07c4896d4275a39a7300510a1127
      updated_at 2017-11-09T11:49:27Z

      -----------------------------------------------------+
      [heat-admin@overcloud-compute-0 ~]$

      neutron qos-bandwidth-limit-rule-create 82040586-3ef8-4052-a4c5-f14251860d4e --max-kbps 10000 --max-burst-kbps 2000

      22:47:59.538 INFO Created a new bandwidth_limit_rule:
      ----------------------------------------------------+

      Field Value

      ----------------------------------------------------+

      id 2ad8bb03-33c8-4a01-a3db-9552ab993838
      max_burst_kbps 2000
      max_kbps 10000

      ----------------------------------------------------+
      [heat-admin@overcloud-compute-0 ~]$

      neutron port-update PORT3 --qos-policy qos_policy

      Updated port: PORT3
      [heat-admin@overcloud-compute-0 ~]$

      Getting VHU Port id:

      neutron port-list | grep "PORT3 " | awk '

      {pr int $2}

      '

      a9c8e071-f5fe-4af8-8eee-989113039b74

      vhu name: vhua9c8e071-f5

      Executing command 'sudo ovs-vsctl list interface vhua9c8e071-f5

      22:48:03.443 INFO _uuid : 9dad1161-25e7-4ad3-a4d5-751cc6218d35
      admin_state : up
      bfd : {}
      bfd_status : {}
      cfm_fault : []
      cfm_fault_status : []
      cfm_flap_count : []
      cfm_health : []
      cfm_mpid : []
      cfm_remote_mpids : []
      cfm_remote_opstate : []
      duplex : []
      error : []
      external_ids :

      {attached-mac="fa:16:3e:86:d8:f4", iface-id="a9c8e071-f5fe-4af8-8eee-989113039b74", iface-status=active, vm-uuid="45725548-e9a4-4cf1-9013-5b3659a09c20"}

      ifindex : 0
      ingress_policing_burst: 0
      ingress_policing_rate: 0
      lacp_current : []
      link_resets : 0
      link_speed : []
      link_state : up
      lldp : {}
      mac : []
      mac_in_use : "00:00:00:00:00:00"
      mtu : 2140
      mtu_request : []
      name : "vhua9c8e071-f5"
      ofport : 293
      ofport_request : []
      options : {}
      other_config : {}
      statistics :

      {"rx_1024_to_1522_packets"=0, "rx_128_to_255_packets"=0, "rx_1523_to_max_packets"=0, "rx_1_to_64_packets"=0, "rx_256_to_511_packets"=2, "rx_512_to_1023_packets"=0, "rx_65_to_127_packets"=8, rx_bytes=1332, rx_dropped=0, rx_errors=0, rx_packets=10, tx_bytes=992, tx_dropped=0, tx_packets=5}

      status : {}
      type : dpdkvhostuser

      Does not match 'ingress_policing_burst: 2000

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            sharmaarun Arun Sharma
            snaidus Srinivas Balajinaidu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days
                2d