Details
-
Epic
-
Status: Done
-
Medium
-
Resolution: Done
-
None
-
None
-
Third Party Operational Domain Manager
-
0
Description
A solution that allows a service provider to have a network automation platform for composite or white labelled services managed by Partner / Third Party domain managers.
Details of the requirements and proposed solution are captured [here|https://wiki.onap.org/display/DW/Third-party+Operational+Domain+Manager]
It will provide ONAP capability to be operational domain manager for third party services. Service providers will be able to use ONAP to provide end to end automation for composite or white labelled services which could be provided and managed by third parties. In case of Tier 1 / Brownfield operators, it’s likely that ONAP might need to interface with existing automation solutions for specific domains.
It provides a generic capability in ONAP for seamlessly on-boarding services from partner (or specific ) domain catalog. Lack of this capability leads to manual creation of partner services in ONAP which is time consuming and error prone. With introduction of this capability, ONAP will be able to consume domain specific service definitions via Open APIs and publish the same to run time components.
Attachments
Issue Links
- clones
-
REQ-1 ONAP Requirement Template
-
- To Do
-
-
REQ-537 Long-term IPv4/IPv6 dual stack networking support
-
- Done
-
- relates to
-
ONAPARC-509 ONAP Thrid Party Operational Domain Manager
-
- Open
-
-
SDC-2378 ONAP as Third Party Domain Manager - Import Third Party Catalog in SDC
-
- Closed
-
-
SDC-2382 Introduce a new category for the 3rd party Service
-
- Closed
-
-
SDC-2383 Expose the API for service creation as an External API
-
- Closed
-
-
SDC-2385 Introduce property mapping rules to define parent-child mapping for properties added in service definition
-
- Closed
-
-
REQ-13 Service Resolving feature
-
- Done
-