-
Epic
-
Resolution: Done
-
Medium
-
None
-
None
-
xNF License Management, Guilin R7
-
Requirement (DEPRECATED)
-
0
-
GO
-
Original Scope
-
S
-
Green
-
GO
-
Green
-
GO
-
Green
-
GO
-
Green
-
GO
Description of Use Case / Requirement:
Continue use case analysis for xNF License Management and derive any requirements to ONAP. The aim is for ONAP to support various types (simple, complex, vendor specific) commercial licensing models and use cases. These will be reflected as multiple, optional solutions for ONAP. The use cases we started with include xNF onboarding, PNF introduction/ONAP PnP, VNF instantiation. Further use cases to be analyzed, eg. usage monitoring for the purpose of invoicing. Based on agreed use cases review relevant ONAP xNF requirements. Possible SW contributions, eg. in SDC, as well as enhancement of ONAP architecture sequence diagrams.
Owners (one of these should be the Assignee - use @ notation):
Link to HLD/LLD (if any):
ArchCom documentation on xNF License Management: https://wiki.onap.org/display/DW/xNF+License+Management+support+-+Guilin-R7
Guilin rel. wiki page on License Management: https://wiki.onap.org/display/DW/Guilin+release+-+functional+requirements+proposed+list#Guilinreleasefunctionalrequirementsproposedlist-xNFLicenseManagement
Dependency Relationships with Other Projects:
Project Impact (Test Only (TO), Code (C)):
Code
Support Status for each Affected Project (Supported (S); Partially Supported (P); Not Supported (N)):
Note: for any affected projects labeled 'P' or 'N', please document the resulting gaps.
VNFRQTS, SDC, Documentation
Integration Leads (use @ notation):
Company Engagement:
Ericsson, Nokia
- is blocked by
-
ONAPARC-577 Guilin-R7 (AR-0032-R7-052020) License Management Architecture Review
- Closed
- relates to
-
SDC-3471 Creation of Vendor Licensing Model is an optional step in VSP onboarding
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...