[CONTROLLER-835] Wrong nodeIdentifier for MD-SAL service lookup Created: 15/Sep/14 Updated: 19/Oct/17 Resolved: 04/May/15 |
|
| Status: | Resolved |
| Project: | controller |
| Component/s: | adsal |
| Affects Version/s: | Helium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michal Rehak | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 1872 | ||||||||
| Description |
|
MD-SAL service lookup in FRM is based on nodeIdentifier which looks like: /nodes/node[id]/aug:flowCapableNode. This usually works. Result is that MD-SAL is not able to directly resolve provider and redirects request to binding independent context and then back to binding aware. Side effects are: performance leak caused by conversions and underlying augmentations are getting lost (discovered by nicira extensions - match). |
| Comments |
| Comment by Carol Sanders [ 04/May/15 ] |
|
This bug is part of the project to Move all ADSAL associated component bugs to ADSAL |