No lookup available for NSP allocated resources
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Group Based Policy |
Triaged
|
Wishlist
|
Magesh GV |
Bug Description
E.g. An IP address is allocated if a NSP specifies that an IP be reserved from the associated PTG (the NSP would have the entry: type:ip_single, name: "vip_ip", value: "self_subnet")
In this case, there is no easy way to look up that the particular IP allocated was a result of the NSP association. One can look up the VIP resources in the system, and then inspect the IP address to find out which belongs to the associated PTG and thus making the correlation - clearly a matter of reverse engineering.
E.g. A Floating IP is requested to be allocated for every PT in a PTG (the NSP would have the entry: type:ip_pool, name: "nat_fip", value: "nat_pool")
In this case a floating IP is allocated for every PT in the PTG. To find out which floating IP is associated with which PT, one would have to find the Port association for each PT, and then look up the Floating IP associated with that port.
The above can be alleviated by providing a catalog of the form:
NSP-ID:name, PTG-ID:name, NSP-Type, NSP-Name, NSP-Allocated-
The "Corresponding-
Changed in group-based-policy: | |
importance: | High → Wishlist |
Changed in group-based-policy: | |
milestone: | kilo-gbp-4 → next |