[TRNSPRTPCE-145] Init North T-API support (CCVPN Use case) Created: 06/Sep/19 Updated: 03/Sep/21 Resolved: 11/Oct/19 |
|
| Status: | Verified |
| Project: | transportpce |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | High |
| Reporter: | Olivier Renais | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 4 weeks, 2 days | ||
| Time Spent: | 1 week, 3 days | ||
| Original Estimate: | 6 weeks | ||
| Description |
|
A first analysis will allow determining whether v2 or v3 of TAPI is the most adapted to handle this use case (considering the roadmap of T-API). Develop North T-API to abstract the OpenROADM topology in ONAP A&AI. For future use in the ONAP CCVPN use case. One Continuous (Any to any connectivity) OpenROADM domain shall be abstracted as a node with its access and interconnection points. translate the OpenROADM topology in the T-API format NB: sendate branch T-API version is 2.0.2 |
| Comments |
| Comment by Olivier Renais [ 11/Oct/19 ] |
|
Needed to change time estimation |