Techniques for scaling a reduced footprint data center

Abstract

Techniques are disclosed for scaling a reduced footprint data center. A networking device can be implemented at the reduced footprint data center and can include a plurality of networking ports. The networking device can be connected to a plurality of reduced footprint server racks using a first networking port of the plurality of networking ports. The plurality of reduced footprint data center server racks can be connected in a ring network and host a cloud service. An additional server rack can be connected to the networking device using a second networking port of the plurality of networking ports. A computing device of the additional server rack can be provisioned to host a portion of a data plane of the cloud service.

Description

PATENT Attorney Docket No.: 088325-1461167 (429240PC) Client Reference No.: ORC24138761-WO-PCT (IaaS #728.10) TECHNIQUES FOR SCALING A REDUCED FOOTPRINT DATA CENTER CROSS-REFERENCES TO RELATED APPLICATIONS

[0001] This international application claims priority to and the benefit of the following applications, the entire contents of which are hereby incorporated by reference in their entirety for all purposes: 1. U.S. Provisional Patent Application 63 / 564,195, filed on March 12, 2024, entitled "SCALABLE FOOTPRINT FOR DEDICATED CLOUD TECHNIQUES"; 2. U.S. Provisional Patent Application 63 / 568,061, filed on March 21, 2024, entitled "NETWORKING FOR A SCALABLE DEDICATED CLOUD FOOTPRINT"; 3. U.S. Provisional Patent Application 63 / 568,234, filed on March 21, 2024, entitled "SCALABLE FOOTPRINT FOR DEDICATED CLOUD TECHNIQUES"; 4. U.S. Provisional Patent Application 63 / 633,966, filed on April 15, 2024, entitled "SCALABLE FOOTPRINT FOR DEDICATED CLOUD TECHNIQUES"; 5. U.S. Provisional Patent Application 63 / 637,691, filed on April 23, 2024, entitled "SCALABLE FOOTPRINT FOR DEDICATED CLOUD TECHNIQUES"; 6. U.S. Provisional Patent Application 63 / 660,377, filed on June 14, 2024, entitled "DRCC ARCHITECTURE UPDATE"; and 7. U.S. Provisional Patent Application 63 / 689,572, filed on August 30, 2024, entitled "TECHNIQUES FOR SCALING A REDUCED FOOTPRINT DATA CENTER." 8. U.S. Patent Application 19 / 068,805, filed on March 3, 2025, entitled "TECHNIQUES FOR SCALING A REDUCED FOOTPRINT DATA CENTER." FIELD

[0002] This disclosure is generally concerned with data centers. More specifically, this disclosure relates to building data centers initially with a minimal number of computing devices and then expanding the data center. BACKGROUND

[0003] Cloud service providers (CSPs) can offer computing infrastructure for customers using resources in several data centers. As cloud computing demand increases, CSPs can improve the availability of cloud resources by scaling the data centers. However, scaling can result in largedata center footprints with a significant number of computing devices requiring a commensurate amount of resources to operate as well as reserving significant computing resources for the effective management of the cloud resources themselves. BRIEF SUMMARY

[0004] Embodiments of the present disclosure relate to cloud computing networks. More particularly, the present disclosure describes architectures, infrastructure, and related techniques for scaling a reduced footprint data center into larger configurations. A typical CSP may provide cloud services to multiple customers. Each customer may have the ability to customize and configure the infrastructure provisioned to support their allocated cloud resources. To manage the infrastructure provisioning for multiple customers, the CSP may reserve computing resources within a data center to provide certain "core" services to both customers and to other services operated by the CSP. For example, services like block storage, object storage, identity and access management, and key management and secrets services are implemented within a "service enclave" of the data center. The service enclave may connect via a substrate network of computing devices (virtual machines and / or bare metal instances) hosted within the data center. The substrate network may be a part of the "underlay network" of the data center, which includes the physical network connecting bare metal devices, smart network interface cards (SmartNICs) of the computing devices, and networking infrastructure like top-of-rack switches. By contrast, CSP customers have infrastructure provisioned in an "overlay network" comprising one or more VCNs of virtualized environments to provide resources for the customer (e.g., compute, storage, etc.).

[0005] The service enclave exists on dedicated hardware within the data center. Because of this, the services hosted within the service enclave are difficult to scale. Whereas additional racks and servers can be implemented within the data center to expand the resources available to CSP customers, the dedicated computing resources for the service enclave are typically of a fixed size that depends on the largest predicted size of the data center. Expanding the service enclave can require a complicated addition of computing resources that may impact the availability of the core services to customers. Additionally, unused resources within the service enclave (e.g., if the service enclave is sized too large for the customer demand from the data center) cannot be easilymade available to the customers, since the service enclave does not typically allow network access from the customer overlay network.

[0006] Even as the demand for cloud services grows, CSPs may want to deploy data centers to meet that demand that initially have the smallest physical footprint possible. Such a footprint can improve the ease of both deploying the physical components and configuring the initial infrastructure while still allowing the data center to scale to meet customer demand. In the reduced footprint, rather than dedicate a portion of the computing hardware to providing the service enclave, the "core services" that are hosted in the service enclave can instead be implemented in the overlay network. By doing so, the core services can be scaled as the data center footprint expands. The computing devices used to construct the reduced footprint data center can be homogenized, improving the initial configuration and the easing the expansion of the footprint when additional, homogeneous devices are added. In addition, by eliminating the substrate network, flexible overlay network shapes are made available for both CSP core services and customers.

[0007] The scaling of a reduced footprint data center can occur in three phases. In a first phase, the reduced footprint data center can be initially deployed using as few as a single server rack configured to provide "core services" in the overlay network while providing compute, storage, database, and other services for customers of the CSP. In this phase, additional, identical reduced footprint server racks can be added and connected in a ring network with the initial rack up to an upper limit of reduced footprint data center racks for a "small footprint." As new reduced footprint server racks are added, the data planes and control planes of core services deployed to the initial server rack can be extended to VMs hosted on the new server racks, while providing additional computing resources to customers of the reduced footprint data center. Once the limit is reached for the ring network (e.g., 6 High Density server racks or 12 Low Density server racks), the reduced footprint data center can scale to a "medium footprint" in a second phase. To extend the network, a networking rack can be installed at the reduced footprint data center and connected to one or more of the existing reduced footprint server racks. Then, additional server racks, which can have a different configuration (e.g., different number of server devices, different components of server devices) than the reduced footprint server racks, can be connected to the networking rack. Existing services in the small footprint can then be expanded tocomputing resources of the additional server rack. Finally, once the number of server racks added exceeds the upper limit available for network connections with the networking rack, the medium footprint data center can scale to an arbitrary sized "large footprint." In the large footprint, an optical networking rack can be connected to the existing networking rack to provide extremely high data rate and bandwidth connections to one or more additional server racks that can be sized as for a conventional data center, with the resources of the new server racks available for customers of the data center. The final configuration of both the medium footprint and the large footprint data centers can be similar to a conventional data center but with the "core services" still hosted in an overlay network implemented on the original "small footprint" reduced footprint server racks.

[0008] Embodiments described herein relate to methods and systems for scaling a reduced footprint data center. A method for scaling a reduced footprint data center can include implementing, at the reduced footprint data center, a networking device having a plurality of networking ports. The networking device can be connected to a plurality of reduced footprint server racks. The plurality of reduced footprint server racks can be connected in a ring network and host a cloud service. The networking device can be connected to the plurality of reduced footprint server racks using at least a first networking port of the plurality of networking ports. The method can also include connecting an additional server rack to the networking device using a second networking port of the plurality of networking ports. The method can also include provisioning a computing device of the additional server rack to host a portion of a data plane of the cloud service.

[0009] Another embodiment is directed to a method for scaling a data center having a plurality of reduced footprint server racks. The method can include implementing, at the data center, an optical networking device. The method can also include connecting the optical networking device to a networking device of the data center. The networking device can be connected to a plurality of reduced footprint server racks hosting a cloud service. The method can also include connecting an additional server rack to the optical networking device and provisioning a computing device of the additional server rack to host a portion of a data plane of the cloud service.

[0010] A further embodiment is directed to a reduced footprint data center server rack. The reduced footprint data center server rack can include one or more power distribution units, one or more network switches connected to the one or more power distribution units, and a plurality of server devices electrically connected to the one or more power distribution units and communicatively connected to the one or more network switches. The plurality of server devices can be configured to host a plurality of cloud services. BRIEF DESCRIPTION OF DRAWINGS

[0011] FIG.1 is a block diagram illustrating an example system architecture of a reduced footprint data center including an initialization device, according to some embodiments.

[0012] FIG.2A is a block diagram illustrating a conventional data center including a plurality of server racks reserved for particular functionality.

[0013] FIG.2B is a block diagram illustrating a reduced footprint data center in which services are in an overlay network, according to some embodiments.

[0014] FIG.3 is a block diagram illustrating networking connections between an overlay network and an underlay network in a reduced footprint data center, according to some embodiments.

[0015] FIG.4A is a block diagram showing the configuration of a low density server rack for use in a reduced footprint data center, according to some embodiments.

[0016] FIG.4B is a block diagram showing the configuration of a high density server rack for use in a reduced footprint data center, according to some embodiments.

[0017] FIG.5 is a block diagram illustrating an example architecture of a reduced footprint data center scaling to a medium footprint, according to some embodiments.

[0018] FIG.6 is a block diagram illustrating an example architecture and of a medium footprint reduced footprint data center scaling to a large footprint, according to some embodiments.

[0019] FIG.7 is a flow diagram of an example process for scaling a reduced footprint data center to a medium footprint, according to some embodiments.

[0020] FIG.8 is a flow diagram of an example process for a reduced footprint data center to a large footprint, according to some embodiments.

[0021] FIG.9 is a block diagram illustrating one pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.

[0022] FIG.10 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.

[0023] FIG.11 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.

[0024] FIG.12 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.

[0025] FIG.13 is a block diagram illustrating an example computer system, according to at least one embodiment. DETAILED DESCRIPTION

[0026] The adoption of cloud services has seen a rapid uptick in recent times. Various types of cloud services are now provided by various different cloud service providers (CSPs). The term cloud service is generally used to refer to a service or functionality that is made available by a CSP to users or customers on demand (e.g., via a subscription model) using systems and infrastructure (cloud infrastructure) provided by the CSP. Typically, the servers and systems that make up the CSP's infrastructure and which is used to provide a cloud service to a customer are separate from the customer's own on-premises servers and systems. Customers can thus avail themselves of cloud services provided by the CSP without having to purchase separate hardware and software resources for the services. Cloud services are designed to provide a subscribing customer easy, scalable, and on-demand access to applications and computing resources without the customer having to invest in procuring the infrastructure that is used for providing the services or functions. Various different types or models of cloud services may be offered such as Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), and others. A customer can subscribe to one or more cloud services provided by a CSP. The customer can be any entity such as an individual, an organization, an enterprise, and the like.

