Use Case Name
| xNF License Management |
Business Driver
This section describes Business Drivers needs.
...
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.
Development Status
| PROJECT | PTL | User Story / Epic | Requirement | ||||||||
| A&AI | NONE | ||||||||||
| AAF | NONE | ||||||||||
| APPC | NONE | ||||||||||
| CLAMP | NONE | ||||||||||
| CC-SDK | NONE | ||||||||||
| DCAE | NONE | ||||||||||
| DMaaP | NONE | ||||||||||
| External API | NONE | ||||||||||
| MODELING | NONE | ||||||||||
Multi-VIM / Cloud | NONE | ||||||||||
| OOF | NONE | ||||||||||
| POLICY | NONE | ||||||||||
| PORTAL | NONE | ||||||||||
| SDN-C | NONE | ||||||||||
| SDC |
| Requirement discussed with SDC PTL during June weekly meeting, it is a stretch goal for Rel 7 target. | |||||||||
| SO | NONE | ||||||||||
| VID | NONE | ||||||||||
| VNFRQTS |
| Discussion ongoing in VNFRQTS meeting | |||||||||
| VNF-SDK | NONE | ||||||||||
| CDS | NONE | ||||||||||
| Documentation | https://jira.onap.org/projects/DOC/issues/DOC-640 |
List of PTLs:Approved Projects
Use Case Diagram
Use cases define how different users interact with a system under design. Each use case represents an action that may be performed by a user (defined in UML as an Actor with a user persona).
...
On this xNF Licensing Management solution use cases (xNF onboarding, PNF introduction/ONAP PnP and VNF instantiation), there are no related ONAP user interactions.
Use Case Functional Definitions
Use Case Title | xNF Licensing Management | ||||||||||||||||||||||||||||||||
Actors (and System Components) | No actors participate in this use case. Participating System Components: xNF and License Service (external to ONAP) | ||||||||||||||||||||||||||||||||
Description | This xNF Licensing Management use case aims to support various types (simple, complex, vendor specific) commercial licensing models. In this particular solution, this achieved by support of ONAP-external License Service. | ||||||||||||||||||||||||||||||||
Points of Contact | |||||||||||||||||||||||||||||||||
Preconditions | The PNF or VNF/CNF needs to be bootstrapped or instantiated; the ONAP-external License Service needs to be operational and reachable by the xNF. | ||||||||||||||||||||||||||||||||
Triggers / Begins when | The use case can begin at any time after PNF or VNF/CNF bootstrapping or instantiation has happened. | ||||||||||||||||||||||||||||||||
Steps / Flows (success) | See the sequence diagrams, slides 4,5,6 in the ArchCom presentation: https://jira.onap.org/secure/attachment/15986/ONAP%20license%20mgmt%20-%20ArchCom%20Guilin.pptx | ||||||||||||||||||||||||||||||||
Post-conditions | The xNF has successfully obtained licenses from the external License Service. | ||||||||||||||||||||||||||||||||
Alternate / Exception Paths | - | ||||||||||||||||||||||||||||||||
Related Use Cases | The PNF Plug and Play use case is a related use case because the licensing service exchange (optional) can happen then. For more information see the PNF Plug and Play Wiki: 5G - PNF Plug and Play#5GPNFPlugandPlay-PNFPLUGANDPLAYwithLICENSINGMANAGEMENT | ||||||||||||||||||||||||||||||||
Assumptions | Existence of ONAP-external License Service which is reachable for the xNF. | ||||||||||||||||||||||||||||||||
Tools / References / Artifacts | Jira tickets: R7 requirement:
ArchCom:
SDC:
VNFRQTS:
Documentation: https://jira.onap.org/projects/DOC/issues/DOC-640 |
Testing
Current Status
End to End flow to be Tested
Test Cases and 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 |
Reference
- ONAP Wiki page Template: Template page Licensing Management in R7