search

Open-Network-Models-and-Interfaces-ONMI / TAPI

LF ONMI Transport API Repository (TAPI)
https://github.com/Open-Network-Models-and-Interfaces-ONMI/TAPI/wiki
Apache License 2.0
95 stars 80 forks source link

ResilienceConstraint, selectionControl. Only one SwitchControl per ConnectivityService? #427

Closed amazzini closed 6 months ago

amazzini commented 5 years ago

Which is the purpose of selectionControl attribute? The comment (same as routeSelectionControl of FcRoute class of Core IM) is “Degree of administrative control applied to the switch selection.” Unclear whether is actually read only (i.e. telling the state of the overall protection scheme as a result of operator command) or provisionable. If provisionable, through updateConnectivityService operation it is possible to lockout/force/manual switch the (unique) SwitchControl, but anyway seems missing where to switch (main or spare etc.). Note that ResilienceConstraint class is 1 to 1 with SwitchControl, but also 0..1 to 1 with ConnectivityService – in other words, a ResilienceConstraint instance must be related to one ConnectivityService. Put all together, there could be only one SwitchControl per ConnectivityService. I wonder whether we need to split ResilienceConstraint into two classes, one dedicated to ConnectivityService and another one dedicated to the single SwitchControl.

amazzini commented 6 months ago

Deferred to the specification of manual switch command use case.