[0027] As indicated above, a CSP is responsible for providing the infrastructure and resources that are used for providing cloud services to subscribing customers. The resources provided by the CSP can include both hardware and software resources. These resources can include, for example, compute resources (e.g., virtual machines, containers, applications, processors), memory resources (e.g., databases, data stores), networking resources (e.g., routers, host machines, load balancers), identity, and other resources. In certain implementations, the resources provided by a CSP for providing a set of cloud services CSP are organized into data centers. A data center may be configured to provide a particular set of cloud services. The CSP is responsible for equipping the data center with infrastructure and resources that are used to provide that particular set of cloud services. A CSP may build one or more data centers.

[0028] The following definitions are useful for portions of a data center built by a CSP:

[0029] Underlay Network – The physical network that sits below the Overlay Network and virtual cloud networks (VCNs) therein. The existing Substrate network is a portion of the Underlay Network. ILOM ports, management and SmartNIC substrate addresses are also part of the underlay network.

[0030] Overlay Network – The network environment that is available for use by executing services and applications, including virtualization environments, that provide the functionality of the data center to both customers and the CSP. The Overlay Network can include VCN(s), virtualization environments, and networking connections from these VCNs in the reduced footprint data center to other cloud computing services of the CSP (e.g., services provided in other data center environments). Specific details about network virtualization and VCNs as part of Infrastructure as a Service are provided below with respect to FIGS.9-13.

[0031] Substrate Network – A portion of the Underlay Network that contains host devices (e.g., bare metal computing devices and / or VMs) running only Substrate Services. In existing environments these host devices may not have SmartNICs. The host devices may be managed by service teams responsible for one or more of the Substrate Services.

[0032] Substrate Services – The list of services that currently run in the Substrate Network, while most of these run in Service Enclave (Block Storage, Object Storage, Identity Service etc.) some substrate service live outside of the service enclave. Currently substrate services have amix of services that must talk to the underlay network (e.g. Network Monitoring) and services that due to historical reasons reside in service enclave (e.g. Object Storage). With the elimination of dedicated substrate host, we expect substrate services to converge into only services that must communicate with the underlay network.

[0033] SmartNIC – A computing component that combines a network interface card with additional functionality for network virtualization to create layers of network abstraction that can be run on top of the physical networking components (e.g., the Underlay Network). The SmartNIC can include processors and memory that can perform computing operations to provide the additional functionality.

[0034] BIOS Device(s) – A computing device or a plurality of computing devices on a server rack in the reduced footprint data center. The BIOS Device(s) may be designed to enable independent and resilient operations during various boot scenarios and network disruptions. The BIOS Device(s) may be configured to facilitate the initial boot processes for the reduced footprint data center, provide essential services during recovery, and ensure the region's stability, especially in power-constrained environments. The BIOS Device hosts a range of functions, all of which can allow the autonomous operation of the region. For example, these functions can include DNS resolution, NTP synchronization, DHCP / ZTP configuration, and various security and provisioning services. By offering these capabilities, the BIOS Device ensures that the rack can bootstrap itself, recover from power or network-related events, and maintain essential connectivity and management functions without relying on external resources. For example, each server rack can have one BIOS device, or can have two or three BIOS devices. In various embodiments, the BIOS device can have similar hardware specifications (e.g., number of processors, amount of memory, amount of attached storage devices) as other server devices on the rack.

[0035] A reduced footprint data center can have a new architecture for a region in which the initial network footprint is as small as feasible (e.g., six racks, four racks, and possibly even a single rack of server devices) while still providing core cloud services and scalability for customer demands. In particular, a reduced footprint data center may not segregate resources for the Service Enclave (SE) from the Customer Enclave (CE). Instead, the Butterfly region will place SE services (e.g., Block Storage, Object Storage, Identity, Key Management, Secrets),which primarily operate in a Substrate Network, into an Overlay Network. This means that a Butterfly region will not have dedicated hosts for the Substrate Network, but will require particular solutions for connectivity with the Substrate services now in the Overlay. In addition, a small portion of fundamental boot services is needed to ensure initial route configuration for the services in the Overlay during startup and / or recovery.

[0036] FIGS.1-3 provide an overview of the concepts embodied by a reduced footprint data center.

[0037] FIG.1 is a block diagram illustrating an example system architecture of a reduced footprint data center 100 including an initialization device 102. As shown in FIG.1, the reduced footprint data center 100 can include six racks of server devices. The racks may be referred to as "Butterfly" racks. The reduced footprint data center 100 can include Butterfly rack 110, Butterfly rack 120, Butterfly rack 130, Butterfly rack 140, Butterfly rack 150, and Butterfly rack 160. In some embodiments, the racks can be identical. For example, Butterfly rack 110 can include the same number of computing and / or networking devices as each other Butterfly rack 120-160.

[0038] Butterfly rack 110 can include two top-of-rack (TOR) switches 106, 108. The TOR switches 106, 108 can each include one or more networking switches configured to provide network communication between the server devices and other computing devices within Butterfly rack 110 as well as one or more networking connections to the other Butterfly racks 120-160 and or other networks including customer network 114.

[0039] The Butterfly rack 110 can also include one or more BIOS device(s) 102. The BIOS device can be a server device configured to execute one or more processes to provide a set of "core services" within the reduced footprint data center 100 during startup / boot processes. The BIOS device(s) 102 can configure one or more components of the reduced footprint data center 100 during startup. For example, the BIOS device(s) 102 can send network configuration information to a networking device within the Butterfly racks 110-160. The networking device can be a SmartNIC attached to a server device within the Butterfly racks 110-160. As another example, the BIOS device(s) 102 can send network configuration information to a substrate access VCN. The substrate access VCN can be deployed to one or more hosts within the reduced footprint data center 100. For example, VMs executing in the Butterfly racks 110-160 can be configured to be a substrate access VCN. The substrate access VCN can be configured to providenetworking routes between one or more other VCNs (e.g., customer VCNs) and the networking devices (e.g., SmartNICs) and other networking components of the substrate services that now execute in their own VCN in the Overlay.

[0040] In some embodiments, the BIOS device(s) 102 can also be configured to host one or more services like a key exchange service (KeS), a device encryption key (DEK) service, or other core services. In addition, the BIOS device(s) 102 can include boot volumes for VMs that are started on host devices in the reduced footprint data center 100. For example, BIOS device(s) 102 can provide boot volumes for VMs on hypervisors hosted on server device(s) 104.

[0041] The Butterfly rack 110 can include one or more additional server device(s) 104. The server device(s) 104 can each include one or more processors and one or more memories that together can store and execute instructions for implementing computing services as described herein, including, for example, compute, storage, VMs, CSP services, customer services and / or applications, and the like. As depicted in FIG.1, each of the Butterfly racks 110-160 can include an identical complement of server device(s) and TORs. In some embodiments, each of the Butterfly racks 110-160 can include a BIOS device, although the techniques described herein can be implemented using only a single BIOS device within the reduced footprint data center 100. Each server device of the server device(s) 104 can include a trusted platform module (TPM). The TPM on each device can be a microcontroller or other processor (or multiple processors) along with storage for performing cryptographical operations like hashing, encryption / decryption, key and key pair generation, and key storage. The TPM may generally conform to a standard characterizing such devices, for example, ISO / IEC 11889.

[0042] The reduced footprint data center 100 can also include a networking rack 112. The networking rack 112 can include one or more networking devices including switches, gateways, routers, and the like for communicatively coupling the Butterfly racks 110-160 to each other and to customer network 114. The customer network 114 can include an on-premises network connected to the reduced footprint data center 100. In some embodiments, the customer network 114 can provide network connectivity to a public network, including the Internet. As described below with respect to FIG. 2, the networking rack 112 may not be part of an initial "Small" reduced footprint data center and may be added to support the scaling of the reduced footprint data center 100.

[0043] FIG.2A is a block diagram illustrating a conventional data center 200 including a plurality of server racks reserved for particular functionality. In a conventional data center 200, the plurality of server racks can each include multiple server devices as well as networking equipment (e.g., TORs) and power supply and distribution equipment. The conventional data center 200 shown in FIG.2A can have a standard footprint of 13 server racks as shown, although additional server racks are possible in larger data centers.

[0044] To provide networking isolation between customer data and CSP data for CSP services executing in the conventional data center 200, a portion of the server racks can be reserved as a service enclave, so that the computing devices on those server racks can host and provide CSP services within the conventional data center 200 without also hosting customer data. As shown in FIG.2A, server racks 1-4 may be included as service enclave racks 202.

[0045] Similarly, a portion of the server racks can be provided as a customer enclave, so that the computing devices on those server racks can host customer services, applications, and associated customer data. Racks 5-7 can be part of the customer enclave racks 204 within conventional data center 200.

[0046] The isolation between the service enclave and the customer enclave can be enforced by software-defined perimeters that define edge devices and / or software within the enclave as distinguished from hardware / software elements outside of the enclave. Access into and out of each enclave may be controlled, monitored, and / or policy driven. For example, access to the service enclave may be based on authorization, limited to authorized clients of the CSP. Such access may be based on one or more credentials provided to the enclave.

[0047] The conventional data center 200 can also include database racks 206 (racks 8-9) and networking racks 208 (racks 10-13). The database racks 206 can include computing devices and storage devices that provide storage and management for databases, data stores, object storage, and similar data persistence techniques within the conventional data center 200. The networking racks 208 can include networking devices that provide connectivity to the computing devices within conventional data center 200 and to other networks (e.g., customer networks, the internet, etc.).

[0048] FIG.2B is a block diagram illustrating a reduced footprint data center 210 in which services are in an overlay network, according to some embodiments. The reduced footprint data center 210 may be an example of reduced footprint data center 100 of FIG.1, including six Butterfly racks, each having a plurality of server devices, networking devices, and power distribution devices.

[0049] Unlike the conventional data center 200, in which particular server racks are reserved as service enclave racks 202 and customer enclave racks 204, the reduced footprint data center 210 can have an Overlay network 212 that spans computing devices in all of the server racks. For example, server devices on Butterfly Rack 1 and Butterfly Rack 6 can host VMs for a VCN in the Overlay network 212. The Overlay network 212 can then include both core services 214 and customer services 216. The core services 214 can include one or more VCNs for the CSP services that would be hosted within the Service Enclave of conventional data center 200 (e.g., on service enclave racks 202). In the reduced footprint data center 210, the core services 214 can exist in the overlay network 212 on any one or more of the server devices within Butterfly racks. Similarly, customer services 216 can exist in the overlay network 212 on host devices on any of the Butterfly racks. In some embodiments the core services 214 may be hosted on specific devices of the reduced footprint data center. For example, the core services 214 may be hosted on Butterfly racks 1-3, while the customer services 216 may be hosted on Butterfly racks 4-6. In other embodiments, the core services 214 and the customer services 216 may be hosted on any of the Butterfly racks, as depicted in FIG. 2B.

