...
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 |
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=vnfrqts and issuetype in (epic) AND fixVersion = "Beijing Release" serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
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 Requirments 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. |
Known Defects and Issues
Provide a link toward the list of all known project bugs.
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
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).
...
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.
Jira | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
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 |
3/8/18 | VNF Requirments | ONAP Beijing M3 Milestone - API data model freeze |
3/29/18 | VNF Requirments | ONAP Beijing M4 Milestone - code freeze |
4/19/18 | VNF Requirments | ONAP Beijing RC0 Milestone |
5/3/18 | VNF Requirments | ONAP Beijing RC1 Milestone |
5/17/18 | VNF Requirments | ONAP Beijing RC2 Milestone |
5/24/18 | VNF Requirments | ONAP Beijing Signoff Milestone |
Resources
Fill out the Resources Committed to the Release centralized page.
Release Milestone
...
Team Internal Milestone
This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.
It is not expected to have a detailed project plan.
Date | ProjectDeliverable | Deliverable | |
---|---|---|---|
1/16/18 | Sprint 7 start | Draft M1 Project Plan available on VNFRQTS Project Wiki M1 checklisy available before ONAP Beijing M1 Milestone - planning process complete 1/18 | |
1/ | 830/18 | VNF Requirments | Draft M1 Project Plan available on VNFRQTS Project Wiki |
1/18/18 | VNF Requirments | ONAP Beijing M1 Milestone | |
2/12/18 | VNF Requirments | ONAP Beijing M2 Milestone | |
3/8/18 | VNF Requirments | ONAP Beijing M3 Milestone | |
3/29/18 | VNF Requirments | ONAP Beijing M4 Milestone | |
4/19/18 | VNF Requirments | ONAP Beijing RC0 Milestone | |
5/3/18 | VNF Requirments | ONAP Beijing RC1 Milestone | |
5/17/18 | VNF Requirments | ONAP Beijing RC2 Milestone | |
5/24/18 | VNF Requirments | ONAP Beijing Signoff Milestone |
Documentation, Training
Sprint 7 complete Sprint 8 start | Draft structure of Use case and test case Descriptions available before ONAP Beijing M2 Milestone - functionality freeze 2/12 | |
2/13/18 | Sprint 8 complete Sprint 9 start | |
2/27/18 | Sprint 9 complete Sprint 10 start | before ONAP Beijing M3 Milestone - API data model freeze 3/8 |
3/13/18 | Sprint 10 complete Sprint 11 start | |
3/27/18 | Sprint 11 complete Sprint 12 start | before ONAP Beijing M4 Milestone - code freeze 3/29 |
4/10/18 | Sprint 12 complete Sprint 13 start | Finalize complete drafts before ONAP Beijing RC0 Milestone 4/19 |
4/24/18 | Sprint 13 complete Sprint 14 start | Bug fixes only prior to RC1 5/3 |
5/8/18 | Sprint 14 complete Sprint 15 start | Bug fixes only prior to RC2 5/17 |
5/22/18 | Sprint 15 complete | Bug fixes only prior to signoff 5/24 |
Documentation, Training
- VNF Guidelines
- component lead - Wenyao Guan (China Mobile)
- Forward looking guidance
- VNF Requirements
- component lead - Herb Patten (AT&T)
- VNF Conformance requirements
- VNF Use Cases
- component lead - Scott Blandford
- tutorial
- VNF Test Case Descriptions
- component lead - Steven Wright
- Description of how to test the VNF Requirements
- Highlight the team contributions to the specific document related to he project (Config guide, installation guide...).
- Highlight the team contributions to the overall Release Documentation and training asset
- High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
- Documentation includes items such as:
- Installation instructions
- Configuration instructions
- Developer guide
- End User guide
- Admin guide
- ...
Note | ||
---|---|---|
| ||
The Documentation project will provide the Documentation Tool Chain to edit, configure, store and publish all Documentation asset. |
...
Each project must edit its project table available at Project FOSS. This vnfrqts project is a documentation project using the LF toolchain coordinated via the documentation project.
Charter Compliance
The project team comply with the ONAP Charter.