Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

To fill out
Gaps identifiedImpactTo fill out
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.

VNF Badging and certification programs are not yet in place, but enabling organizational arrangements e.g. LFN C&V committee are making these more viable.

Hardware / infrastructure requirementsThe Beijing release requirements had a placeholder (Chapter 6) for VNF requirements associated with the hardware execution environment. Additional requirements are expected in this area from the Multi-VIM project, and perhaps the PNF related features.
HEAT/TOSCA requirementsThe Beijing release requirements has text on HEAT and TOSCA requirements but not all were numbered requirements text. This is expected to be improved as part of the Casablanca release work.
  • Known Defects and Issues

Provide a link toward the list of all known project bugs.

Jira
serverONAP JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = sanbox and issuetype in (bug) VNFRQTS AND issuetype = Bug AND status = "To Do"
serverId425b2b0a-557c-3c0c-b515-579789cceedb

...