...
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 requirementsof 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.
...
| 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
...
| Date | Project | Deliverable |
|---|---|---|
| 1/16/18 | Sprint 1 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/30/18 | Sprint 1 7 complete Sprint 2 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 2 8 complete Sprint 3 9 start | |
| 2/27/18 | Sprint 3 9 complete Sprint 4 10 start | before ONAP Beijing M3 Milestone - API data model freeze 3/8 |
| 3/13/18 | Sprint 4 10 complete Sprint 5 11 start | |
| 3/27/18 | Sprint 5 11 complete Sprint 6 12 start | before ONAP Beijing M4 Milestone - code freeze 3/29 |
| 4/10/18 | Sprint 6 12 complete Sprint 7 13 start | Finalize complete drafts before ONAP Beijing RC0 Milestone 4/19 |
| 4/24/18 | Sprint 7 13 complete Sprint 8 14 start | Bug fixes only prior to RC1 5/3 |
| 5/8/18 | Sprint 8 14 complete Sprint 9 15 start | Bug fixes only prior to RC2 5/17 |
| 5/22/18 | Sprint 9 15 complete | Bug fixes only prior to signoff 5/24 |
...