To move one or more sites to an existing service, users can execute the below API:

POST /restconf/operations/nsp-service-stitch:move-sites

{

"input":{

"target-service-identifier":"/nsp-service:services/service-layer/eline[service-id=${futureSvcID}]",

"site-identifiers": [

"/nsp-service:services/service-layer/eline[service-id=${currentSvcID}]/site[site-id=${siteID}][name=${siteName}]"

]

}

}

Where

futureSvcID is the ID of a preexisting service to which the site(s) will move

currentSvcID is the ID of the service to which the site(s) are currently bound

siteID is the ID of the site to be moved

siteName is the name of the site to be moved

This method can be used after you’ve changed the name of a previously-deployed service to reestablish connection to its former sites. As compared to deleting and recreating the service, using the above API will minimize down time.

Note: This API is only supported for services with sites that are exclusively MDM-managed. The service’s lifecycle also cannot be managed by service management.

To move one or more sites to a new service, users can execute the below API:

POST /restconf/operations/nsp-service-stitch:move-sites

{

"input":{

"target-service-name":"{newSvcID}",

"site-identifiers": [

"/nsp-service:services/service-layer/eline[service-id=${currentSvcID}]/site[site-id=${siteID}][name=${siteName}]"

]

}

}

Where

newSvcID is the ID of a new service to which the site(s) will move

currentSvcID is the ID of the service to which the site(s) are currently bound

siteID is the ID of the site to be moved

siteName is the name of the site to be moved

This method can be used to generate a new service to which the specified site(s) will move. The type of service that is generated will be based on the type of service to which the site(s) were previously bound.

Note: This API is only supported for services with sites that are exclusively MDM-managed. The service’s lifecycle also cannot be managed by service management.