...
The TSC identified the following Use cases for Release A:
Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
---|---|---|
Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
Amsterdam | Use Case: Residential Broadband vCPE (Approved) | vBNG, vG_MUX, vG, vAAA, vDHCP, vDNS |
Amsterdam | Use Case: vFW/vDNS (Approved) | vFW, vPacketGenerator, vDataSink, vDNS, vLoadBalancer, all VPP based. |
Amsterdam | Use Case: VoLTE(approved) | vSBC, vPCSCF, vSPGW, vPCRF, VI/SCSCF, vTAS, VHSS, vMME |
Beijing | 5G- RAN deployment, Slicing, SON | |
Beijing | Enterprise vCPE --potential R1 use cases’ extension | vCPE, vAAA, vDHCP |
Beijing | ONAP Change Management | |
Beijing | SD-WAN | vBG |
Beijing | Scale Out | VOLTE, vDNS |
Beijing | Centralised Parser Distribution |
The VNF Requirements developed by this project are applicable to the VNFs identified in the TSC E2E use cases.
...
Describe the MVP for this release.
- A VNF Guidelines document summarizing VNF provider oriented deliverables and providing informative, forward lookiging guidance.
- A set of Integrated VNF Requirements for use as prototype RFP text.
- VNF Test Descriptions for use by VNF Validation project, and VNF SDK Project traceable from the VNF Requirments.
- Appendix identifying which VNF requirements are testable by inspection of the VNF Package, and where the tests are implemented.
- VNF Use Case - VNF Provider Guidelines for VNF Scale Out Use Case
- Manual Scale out
- Automated Scale Out
- VNF Badging Categories
- Groomed list of VNF Requirements for VNF Badging
- Groomed list of VNF Requirements for VNF Certification by testing
Functionalities
List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox and issuetype in (epic) VNFRQTS AND issuetype = Epic AND status = "To Do" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = sanbox and issuetype in (story) VNFRQTS AND issuetype = Story AND status = "To Do" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
Amsterdam- deliver overview VNF Guidelines & prototype RFP text requirements.
Beijing - Update Amsterdam deliverable for new ONAP features, Test Descriptions for VNF Package Testing, VNF Scaling Use case, tooling improvements
Casablanca - Extend tracability of VNF requirements into testing (VNF Requirements Database),additional VNF provider use cases, Update Bejing deliverable for new ONAP features
Dublin - Design time VNF testing description, additional VNF provider use cases, Update Casablanca deliverable for new ONAP features
El Alto - Run time VNF testing description, update Dublin deliverable for new ONAP features
Frankfurt - Update El Alto deliverable for new ONAP features
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
Deliverable Name | Deliverable Description | ||
---|---|---|---|
VNF Guidelines | Documentation. Provides a high level informative overview of guidance towards VNF providers. (provided since Amsterdam release) | ||
VNF Requirements | Documentation. Provides individually numbered requirements for VNFs (provided since Amsterdam release) | ||
VNF Use Cases | Documentation. Provides guidelines for VNF providers on use cases on interest to VNF providers (new deliverable in Beijing release) | ||
VNF Test Case | Documentation. Provides test case descriptions for how to test VNFs. (new deliverable in Beijing release) | ||
VNF EPICs | documentation ( future) | To fill out | To fill out |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.
Deliverable | repo | Files Structure of repo |
VNF Guidelines: | vnfrqts/guidelines | File per chapter |
VNF Requirements: | vnfrqts/requirements | File per chapter |
VNF Use Cases: | vnfrqts/usecases | File per Use Case |
VNF Test Descriptions: | vnfrqts/testcases | File Per Test Case Dscription |
VNF EPICs: | vnfrqts/epics | not used in Casablanca Release |
Architecture
High level architecture diagram
...