...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation, |
| Participating Company | AT&T, China Mobile, Amdocs, Ericsson. |
...
Release first proposed | TSC Use Case | VNFs identified in /impacted 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.
...
| Casablanca |
PNF onboarding & Packaging PNF Registration, VES Event domain | |
| Casablanca | CCVPN(Cross Domain and Cross Layer VPN) USE CASE |
|
| Casablanca | Centralized Representation and Consistent Identification of Cloud Regions In ONAP | |
| Casablanca | Change Management Extensions |
|
| Casablanca | Edge Automation through ONAP | Access Management will leverage the PNF management |
| Casablanca | OpenSource Access Manager | Access Management will leverage the PNF management |
| Casablanca | Scaling Use Case Extension | In Beijing the operator had to manually select the controller type (SDNC or APPC) within VID. The controller type should be part of the VNF model and not a run time option. |
| Casablanca | HPA Casablanca Plans (ONAP) |
|
The VNF Requirements developed by this project are applicable to the VNFs identified in the TSC E2E use cases.
- a VNF Provider (developer) using VNF Requirements in designing, testing, and certifying a VNF for use on ONAP
- a Service Provider using VNF Requirements as prototype text for RFPs to acquire VNFs to run in an ONAP context see VNFRQTS-16
- VNF Validation Project uses VNF Test Descriptions developed by this project to implement VNF testing for validation purposes.
- VNF SDK Project also uses VNF TEst Descriptions developed by this project to implement VNF testing for validation purposesuses VNF TEst Descriptions developed by this project to implement VNF testing for validation purposes
The VNF Requirements also cover nonfunctional requirements. ONAP non-functional requirements proposed for the Casablanca release that impact the VNF requirements include:
- Security
- Description of how the xNFs receive their certificates
Minimum Viable Product
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
...
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 DscriptionDescription |
| VNF EPICs: | vnfrqts/epics | not used in Casablanca Release |
...
List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
Other ONAP projects that this VNF Requirements project depends on:
- SDN-C (for API requirements on VNFs)
- APPC (for VNF configuration requirements)
- VF-C (for VNF life cycle managment and configuration)
- Service Design & Creation (for VNF onboarding)
- DCAE (for VNF reporting requirements)
- Authentication and authorization Framework (for VNF Security Requirements)
- Modeling (for Tosca Data Modeling for VNF)
- Multi-VIM/ MultiCloud (for network cloud infrastructure requirements)
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| APPC | VNF configuration requirements | M2 | M3 | APPC Documentation |
| Authentication and authorization Framework | VNF Security Requirements | M2 | M3 | |
| DCAE | VNF reporting requirements | M2 | M3 | DCAE APIs documentation |
| Modeling | Tosca Data Modeling for VNF | N/A | ONAP Modelling Specifications | |
| Multi-VIM/ MultiCloud | network cloud infrastructure requirements | N/A | MultiCloud Documentation | |
| SDN-C | API requirements on VNFs | M2 | M3 | SDNC APIs documentation |
| Service Design & Creation | VNF onboarding | M2 | M3 | SDC documentation |
| VF-C | VNF life cycle management and configuration | M2 | M3 | VF-C APIs documentation |
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| Documentation | References to deliverables produced by this project may be included in various ONAP release documents maintained through the documentation project | N/A see the VNFRQTS <> Documentation Project Workflows wiki page | Continuous Delivery ( build via Docs Jenkins Job) | docs.onap.org |
Reference VNFs (now Integration Project) | Reference VNFs should be VNF Requirement compliant. The Integration Project maintaining those Reference VNFS would be dependent on the VNF Requirements for validating compliance. | N/A see the VNFRQTS <> Integration Project Workflow wiki page | Beijing release version published, Casablanca version in process | consolidated list of VNF Requirements published in Appendix 8d of docs.onap.org |
| VNF SDK | VNF tooling should support the development and packaging of VNFs that are conformant to the VNF Requirements | NA see the VNFRQTS<> VNFSDK project Workflow wiki page | Beijing release version published, Casablanca version in process | VNF Test Description lists testable requirements. Appendix captures which are tested by VNFSDK |
| VNF Validation program (ICE) | VNF Validation should be traceable against the VNF Requirements | N/A see the VNFRQTS <> VNF Validation project Workflow wiki page. | Beijing release version published, Casablanca version in process | VNF Test Description lists testable requirements. Appendix captures which are tested by VVP |
...
The VNF Requirements is documentation built using the LF toolchain from .rst files into html. This tooclhain is administered by the documentation project. The toolchain provides for syntax checks of the documentation within Sphinx, doc8 etc.
...
| Risk identified | Mitigation Plan | Contingency Plan |
|---|---|---|
| ONAP supporting multiple onboarding formats | work with VNF SDK, VVP and SDC to minimize the risk. | Document the desired direction in the forward looking VNF Guidelines |
| Inconsistency between published VNF Requirements and ONAP Platform |
| document discrepancy in release notes |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
| Milestone | Deliverable | Date |
|---|---|---|
| M0 | Intent to Participate | June 14, 2018 |
| M1 | Release Plan M1 Checklist | June 28, 2018 |
| M2 | M2 Checklist | July 26, 2018 |
| M3 M3 | M3 Checklist | August 23, 2018 |
| M4 M4Checklist | M4 Checklist | September 20, 2018 |
| RC0 RC0 | RC0 Checklist | October 11, 2018 |
| RC1 | RC1ChecklistRC1Checklist | October 25, 2018 |
| RC2 RC2 | RC2 Checklist | November 8, 2018 |
| Signoff Signoff | Signoff Checklist | November 15, 2018 |
...
Documentation, Training
- The VNF Requirements is documentation built using the LF toolchain from .rst files into html. This tooclhain is administered by the documentation project. The toolchain provides for syntax checks of the documentation within Sphinx, doc8 etc.
- The VNFRQTS Project publishes a VNF Provider User Guide:
- VNF Guidelines
- Component lead - Wenyao Guan (China Mobile)
- VNF Requirements
- Component Lead - Hagop Bozawglanian (AT&T)
- VNF Provider Use Cases
- Component Lead - Scott Blandford (AT&T)
- VNF Test Descriptions
- Component Lead - Steven Wright (AT&T)
- Release Notes
- VNF Guidelines
Other Information
...