You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently TAPI does not allow users to enable/disable resources to prevent them to be used. The most clear case is to block a link/node/node-edge-point for a maintenance operation.
From current definition it seems the "admin-state" attribute associated to many TAPI objects would be the appropiate element to modify the state of a resource ( LOCKED/UNLOCKED), however is not writable (config false) in the model.
It is needed to evaluate how this use case can be implemented, a possible solution would be to define a new "intent-alike" structure within "OAM" tapi service, to allow the user to put a resource in maintenance
The text was updated successfully, but these errors were encountered:
Currently TAPI does not allow users to enable/disable resources to prevent them to be used. The most clear case is to block a link/node/node-edge-point for a maintenance operation.
From current definition it seems the "admin-state" attribute associated to many TAPI objects would be the appropiate element to modify the state of a resource ( LOCKED/UNLOCKED), however is not writable (config false) in the model.
It is needed to evaluate how this use case can be implemented, a possible solution would be to define a new "intent-alike" structure within "OAM" tapi service, to allow the user to put a resource in maintenance
The text was updated successfully, but these errors were encountered: