**Introduction**
====================
-- These requirements are specific to the Amsterdam release of ONAP.
+- These requirements are specific to the current release of ONAP.
It is the initial release of requirements based on a merge of the Open-O
and OpenECOMP requirements.
- Requirements are identified as either MUST, MUST NOT, SHOULD, SHOULD NOT,
- The VNF Provider
- The VNF Heat Orchestration Template
- The VNF Package
-- Chapter 4 contains the VNF/PNF requirements involving the design and
- development of VNFs/PNFs. These requirements help VNFs/PNFs operate
+- Chapter 4 contains the xNF requirements involving the design and
+ development of xNFs. These requirements help VNFs/PNFs operate
efficiently within a cloud environment. Requirements cover design,
resiliency, security, modularity and DevOps.
-- Chapter 5 describes the different data models the VNF/PNF provider
+- Chapter 5 describes the different data models the xNF provider
needs to understand. There are currently 2 models described in this
document:
element within the TOSCA onboarding package.
- Chapter 6 details the requirements specific to an implementation.
The current implementations documented are OpenStack and Azure.
-- Chapter 7 provides the comprehensive set of requirements for VNFs/PNFs to
+- Chapter 7 provides the comprehensive set of requirements for xNFs to
be on-boarded, configured and managed by ONAP.
- Chapter 8 is the appendix that provide a number of detailed data record
- formats.
+ formats. It also contains a list of the requirements that are listed
+ in the other chapters as well as examples and models that are referenced
+ throughout the rest of the chapters.