Adding dependency validations for QoS on ports and network

[Manjeet Singh Bhatia]

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

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/417260

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/417260
Committed: https://git.openstack.org/cgit/openstack/networking-odl/commit/?id=1f93f80037f166a5a7f1a2e79ae738680a5f56ed
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

[Isaku Yamahata (yamahata)]

it's already classified for triage.