...
Controller Design Studio (CDS)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Inventory ---------The Controller Design Studio (CDS) community in ONAP has contributed a
framework to automate the resolution of resources for instantiation and any
config provisioning operation, such as day0, day1 or day2 configuration. The
essential function of CDS is to create and populate a controller blueprint,
crate a configuration file from this Controller blueprint, and associate at
design time this configuration file (configlet) to a PNF/VNF/CNF during the
design phase. CDS removes dependence on code releases and the delays they cause
and puts the control of services into the hands of the service providers. Users
can change a model and its parameters with great flexibility to fetch data from
external systems (e.g., IPAM) that is required in real deployments. This makes
service providers more responsive to their customers and able to deliver
products that more closely match the needs of those customers.
Inventory ^^^^^^^^^ Active and Available Inventory (A&AI) provides real-time views of a system's resources, services, products and their relationships with each other, and also retains a historical view. The views provided by A&AI relate data managed by multiple ONAP instances, Business Support Systems (BSS), Operation Support Systems (OSS), and network applications to form a "top to bottomviewbottom"view ranging from the products end users buy, to the resources that form the raw material for creating the products. A&AI not only forms a registry of products, services, and resources, it also maintains up-to-date views of the relationships between these inventory items. To deliver the promised dynamism of SDN/NFV, A&AI is updated in real time by the controllers as they make changes in the network environment. A&AI is metadata-driven, allowing new inventory types to be added dynamically and quickly via SDC catalog definitions, eliminating the need for lengthy development cycles. Policy Framework ----------------^^^^^^^^^^^^^^^^ The Policy framework provides policy based decision making capability and supports multiple policy engines and can distribute policies through policy design capabilities in SDC, simplifying the design process. Multi Cloud Adaptation ---------------------- Multi-VIM/Cloud provides and infrastructure adaptation layer for VIMs/Clouds in exposing advanced hardware platform awareness and cloud agnostic intent capabilities, besides standard capabilities, which are used by OOF and other components for enhanced cloud selection and SO/VF-C for cloud agnostic workload deployment. Closed Control Loop Automation Management Platform Function in Policy (Policy - CLAMP) -------------------------------------------------------------------------------------- Closed loop control is provided by cooperation among a number of design-time and run-time elements. The Runtime loop starts with data collectors from Data Collection, Analytics and Events (DCAE). ONAP includes the following collectors: VES for events, HV-VES for high-volume events, SNMP for SNMP traps, File Collector to receive files, and Restconf Collector to collect the notifications. After data collection/verification phase, data are moved through the loop of micro-services like Homes for event detection, Policy for determining actions, and finally, controllers and orchestrators to implement actions PolicyCLAMP is used to monitor the loops themselves. DCAE also supports (Platform for Network Data Analytics) PNDA analytics capabilities. Policy-CLAMP and DCAE all have design time aspects to support the creation of the loops. We refer to this automation pattern as closed control loop automationin that it provides the necessary automation to proactively respond to network and service conditions without human intervention. A high-level schematic of the closed control loop automation and the various phases within the service lifecycle using the automation is depicted in Figure 3. Closed control loop control is provided by Data Collection, Analytics and Events (DCAE) and one or more of the other ONAP runtime components. Collectively, they provide FCAPS (Fault Configuration Accounting Performance Security) functionality. DCAE collects performance, usage, and configuration data; provides computation of analytics; aids in troubleshooting; and publishes events, data and analytics (e.g., to policy, orchestration, and the data lake). Another component, Holmes, connects to DCAE and provides alarm correlation for ONAP, new data collection capabilities with High Volume VES, and bulk performance management support. Working with the Policy Framework and CLAMP, these components detect problems in the network and identify the appropriate remediation. In some cases, the action will be automatic, and they will notify Service Orchestrator or one of the controllers to take action. In other cases, as configured by the operator, they will raise an alarm but require human intervention before executing the change. The policy framework is extended to support additional policy decision capabilities with the introduction of adaptive policy execution.
The CLAMP component is fully integrated within the Policy component since Istanbul-R9
release. CLAMP's functional role to provision Policy has been enhanced to support
provisioning of policies outside of the context of a Control Loop and therefore act
as a Policy UI.
|image3|**Figure 3: ONAP Closed Control Loop Automation** Shared Services =============== ONAP provides a set of operational services for all ONAP components including security, activity logging, reporting, common data layer, access control, secret and credential management, resiliency, and software lifecycle management. Operating in a virtualized environment introduces new security challenges and opportunities. ONAP provides increased security by embedding access controls in each ONAP platform component, augmented by analytics and policy components specifically designed for the detection and mitigation of security violations. ONAP Modeling ============= ONAP provides models to assist with service design, the development of ONAP service components, and with the improvement of standards interoperability. Models are an essential part for the design time and runtime framework development. The ONAP modeling project leverages the experience of member companies, standard organizations and other open source projects to produce models which are simple, extensible, and reusable. The goal is to fulfill the requirements of various use cases, guide the development and bring consistency among ONAP components and explore a common model to improve the interoperability of ONAP. ONAP supports the following Models: - A VNF Descriptor Information Model based on ETSI NFV IFA011 v.2.5.1 with appropriate modifications aligned with ONAP requirements - A PNF Descriptor Information Model based on ETSI NFV IFA014 v2.5.1 - A VNF Descriptor TOSCA based Data Model based on IM and ETSI NFV SOL001 v 2.5.1 has been implemented by SDC and supported by vCPE use case. - VNF Package format leveraging the ETSI NFV SOL004 specification and supported by VNF SDK project - A VNF instance model based on ETSI NFV IFA specification and A&AI implementation
- A new CNF modeling descriptor, Application Service Descriptor (ASD), has been
introduced to simplify CNF modeling and orchestration, and to reduce redundancies
between orchestration and Kubernetes-based resource descriptors - A Network Service Descriptor (NSD) has been realized by the VFC and SO-NFVO
(using the modeling project parsing capabilities) - These models enable ONAP to interoperate with implementations based on standards and improve industry collaboration. - Root model which presents the relationship between different models - Business and Interaction model based on TMF specifications - VES model based on VES 7.x specification The Model Utilities in the ONAP Shared Utilities provides ETSI catalog capabilities,
including ETSI NFV model and package (SOL001, SOL004, SOL007) parser and ETSI
package management functionalities.
Industry Alignment ================== ONAP support and collaboration with other standards and open-source communities is evident in the architecture. - MEF and TMF interfaces are used in the External APIs - In addition to the ETSI-NFV defined VNFD and NSD models mentioned above, ONAP supports the NFVO interfaces (SOL005 between the SO and VFC/SO-NFVO, SOL003 from either the SO (thru SOL003 Adapter) or VFC to an external VNFM).
- Application Service Descriptor (ASD) v1.0 specification for the CNF is approved, and
ASD specification is promoted as the O-RAN standard. Read this white paper for more information: The Progress of ONAP: Harmonizing Open Source and Standards. ONAP Blueprints =============== ONAP can support an unlimited number of use cases, within reason. However, to provide concrete examples of how to use ONAP to solve real-world problems, the community has created a set of blueprints. In addition to helping users rapidly adopt the ONAP platform through end-to-end solutions, these blueprints also help the community prioritize their work. With the ONAP Dublin release, we introduced a new blueprint in the area of residential connectivity: Broadband Service. Prior blueprints were vCPE, VoLTE, vFW/vDNS, 5G, and CCVPN. 5G and CCVPN underwent feature enhancements during the Dublin release. 5G Blueprint ------------ The 5G blueprint is a multi-release effort, with three key initiatives around PNF integration, network optimization, and network slicing. The combination of eMBB that promises peak data rates of 20 Mbps, uRLLC that guarantees sub-millisecond response times and MMTC that can support 0.92 devices per sq. ft. brings with it some unique requirements. First, ONAP needs to optimize the network around real time and bulk analytics, place VNFs on the correct edge cloud, scale and heal services, and provide edge automation. Next, ONAP needs to handle end-to-end network slicing. These requirements have led to the three above-listed initiatives. Between the Casablanca and Dublin releases, the 5G blueprint incorporates PNF integration, edge automation, real-time and bulk analytics, homing (VNF placement), scaling and modeling work that will support end-to-end network slicing in future releases. |image4|**Figure 4. Disaggregated Hybrid RAN** Read the 5G Blueprint to learn more. Residential Connectivity Blueprints ----------------------------------- Two ONAP blueprints (vCPE and BBS) address the residential connectivity use case. Virtual CPE (vCPE) .................. Currently, services offered to a subscriber are restricted to what is designed into the broadband residential gateway. In the blueprint, the customer has a slimmed down physical CPE (pCPE) attached to a traditional broadband network such as DSL, DOCSIS, or PON (Figure 5). A tunnel is established to a data center hosting various VNFs providing a much larger set of services to the subscriber at a significantly lower cost to the operator. In this blueprint, ONAP supports complex orchestration and management of open source VNFs and both virtual and underlay connectivity. |image5|
**Figure 5. ONAP vCPE Architecture** Read the Residential vCPE Use Case with ONAP blueprint to learn more. Broadband Service (BBS) ....................... This blueprint provides multi-gigabit residential internet connectivity services based on PON (Passive Optical Network) access technology. A key element of this blueprint is to show automatic re-registration of an ONT (Optical Network Terminal) once the subscriber moves (nomadic ONT) as well as service subscription plan changes. This blueprint uses ONAP for the design, deployment, lifecycle management, and service assurance of broadband services. It further shows how ONAP can orchestrate services across different locations (e.g. Central Office, Core) and technology domains (e.g. Access, Edge). |image6|
**Figure 6. ONAP BBS Architecture** Read the Residential Connectivity Blueprint to learn more. Voice over LTE (VoLTE) Blueprint -------------------------------- This blueprint uses ONAP to orchestrate a Voice over LTE service. The VoLTE blueprint incorporates commercial VNFs to create and manage the underlying vEPC and vIMS services by interworking with vendor-specific components, including VNFMs, EMSs, VIMs and SDN controllers, across Edge Data Centers and a Core Data Center. ONAP supports the VoLTE use case with several key components: SO, VF-C, SDN-C, and Multi-VIM/ Cloud. In this blueprint, SO is responsible for VoLTE end-to-end service orchestration working in collaboration with VF-C and SDN-C. SDN-C establishes network connectivity, then the VF-C component completes the Network Services and VNF lifecycle management (including service initiation, termination and manual scaling) and FCAPS (fault, configuration, accounting, performance, security) management. This blueprint also shows advanced functionality such as scaling and change management. |image7|
**Figure 7. ONAP VoLTE Architecture Open Network Automation Platform** Read the VoLTE Blueprint to learn more. CCVPN (Cross Domain and Cross Layer VPN) Blueprint -------------------------------------------------- CSPs, such as CMCC and Vodafone, see a strong demand for high-bandwidth, flat, high-speed OTN (Optical Transport Networks) across carrier networks. They also want to provide a high-speed, flexible and intelligent service for high-value customers, and an instant and flexible VPN service for SMB companies. |image8|
**Figure 8. ONAP CCVPN Architecture** The CCVPN (Cross Domain and Cross Layer VPN) blueprint is a combination of SOTN (Super high-speed Optical Transport Network) and ONAP, which takes advantage of the orchestration ability of ONAP, to realize a unified management and scheduling of resource and services. It achieves cross-domain orchestration and ONAP peering across service providers. In this blueprint, SO is responsible for CCVPN end-to-end service orchestration working in collaboration with VF-C and SDN-C. SDN-C establishes network connectivity, then the VF-C component completes the Network Services and VNF lifecycle management. ONAP peering across CSPs uses east-west API which is being aligned with the MEF Interlude API. The key innovations in this use case are physical network discovery and modeling, cross-domain orchestration across multiple physical networks, cross operator end-to-end service provisioning and close-loop reroute for cross-domain service. The Dublin release added support for dynamic changes (branch sites, VNFs) and intelligent service optimization. To provide an extension work, many enhancement functions have been added into CCVPN blueprint in Dublin release. Multi-sites VPN service, service change and close-loop bandwidth adjustment will be realized in Dublin release, other functions, like AI Apps, SFC and E-LAN service will be supported in the next few releases. Read the CCVPN Blueprint to learn more. vFW/vDNS Blueprint ------------------ The virtual firewall, virtual DNS blueprint is a basic demo to verify that ONAP has been correctly installed and to get a basic introduction to ONAP. The blueprint consists of 5 VNFs: vFW, vPacketGenerator, vDataSink, vDNS and vLoadBalancer. The blueprint exercises most aspects of ONAP, showing VNF onboarding, network service creation, service deployment and closed-loop automation. The key components involved are SDC, CLAMP, SO, APP-C, DCAE and Policy. In the Dublin release, the vFW blueprint has been demonstrated by using a mix of a CNF and VNF. Conclusion ========== The ONAP platform provides a comprehensive platform for real-time, policy-driven orchestration and automation of physical and virtual network functions that will enable software, network, IT and cloud providers and developers to rapidly automate new services and support complete lifecycle management. By unifying member resources, ONAP will accelerate the development of a vibrant ecosystem around a globally shared architecture and implementation for network automation with an open standards focus faster than any one product could on its own. Resources ========= Watch videos about the major platform components on `YouTube <https://www.youtube.com/channel/UCmzybjwmY1te0FHxLFY-Uog>`_ and `Youku <https://i.youku.com/i/UNTI4MjA5MDg5Ng==?spm=a2h1n.8251843.0.0>`_. Read about how ONAP can be deployed using containers. .. |image1| image:: media/ONAP-toplevel.png :width: 6.5in :height: 3.13548in .. |image2| image:: media/ONAP-fncview.png :width: 6.5in :height: 3.409in .. |image3| image:: media/ONAP-closedloop.png :width: 6in :height: 2.6in .. |image4| image:: media/ONAP-5G.png :width: 6in :height: 2.6in .. |image5| image:: media/ONAP-vcpe.png :width: 6.5in :height: 3.28271in .. |image6| image:: media/ONAP-bbs.png :width: 6.5in :height: 3.02431in .. |image7| image:: media/ONAP-volte.png :width: 6.5in :height: 3.02431in .. |image8| image:: media/ONAP-ccvpn.png :width: 6.5in