[TRNSPRTPCE-116] Support for ROADM connection map Created: 08/May/19 Updated: 03/Sep/21 Resolved: 03/Sep/21 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Medium |
| Reporter: | Jonas Mårtensson | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When building the OpenROADM topology, it is currently assumed that all degrees and SRGs are fully connected, i.e. express links always exist between all degrees and add-drop links always exist between SRGs and all degrees. The OpenROADM device YANG model includes the connection-map attribute to describe any connectivity restrictions between degrees and SRGs. Is there any plan to take the connection-map into account when building the OpenROADM topology? |
| Comments |
| Comment by Olivier Renais [ 28/May/19 ] |
|
Yes. But to be honest this is not one of our highest priority. At that time we assume all OR equipment provide full connectivity with no specific restrictions according to the SRG/degree we consider. So this is not in the short (even mid-term) roadmap |