[0050] FIG.3 is a block diagram illustrating an example network architecture of networking connections between one or more VCNs (substrate service VCNs) in an Overlay network 302 and the Underlay network 322 in a reduced footprint data center 300, according to some embodiments. The reduced footprint data center 300 can be an example of other reduced footprint data centers described herein, including reduced footprint data center 100 of FIG.1.

[0051] In the reduced footprint data center 300, the CSP services that were previously implemented in the SE (e.g., hosted on service enclave racks 202 of FIG.2) can now execute in one or more substrate service VCNs 304-408. For example, substrate service VCN-1304 can be a VCN for a Compute service control plane, substrate service VCN-2306 can be a VCN for a PKI service, and substrate service VCN-N 308 can be a VCN for a Block Storage service. SEservice control and data planes can be separated into different VCNs. The substrate service VCNs 304-408 can exist in the Overlay network 302. The Overlay network 302 can also include customer VCN(s) 316, which can be limited in their connectivity to the Underlay network 322.

[0052] Each substrate service VCN can have its own route table that defines the network traffic routing rules for forwarding network traffic within the network of the reduced footprint data center 300. As shown in FIG.3, substrate service VCN-1 can have VCN-1 route table 310, substrate service VCN-2 can have VCN-2 route table 312, and substrate service VCN-N 308 can have VCN-N route table 314. The routing information of each of the substrate service VCNs 304-408 can be initially configured when the reduced footprint data center 300 is first built so that network traffic to / from the core SE services can be routed between the Overlay network 302 and the Underlay network 322.

[0053] The Underlay network 322 can include various devices and other networking endpoints that are connected via the physical networking components of the reduced footprint data center 300. As shown in FIG. 3, the Underlay network 322 can include, without limitation, ILOM(s) 324, Bastions 326, NTP server(s) 328, BIOS services 330, and VNIC(s) 332. The ILOM(s) 324 can be computing devices and network targets that provide access to the server devices of reduced footprint data center 300 for both in-band and out-of-band management. For example, the ILOM(s) 324 can allow for remote management of the associated server devices within the server racks of reduced footprint data center 300 that is separate from the networking pathways defined for the region. The Bastions 326 can be services executing on the server devices of the reduced footprint data center 300 that provide network access via the Underlay network 322 and do not have public network addresses. The Bastions 326 can provide remote access to computing resources within the reduced footprint data center 300 in conjunction with a Bastion service that operates on the Underlay network 322. The Bastion service may be an SE service that is not moved to the Overlay network 302 in the reduced footprint data center 300. Similarly, network time protocol (NTP) servicers 328 may operate in the Underlay network 322 to provide accurate timing to devices and services within the reduced footprint data center 300. BIOS services 330 can include services that are hosted on the one or more initialization devices on the server racks in the reduced footprint data center 300. For example, BIOS services 330 can include a key encryption service usable to encrypt / decrypt data on the server devices of reduced footprint datacenter 300 during the initial boot process. As another example, the BIOS services 330 can include a network configuration service that can provide the initial network configuration for devices within the reduced footprint data center 300. The VNIC(s) 332 can include network interfaces defined by SmartNICs connected to the server devices within the reduced footprint data center 300.

[0054] With SE services moved from to the Overlay network 302, the SE services may still need network connectivity with the Underlay network 322 to properly function. To provide this connectivity, a substrate access VCN 318 can be implemented within the reduced footprint data center 300. The substrate access VCN 318 can include a dynamic routing gateway (DRG) that allows communication between the substrate service VCNs 304-408 and the Underlay network 322. The substrate access VCN 318 can then have a DRG route table 320 that can define a single route rule for reaching the Underlay network 322 from the substrate service VCNs 304-408.

[0055] To avoid circular dependencies when the reduced footprint data center 300 is first built or recovers from a shutdown event, an initialization device (e.g., BIOS device(s) 102 of FIG.1) can be used to configure the network addresses and routes for a substrate access VCN 318, a dynamic route gateway within the substrate access VCN 318, and / or one or more SmartNICs of the Underlay network 322. When the server devices of each reduced footprint data center 300 server racks are booted, the substrate access VCN 318 can be deployed to communicatively connect the one or more substrate service VCNs 304-408 with the Underlay network 322. The initialization device can send network configuration information to the substrate access VCN 318 to configure the DRG route table 320 to provide initial network addresses (e.g., IP addresses) for each endpoint of the substrate service VCNs 304-408 in the Overlay network 302 until a DHCP service and other networking services are available in their respective substrate service VCNs.

[0056] In addition, the initialization device can send networking configuration information to define one or more static routes for the dynamic routing gateway as part of the DRG routing table 320. The static routes can characterize a networking connection between the Underlay network 322, including a SmartNIC connected to each server device of the reduced footprint data center (e.g., server device(s) 110 of FIG. 1), and each substrate service VCN 304-408.

