Andrea Mazzini and Arturo Mayoral, review of existing open issues regarding the yang2oas tool. Agreed that currently there are two known issues (agreed that #430 is not related to RESTCONF compliance):
Generated .yaml modules do not include these API listed in TR-547:
Agreed that these API can be removed from TR-547, leveraging field based filtering, e.g.
/tapi-common:context/tapi-connectivity:connectivity-context/ according to RESTCONF shall include in the reply all composed entities, i.e. in this case all ConnectivityServices and their CSEPs.
Agreed that TR-547 shall include which fieldand depth are required per each API.
Note 1: Arturo Mayoral says that filtering is essential to flow control. Streaming should be the best future solution.
Note 2: the yang2oas tool will not generate all possible filtering capabilities, hence the (required) filtered API shall be manually built. Arturo Mayoral thinks that a good guidance/description can fill the gap.
Arturo Mayoral says that the issue is not completely solved. The augmentations are coded in a way (x-augmentation) which is not understood by further tools which take the .yaml as input. Karthik Sethuraman manual editing may be complex in case of multiple augmentations (e.g. TapiEth spec class which augments TapiOam class which in turn augments TapiConnectivity class).
Agreed to plan a slot on Wednesday 21 to continue the analysis.
Note the "FAILED" CS state when the ConnectivityService intent eventually fails, i.e. the server controller is not able to fulfil the request. At this stage, it is possible to either delete or update the "FAILED" ConnectivityService.
"Atomic" behavior implies that all Connections that were created are removed when the CS provisioning "fails".
"soft"/"controlled" lockout: the resource is put in oos only when there are no more supported resources but is not deleted, hence is expected a future unlock.
"soft"/"controlled" deletion: the resource is definitively deleted - i.e. the identifier cannot be reused, only when there are no more supported resources.
Client/server Connectivity-services relations and implications for deletions
Below a summary of agreements:
The ConnectivityService (CS) provisioning can cause the creation of server ConnectivityServices. As a general rule, a CS will be created for each supporting Top Connection, to allow editing of all network layers. E.g. a DSR CS provisioning will cause the creation of
DSR Top Connection
ODU4 CS and its ODU4 Top Connection
OTSi CS and its OTSi Top Connection
MC CS and its MC Top Connection
The deletion of a CS does not imply the deletion of any server CS (controlled behavior).
This allows to reuse CS as routing constraints of new client CS.
For further evaluation a possible exception in case e.g. no multiplexing, deletion of DSR 10G CS may imply deletion of unique, dedicated server ODU2 CS.
The deletion of a CS is rejected if any client CS exists (need to design a "in use" state of the CS).
Nigel Davis , qianjia and Malcolm Betts underline that the provisioning of the ODU4 on ENNI side is not necessarily in the scope of DSR ConnectivityService provisioning.
After long and detailed discussions, the team reaches a preliminary agreement on this view, where the ENNI-ODU4 related provisioning is independent from DSR provisioning:
Agreed that the ENNI can be pre-provisioned by server controller till OTSi or OTU or ODU layers. In other words, the topology model may offer hooks (potential CTPs) for connectivity provisioning at different layers.
So far TAPI model encapsulated OTU and ODU in same ODU CEP object. The team carefully evaluates the pros and cons to de-encapsulate OTU layer, for the following reasons:
Meeting ID: 810 8906 8444 Passcode: 681529 One tap mobile +19292056099,,81089068444#,,,,,,0#,,681529# US (New York) +13017158592,,81089068444#,,,,,,0#,,681529# US (Germantown)
Dial by your location +1 929 205 6099 US (New York) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) Meeting ID: 810 8906 8444 Passcode: 681529 Find your local number: https://us02web.zoom.us/u/kdFJwLpSVr
TAPI Virtual Meeting - Day 4
Mon Nov 9, 2020 07:00 – 12:00 Eastern Time - New York
Topic: TAPI Virtual Meeting Time: Nov 9, 2020 04:00 AM Pacific Time (US and Canada)
Meeting ID: 833 4319 7217 Passcode: 851992 One tap mobile +13017158592,,83343197217#,,,,,,0#,,851992# US (Germantown) +13126266799,,83343197217#,,,,,,0#,,851992# US (Chicago)
Dial by your location +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 929 205 6099 US (New York) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) Meeting ID: 833 4319 7217 Passcode: 851992 Find your local number: https://us02web.zoom.us/u/keCpZTa4ag