| Status | Choose One: DRAFT | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Submitter | Steven Wright | ||||||||
| Contributors | Names of additional contributorsOrange | ||||||||
| Proposed Release | Casablanca | ||||||||
| JIRA Ticket(s) |
|
...
The objective is to extract / summarize VNF Requirements into a VNF Badge. The VNF Requirements were original developed as prototype RFP text. Not all of the Requirements are testable ( either currently or in the near future).ONAP VNF Requirements evolve with ONAP releases. ( See e.g. Casablanca release notes ). The test implementations are also expected to evolve with ONAP releases. The VVP project is implementing HEAT related test scripts. The VNFSDK project is implementing TOSCA based test scripts. Test scripts may be invoked in a variety of different use cases. The proportion of testable requirements having tests implemented is expected to increase with each ONAP release. The scope of testing is expected to evolve from onboarding (Package inspection), to Life Cycle operations and Functional testing. In Casablanca test descriptions are available for VNF Package inspection tests. Test Case Descriptions for Life Cycle operations may be candidate work items for future releases.
...
ONAP supports several different VNF Package formats for onboarding : HEAT based, TOSCA Based (VFC:Generic VNFM, VFC:SVNFM) and (Proposed for Dublin: Helm based ( see Req #1)). In Casablanca the number of Requirements & tests for these formats is:
...