[0057] Finally, the initialization device can send network configuration information to each of the SmartNICs to provide each SmartNIC a network address (e.g., a network address for theSmartNICs' endpoints in the Underlay network 322). Configuring each of these components of the reduced footprint data center can be done in response to the initialization device receiving indications that the corresponding component has been brought up to an active state (e.g., SmartNIC powered on and reachable over the Underlay network 322, substrate access VCN 318 deployed to one or more hosts within the reduced footprint data center 300, etc.). Reduced Footprint Data Center Scaling

[0058] To meet the desired "as small as feasible" footprint, a new reduced footprint rack design can be used, including next-generation server devices referred to as "hyperconverged servers" that are configured to have the highest possible resource density (e.g., 2x 192 core processors, 24x 256 GB DDR5 RAM modules, a smart network interface card (SmartNIC)). The reduced footprint racks can have a standardized shape (e.g., six hyperconverged servers in a "low density" configuration; 12 hyperconverged servers in a "high density" configuration). The new server architecture can allow for deployment of a reduced footprint data center having only a single rack hosting most of the core CSP services while still providing cloud resources to the customer. The initial footprint can then be scaled out according to three regimes:

[0059] Small Footprint – Beginning with a single reduced footprint rack, additional reduced footprint racks can be added to the small footprint (1-6 high density reduced footprint racks or 2- 12 low density reduced footprint racks). Each additional reduced footprint rack can be connected to the existing footprint in a ring network using the TOR switches on each rack. Because the service control planes are functional in the Overlay of the initial reduced footprint rack, the additional racks can be adapted to provide additional data plane resources for those services. Each reduced footprint rack can support connections to the customer's network.

[0060] Medium Footprint – From a Small footprint reduced footprint data center, additional racks can be added. To support racks beyond the upper capacity of the Small footprint, a new networking rack can be connected to the existing reduced footprint data center and then connected to the additional racks. The additional racks can be conventional racks rather than reduced footprint racks. The ring network of the Small footprint is preserved even with the connection to the networking rack. The networking rack can support connections to 64 total racks (inclusive of the reduced footprint racks) and provides the connection to the customer's network. Example specifications for the networking rack include two chasses that each have 4LCs each with 24x400G ports for a total of 384x100G links, 8x100G connections to each server rack (up to 64 racks), up to 128x100G towards the customer network, and up to 128x100G available for future expansion.

[0061] Large Footprint – From the Medium footprint reduced footprint data center, additional capacity beyond 64 total racks requires adding an optical gate rack for connecting additional racks beyond the 64 limit. The additional rack footprint can include racks (e.g., QFab) supporting Exadata or other high-capacity, high-throughput data service.

[0062] Numerous advantages can be realized by removing services from the Substrate. Services teams can eliminate duplicated work (e.g., networking configuration for Underlay and Overlay connectivity), a CSP can completely eliminate some services, compute and storage capacity becomes fungible across all services in the Overlay, and service connectivity is greatly simplified. Services teams can be agnostic about the configuration of their services. If the hosts are provisioned to communicate with the Substrate Access VCN, then the services function as any other customer service. Importantly, a reduced footprint data center does not dedicate a significant fraction of its computing resources to CSP services from the beginning in an unchangeable way. If the CSP services can be scaled down to meet customer needs, the freed resources can be provided to the customer without the need for a physical scale-up. In a complementary way, CSP services can also scale-up in the same way as customer services, since the CSP services now reside in the CE Overlay network. An initial "Small" reduced footprint data center footprint (e.g., one rack) greatly speeds up the deployment of a data center at a customer while allowing easy expansion through various footprint scales. The scaled footprints still retain the services in the virtualized Overlay network, so the expansion can be seamless.

[0063] FIG.4A is a block diagram showing the configuration of a low density server racks 400 for use in a reduced footprint data center, according to some embodiments. The low density server racks 400 can include two Butterfly racks, Butterfly rack 410 and Butterfly rack 420. Butterfly rack 410 and Butterfly rack 420 can be examples of the Butterfly racks described above with respect to FIG.1, for example Butterfly rack 110.

[0064] In some embodiments, the Butterfly racks 410, 420 can be standard 42U size server racks. Both Butterfly rack 410 and Butterfly rack 420 can have identical components. As shown in FIG.4A, Butterfly racks 410, 420 can both include two TORs (TORs 406, 408 in Butterflyrack 410, TORs 426, 428 in Butterfly rack 420), a server device used for initialization operations in the reduced footprint data center (BIOS device(s) 402 in Butterfly rack 410, BIOS device(s) 422 in Butterfly rack 420), and two power distribution units (PDUs) 412. As depicted in FIG. 4A, each Butterfly rack 410, 420 can have three BIOS device(s) 402. In some embodiments, each Butterfly rack 410, 420 can have more or fewer BIOS devices, including one BIOS device.

[0065] In the lower density configuration, each of the Butterfly racks 410, 420 can include six server devices 404. The server devices 404 may be identical devices. As described briefly above, these server devices 404 may be "hyperconverged servers" that are configured to have the highest possible resource density for processing, memory, storage, and networking. As an example of the configuration, each server device 404 can include two 192 core processors, 24 256 GB DDR5 RAM modules (for 6 TB total memory), a SmartNIC supporting two 100G uplinks, a host NIC also supporting two 100G uplinks, two 960 GB m.2 NVMe boot drives, 14 15.6 TB NVMe storage drives, and a TPM. The PDUs 412 for the low density server racks 400 may be configured to provide sufficient power to the six server devices on each of the Butterfly racks 410, 420. However, one skilled in the art would appreciate that server devices having even greater computing resource density are possible in the server racks described herein.

[0066] FIG.4B is a block diagram showing the configuration of a high density server rack 430 for use in a reduced footprint data center, according to some embodiments. The high density server rack 430 can include a single 42U server rack that provides the same computing power as the low density server racks 400. As with the low density server racks 400, the high density server rack 430 can include two TORs 436, 438, three BIOS device(s) 432, PDUs 432, and 12 server devices 434. Each of the server devices 434 can be a hyperconverged server device as described above with respect to FIG.4A. In some embodiments, the high density server rack 430 can have more or fewer BIOS devices than depicted in FIG. 4B, including a single BIOS device.

[0067] FIG.5 is a block diagram illustrating an example architecture of a reduced footprint data center 500 scaling to a medium footprint, according to some embodiments. The reduced footprint data center 500 can include a plurality of reduced footprint server racks 502. Each of the plurality of reduced footprint server racks 502 can be an example of one of the Butterfly racks 110-160 described above with respect to FIG. 1. In a six server configuration, each of theserver racks 502 may be an example of high density server rack 430 described above with respect to FIG.4B.

[0068] The plurality of reduced footprint server racks 502 can be connected in a ring network 504 using directional network connection between each seat of TOR switches on each of the server racks. For example, a first TOR switch at each rack can be connected to a first TOR switch of two adjacent server racks, such that data communication from the server rack flows in one direction. A second TOR switch at each rack can be connected to a second TOR switch of two adjacent server racks, providing data communication between the racks in the opposite direction. The first TOR switch and the second TOR switch at each rack can be connected to one another and to each server device on the rack, providing multiple, redundant network paths from any server device of any one server rack to another server device on another server rack. The ring network 504 can therefore allow low latency and highly available network connections between resources hosted on any computing device (e.g., server device) in the plurality of reduced footprint server racks 502.

[0069] As described briefly above, the "Small" footprint reduced footprint data center can have an upper limit of reduced footprint server racks that are supported within the ring network 504. For example, a high density reduced footprint server rack (e.g., high density server rack 430) can include 12 server devices, so that the six total high density server racks may be supported in the ring network 504. As another example, a low density reduced footprint server rack (e.g., low density server racks 400) can include 6 server devices, so that 12 total low density server racks may be supported in the ring network 504. Once the "Small" footprint reduced footprint data center reaches the maximum size, the data center can scale out to a "Medium" footprint data center.

[0070] A networking rack 506 can be implemented at the reduced footprint data center. The networking rack 506 can be an example of networking rack 110 described above with respect to FIG.1. The networking rack 506 can include a plurality of networking ports that can be used to connect to one or more of the plurality of reduced footprint server racks. For example, the networking rack 506 can be connected to a first reduced footprint server rack using connection 508. The networking rack 506 can be, for example, a two chassis system having 4 LCs each with 54x400G ports for a total of 384x100G links in each chassis. The networking rack 506 in thisexample can have 8x100G connections to each server rack (up to 64 racks), up to 128x100G towards the customer network, and up to 128x100G available for future expansion towards an additional site (Large footprint).

[0071] Once the networking rack 506 has been implemented and connected, additional server racks 510 can be installed in the reduced footprint data center. The additional server racks 510 can be different from the reduced footprint server racks of the plurality of reduced footprint server racks 502. For example, the additional server racks 510 can include a different number of server devices, with each server device including a different amount of computing and / or storage resources (e.g., processors, processing cores, dynamic memory, non-volatile storage, etc.). Once the additional server racks 510 have been connected to the networking rack 506, a cloud service hosted on the plurality of reduced footprint server racks 502 can be expanded to utilize the computing resources of the additional server racks 510. As one example, a cloud service (e.g., Compute) hosted in the plurality of reduced footprint server racks 502 can have a portion of its data plane provisioned on one of the server devices of the additional server racks 510, thereby allowing the Compute service to instantiate VMs on the additional server racks 510.

[0072] FIG.6 is a block diagram illustrating an example architecture and of a medium footprint reduced footprint data center 500 scaling to a large footprint data center 600, according to some embodiments. As described above with respect to FIG.5, the reduced footprint data center 500 can include a plurality of reduced footprint server racks 502. Each of the plurality of reduced footprint server racks 502 can be an example of one of the Butterfly racks 110-160 described above with respect to FIG.1.

[0073] The medium footprint reduced footprint data center 500 can continue to add additional server racks until reaching an upper limit. For example, including the plurality of reduced footprint server racks 502, the medium footprint reduced footprint data center 500 can have up to 64 total server racks. The additional server rack 612 may represent the final server rack of the maximum number of server racks supported by the networking rack 506. For example, the additional server rack 612 may be the 64thserver rack of the medium footprint reduced footprint data center 500.

[0074] An optical rack 620 can be installed at the medium footprint reduced footprint data center 500 to scale the medium footprint reduced footprint data center 500 to a "Large" footprint.The optical rack 620 can be a high-capacity, high-throughput networking device that supports high data rate connections between the networking rack 506 and the additional racks 622 of a (up to) full-sized conventional data center of the "Large" footprint. The additional racks 622 can be any arbitrary configuration of racks of server devices, including more or fewer server devices than the server racks 510, 612 and the plurality of reduced footprint server racks 502. Once the additional racks 622 are connected, a cloud service hosted on the plurality of reduced footprint server racks 502 can expand to use resources available from the additional racks 622. For example, a Compute service can be configured to have a portion of its data plane at a computing device of the additional racks 622, thereby allowing VMs to be instantiated at the additional racks 622 for customer use.

[0075] FIG.7 is a flow diagram of an example process 700 for scaling a reduced footprint data center to a medium footprint, according to some embodiments. The process 700 can be performed by components of the reduced footprint data center (e.g., reduced footprint data center 500 of FIG.5).

[0076] The process 700 can begin at block 702 by implementing a networking device (e.g., networking rack 506 of FIG.5) at the reduced footprint data center. The networking device can include a plurality of networking ports. In some embodiments, implementing the networking device can include installing the networking device at the reduced footprint data center and / or receiving an indication that an installation of the networking device has been completed.

[0077] At block 704, the networking device can be connected to a plurality of reduced footprint server racks. The plurality of reduced footprint server racks can include one or more server devices (e.g., server device(s) 104 of FIG. 1) connected in a ring network (e.g., ring network 504 of FIG. 5). In some embodiments, the plurality of reduced footprint server racks can include twelve server racks. The plurality of reduced footprint server racks can host a cloud service or, in some embodiments, a plurality of cloud service. The cloud service can be one of the "core services" (e.g., Compute, Block Storage, Key Management, etc.) that are implemented in the Overlay network of a reduced footprint data center. The networking device can be connected to the plurality of reduced footprint server racks using at least a first networking port of the plurality of networking ports. For example, one of the TOR switches of a reduced footprint server rack can be connected the networking device via one of the networking ports of thenetworking device. In some embodiments, each of the reduced footprint server racks can be connected to a corresponding networking port of the plurality of networking ports. For example, a TOR switch of each reduced footprint server rack can be connected to a corresponding network port of the networking device.

[0078] In some embodiments, connecting the networking device to the plurality of reduced footprint server racks preserves the ring network of the reduced footprint server racks. For example, traffic routed between devices on the reduced footprint server racks may route through the ring network rather than through the networking device.

[0079] At block 706, an additional server rack (e.g., additional server racks 510 of FIG.5) can be connected to the networking device using a second networking port of the plurality of networking ports. The additional server rack can include one or more server devices, which can be different from the server devices of the reduced footprint server racks.

[0080] At block 708, a computing device of the additional server rack can be provisioned to host a portion of a data plane of the cloud service. The computing device of the additional server rack can be provisioned by a provisioning service configured to provision infrastructure components (e.g., setup and configure bare metal devices, virtual devices, etc.) and deploy software resources to those infrastructure components. The provisioning service itself may be hosted in a data center of a CSP that is operating at a different location than the reduced footprint data center.

[0081] In some embodiments, a second computing device of the additional server rack can be provisioned with infrastructure components configured to host an additional cloud service. For example, the CSP may implement another service on resources available in the reduced footprint data center, including resources of the additional server rack. The additional cloud service can be deployed to the second computing device. In some embodiments, deploying the additional cloud service can include deploying a cloud service control plane to the infrastructure components of the second computing device.

[0082] FIG.8 is a flow diagram of an example process 800 for a reduced footprint data center to a large footprint, according to some embodiments. The process 800 can be performed bycomponents of the reduced footprint data center (e.g., reduced footprint data center 600 of FIG. 6).

[0083] The process 800 can begin at block 802 by implementing an optical networking device (e.g., optical rack 620 of FIG.6) at the data center. Implementing the optical networking device can include receiving an indication that the optical networking device has been installed at the data center and configuring the optical networking device to connect to the networking device.

[0084] At block 804, the optical networking device can be connected to a networking device (e.g., networking rack 506 of FIG.5) of the data center. The networking device can be connected to a plurality of reduced footprint server racks (e.g., reduced footprint server racks 502 of FIG. 5). The plurality of reduced footprint server racks can host a cloud service (or a plurality of core cloud services). The plurality of reduced footprint server racks can be connected in a ring network.

[0085] At block 806, an additional server rack (e.g., one of additional racks 622) can be connected to the optical networking device. The additional server rack can be different from the server racks added to the data center when scaling from the reduced footprint server racks to a "Medium" footprint reduced footprint data center.

[0086] At block 808, a computing device of the additional server rack can be provisioned to host a portion of a data plane of the cloud service. For example, a core cloud service can have its data plane expanded to use newly available resources in the additional server rack.

[0087] With the additional resources of the additional server rack, the expanding data center can add additional functionality. In some embodiments, a high-throughput networking device can be connected to the to the optical networking device and a high-capacity server rack can be connected to the high-throughput networking device. The high-capacity server rack can be configured to host a high-capacity database service at the high-capacity server rack.

[0088] In some embodiments, a second computing device of the additional server rack can be provisioned with infrastructure components configured to host an additional cloud service. For example, the CSP may implement another service on resources available in the reduced footprint data center, including resources of the additional server rack. The additional cloud service can be deployed to the second computing device. In some embodiments, deploying the additional cloudservice can include deploying a cloud service control plane to the infrastructure components of the second computing device. Example Infrastructure as a Service Architectures

[0089] As noted above, infrastructure as a service (IaaS) is one particular type of cloud computing. IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In an IaaS model, a cloud computing provider can host the infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., a hypervisor layer), or the like). In some cases, an IaaS provider may also supply a variety of services to accompany those infrastructure components (example services include billing software, monitoring software, logging software, load balancing software, clustering software, etc.). Thus, as these services may be policy-driven, IaaS users may be able to implement policies to drive load balancing to maintain application availability and performance.

[0090] In some instances, IaaS customers may access resources and services through a wide area network (WAN), such as the Internet, and can use the cloud provider's services to install the remaining elements of an application stack. For example, the user can log in to the IaaS platform to create virtual machines (VMs), install operating systems (OSs) on each VM, deploy middleware such as databases, create storage buckets for workloads and backups, and even install enterprise software into that VM. Customers can then use the provider's services to perform various functions, including balancing network traffic, troubleshooting application issues, monitoring performance, managing disaster recovery, etc.

