Ricard Vilalta

Alignment of swagger with restconf

1

For T-API 2.0 alignment with RFC restconf will be needed. 1. for configuration and state data: /restconf/data/… and not /restconf/config/… 2. access to lists by key should look like: …/_topology=top0...

path is a prohibited keyword in swagger. The tooling doesn't distinguish it. Two solutions: a) the swagger plugin adds _def to path object name (path_def). b) we rename path in...

TAPI security mechanism

3

Received: While trying connect TAPI controller, I bumped into authentication issues. I see no reference to security in the SWAGGER files, meaning each vendor can implement its own security mechanism....

Related: https://github.com/OpenNetworkingFoundation/Snowmass-ONFOpenTransport/issues/163 Alignment with RFC restconf will be needed: a) for configuration and state data: /restconf/data/… and not /restconf/config/… b) access to lists by key should look like: …/_topology=top0 and...

Example: getattr(sys.modules[**name**], **name**).add_url_rule("/restconf/config/Context/_connection//_connectionPort//_connectionEndPoint/_layerProtocol//", view_func = globals()["Context_ConnectionUuid_ConnectionportLocalid_Connectionendpoint_LayerprotocolLocalidMethodView"].as_vie Proposed solution: Add a counter to the duplicated parameter e.g.

Example: list costCharacteristic { ``` key 'costName costValue costAlgorithm'; config false; min-elements 1; uses CostCharacteristic; description "The list of costs where each cost relates to some aspect of the TopologicalEntity.";...