Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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. 
    • Network elements required to be available to avoid network outages during the maintenance on the target element.
  • 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.
  • Change Management (CM) Schedule Optimizer Engine API  API  - Definition of the interface to the schedule optimization engine. Minizinc-based scheduler optimizer engine is targeted for Dublin.

...