[0091] In most cases, a cloud computing model may require the participation of a cloud provider. The cloud provider may, but need not be, a third-party service that specializes in providing (e.g., offering, renting, selling) IaaS. An entity might also opt to deploy a private cloud, becoming its own provider of infrastructure services.

[0092] In some examples, IaaS deployment is the process of putting a new application, or a new version of an application, onto a prepared application server or the like. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed by the cloud provider, below the hypervisor layer (e.g., the servers, storage, networkhardware, and virtualization). Thus, the customer may be responsible for handling (OS), middleware, and / or application deployment (e.g., on self-service virtual machines (e.g., that can be spun up on demand)) or the like.

[0093] In some examples, IaaS provisioning may refer to acquiring computers or virtual hosts for use, and even installing needed libraries or services on them. In most cases, deployment does not include provisioning, and the provisioning may need to be performed first.

[0094] In some cases, there are two different challenges for IaaS provisioning. First, there is the initial challenge of provisioning the initial set of infrastructure before anything is running. Second, there is the challenge of evolving the existing infrastructure (e.g., adding new services, changing services, removing services, etc.) once everything has been provisioned. In some cases, these two challenges may be addressed by enabling the configuration of the infrastructure to be defined declaratively. In other words, the infrastructure (e.g., what components are needed and how they interact) can be defined by one or more configuration files. Thus, the overall topology of the infrastructure (e.g., what resources depend on which, and how they each work together) can be described declaratively. In some instances, once the topology is defined, a workflow can be generated that creates and / or manages the different components described in the configuration files.

[0095] In some examples, an infrastructure may have many interconnected elements. For example, there may be one or more virtual private clouds (VPCs) (e.g., a potentially on-demand pool of configurable and / or shared computing resources), also known as a core network. In some examples, there may also be one or more inbound / outbound traffic group rules provisioned to define how the inbound and / or outbound traffic of the network will be set up and one or more virtual machines (VMs). Other infrastructure elements may also be provisioned, such as a load balancer, a database, or the like. As more and more infrastructure elements are desired and / or added, the infrastructure may incrementally evolve.

[0096] In some instances, continuous deployment techniques may be employed to enable deployment of infrastructure code across various virtual computing environments. Additionally, the described techniques can enable infrastructure management within these environments. In some examples, service teams can write code that is desired to be deployed to one or more, but often many, different production environments (e.g., across various different geographiclocations, sometimes spanning the entire world). However, in some examples, the infrastructure on which the code will be deployed may need to first be set up. In some instances, the provisioning can be done manually, a provisioning tool may be utilized to provision the resources, and / or deployment tools may be utilized to deploy the code once the infrastructure is provisioned.

[0097] FIG.9 is a block diagram 900 illustrating an example pattern of an IaaS architecture, according to at least one embodiment. Service operators 902 can be communicatively coupled to a secure host tenancy 904 that can include a virtual cloud network (VCN) 906 and a secure host subnet 908. In some examples, the service operators 902 may be using one or more client computing devices, which may be portable handheld devices (e.g., an iPhone®, cellular telephone, an iPad®, computing tablet, a personal digital assistant (PDA)) or wearable devices (e.g., a Google Glass® head mounted display), running software such as Microsoft Windows Mobile®, and / or a variety of mobile operating systems such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, and the like, and being Internet, e-mail, short message service (SMS), Blackberry®, or other communication protocol enabled. Alternatively, the client computing devices can be general purpose personal computers including, by way of example, personal computers and / or laptop computers running various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux operating systems. The client computing devices can be workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems, including without limitation the variety of GNU / Linux operating systems, such as for example, Google Chrome OS. Alternatively, or in addition, client computing devices may be any other electronic device, such as a thin-client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and / or a personal messaging device, capable of communicating over a network that can access the VCN 906 and / or the Internet.

[0098] The VCN 906 can include a local peering gateway (LPG) 910 that can be communicatively coupled to a secure shell (SSH) VCN 912 via an LPG 910 contained in the SSH VCN 912. The SSH VCN 912 can include an SSH subnet 914, and the SSH VCN 912 can be communicatively coupled to a control plane VCN 916 via the LPG 910 contained in the control plane VCN 916. Also, the SSH VCN 912 can be communicatively coupled to a dataplane VCN 918 via an LPG 910. The control plane VCN 916 and the data plane VCN 918 can be contained in a service tenancy 919 that can be owned and / or operated by the IaaS provider.

[0099] The control plane VCN 916 can include a control plane demilitarized zone (DMZ) tier 920 that acts as a perimeter network (e.g., portions of a corporate network between the corporate intranet and external networks). The DMZ-based servers may have restricted responsibilities and help keep breaches contained. Additionally, the DMZ tier 920 can include one or more load balancer (LB) subnet(s) 922, a control plane app tier 924 that can include app subnet(s) 926, a control plane data tier 928 that can include database (DB) subnet(s) 930 (e.g., frontend DB subnet(s) and / or backend DB subnet(s)). The LB subnet(s) 922 contained in the control plane DMZ tier 920 can be communicatively coupled to the app subnet(s) 926 contained in the control plane app tier 924 and an Internet gateway 934 that can be contained in the control plane VCN 916, and the app subnet(s) 926 can be communicatively coupled to the DB subnet(s) 930 contained in the control plane data tier 928 and a service gateway 936 and a network address translation (NAT) gateway 938. The control plane VCN 916 can include the service gateway 936 and the NAT gateway 938.

[0100] The control plane VCN 916 can include a data plane mirror app tier 940 that can include app subnet(s) 926. The app subnet(s) 926 contained in the data plane mirror app tier 940 can include a virtual network interface controller (VNIC) 942 that can execute a compute instance 944. The compute instance 944 can communicatively couple the app subnet(s) 926 of the data plane mirror app tier 940 to app subnet(s) 926 that can be contained in a data plane app tier 946.

[0101] The data plane VCN 918 can include the data plane app tier 946, a data plane DMZ tier 948, and a data plane data tier 950. The data plane DMZ tier 948 can include LB subnet(s) 922 that can be communicatively coupled to the app subnet(s) 926 of the data plane app tier 946 and the Internet gateway 934 of the data plane VCN 918. The app subnet(s) 926 can be communicatively coupled to the service gateway 936 of the data plane VCN 918 and the NAT gateway 938 of the data plane VCN 918. The data plane data tier 950 can also include the DB subnet(s) 930 that can be communicatively coupled to the app subnet(s) 926 of the data plane app tier 946.

[0102] The Internet gateway 934 of the control plane VCN 916 and of the data plane VCN 918 can be communicatively coupled to a metadata management service 952 that can be communicatively coupled to public Internet 954. Public Internet 954 can be communicatively coupled to the NAT gateway 938 of the control plane VCN 916 and of the data plane VCN 918. The service gateway 936 of the control plane VCN 916 and of the data plane VCN 918 can be communicatively coupled to cloud services 956.

[0103] In some examples, the service gateway 936 of the control plane VCN 916 or of the data plane VCN 918 can make application programming interface (API) calls to cloud services 956 without going through public Internet 954. The API calls to cloud services 956 from the service gateway 936 can be one-way: the service gateway 936 can make API calls to cloud services 956, and cloud services 956 can send requested data to the service gateway 936. But, cloud services 956 may not initiate API calls to the service gateway 936.

[0104] In some examples, the secure host tenancy 904 can be directly connected to the service tenancy 919, which may be otherwise isolated. The secure host subnet 908 can communicate with the SSH subnet 914 through an LPG 910 that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet 908 to the SSH subnet 914 may give the secure host subnet 908 access to other entities within the service tenancy 919.

[0105] The control plane VCN 916 may allow users of the service tenancy 919 to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN 916 may be deployed or otherwise used in the data plane VCN 918. In some examples, the control plane VCN 916 can be isolated from the data plane VCN 918, and the data plane mirror app tier 940 of the control plane VCN 916 can communicate with the data plane app tier 946 of the data plane VCN 918 via VNICs 942 that can be contained in the data plane mirror app tier 940 and the data plane app tier 946.

[0106] In some examples, users of the system, or customers, can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet 954 that can communicate the requests to the metadata management service 952. The metadata management service 952 can communicate the request to the control plane VCN 916 through the Internet gateway 934. The request can be received by the LB subnet(s) 922 contained in the control plane DMZ tier 920. The LB subnet(s) 922 may determine that the request is valid, and in response tothis determination, the LB subnet(s) 922 can transmit the request to app subnet(s) 926 contained in the control plane app tier 924. If the request is validated and requires a call to public Internet 954, the call to public Internet 954 may be transmitted to the NAT gateway 938 that can make the call to public Internet 954. Metadata that may be desired to be stored by the request can be stored in the DB subnet(s) 930.

[0107] In some examples, the data plane mirror app tier 940 can facilitate direct communication between the control plane VCN 916 and the data plane VCN 918. For example, changes, updates, or other suitable modifications to configuration may be desired to be applied to the resources contained in the data plane VCN 918. Via a VNIC 942, the control plane VCN 916 can directly communicate with, and can thereby execute the changes, updates, or other suitable modifications to configuration to, resources contained in the data plane VCN 918.

[0108] In some embodiments, the control plane VCN 916 and the data plane VCN 918 can be contained in the service tenancy 919. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN 916 or the data plane VCN 918. Instead, the IaaS provider may own or operate the control plane VCN 916 and the data plane VCN 918, both of which may be contained in the service tenancy 919. This embodiment can enable isolation of networks that may prevent users or customers from interacting with other users’, or other customers’, resources. Also, this embodiment may allow users or customers of the system to store databases privately without needing to rely on public Internet 954, which may not have a desired level of threat prevention, for storage.

[0109] In other embodiments, the LB subnet(s) 922 contained in the control plane VCN 916 can be configured to receive a signal from the service gateway 936. In this embodiment, the control plane VCN 916 and the data plane VCN 918 may be configured to be called by a customer of the IaaS provider without calling public Internet 954. Customers of the IaaS provider may desire this embodiment since database(s) that the customers use may be controlled by the IaaS provider and may be stored on the service tenancy 919, which may be isolated from public Internet 954.

