Beijing Release Planning Template
DRAFT PROPOSAL FOR COMMENTS
The content of this template is expected to be fill out for M1 Release Planning Milestone.
- 1 Overview
- 2 Scope
- 3 Release Deliverables
- 4 Sub-Components
- 5 Architecture
- 6 Testing and Integration Plans
- 7 Gaps
- 8 Known Defects and Issues
- 9 Risks
- 10 Resources
- 11 Release Milestone
- 12 Team Internal Milestone
- 13 Documentation, Training
- 14 Other Information
Overview
Project Name | VNFRQTS |
|---|---|
Target Release Name | Beijing |
Project Lifecycle State | Incubation . Refer to ONAP Charter, section 3.3 Project Lifecycle for further information |
Participating Company | AT&T, China Mobile, Orange, Bell Canada, Amdocs, VMWare, Huawei, ZTE, Intel |
Scope
What is this release trying to address?
Use Cases
Describe the use case this release is targeted for (better if reference to customer use case).
The TSC identified the following Use cases for Release A:
Release first proposed | TSC Use Case | VNFs identified in TSC Use case |
|---|---|---|
Amsterdam | vBNG, vG_MUX, vG, vAAA, vDHCP, vDNS | |
Amsterdam | vFW, vPacketGenerator, vDataSink, vDNS, vLoadBalancer, all VPP based. | |
Amsterdam | vSBC, vPCSCF, vSPGW, vPCRF, VI/SCSCF, vTAS, VHSS, vMME | |
Beijing | ||
Beijing | vCPE, vAAA, vDHCP | |
Beijing | ||
Beijing | vBG | |
Beijing | VOLTE, vDNS | |
Beijing |
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.
Minimum Viable Product
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, traceable from the VNF Requirments
VNF Use Case - VNF Provider Guidelines for VNF Scale Out Use Case
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.
Epics
Stories
Longer term roadmap
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 testing ( VNF Requirments 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 Casablancadeliverable 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) |
Sub-Components
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 Beijing Release |
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
Architecture
High level architecture diagram
The VNF Requirements Project is not delivering ONAP platform code, rather it delivers documentation targeted to VNF providers to enable thme to develop VNFS which can be more easily onboarded and operated by an Operator using an ONAP platform.
Platform Maturity
Refering to CII Badging Security Program and Platform Maturity Requirements, fill out the table below by indicating the actual level , the targeted level for the current release and the evidences on how you plan to achieve the targeted level.
Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
Performance | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Stability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Resiliency | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Security | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Scalability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Manageability | NA | VNFRQTS is primarily a documentation project and does not deliver ONAP platform code |
| |
Usability | 1 | VNF Guidelines VNF Requirements VNF Use Cases (new) VNF Test Case Descriptions (new) | http://docs.onap.org/en/latest/guides/onap-user/vnfprovider.html additional types of documentation to move towards level 2 with: Use cases (tutorial/ usability) Test Case Descriptions (testing) |
|
API Incoming Dependencies
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)
The VNF Requirments does not produce code interfaciong with platform APIs. The VNF Requirments do consoliate requirements from ONAP platform compontents that impact the design and development of VNFs. These ONAP platform components in the table below generate APIs that impact VNFs and so these are generally reflected in the VNF Requirements.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
VNF configuration requirements | M2 | M3 | ||
VNF Security Requirements | M2 | M3 | ||
VNF reporting requirements | M2 | M3 | ||
Tosca Data Modeling for VNF | N/A | |||
network cloud infrastructure requirements | N/A | |||
API requirements on VNFs | M2 | M3 | ||
VNF onboarding | M2 | M3 | ||
VNF life cycle management and configuration | M2 | M3 |
API Outgoing Dependencies
The VNF Requirements do not provide code with APIs, but the VNF Requirements are used as inputs by a number of other ONAP projects.
API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
VNF tooling should support the development and packaging of VNFs that are conformant to the VNF Requirements | N/A | |||
VNF Validation should be traceable against the VNF Requirements | N/A see the VNFRQTS <> VNF Validation project Workflowwiki page | |||
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 | |||
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 |
Third Party Products Dependencies
The VNF Requirements is documentation rather than code so there is no dependency on 3rd party products other than the documentation and development tool chains provided through the Linux Foundation.
Testing and Integration Plans
Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.
Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.
Gaps
This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.
Gaps identified | Impact |
|---|---|
VNF Requirements linkage to testing | VNF Requirements are current provided for RFP purposes, but the linkage to testing and validation of those requirments is not yet in place This release provides initial generic test plan descriptions for testing of VNFs based on the VNF Package. It does not provide test descriptions for design time or run time functional testing of VNFs. The testing linkage is also costrained by the scope of the VNF Information model in the VNF Package and the relationships identified between that information model and the VNF requirements. |
Hardware / infrastructure requirements | The Amsterdam release requirments had a placeholder (Chapter 6) for VNF requirements associated with the hardwrae executuion environment. Additional requirments are expected in this area from the Multi-VIM project, and perhaps the PNF related features. |
HEAT/TOSCA requirements | The Amsterdam release requirments has text on HEAT and TOSCA requirmenst but not numbered requirments text. This is expected to be improved as part of the Beijing release work. |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
Risks
List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).
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 |
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.
Date | Project | Deliverable |
|---|---|---|
1/8/18 | VNF Requirments | Draft M1 Project Plan available on VNFRQTS Project Wiki |
1/18/18 | VNF Requirments | ONAP Beijing M1 Milestone - planning process complete |
2/12/18 | VNF Requirments | ONAP Beijing M2 Milestone - functionality freeze |