Adding dependency validations for QoS on ports and network

Bug #1654061 reported by Manjeet Singh Bhatia
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Manjeet Singh Bhatia

Bug Description

we have a dependency of QoS operation on network and port to which policies are attached, but since
it is not possible to get parent resource id (network or port id from qos data), which makes both totally independent operations, So one solution could be fetch all rows whose object type is network or port and
they are pending or processing state, then for each item check if any corresponding qos policy is attached,
if so then return false and operation on qos policy would be invalid

Changed in networking-odl:
assignee: nobody → Manjeet Singh Bhatia (manjeet-s-bhatia)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to networking-odl (master)

Related fix proposed to branch: master

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to networking-odl (master)

Submitter: Jenkins
Branch: master

commit 1f93f80037f166a5a7f1a2e79ae738680a5f56ed
Author: Manjeet Singh Bhatia <email address hidden>
Date: Fri Jan 6 01:38:16 2017 +0000

    Add a method to query operations

    While implementing QoS, we figured out dependency of operation
    on network and port can't be completed with existing api, because
    QoS policy data does not have networks and ports id which are
    attached to it. This patch will add a method which will fetch
    all operations on resources in pending or processing state.

    So Idea to solve dependency validation for QoS is to fetch all
    rows on network and port operations which are in pending or
    processing state using method added in this patch and verify
    for each row if network data or port data have specific QoS policy
    hooked to it.

    Change-Id: I4d1e44b18e41ffd80c6ea85000c6a212d3f459b2
    Related-Bug: #1654061

Changed in networking-odl:
status: New → Fix Released
status: Fix Released → New
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Isaku Yamahata (yamahata) wrote :

it's already classified for triage.

Changed in networking-odl:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.