[0110] FIG.10 is a block diagram 1000 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators 1002 (e.g., service operators 902 of FIG.9) can be communicatively coupled to a secure host tenancy 1004 (e.g., thesecure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1006 (e.g., the VCN 906 of FIG.9) and a secure host subnet 1008 (e.g., the secure host subnet 908 of FIG. 9). The VCN 1006 can include a local peering gateway (LPG) 1010 (e.g., the LPG 910 of FIG. 9) that can be communicatively coupled to a secure shell (SSH) VCN 1012 (e.g., the SSH VCN 912 of FIG.9) via an LPG 910 contained in the SSH VCN 1012. The SSH VCN 1012 can include an SSH subnet 1014 (e.g., the SSH subnet 914 of FIG. 9), and the SSH VCN 1012 can be communicatively coupled to a control plane VCN 1016 (e.g., the control plane VCN 916 of FIG. 9) via an LPG 1010 contained in the control plane VCN 1016. The control plane VCN 1016 can be contained in a service tenancy 1019 (e.g., the service tenancy 919 of FIG.9), and the data plane VCN 1018 (e.g., the data plane VCN 918 of FIG.9) can be contained in a customer tenancy 1021 that may be owned or operated by users, or customers, of the system.

[0111] The control plane VCN 1016 can include a control plane DMZ tier 1020 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include LB subnet(s) 1022 (e.g., LB subnet(s) 922 of FIG.9), a control plane app tier 1024 (e.g., the control plane app tier 924 of FIG. 9) that can include app subnet(s) 1026 (e.g., app subnet(s) 926 of FIG.9), a control plane data tier 1028 (e.g., the control plane data tier 928 of FIG.9) that can include database (DB) subnet(s) 1030 (e.g., similar to DB subnet(s) 930 of FIG.9). The LB subnet(s) 1022 contained in the control plane DMZ tier 1020 can be communicatively coupled to the app subnet(s) 1026 contained in the control plane app tier 1024 and an Internet gateway 1034 (e.g., the Internet gateway 934 of FIG. 9) that can be contained in the control plane VCN 1016, and the app subnet(s) 1026 can be communicatively coupled to the DB subnet(s) 1030 contained in the control plane data tier 1028 and a service gateway 1036 (e.g., the service gateway 936 of FIG.9) and a network address translation (NAT) gateway 1038 (e.g., the NAT gateway 938 of FIG. 9). The control plane VCN 1016 can include the service gateway 1036 and the NAT gateway 1038.

[0112] The control plane VCN 1016 can include a data plane mirror app tier 1040 (e.g., the data plane mirror app tier 940 of FIG.9) that can include app subnet(s) 1026. The app subnet(s) 1026 contained in the data plane mirror app tier 1040 can include a virtual network interface controller (VNIC) 1042 (e.g., the VNIC of 942) that can execute a compute instance 1044 (e.g., similar to the compute instance 944 of FIG.9). The compute instance 1044 can facilitate communication between the app subnet(s) 1026 of the data plane mirror app tier 1040 and theapp subnet(s) 1026 that can be contained in a data plane app tier 1046 (e.g., the data plane app tier 946 of FIG. 9) via the VNIC 1042 contained in the data plane mirror app tier 1040 and the VNIC 1042 contained in the data plane app tier 1046.

[0113] The Internet gateway 1034 contained in the control plane VCN 1016 can be communicatively coupled to a metadata management service 1052 (e.g., the metadata management service 952 of FIG.9) that can be communicatively coupled to public Internet 1054 (e.g., public Internet 954 of FIG. 9). Public Internet 1054 can be communicatively coupled to the NAT gateway 1038 contained in the control plane VCN 1016. The service gateway 1036 contained in the control plane VCN 1016 can be communicatively coupled to cloud services 1056 (e.g., cloud services 956 of FIG.9).

[0114] In some examples, the data plane VCN 1018 can be contained in the customer tenancy 1021. In this case, the IaaS provider may provide the control plane VCN 1016 for each customer, and the IaaS provider may, for each customer, set up a unique compute instance 1044 that is contained in the service tenancy 1019. Each compute instance 1044 may allow communication between the control plane VCN 1016, contained in the service tenancy 1019, and the data plane VCN 1018 that is contained in the customer tenancy 1021. The compute instance 1044 may allow resources, that are provisioned in the control plane VCN 1016 that is contained in the service tenancy 1019, to be deployed or otherwise used in the data plane VCN 1018 that is contained in the customer tenancy 1021.

[0115] In other examples, the customer of the IaaS provider may have databases that live in the customer tenancy 1021. In this example, the control plane VCN 1016 can include the data plane mirror app tier 1040 that can include app subnet(s) 1026. The data plane mirror app tier 1040 can reside in the data plane VCN 1018, but the data plane mirror app tier 1040 may not live in the data plane VCN 1018. That is, the data plane mirror app tier 1040 may have access to the customer tenancy 1021, but the data plane mirror app tier 1040 may not exist in the data plane VCN 1018 or be owned or operated by the customer of the IaaS provider. The data plane mirror app tier 1040 may be configured to make calls to the data plane VCN 1018 but may not be configured to make calls to any entity contained in the control plane VCN 1016. The customer may desire to deploy or otherwise use resources in the data plane VCN 1018 that are provisionedin the control plane VCN 1016, and the data plane mirror app tier 1040 can facilitate the desired deployment, or other usage of resources, of the customer.

[0116] In some embodiments, the customer of the IaaS provider can apply filters to the data plane VCN 1018. In this embodiment, the customer can determine what the data plane VCN 1018 can access, and the customer may restrict access to public Internet 1054 from the data plane VCN 1018. The IaaS provider may not be able to apply filters or otherwise control access of the data plane VCN 1018 to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN 1018, contained in the customer tenancy 1021, can help isolate the data plane VCN 1018 from other customers and from public Internet 1054.

[0117] In some embodiments, cloud services 1056 can be called by the service gateway 1036 to access services that may not exist on public Internet 1054, on the control plane VCN 1016, or on the data plane VCN 1018. The connection between cloud services 1056 and the control plane VCN 1016 or the data plane VCN 1018 may not be live or continuous. Cloud services 1056 may exist on a different network owned or operated by the IaaS provider. Cloud services 1056 may be configured to receive calls from the service gateway 1036 and may be configured to not receive calls from public Internet 1054. Some cloud services 1056 may be isolated from other cloud services 1056, and the control plane VCN 1016 may be isolated from cloud services 1056 that may not be in the same region as the control plane VCN 1016. For example, the control plane VCN 1016 may be located in "Region 1," and cloud service "Deployment 9," may be located in Region 1 and in "Region 2." If a call to Deployment 9 is made by the service gateway 1036 contained in the control plane VCN 1016 located in Region 1, the call may be transmitted to Deployment 9 in Region 1. In this example, the control plane VCN 1016, or Deployment 9 in Region 1, may not be communicatively coupled to, or otherwise in communication with, Deployment 9 in Region 2.

[0118] FIG.11 is a block diagram 1100 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators 1102 (e.g., service operators 902 of FIG.9) can be communicatively coupled to a secure host tenancy 1104 (e.g., the secure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1106 (e.g., the VCN 906 of FIG.9) and a secure host subnet 1108 (e.g., the secure host subnet 908 of FIG. 9). The VCN 1106 can include an LPG 1110 (e.g., the LPG 910 of FIG.9) that can becommunicatively coupled to an SSH VCN 1112 (e.g., the SSH VCN 912 of FIG. 9) via an LPG 1110 contained in the SSH VCN 1112. The SSH VCN 1112 can include an SSH subnet 1114 (e.g., the SSH subnet 914 of FIG.9), and the SSH VCN 1112 can be communicatively coupled to a control plane VCN 1116 (e.g., the control plane VCN 916 of FIG.9) via an LPG 1110 contained in the control plane VCN 1116 and to a data plane VCN 1118 (e.g., the data plane 918 of FIG.9) via an LPG 1110 contained in the data plane VCN 1118. The control plane VCN 1116 and the data plane VCN 1118 can be contained in a service tenancy 1119 (e.g., the service tenancy 919 of FIG.9).

[0119] The control plane VCN 1116 can include a control plane DMZ tier 1120 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include load balancer (LB) subnet(s) 1122 (e.g., LB subnet(s) 922 of FIG.9), a control plane app tier 1124 (e.g., the control plane app tier 924 of FIG.9) that can include app subnet(s) 1126 (e.g., similar to app subnet(s) 926 of FIG.9), a control plane data tier 1128 (e.g., the control plane data tier 928 of FIG.9) that can include DB subnet(s) 1130. The LB subnet(s) 1122 contained in the control plane DMZ tier 1120 can be communicatively coupled to the app subnet(s) 1126 contained in the control plane app tier 1124 and to an Internet gateway 1134 (e.g., the Internet gateway 934 of FIG. 9) that can be contained in the control plane VCN 1116, and the app subnet(s) 1126 can be communicatively coupled to the DB subnet(s) 1130 contained in the control plane data tier 1128 and to a service gateway 1136 (e.g., the service gateway of FIG. 9) and a network address translation (NAT) gateway 1138 (e.g., the NAT gateway 938 of FIG.9). The control plane VCN 1116 can include the service gateway 1136 and the NAT gateway 1138.

[0120] The data plane VCN 1118 can include a data plane app tier 1146 (e.g., the data plane app tier 946 of FIG.9), a data plane DMZ tier 1148 (e.g., the data plane DMZ tier 948 of FIG. 9), and a data plane data tier 1150 (e.g., the data plane data tier 950 of FIG. 9). The data plane DMZ tier 1148 can include LB subnet(s) 1122 that can be communicatively coupled to trusted app subnet(s) 1160 and untrusted app subnet(s) 1162 of the data plane app tier 1146 and the Internet gateway 1134 contained in the data plane VCN 1118. The trusted app subnet(s) 1160 can be communicatively coupled to the service gateway 1136 contained in the data plane VCN 1118, the NAT gateway 1138 contained in the data plane VCN 1118, and DB subnet(s) 1130 contained in the data plane data tier 1150. The untrusted app subnet(s) 1162 can becommunicatively coupled to the service gateway 1136 contained in the data plane VCN 1118 and DB subnet(s) 1130 contained in the data plane data tier 1150. The data plane data tier 1150 can include DB subnet(s) 1130 that can be communicatively coupled to the service gateway 1136 contained in the data plane VCN 1118.

[0121] The untrusted app subnet(s) 1162 can include one or more primary VNICs 1164(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1166(1)-(N). Each tenant VM 1166(1)-(N) can be communicatively coupled to a respective app subnet 1167(1)-(N) that can be contained in respective container egress VCNs 1168(1)-(N) that can be contained in respective customer tenancies 1170(1)-(N). Respective secondary VNICs 1172(1)-(N) can facilitate communication between the untrusted app subnet(s) 1162 contained in the data plane VCN 1118 and the app subnet contained in the container egress VCNs 1168(1)-(N). Each container egress VCNs 1168(1)-(N) can include a NAT gateway 1138 that can be communicatively coupled to public Internet 1154 (e.g., public Internet 954 of FIG.9).

[0122] The Internet gateway 1134 contained in the control plane VCN 1116 and contained in the data plane VCN 1118 can be communicatively coupled to a metadata management service 1152 (e.g., the metadata management system 952 of FIG.9) that can be communicatively coupled to public Internet 1154. Public Internet 1154 can be communicatively coupled to the NAT gateway 1138 contained in the control plane VCN 1116 and contained in the data plane VCN 1118. The service gateway 1136 contained in the control plane VCN 1116 and contained in the data plane VCN 1118 can be communicatively coupled to cloud services 1156.

[0123] In some embodiments, the data plane VCN 1118 can be integrated with customer tenancies 1170. This integration can be useful or desirable for customers of the IaaS provider in some cases such as a case that may desire support when executing code. The customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects. In response to this, the IaaS provider may determine whether to run code given to the IaaS provider by the customer.

[0124] In some examples, the customer of the IaaS provider may grant temporary network access to the IaaS provider and request a function to be attached to the data plane app tier 1146. Code to run the function may be executed in the VMs 1166(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN 1118. Each VM 1166(1)-(N) may beconnected to one customer tenancy 1170. Respective containers 1171(1)-(N) contained in the VMs 1166(1)-(N) may be configured to run the code. In this case, there can be a dual isolation (e.g., the containers 1171(1)-(N) running code, where the containers 1171(1)-(N) may be contained in at least the VM 1166(1)-(N) that are contained in the untrusted app subnet(s) 1162), which may help prevent incorrect or otherwise undesirable code from damaging the network of the IaaS provider or from damaging a network of a different customer. The containers 1171(1)- (N) may be communicatively coupled to the customer tenancy 1170 and may be configured to transmit or receive data from the customer tenancy 1170. The containers 1171(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN 1118. Upon completion of running the code, the IaaS provider may kill or otherwise dispose of the containers 1171(1)-(N).

[0125] In some embodiments, the trusted app subnet(s) 1160 may run code that may be owned or operated by the IaaS provider. In this embodiment, the trusted app subnet(s) 1160 may be communicatively coupled to the DB subnet(s) 1130 and be configured to execute CRUD operations in the DB subnet(s) 1130. The untrusted app subnet(s) 1162 may be communicatively coupled to the DB subnet(s) 1130, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s) 1130. The containers 1171(1)-(N) that can be contained in the VM 1166(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s) 1130.

[0126] In other embodiments, the control plane VCN 1116 and the data plane VCN 1118 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 1116 and the data plane VCN 1118. However, communication can occur indirectly through at least one method. An LPG 1110 may be established by the IaaS provider that can facilitate communication between the control plane VCN 1116 and the data plane VCN 1118. In another example, the control plane VCN 1116 or the data plane VCN 1118 can make a call to cloud services 1156 via the service gateway 1136. For example, a call to cloud services 1156 from the control plane VCN 1116 can include a request for a service that can communicate with the data plane VCN 1118.

[0127] FIG.12 is a block diagram 1200 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. Service operators 1202 (e.g., serviceoperators 902 of FIG.9) can be communicatively coupled to a secure host tenancy 1204 (e.g., the secure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1206 (e.g., the VCN 906 of FIG.9) and a secure host subnet 1208 (e.g., the secure host subnet 908 of FIG. 9). The VCN 1206 can include an LPG 1210 (e.g., the LPG 910 of FIG.9) that can be communicatively coupled to an SSH VCN 1212 (e.g., the SSH VCN 912 of FIG. 9) via an LPG 1210 contained in the SSH VCN 1212. The SSH VCN 1212 can include an SSH subnet 1214 (e.g., the SSH subnet 914 of FIG.9), and the SSH VCN 1212 can be communicatively coupled to a control plane VCN 1216 (e.g., the control plane VCN 916 of FIG.9) via an LPG 1210 contained in the control plane VCN 1216 and to a data plane VCN 1218 (e.g., the data plane 918 of FIG.9) via an LPG 1210 contained in the data plane VCN 1218. The control plane VCN 1216 and the data plane VCN 1218 can be contained in a service tenancy 1219 (e.g., the service tenancy 919 of FIG.9).

[0128] The control plane VCN 1216 can include a control plane DMZ tier 1220 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include LB subnet(s) 1222 (e.g., LB subnet(s) 922 of FIG.9), a control plane app tier 1224 (e.g., the control plane app tier 924 of FIG. 9) that can include app subnet(s) 1226 (e.g., app subnet(s) 926 of FIG.9), a control plane data tier 1228 (e.g., the control plane data tier 928 of FIG.9) that can include DB subnet(s) 1230 (e.g., DB subnet(s) 1130 of FIG. 11). The LB subnet(s) 1222 contained in the control plane DMZ tier 1220 can be communicatively coupled to the app subnet(s) 1226 contained in the control plane app tier 1224 and to an Internet gateway 1234 (e.g., the Internet gateway 934 of FIG.9) that can be contained in the control plane VCN 1216, and the app subnet(s) 1226 can be communicatively coupled to the DB subnet(s) 1230 contained in the control plane data tier 1228 and to a service gateway 1236 (e.g., the service gateway of FIG. 9) and a network address translation (NAT) gateway 1238 (e.g., the NAT gateway 938 of FIG.9). The control plane VCN 1216 can include the service gateway 1236 and the NAT gateway 1238.

[0129] The data plane VCN 1218 can include a data plane app tier 1246 (e.g., the data plane app tier 946 of FIG.9), a data plane DMZ tier 1248 (e.g., the data plane DMZ tier 948 of FIG. 9), and a data plane data tier 1250 (e.g., the data plane data tier 950 of FIG. 9). The data plane DMZ tier 1248 can include LB subnet(s) 1222 that can be communicatively coupled to trusted app subnet(s) 1260 (e.g., trusted app subnet(s) 1160 of FIG.11) and untrusted app subnet(s)1262 (e.g., untrusted app subnet(s) 1162 of FIG. 11) of the data plane app tier 1246 and the Internet gateway 1234 contained in the data plane VCN 1218. The trusted app subnet(s) 1260 can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218, the NAT gateway 1238 contained in the data plane VCN 1218, and DB subnet(s) 1230 contained in the data plane data tier 1250. The untrusted app subnet(s) 1262 can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218 and DB subnet(s) 1230 contained in the data plane data tier 1250. The data plane data tier 1250 can include DB subnet(s) 1230 that can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218.

[0130] The untrusted app subnet(s) 1262 can include primary VNICs 1264(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1266(1)-(N) residing within the untrusted app subnet(s) 1262. Each tenant VM 1266(1)-(N) can run code in a respective container 1267(1)-(N), and be communicatively coupled to an app subnet 1226 that can be contained in a data plane app tier 1246 that can be contained in a container egress VCN 1268. Respective secondary VNICs 1272(1)-(N) can facilitate communication between the untrusted app subnet(s) 1262 contained in the data plane VCN 1218 and the app subnet contained in the container egress VCN 1268. The container egress VCN can include a NAT gateway 1238 that can be communicatively coupled to public Internet 1254 (e.g., public Internet 954 of FIG.9).

[0131] The Internet gateway 1234 contained in the control plane VCN 1216 and contained in the data plane VCN 1218 can be communicatively coupled to a metadata management service 1252 (e.g., the metadata management system 952 of FIG.9) that can be communicatively coupled to public Internet 1254. Public Internet 1254 can be communicatively coupled to the NAT gateway 1238 contained in the control plane VCN 1216 and contained in the data plane VCN 1218. The service gateway 1236 contained in the control plane VCN 1216 and contained in the data plane VCN 1218 can be communicatively coupled to cloud services 1256.

[0132] In some examples, the pattern illustrated by the architecture of block diagram 1200 of FIG.12 may be considered an exception to the pattern illustrated by the architecture of block diagram 1100 of FIG.11 and may be desirable for a customer of the IaaS provider if the IaaS provider cannot directly communicate with the customer (e.g., a disconnected region). The respective containers 1267(1)-(N) that are contained in the VMs 1266(1)-(N) for each customercan be accessed in real-time by the customer. The containers 1267(1)-(N) may be configured to make calls to respective secondary VNICs 1272(1)-(N) contained in app subnet(s) 1226 of the data plane app tier 1246 that can be contained in the container egress VCN 1268. The secondary VNICs 1272(1)-(N) can transmit the calls to the NAT gateway 1238 that may transmit the calls to public Internet 1254. In this example, the containers 1267(1)-(N) that can be accessed in real- time by the customer can be isolated from the control plane VCN 1216 and can be isolated from other entities contained in the data plane VCN 1218. The containers 1267(1)-(N) may also be isolated from resources from other customers.

[0133] In other examples, the customer can use the containers 1267(1)-(N) to call cloud services 1256. In this example, the customer may run code in the containers 1267(1)-(N) that requests a service from cloud services 1256. The containers 1267(1)-(N) can transmit this request to the secondary VNICs 1272(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet 1254. Public Internet 1254 can transmit the request to LB subnet(s) 1222 contained in the control plane VCN 1216 via the Internet gateway 1234. In response to determining the request is valid, the LB subnet(s) can transmit the request to app subnet(s) 1226 that can transmit the request to cloud services 1256 via the service gateway 1236.

[0134] It should be appreciated that IaaS architectures 900, 1000, 1100, 1200 depicted in the figures may have other components than those depicted. Further, the embodiments shown in the figures are only some examples of a cloud infrastructure system that may incorporate an embodiment of the disclosure. In some other embodiments, the IaaS systems may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration or arrangement of components.

[0135] In certain embodiments, the IaaS systems described herein may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. An example of such an IaaS system is the Oracle Cloud Infrastructure (OCI) provided by the present assignee.

[0136] FIG.13 illustrates an example computer system 1300, in which various embodiments may be implemented. The system 1300 may be used to implement any of the computer systems described above. As shown in the figure, computer system 1300 includes a processing unit 1304that communicates with a number of peripheral subsystems via a bus subsystem 1302. These peripheral subsystems may include a processing acceleration unit 1306, an I / O subsystem 1308, a storage subsystem 1318 and a communications subsystem 1324. Storage subsystem 1318 includes tangible computer-readable storage media 1322 and a system memory 1310.

[0137] Bus subsystem 1302 provides a mechanism for letting the various components and subsystems of computer system 1300 communicate with each other as intended. Although bus subsystem 1302 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1302 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.

[0138] Processing unit 1304, which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 1300. One or more processors may be included in processing unit 1304. These processors may include single core or multicore processors. In certain embodiments, processing unit 1304 may be implemented as one or more independent processing units 1332 and / or 1334 with single or multicore processors included in each processing unit. In other embodiments, processing unit 1304 may also be implemented as a quad-core processing unit formed by integrating two dual- core processors into a single chip.

[0139] In various embodiments, processing unit 1304 can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processor(s) 1304 and / or in storage subsystem 1318. Through suitable programming, processor(s) 1304 can provide various functionalities described above. Computer system 1300 may additionally include a processing acceleration unit 1306, which can include a digital signal processor (DSP), a special-purpose processor, and / or the like.

[0140] I / O subsystem 1308 may include user interface input devices and user interface output devices. User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and / or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands. User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and / or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.

[0141] User interface input devices may also include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio / visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices. Additionally, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasonography devices. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.

[0142] User interface output devices may include a display subsystem, indicator lights, or non- visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like. In general, use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from computer system 1300 to a user or other computer. For example, user interface output devices may include, without limitation, a variety of display devices that visually conveytext, graphics and audio / video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.

[0143] Computer system 1300 may comprise a storage subsystem 1318 that provides a tangible non-transitory computer-readable storage medium for storing software and data constructs that provide the functionality of the embodiments described in this disclosure. The software can include programs, code, instructions, scripts, etc., that when executed by one or more cores or processors of processing unit 1304 provide the functionality described above. Storage subsystem 1318 may also provide a repository for storing data used in accordance with the present disclosure.

[0144] As depicted in the example in FIG. 13, storage subsystem 1318 can include various components including a system memory 1310, computer-readable storage media 1322, and a computer readable storage media reader 1320. System memory 1310 may store program instructions that are loadable and executable by processing unit 1304. System memory 1310 may also store data that is used during the execution of the instructions and / or data that is generated during the execution of the program instructions. Various different kinds of programs may be loaded into system memory 1310 including but not limited to client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), virtual machines, containers, etc.

[0145] System memory 1310 may also store an operating system 1316. Examples of operating system 1316 may include various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux operating systems, a variety of commercially-available UNIX® or UNIX-like operating systems (including without limitation the variety of GNU / Linux operating systems, the Google Chrome® OS, and the like) and / or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® OS, and Palm® OS operating systems. In certain implementations where computer system 1300 executes one or more virtual machines, the virtual machines along with their guest operating systems (GOSs) may be loaded into system memory 1310 and executed by one or more processors or cores of processing unit 1304.

[0146] System memory 1310 can come in different configurations depending upon the type of computer system 1300. For example, system memory 1310 may be volatile memory (such as random access memory (RAM)) and / or non-volatile memory (such as read-only memory(ROM), flash memory, etc.) Different types of RAM configurations may be provided including a static random access memory (SRAM), a dynamic random access memory (DRAM), and others. In some implementations, system memory 1310 may include a basic input / output system (BIOS) containing basic routines that help to transfer information between elements within computer system 1300, such as during start-up.

[0147] Computer-readable storage media 1322 may represent remote, local, fixed, and / or removable storage devices plus storage media for temporarily and / or more permanently containing, storing, computer-readable information for use by computer system 1300 including instructions executable by processing unit 1304 of computer system 1300.

[0148] Computer-readable storage media 1322 can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and / or transmission of information. This can include tangible computer- readable storage media such as RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media.

[0149] By way of example, computer-readable storage media 1322 may include a hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive that reads from or writes to a removable, nonvolatile magnetic disk, and an optical disk drive that reads from or writes to a removable, nonvolatile optical disk such as a CD ROM, DVD, and Blu-Ray® disk, or other optical media. Computer-readable storage media 1322 may include, but is not limited to, Zip® drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tape, and the like. Computer-readable storage media 1322 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs. The disk drives and their associated computer-readablemedia may provide non-volatile storage of computer-readable instructions, data structures, program services, and other data for computer system 1300.

[0150] Machine-readable instructions executable by one or more processors or cores of processing unit 1304 may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium can include physically tangible memory or storage devices that include volatile memory storage devices and / or non-volatile storage devices. Examples of non-transitory computer-readable storage medium include magnetic storage media (e.g., disk or tapes), optical storage media (e.g., DVDs, CDs), various types of RAM, ROM, or flash memory, hard drives, floppy drives, detachable memory drives (e.g., USB drives), or other type of storage device.

[0151] Communications subsystem 1324 provides an interface to other computer systems and networks. Communications subsystem 1324 serves as an interface for receiving data from and transmitting data to other systems from computer system 1300. For example, communications subsystem 1324 may enable computer system 1300 to connect to one or more devices via the Internet. In some embodiments communications subsystem 1324 can include radio frequency (RF) transceiver components for accessing wireless voice and / or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.11 family standards, or other mobile communication technologies, or any combination thereof)), global positioning system (GPS) receiver components, and / or other components. In some embodiments communications subsystem 1324 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.

[0152] In some embodiments, communications subsystem 1324 may also receive input communication in the form of structured and / or unstructured data feeds 1326, event streams 1328, event updates 1330, and the like on behalf of one or more users who may use computer system 1300.

[0153] By way of example, communications subsystem 1324 may be configured to receive data feeds 1326 in real-time from users of social networks and / or other communication services such as Twitter® feeds, Facebook® updates, web feeds such as Rich Site Summary (RSS) feeds, and / or real-time updates from one or more third party information sources.

[0154] Additionally, communications subsystem 1324 may also be configured to receive data in the form of continuous data streams, which may include event streams 1328 of real-time events and / or event updates 1330, that may be continuous or unbounded in nature with no explicit end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.

[0155] Communications subsystem 1324 may also be configured to output the structured and / or unstructured data feeds 1326, event streams 1328, event updates 1330, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system 1300.

[0156] Computer system 1300 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.

[0157] Due to the ever-changing nature of computers and networks, the description of computer system 1300 depicted in the figure is intended only as a specific example. Many other configurations having more or fewer components than the system depicted in the figure are possible. For example, customized hardware might also be used and / or particular elements might be implemented in hardware, firmware, software (including applets), or a combination. Further, connection to other computing devices, such as network input / output devices, may be employed. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and / or methods to implement the various embodiments.

[0158] Although specific embodiments have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the disclosure. Embodiments are not restricted to operation within certain specific data processing environments, but are free to operate within a plurality of data processing environments. Additionally, although embodiments have been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of thepresent disclosure is not limited to the described series of transactions and steps. Various features and aspects of the above-described embodiments may be used individually or jointly.

[0159] Further, while embodiments have been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present disclosure. Embodiments may be implemented only in hardware, or only in software, or using combinations thereof. The various processes described herein can be implemented on the same processor or different processors in any combination. Accordingly, where components or services are described as being configured to perform certain operations, such configuration can be accomplished, e.g., by designing electronic circuits to perform the operation, by programming programmable electronic circuits (such as microprocessors) to perform the operation, or any combination thereof. Processes can communicate using a variety of techniques including but not limited to conventional techniques for inter process communication, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times.

[0160] The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope as set forth in the claims. Thus, although specific disclosure embodiments have been described, these are not intended to be limiting. Various modifications and equivalents are within the scope of the following claims.

[0161] The use of the terms "a" and "an" and "the" and similar referents in the context of describing the disclosed embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms "comprising," "having," "including," and "containing" are to be construed as open-ended terms (i.e., meaning "including, but not limited to,") unless otherwise noted. The term "connected" is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein and each separate value is incorporated into the specification as if it were individually recited herein. All methodsdescribed herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., "such as") provided herein, is intended merely to better illuminate embodiments and does not pose a limitation on the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.

[0162] Disjunctive language such as the phrase "at least one of X, Y, or Z," unless specifically stated otherwise, is intended to be understood within the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

[0163] Preferred embodiments of this disclosure are described herein, including the best mode known for carrying out the disclosure. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. Those of ordinary skill should be able to employ such variations as appropriate and the disclosure may be practiced otherwise than as specifically described herein. Accordingly, this disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein.

[0164] All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

[0165] In the foregoing specification, aspects of the disclosure are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the disclosure is not limited thereto. Various features and aspects of the above-described disclosure may be used individually or jointly. Further, embodiments can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive.

Claims

WHAT IS CLAIMED IS:

1. A method for scaling a reduced footprint data center, the method comprising: implementing, at the reduced footprint data center, a networking device comprising a plurality of networking ports; connecting the networking device to a plurality of reduced footprint server racks, the plurality of reduced footprint server racks connected in a ring network and hosting a cloud service, the networking device connected to the plurality of reduced footprint server racks using at least a first networking port of the plurality of networking ports; connecting an additional server rack to the networking device using a second networking port of the plurality of networking ports; and provisioning a computing device of the additional server rack to host a portion of a data plane of the cloud service.

2. The method of claim 1, wherein connecting the networking device to the plurality of reduced footprint server racks further comprises connecting each of the reduced footprint server racks to a corresponding networking port of the plurality of networking ports.

3. The method of claim 1, wherein connecting the networking device to the plurality of reduced footprint server racks preserves the ring network of the reduced footprint server racks.

4. The method of claim 1, wherein the plurality of reduced footprint server racks comprises twelve reduced footprint server racks.

5. The method of claim 1, wherein the plurality of reduced footprint server racks comprises six reduced footprint server racks.

6. The method of claim 1, wherein the computing device is a first computing device, and further comprising: provisioning a second computing device of the additional server rack with infrastructure components configured to host an additional cloud service; and deploying the additional cloud service to the second computing device.

7. The method of claim 6, wherein deploying the additional cloud service comprises deploying a cloud service control plane to the infrastructure components of the second computing device.

8. The method of claim 1, wherein the plurality of reduced footprint server racks further hosts a plurality of core cloud services.

9. A method for scaling a data center comprising a plurality of reduced footprint server racks, the method comprising: implementing, at the data center, an optical networking device; connecting the optical networking device to a networking device of the data center, the networking device connected to a plurality of reduced footprint server racks, the plurality of reduced footprint server racks hosting a cloud service; connecting an additional server rack to the optical networking device; and provisioning a computing device of the additional server rack to host a portion of a data plane of the cloud service.

10. The method of claim 9, further comprising: connecting a high-throughput networking device to the optical networking device; connecting a high-capacity server rack to the high-throughput networking device; and implementing a high-capacity database service at the high-capacity server rack.

11. The method of claim 9, wherein the plurality of reduced footprint server racks are connected in a ring network.

12. The method of claim 9, wherein the plurality of reduced footprint server racks comprise six high density reduced footprint server racks.

13. The method of claim 9, wherein implementing the optical networking device comprises receiving an indication that the optical networking device has been installed at the data center; and configuring the optical networking device to connect to the networking device.

14. The method of claim 9, wherein the plurality of reduced footprint server racks further hosts a plurality of core cloud services.

15. The method of claim 9, wherein the computing device is a first computing device, and further comprising: provisioning a second computing device of the additional server rack with infrastructure components configured to host an additional cloud service; and deploying the additional cloud service to the second computing device.

16. The method of claim 15, wherein deploying the additional cloud service comprises deploying a cloud service control plane to the infrastructure components of the second computing device.

17. A reduced footprint data center server rack, comprising: one or more power distribution units; one or more network switches connected to the one or more power distribution units; and a plurality of server devices electrically connected to the one or more power distribution units and communicatively connected to the one or more network switches, the plurality of server devices configured to host a plurality of cloud services.

18. The reduced footprint data center server rack of claim 17, wherein the plurality of server devices comprises a plurality of identical server devices.

19. The reduced footprint data center server rack of claim 17, wherein the plurality of server devices comprises a plurality of hyperconverged server devices.

20. The reduced footprint data center server rack of claim 17, wherein the plurality of server devices comprises six hyperconverged server devices.

Images