Versions Compared

Key

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

...

The use case is being divided into sub use cases in order to limit the scope of changes for E F release.

...

Import Service Catalog

Submit Order

...

9 – ONAP Ext API invokes the Third Party Ordering API


Sub Use Case 1 (targeted for F Release)

Import Service Catalog

Below sequence diagrams are depicting the Catalog Sync functionality in more detail:

...

High level flow of the activities for importing an external Service Catalog into ONAP with Payload Detail

...

Automated VNF Life Cycle Management – to cater for change management, incident management and version/configuration management

Service Assurance enablement for Third Party Domains’ exposed services

Control Automation:

Following items for VNF LCM and Service Assurance for Third Party Domain are being considered for the next phase of the use case for F release

  • The service life cycle management action can trigger for:
    • CM: change management (capacity increase to meet scaling demands);
    • IM: incident management (problem identification and fix); and
    • VM: version/config. management (VNFs’ adaptation to topology/config changes during run time of the service)
  • Remediation actions are executed automatically using ONAP as ODM

Project Impact:

Projects impacted as part of sub use case 1

  • SDC
    • In order to import the Service Catalog, Service load will have to be sent to SDC from Ext API.
    • JSON representation of the Service load needs to be identified and agreed with SDC team
    Ext API
    • TMF 633 POST needs to be implemented in
  • Ext APIInvoking the Third party Ordering API

...

  • (

...

  • yet to

...

  • be analyzed and scoped)


Work Commitment:

Telstra team will work on SDC and Ext API changesWe welcome partner contributions into this usecase.

...