The following 3 APIs will be introduced in Dublin to support the OOF CMSO Architecture:

• Topology Service API - Definition of the  interface to be implemented by individual carriers to support providing topology data necessary for CMSO to present conflict free scheduling of maintenance on a target network element. The ONAP implmentation of this interface will provide network topology information that is available in A&AI, however, the API will be designed to enable carriers to implement network topology data that is necessary to meet their scheduling needs.
  • Network elements required to be available in order to complete the maintenance on the target element. (REST) - Commonly referred to as vertical conflict avoidance.
  • Network elements required to be available to avoid network outages during the maintenance on the target element. - Commonly referred to as horizontal conflict avoidance.
  • Topology Service API Swagger

• Change Management (CM) Ticket Management API - Definition of the interface to be implemented by individual carriers to provide scheduled outages of network elements/assets returned by the Topolgy API to determine availabliilty. (REST)
  • CM Ticket Management API Swagger

• Change Management (CM) Schedule Optimizer API  - Definition of the interface to the schedule optimization manager. (REST)
  
  • Change Management (CM) Schedule Optimizer API Swagger

The existing CMSO Create Schedule API will be deprecated in favor of the CMSO Create Optimized Schedule API. This new API will enable providing customized information to the schedule optimizer three new APIs. 

• CMSO Create Optimized Schedule API Swagger

The interface to the Change Management (CM) Schedule Optimizer Engine is not a REST API but rather a internal definition of the input/output to the MiniZinc based schedule optimizer engine.targeted for Dublin.

• CMSO Optimizer Engine Interface (non-Swagger)

Image Added

CMSO API Swagger Pages