LICENSING MANAGEMENT
Description
Start from 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. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.
BUSINESS DRIVER
Executive Summary -
Start from 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. The use cases to start with include xNF onborading, PNF introduction/ONAP PnP, VNF instantation. Based on agreed use cases review relevant ONAP xNF requirements. No impacts to ONAP components foreseen in R6 Frankfurt, potentially minor update of ONAP architecture.
Business Impact - xNF License Management is a critical business function. Agreed use cases should allow ONAP to flexibly support commercial licensing models.
Business Markets - This use case applies to any domain (wireless, transport, optical, wireline) that ONAP will manage. It is not a market specific function.
Funding/Financial Impacts - The use case is fundamental for supporting efficiently business agreements between the operator and the vendor.
Organization Mgmt, Sales Strategies - There is no additional organizational management or sales strategies for this use case outside of a service providers "normal" ONAP deployment and its attendant organizational resources from a service provider.
SUPPORTING FILES:
Use Case Contacts & Team
@Timo Perala
@Samuli Kuusela
DEVELOPMENT IMPACTS
There is no expected Software Impact to any of the ONAP platform components for this Use Case, aside from possibly modeling and architecture work.
PROJECT | PTL | User Story / Epic | Requirement |
A&AI | @James Forsyth |
|
|
AAF | @Jonathan Gathman |
|
|
APPC | @Takamune Cho |
|
|
CLAMP | @Gervais-Martial Ngueko |
|
|
CC-SDK | @Dan Timoney |
|
|
DCAE | @Vijay Kumar |
|
|
DMaaP | @Mandar Sawant |
|
|
External API | @Matthieu Geerebaert |
|
|
MODELING | @Hui Deng | Epic #1: Introduction of basic Licensing Modeling
| Modeling for Licensing Management (@Kevin Scaggs ) |
Multi-VIM / Cloud | @Bin Yang |
|
|
OOF | @Shankaranarayanan Puzhavakath Narayanan |
|
|
POLICY | @Pamela Dragosh |
|
|
PORTAL | @Manoop Talasila |
|
|
SDN-C | @Dan Timoney |
|
|
SDC | @Ofir Sonsino |
|
|
SO | @Seshu Kumar Mudiganti |
|
|
VID | @ittay |
|
|
VNFRQTS | @Steven wright |
|
|
VNF-SDK | @victor gao |
|
|
CDS | @Yuriy Malakov |
|
|
List of PTLs:Approved Projects
*Each Requirement should be tracked by its own User Story in JIRA
Test Cases and Status
# | Test Case | Status |
|---|---|---|
1 | There should be a test case for each item in the sequence diagram | Not yet tested |
2 | create additional requirements as needed for each discreet step | Complete |
3 | Test cases should cover entire Use Case | Partially Complete |
4 | Test Cases should include enough detail for testing team to implement the test | Failed |