ponents. ONAP provides high utilization of network resources by combining dynamic, policy-enforced functions for component and workload shaping, placement, execution, and administration. These functions are built into ONAP, and utilize the network cloud; when combined, these provide a unique level of operational and administrative capabilities for workloads that run natively within the ecosystem. They will also extend many of these capabilities into third-party cloud ecosystems as interoperability standards for network clouds evolve. Diverse workloads are at the heart of the capabilities enabled by ONAP. The service design and creation capabilities and policy recipes eliminate many of the manual and long-running processes performed via traditional OSSs (e.g., break-fix largely moves to a plan and build function). ONAP provides external applications (OSS/business support system [BSS], customer apps, and third-party integration) with a secured, RESTful application programming interfaces (API) access control to ONAP services, events, and data. The Network Operating System ONAP: LOGICAL TECHNICAL ARCHITECTURE In order to completely understand what drove the definition of the ONAP logical technical archi- tecture and the functions ascribed to it, it is helpful to consider the initial drivers of the software- defined network (SDN) cloud and network functions virtualization (NFV) efforts. When the network cloud effort began, cloud technology was being adopted, focusing primarily on information technology (IT) or corporate applications. The cloud technology provided the ability to manage diverse workloads of applications dynamically. Included among the cloud capabilities were 1. Real-time instantiation of virtual machines (VMs) on commercial hardware 2. Dynamic assignment of applications and workloads to VMs 3. Dynamic movement of applications and dependent functions to different VMs on servers within and across data centers in different geographies 4. Dynamic control of resources made available to applications (CPU, mem