data centers. Several options are currently being explored to provide the integration between the large-scale centralized AT&T Integrated Cloud (AIC) nodes and the highly distributed access nodes. The first option is to treat the access nodes as peripherals, which perform specific functions or provide specific customized interfaces. This can be an appropriate option for simple and sta- ble access functions that do not need to be updated to provide new capabilities for new services. However, because this option relegates the software on the access node to its own compute struc- ture, it removes that software from the benefits of being part of the overall network cloud compute structure. In a sense, this software essentially becomes a new form of embedded software-being different only in that its interfaces are designed to work with an ONAP SDN/NFV environment. The second option would be to modify the overall network cloud software infrastructure to support smaller highly distributed environments. This requires expanding the configurability of all components SO that they can scale down to support very small distributed "data centers," as measured by the number of compute, storage, and switching nodes. Ideally, this might enable the AIC environment to include distributed embedded processors as a native part of its architecture, allowing the compute resources embedded in a SOC to become part of a small cloud implementa- tion. While current technology has not demonstrated a single orchestration architecture that can efficiently span the extreme dynamic range required to support this approach, new orchestrators Network Access or extensions of current orchestrators to support smaller configurations are under investigation and should be feasible. One example of use of this type of configuration would be the instantiation of a localized lightweight remote orchestration agent at the small cloud node that could allow remoting most of the ONAP capabilities to a larger cloud node. With the support of sufficiently small con- f