NSO Actions - need restconf URL for cleanup, syncfrom and syncto actions: Hi,Working on NSO actions using restconf.Actions:clean-upsync-fromsync-tothe restconf URL will be,https://<hostip:port>/crosswork/proxy/nso/restconf/data/<model-path>For Transport Slicing, what path should be supplied?Sample model-path for L2VPN:clean-up:/ietf-l2vpn-ntw:l2nm-actions/cleanupsync-from ; sync-to:/ietf-l2vpn-ntw:l2nm-actions/error-recovery
Hi Magesh,You can use the following for transport slicing:Cleanup:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/cleanup</pre></div></div>Inputs:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>   | +---x cisco-nss:cleanup               | | +---w cisco-nss:input     | | | +---w cisco-nss:service     -> /network-slice-services/cisco-nss:slice-service-plan/service-id   | | | +---w cisco-nss:sdp*       -> /network-slice-services/cisco-nss:slice-service-plan/plan/component/name   | | | +---w cisco-nss:no-networking  boolean</pre></div></div>Error Recovery:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/error-recovery</pre></div></div>Inputs:<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"><pre>   | +---x cisco-nss:error-recovery            |   +---w cisco-nss:input     |   | +---w cisco-nss:service      -> /network-slice-services/cisco-nss:slice-service-plan/service-id   |   | +---w cisco-nss:sync-direction  enumeration</pre></div></div>Let me know if you need anymore help.Thanks, RegiThanks Reginald. Let me check and confirmHi,In clean-up, we have one parameter,<div class='table-wrap'><table class='confluenceTable'><tbody><tr><td class='confluenceTd'>&nbsp;</td><td class='confluenceTd'>&nbsp;</td><td class='confluenceTd'> +---w cisco-nss:sdp*       -> /network-slice-services/cisco-nss:slice-service-plan/plan/component/name</td></tr></tbody></table></div>Do we need to pass the "sdp-id" of the particular service?Hi,If we have to pass the SDP IDs then do we need to pass all the SDP ids for the service?Hi,I tried the below URL,payload and got the response.URL:https://<ip>/crosswork/proxy/nso/restconf/data/ietf-network-slice-service:network-slice-services/cisco-network-slice-service:actions/cleanuppayload:{  "no-networking": false,  "service": "Dedic-520",  "sdp" : }"0","1","2" are the SDP-IDs for the service "Dedic-520".Response:{  "cisco-network-slice-service:output": {    "success": false,    "detail": "Cleaning up IETF NSS service: Dedic-520 nn Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{0}n Removed service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{0}n Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{1}n Removed service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{1}n Removing service /network-slice-services/slice-service{Dedic-520}/sdps/sdp{2}nERROR: too few elems (15): too few /ietf-nss:network-slice-services/slice-service{Dedic-520}/sdps/sdp, 0 configured, at least 1 must be configurednSTATUS_CODE: TSDN-IETF-NSS-503nREASON: Cleanup failednCATEGORY: custom-actionnSEVERITY: ERRORnContext n"  }}So, i got some response. Even though, its not success, can i assume that the payload is correct and NSO does some action on it?You're not required to input sdp-id. The sdp-id is only need if you want to cleanup a specific component, but if you're trying to cleanup the entire service then you do not need to define the sdp-idThanks,RegiThanks Regi