[GBP-201] Need containers in tenant for policy and forwarding-context Created: 04/Dec/15 Updated: 09/Dec/15 Resolved: 09/Dec/15 |
|
| Status: | Resolved |
| Project: | groupbasedpolicy |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Keith Burns | Assignee: | Martin Sunal |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4724 |
| Description |
|
Recent changes to centralise endpoints and create service and step towards renderer listening on ResolvedPolicy instead of Tenant OPER IID have highlighted state issues with listeners. The separation of policy and forwarding-context into containers in Tenant will resolve this, but this is technically an API change that we only discovered this morning after merging https://git.opendaylight.org/gerrit/#/c/30666/ A patch is being worked ASAP, and an email will be sent highlighting the minor change to API (its the addition of "/policy" and "/forwarding-context" to the existing tenant API: restconf/config/policy:tenants/policy:tenant/<tenant-name>/ id will become: id |
| Comments |
| Comment by Martin Sunal [ 07/Dec/15 ] |