Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »


View the CMSO Create Optimized Schedule documentation in the interactive swagger UI 


Create Optimized Schedule Request Example


This example represents CMSO Create Optimized Schedule for Dublin release. Significant changes are:


Replacement of domainData with commonData name / value structure. This structure is used to provide carrier specific to all of the underlying interfaces, some of which are carrier specific (i.e. Topology and Ticket Management).

Inclusion of elementData name / value structure for every element to be changed.  This structure is used to provide carrier specific to all of the underlying interfaces, some of which are carrier specific (i.e. Topology and Ticket Management).

Move of callbackData from domainData structure to the request attribute for each element.   The request attribute represents the exact message to b provided to SO to initiate the change request.

policies  array that provides for providing policy information to the underlying APIs along with the potential for modifiers to the policy.

Response to Create Optimized Schedule Request is status indicating that the request was accepted for optimization.

  • No labels