zed infra- structure (VI) manager. ONAP expands the scope of ETSI MANO coverage by including control- ler, data collection and analytics, portal, and policy components. Policy plays an important role to control and manage behavior of various VNFs and the management framework. ONAP also significantly increases the scope of ETSI MANO's resource description to include complete meta- data for lifecycle management of the virtual environment (infrastructure as well as VNFs). The ONAP design framework is used to create resource/service/product/offer definitions (consistent with MANO), as well as engineering rules, recipes for various actions, policies, and processes. The metadata-driven generic VNF manager (i.e., ONAP) allows quick onboarding of new VNF types; doing this without going through long development and integration cycles and efficiently manag- ing cross dependencies between various VNFs is key. Once a VNF is onboarded, the design time framework facilitates rapid incorporation into future services. ETSI MANO E2E Architecture View ONAP Architecture View Os-Ma OSS/BSS ONAP Execution OSS/BSS Orchestrator ONAP Design Framework Framework Se-Ma Service, VNF and Infrastructure Description Meta Data for Service, VNF and Or-Vnfm Infrastructure (Description, Constraints, Recipes, Policies, and processes) Orchestrator EMS 1 EMS 2 (MSO) EMS 3 Manager(s) Ve-Vnfm-vnf Ve-Vnfm VNF 1 VNF 2 VNF 1 VNF 3 VNF 2 VNF 3 Or-Vi Controllers Vn-Nf Vi-Vnfm Vh-Nf Virtual Virtual Virtual Virtual Virtual Virtual Computing Storage Network Computing Storage Network Infrastructure Nf-Vi Virtualized Nf-Vi Orchestrator Virtualization Layer Infrastructure Virtualization Layer VI-Ha Manager(s) VI-Ha Hardware resources Infrastructure Hardware resources Computing Storage Network Controller Hardware Computing Storage Network Hardware Hardware Hardware Hardware Hardware Execution reference points Other reference points Main NFV reference points Execution reference points Other reference points Main NFV reference points FIGURE 7.3 Comparison of ETSI MAN