Scalability in multi-tier network fabrics

Abstract

For a network of switches included in a multi-tier network fabric, an uplink port of each switch included in a first tier of switches is partitioned into a first plurality of sub-ports. A downlink port of each switch included in a second tier of switches is partitioned into the first plurality of sub-ports. For each uplink port of each switch included in the first tier of switches, a plurality of subsets of sub-ports is generated, where each subset of sub-ports of the switch is communicatively coupled to a different switch included in the second tier of switches. A packet is transmitted from a first GPU coupled to a first switch included in the first tier of switches to a second GPU coupled to a second switch included in the first tier of switches via utilizing one of the sub-ports of the uplink port of the first switch.

Description

Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) SCALABILITY IN MULTI-TIER NETWORK FABRICSCROSS-REFERENCES TO RELATED APPLICATIONS

[0001] This application is a non-provisional of and claims the benefit of the filing date of U. S. Provisional Application No. 63 / 778,217, filed on March 26, 2025, the contents of which are incorporated herein by reference in its entirety for all purposes.FIELD

[0002] The present disclosure relates to mechanisms of scaling high-performance graphical processing unit (GPU) network fabrics to facilitate execution of customer AI / ML workloads.BACKGROUND

[0003] Organizations continue to move business applications and databases to the cloud to reduce the cost of purchasing, updating, and maintaining on premise hardware and software. High performance computer applications consistently consume all of the available compute power to achieve a specific outcome or result. Such applications require dedicated network performance, fast storage, high compute capabilities, and significant amounts of memory — resources that are in short supply in the virtualized infrastructure that constitutes today’s commodity clouds.

[0004] GPU platforms are key components for the testing and development of Al and ML models (e.g., large language models). Scalability in GPU network fabrics is fundamentally about enabling thousands — or even tens of thousands — of GPUs to communicate with extremely low latency and very high bandwidth while maintaining near-linear performance scaling for distributed training and inference workloads. Unlike traditional data center traffic, GPU workloads (such as large-scale Al model training) generate intensive east-west traffic dominated by collective communication patterns like all-reduce, all-gather, and broadcast. If the fabric cannot sustain full bisection bandwidth with minimal congestion, training efficiency drops sharply as cluster size increases.

[0005] Modern GPU clusters often rely on high-performance interconnects such as InfiniBand and NVLink to provide scalable bandwidth within and across nodes. Within a server, NVLink enables GPUs to share memory coherently at very high speeds. Across servers, InfiniBand fabricsAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) use features like Remote Direct Memory Access (RDMA), adaptive routing, and congestion control to minimize CPU overhead and reduce latency. Scalable topologies expand clusters by¬ adding additional tiers (of switches) without disrupting existing workloads, thereby preserving performance predictability as the system grows,

[0006] However, the inclusion of additional tiers of switches in the network architecture (to achieve scalability) is not a cost effective solution and moreover increases the complexity of the control plane that manages the network fabric. Embodiments discussed herein address these and other issues.SUMMARY

[0007] The present disclosure relates to mechanisms of scaling high-performance graphical processing unit (GPU) network fabrics to facilitate execution of customer AI / ML workloads. Various embodiments are described herein, including methods, systems, non-transitory computer-readable storage media storing programs, code, or instructions executable by one or more processors, and the like. These illustrative embodiments are mentioned not to limit or define the disclosure, but to provide examples to aid understanding thereof. Additional embodiments are discussed in the detailed description section, and further description is provided therein.

[0008] One embodiment of the present disclosure is directed to a method comprising: for a network of switches included in a multi-tier network fabric, partitioning, for each switch included in a first tier of switches, an uplink port of the switch into a first plurality of sub-ports; partitioning, for each switch included in a second tier of switches, a downlink port of the switch into the first plurality of sub-ports; generating, for each uplink port of each switch included in the first tier of switches, a plurality of subsets of sub-ports, wherein each subset of sub-ports of the switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches; and transmitting a packet from a first GPU coupled to a first switch included in the first tier of switches to a second GPU coupled to a second switch included in the first tier of switches via utilizing one of the sub-ports of the uplink port of the first switch.

[0009] An aspect of the present disclosure provides for a computing device comprising one or more data processors, and a non-transitory computer readable storage medium containingAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) instructions which, when executed on the one or more data processors, cause the computing device to perform part or all of one or more methods disclosed herein.

[0010] Another aspect of the present disclosure provides for a computer-program product tangibly embodied in a non- transitory machine-readable storage medium, including instructions configured to cause one or more data processors to perform part or all of one or more methods disclosed herein.

[0011] The foregoing, together with other features and embodiments will become more apparent upon referring to the following specification, claims, and accompanying drawings.BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Features, embodiments, and advantages of the present disclosure are better understood when the following Detailed Description is read with reference to the accompanying drawings.

[0013] FIG, 1 is a high level diagram of a distributed environment showing a virtual or overlay cloud network hosted by a cloud service provider infrastructure according to certain embodiments.

[0014] FIG, 2 depicts a simplified architectural diagram of the physical components in the physical network within CSPI according to certain embodiments.

[0015] FIG 3 shows an example arrangement within CSPI where a host machine is connected to multiple network virtualization devices (NVDs) according to certain embodiments.

[0016] FIG 4 depicts connectivity between a host machine and an NVD for providing I / O virtualization for supporting multitenancy according to certain embodiments.

[0017] FIG 5 depicts a simplified block diagram of a physical network provided by a CSPI according to certain embodiments.

[0018] FIG. 6 depicts an exemplary rack housing network resources, according to certain embodiments.

[0019] FIG. 7 illustrates an exemplary compute tray included in a rack, according to certain embodiments.

[0020] FIG. 8A illustrates an exemplary switch included in a network fabric, according to certain embodiments.

[0021] FIG. 8B illustrates an exemplary architecture of a network fabric, according to certain embodiments.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0022] FIG. 9 depicts a flowchart illustrating steps performed in achieving scalability in the network fabric, according to certain embodiments.

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

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

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

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

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

[0028] In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of certain embodiments. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.Example Architecture of Cloud Infrastructure

[0029] The term cloud service is generally used to refer to a service that is made available by a cloud services provider (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 are separate from the customer's own on-premise 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 access to applications and computing resources without the customer having to invest in procuring the infrastructure that is used for providing the services.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0030] There are several cloud service providers that offer various types of cloud services. There are various different types or models of cloud services including Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (laaS), and others.

[0031] 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 enterpri e, and the like. When a customer subscribes to or registers for a service provided by a CSP, a tenancy or an account is created for that customer. The customer can then, via this account, access the subscribed-to one or more cloud resources associated with the account,

[0032] As noted above, infrastructure as a service (laaS) is one particular type of cloud computing service. In an laaS model, the CSP provides infrastructure (referred to as cloud services provider infrastructure or CSPI) that can be used by customers to build their own customizable networks and deploy customer resources. The customer's resources and networks are thus hosted in a distributed environment by infrastructure provided by a CSP. This is different from traditional computing, where the customer's resources and networks are hosted by infrastructure provided by the customer.

[0033] The CSPI may comprise interconnected high-performance compute resources including various host machines, memory resources, and network resources that form a physical network, which is also referred to as a substrate network or an underlay network. The resources in CSPI may be spread across one or more data centers that may be geographically spread across one or more geographical regions. Virtualization software may be executed by these physical resources to provide a virtualized distributed environment. The virtualization creates an overlay network (also known as a software- based network, a software-defined network, or a virtual network) over the physical network. The CSPI physical network provides the underlying basis for creating one or more overlay or virtual networks on top of the physical network. The virtual or overlay networks can include one or more virtual cloud networks (VCNs). The virtual networks are implemented using software virtualization technologies (e.g., hypervisors, functions performed by network virtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR) switches, smart TORs that implement one or more functions performed by an NVD, and other mechanisms) to create layers of network abstraction that can be run on top of the physical network. Virtual networks can take on many forms, including peer-to-peer networks, IP networks, and others. Virtual networks are typically either Layer-3 IP networks or Layer-2 VLANs. This method ofAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) virtual or overlay networking is often referred to as virtual or overlay Layer-3 networking. Examples of protocols developed for virtual networks include IP-in-IP (or Generic Routing Encapsulation (GRE)), Virtual Extensible LAN (VXLAN — IETF RFC 7348), Virtual Private Networks (VPNs) (e.g., MPLS Layer-3 Virtual Private Networks (RFC 4364)), VMware's NSX, GENEVE (Generic Network Virtualization Encapsulation), and others.

[0034] For TaaS, the infrastructure (CSPI) provided by a CSP can be configured to provide virtualized computing resources over a public network (e.g., the Internet), In an laaS model, a cloud computing services 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 laaS provider may also supply a variety of services to accompany those infrastructure components (e.g., billing, monitoring, logging, security, load balancing and clustering, etc.). Thus, as these services may be policy-driven, laaS users may be able to implement policies to drive load balancing to maintain application availability and performance. CSPI provides infrastructure and a set of complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available hosted distributed environment. CSPI offers high-performance compute resources and capabilities and storage capacity in a flexible virtual network that is securely accessible from various networked locations such as from a customer's on-premises network. When a customer subscribes to or registers for an laaS service provided by a CSP, the tenancy created for that customer is a secure and isolated partition within the CSPI where the customer can create, organize, and administer their cloud resources.

[0035] Customers can build their own virtual networks using compute, memory, and networking resources provided by CSPI. One or more customer resources or workloads, such as compute instances, can be deployed on these virtual networks. For example, a customer can use resources provided by CSPI to build one or multiple customizable and private virtual network(s) referred to as virtual cloud networks (VCNs). A customer can deploy one or more customer resources, such as compute instances, on a customer VCN. Compute instances can take the form of virtual machines, bare metal instances, and the like. The CSPI thus provides infrastructure and a set of complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available virtual hosted environment. The customer does not manage or control the underlying physical resources provided by CSPI but has control overAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., firewalls).

[0036] The CSP may provide a console that enables customers and network administrators to configure, access, and manage resources deployed in the cloud using CSPI resources. In certain embodiments, the console provides a web-based user interface that can be used to access and manage CSPI. In some implementations, the console is a web-based application provided by the CSP.

[0037] CSPI may support single-tenancy or multi-tenancy architectures. In a single tenancy¬ architecture, a software (e.g., an application, a database) or a hardware component (e.g., a host machine or a server) serves a single customer or tenant. In a multi-tenancy architecture, a software or a hardware component serves multiple customers or tenants. Thus, in a multi-tenancy architecture, CSPI resources are shared between multiple customers or tenants. In a multi-tenancy situation, precautions are taken and safeguards put in place within CSPI to ensure that each tenant's data is isolated and remains invisible to other tenants.

[0038] In a physical network, a network endpoint ("endpoint") refers to a computing device or system that is connected to a physical network and communicates back and forth with the network to which it is connected. A network endpoint in the physical network may be connected to a Local Area Network (LAN), a Wide Area Network (WAN), or other type of physical network. Examples of traditional endpoints in a physical network include modems, hubs, bridges, switches, routers, and other networking devices, physical computers (or host machines), and the like. Each physical device in the physical network has a fixed network address that can be used to communicate with the device. This fixed network address can be a Layer-2 address (e.g., a MAC address), a fixed Layer-3 address (e.g., an IP address), and the like. In a virtualized environment or in a virtual network, the endpoints can include various virtual endpoints such as virtual machines that are hosted by components of the physical network (e.g., hosted by physical host machines). These endpoints in the virtual network are addressed by overlay addresses such as overlay Layer-2 addresses (e.g., overlay MAC addresses) and overlay Layer-3 addresses (e.g., overlay IP addresses). Network overlays enable flexibility by allowing network managers to move around the overlay addresses associated with network endpoints using software management (e.g., via software implementing a control plane for the virtual network). Accordingly, unlike in a physical network, in a virtual network, an overlay address (e.g., an overlay IP address) can be moved fromAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) one endpoint to another using network management software. Since the virtual network is built on top of a physical network, communications between components in the virtual network involves both the virtual network and the underlying physical network. In order to facilitate such communications, the components of CSPI are configured to learn and store mappings that map overlay addresses in the virtual network to actual physical addresses in the substrate network, and vice versa. These mappings are then used to facilitate the communications. Customer traffic is encapsulated to facilitate routing in the virtual network.

[0039] Accordingly, physical addresses (e.g., physical IP addresses) are associated with components in physical networks and overlay addresses (e.g., overlay IP addresses) are associated with entities in virtual networks. Both the physical IP addresses and overlay IP addresses are types of real IP addresses. These are separate from virtual IP addresses, where a virtual IP address maps to multiple real IP addresses. A virtual IP address provides a 1-to-many mapping between the virtual IP address and multiple real IP addresses.

[0040] The cloud infrastructure or CSPI is physically hosted in one or more data centers in one or more regions around the world. The CSPI may include components in the physical or substrate network and virtualized components (e.g., virtual networks, compute instances, virtual machines, etc.) that are in a virtual network built on top of the physical network components. In certain embodiments, the CSPI is organized and hosted in realms, regions and availability domains. A region is typically a localized geographic area that contains one or more data centers. Regions are generally independent of each other and can be separated by vast distances, for example, across countries or even continents. For example, a first region may be in Australia, another one in Japan, yet another one in India, and the like. CSPI resources are divided among regions such that each region has its own independent subset of CSPI resources. Each region may provide a set of core infrastructure services and resources, such as, compute resources (e.g., bare metal servers, virtual machine, containers and related infrastructure, etc.); storage resources (e.g., block volume storage, file storage, object storage, archive storage); networking resources (e.g., virtual cloud networks (VCNs), load balancing resources, connections to on-premise networks), database resources; edge networking resources (e.g., DNS); and access management and monitoring resources, and others. Each region generally has multiple paths connecting it to other regions in the realm.

[0041] Generally, an application is deployed in a region (i.e,, deployed on infrastructure associated with that region) where it is most heavily used, because using nearby resources is fasterAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) than using distant resources. Applications can also be deployed in different regions for various reasons, such as redundancy to mitigate the risk of region-wide events such as large weather systems or earthquakes, to meet varying requirements for legal jurisdictions, tax domains, and other business or social criteria, and the like,

[0042] The data centers within a region can be further organized and subdivided into availability domains (ADs). An availability domain may correspond to one or more data centers located within a region. A region can be composed of one or more availability domains. In such a distributed environment, CSPI resources are either region-specific, such as a virtual cloud network (VCN), or availability domain-specific, such as a compute instance.

[0043] ADs within a region are isolated from each other, fault tolerant, and are configured such that they are very unlikely to fail simultaneously. This is achieved by the ADs not sharing critical infrastructure resources such as networking, physical cables, cable paths, cable entry points, etc., such that a failure at one AD within a region is unlikely to impact the availability of the other ADs within the same region. The ADs within the same region may be connected to each other by a low latency, high bandwidth network, which makes it possible to provide high-availability connectivity to other networks (e.g., the Internet, customers' on-premise networks, etc.) and to build replicated systems in multiple ADs for both high-availability and disaster recovery. Cloud services use multiple ADs to ensure high availability and to protect against resource failure. As the infrastructure provided by the laaS provider grows, more regions and ADs may be added with additional capacity. Traffic between availability domains is usually encrypted.

[0044] In certain embodiments, regions are grouped into realms. A realm is a logical collection of regions. Realms are isolated from each other and do not share any data. Regions in the same realm may communicate with each other, but regions in different realms cannot. A customer's tenancy or account with the CSP exists in a single realm and can be spread across one or more regions that belong to that realm. Typically, when a customer subscribes to an laaS service, a tenancy or account is created for that customer in the customer-specified region (referred to as the "home" region) within a realm. A customer can extend the customer's tenancy across one or more other regions within the realm. A customer cannot access regions that are not in the realm where the customer's tenancy exists,

[0045] An laaS provider can provide multiple realms, each realm catered to a particular set of customers or users. For example, a commercial realm may be provided for commercial customers.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) As another example, a realm may be provided for a specific country for customers within that country. As yet another example, a government realm may be provided for a government, and the like. For example, the government realm may be catered for a specific government and may have a heightened level of security than a commercial realm. For example, Oracle Cloud Infrastructure (OCT) currently offers a realm for commercial regions and two realms (e.g., FedRAMP authorized and ILS authorized) for government cloud regions.

[0046] In certain embodiments, an AD can be subdivided into one or more fault domains. A fault domain is a grouping of infrastructure resources within an AD to provide anti-affinity. Fault domains allow for the distribution of compute instances such that the instances are not on the same physical hardware within a single AD. This is known as anti-affinity. A fault domain refers to a set of hardware components (computers, switches, and more) that share a single point of failure. A compute pool is logically divided up into fault domains. Due to this, a hardware failure or compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. Depending on the embodiment, the number of fault domains for each? XD may vary. For instance, in certain embodiments each AD contains three fault domains. A fault domain acts as a logical data center within an AD.

[0047] When a customer subscribes to an laaS service, resources from CSPI are provisioned for the customer and associated with the customer's tenancy. The customer can use these provisioned resources to build private networks and deploy resources on these networks. The customer networks that are hosted in the cloud by the CSPI are referred to as virtual cloud networks (VCNs). A customer can set up one or more virtual cloud networks (VCNs) using CSPI resources allocated for the customer. A VCN is a virtual or software defined private network. The customer resources that are deployed in the customer's VCN can include compute instances (e.g., virtual machines, bare-metal instances) and other resources. These compute instances may represent various customer workloads such as applications, load balancers, databases, and the like. A compute instance deployed on a VCN can communicate with public accessible endpoints ("public endpoints") over a public network such as the Internet, with other instances in the same VCN or other VCNs (e.g,, the customer's other VCNs, or VCNs not belonging to the customer), with the customer's on-premise data centers or networks, and with service endpoints, and other types of endpoints.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0048] The CSP may provide various services using the CSPI. In some instances, customers of CSPI may themselves act like service providers and provide services using CSPI resources. A service provider may expose a service endpoint, which is characterized by identification information (e.g., an IP Address, a DNS name and port). A customer's resource (e.g., a compute instance) can consume a particular service by accessing a service endpoint exposed by the service for that particular service. These service endpoints are generally endpoints that are publicly accessible by users using public IP addresses associated with the endpoints via a public communication network such as the Internet, Network endpoints that are publicly accessible are also sometimes referred to as public endpoints.

[0049] In certain embodiments, a service provider may expose a service via an endpoint (sometimes referred to as a service endpoint) for the service. Customers of the service can then use this service endpoint to access the service. In certain implementations, a service endpoint provided for a service can be accessed by multiple customers that intend to consume that service. In other implementations, a dedicated service endpoint may be provided for a customer such that only that customer can access the service using that dedicated service endpoint.

[0050] In certain embodiments, when a VCN is created, it is associated with a private overlay Classless Inter-Domain Routing (CIDR) address space, which is a range of private overlay IP addresses that are assigned to the VCN (e.g., 10.0 / 16). A VCN includes associated subnets, route tables, and gateways. A VCN resides within a single region but can span one or more or all of the region's availability domains. A gateway is a virtual interface that is configured for a VCN and enables communication of traffic to and from the VCN to one or more endpoints outside the VCN. One or more different types of gateways may be configured for a VCN to enable communication to and from different types of endpoints.

[0051] A VCN can be subdivided into one or more sub-networks such as one or more subnets. A subnet is thus a unit of configuration or a subdivision that can be created within a VCN. A VCN can have one or multiple subnets. Each subnet within a V CN is associated with a contiguous range of overlay IP addresses (e.g., 10.0.0.0 / 24 and 10.0.1.0 / 24) that do not overlap with other subnets in that VCN and which represent an address space subset within the address space of the VCN.

[0052] Each compute instance is associated with a virtual network interface card (VNIC) that enables the compute instance to participate in a subnet of a VCN. A VNIC is a logical representation of physical Network Interface Card (NIC). In general, a VNIC is an interfaceAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) between an entity (e.g., a compute instance, a service) and a virtual network. A VNIC exists in a subnet, has one or more associated IP addresses, and associated security rules or policies. A VNIC is equivalent to a Layer-2 port on a switch. A VNIC is attached to a compute instance and to a subnet within a VCN, A VNIC associated with a compute instance enables the compute instance to be a part of a subnet of a VCN and enables the compute instance to communicate (e.g., send and receive packets) with endpoints that are on the same subnet as the compute instance, with endpoints in different subnets in the VCN, or with endpoints outside the VCN. The VNIC associated with a compute instance thus determines how the compute instance connects with endpoints inside and outside the VCN. A VNIC for a compute instance is created and associated with that compute instance when the compute instance is created and added to a subnet within a VCN. For a subnet comprising a set of compute instances, the subnet contains the VNICs corresponding to the set of compute instances, each VNIC attached to a compute instance within the set of computer instances.

[0053] Each compute instance is assigned a private overlay IP address via the VNIC associated with the compute instance. This private overlay IP address is assigned to the VNIC that is associated with the compute instance when the compute instance is created and used for routing traffic to and from the compute instance. All VNICs in a given subnet use the same route table, security lists, and DHCP options. As described above, each subnet within a VCN is associated with a contiguous range of overlay IP addresses (e.g., 10.0.0.0 / 24 and 10.0.1.0 / 24) that do not overlap with other subnets in that VCN and which represent an address space subset within the address space of the VCN. For a VNIC on a particular subnet of a VCN, the private overlay IP address that is assigned to the VNIC is an address from the contiguous range of overlay IP addresses allocated for the subnet.

[0054] In certain embodiments, a compute instance may optionally be assigned additional overlay IP addresses in addition to the private overlay IP address, such as, for example, one or more public IP addresses if in a public subnet. These multiple addresses are assigned either on the same VNIC or over multiple VNICs that are associated with the compute instance. Each instance however has a primary VNIC that is created during instance launch and is associated with the overlay private IP address assigned to the instance — this primary VNIC cannot be removed. Additional VNICs, referred to as secondary VNICs, can be added to an existing instance in the same availability domain as the primary VNIC, All the VNICs are in the same availability domainAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) as the instance. A secondary VNIC can be in a subnet in the same VCN as the primary VNIC, or in a different subnet that is either in the same VCN or a different one.

[0055] A compute instance may optionally be assigned a public IP address if it is in a public subnet, A subnet can be designated as either a public subnet or a private subnet at the time the subnet is created, A private subnet means that the resources (e.g., compute instances) and associated VNICs in the subnet cannot have public overlay IP addresses. A public subnet means that the resources and associated VNICs in the subnet can have public IP addresses. A customer can designate a subnet to exist either in a single availability domain or across multiple availability domains in a region or realm.

[0056] As described above, a VCN may be subdivided into one or more subnets. In certain embodiments, a Virtual Router (VR) configured for the VCN (referred to as the VCN VR or just VR) enables communications between the subnets of the VCN. For a subnet within a VCN, the VR represents a logical gateway for that subnet that enables the subnet (i.e., the compute instances on that subnet) to communicate with endpoints on other subnets within the VCN, and with other endpoints outside the VCN. The VCN VR is a logical entity that is configured to route traffic between VNICs in the VCN and virtual gateways ("gateways") associated with the VCN. Gateways are further described below with respect to FIG. 1. A VCN VR is a Layer-3 / IP Layer concept. In one embodiment, there is one VCN VR for a VCN where the VCN VR has potentially an unlimited number of ports addressed by IP addresses, with one port for each subnet of the VCN. In this manner, the VCN VR has a different IP address for each subnet in the VCN that the VCN VR is attached to. The VR is also connected to the various gateways configured for a VCN. In certain embodiments, a particular overlay IP address from the overlay IP address range for a subnet is reserved for a port of the VCN VR for that subnet. For example, consider a VCN having two subnets with associated address ranges 10.0 / 16 and 10.1 / 16, respectively. For the first subnet within the VCN with address range 10.0 / 16, an address from this range is reserved for a port of the VCN VR for that subnet. In some instances, the first IP address from the range may be reserved for the VCN VR. For example, for the subnet with overlay IP address range 10.0 / 16, IP address 10,0.0.1 may be reserved for a port of the VCN VR for that subnet. For the second subnet within the same VCN with address range 10,1 / 16, the VCN VR may have a port for that second subnet with IP address 10.1,0.1. The V CN VR has a different IP address for each of the subnets in the VCN.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0057] In some other embodiments, each subnet within a V CN may have its own associated VR that is addressable by the subnet using a reserved or default IP address associated with the VR. The reserved or default IP address may, for example, be the first IP address from the range of IP addresses associated with that subnet. The VNICs in the subnet can communicate (e.g., send and receive packets) with the VR associated with the subnet using this default or reserved IP address. In such an embodiment, the VR is the ingress / egress point for that subnet. The VR associated with a subnet within the VCN can communicate with other VRs associated with other subnets within the VCN. The VRs can also communicate with gateways associated with the VCN. The VR function for a subnet is running on or executed by one or more NVDs executing VNICs functionality for VNICs in the subnet.

[0058] Route tables, security rules, and DHCP options may be configured for a VCN. Route tables are virtual route tables for the VCN and include rules to route traffic from subnets within the VCN to destinations outside the VCN by way of gateways or specially configured instances. A VCN's route tables can be customized to control how packets are forwarded / routed to and from the VCN. DHCP options refers to configuration information that is automatically provided to the instances when they boot up.

[0059] Security rules configured for a VCN represent overlay firewall rules for the VCN. The security rules can include ingress and egress rules, and specify the types of traffic (e.g., based upon protocol and port) that is allowed in and out of the instances within the VCN. The customer can choose whether a given rule is stateful or stateless. For instance, the customer can allow incoming SSH traffic from anywhere to a set of instances by setting up a stateful ingress rule with source CIDR 0.0.0.0 / 0, and destination TCP port 22. Security rules can be implemented using network security groups or security lists. A network security group consists of a set of security rules that apply only to the resources in that group. A security' list, on the other hand, includes rules that apply to all the resources in any subnet that uses the security list. A VCN may be provided with a default security list with default security rules. DHCP options configured for a VCN provide configuration information that is automatically provided to the instances in the VCN when the instances boot up.

[0060] In certain embodiments, the configuration information for a VCN is determined and stored by a VCN Control Plane. The configuration information for a VCN may include, for example, information about: the address range associated with the VCN, subnets within the VCNAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) and associated information, one or more VRs associated with the VCN, compute instances in the VCN and associated VNICs, NVDs executing the various virtualization network functions (e.g., VNICs, VRs, gateways) associated with the VCN, state information for the VCN, and other VCN-related information. In certain embodiments, a VCN Distribution Service publishes the configuration information stored by the VCN Control Plane, or portions thereof, to the NVDs. The distributed information may be used to update information (e.g., forwarding tables, routing tables, etc.) stored and used by the NVDs to forward packets to and from the compute instances in the VCN.

[0061] In certain embodiments, the creation of VCNs and subnets are handled by a VCN Control Plane (CP) and the launching of compute instances is handled by a Compute Control Plane. The Compute Control Plane is responsible for allocating the physical resources for the compute instance and then calls the VCN Control Plane to create and attach VNICs to the compute instance. The VCN CP also sends VCN data mappings to the VCN data plane that is configured to perform packet forwarding and routing functions. In certain embodiments, the VCN CP provides a distribution service that is responsible for providing updates to the VCN data plane. Examples of a VCN Control Plane are also depicted in FIGs. 12, 13, 14, and 15 (see references 1216, 1316, 1416, and 1516) and described below.

[0062] A customer may create one or more VCNs using resources hosted by CSPI. A compute instance deployed on a customer VCN may communicate with different endpoints. These endpoints can include endpoints that are hosted by CSPI and endpoints outside CSPI.

[0063] Various different architectures for implementing cloud-based service using CSPI are depicted in FIGs. 1, 2, 3, 4, 5, 12, 13, 14, and 15 are described below. FIG. 1 is a high level diagram of a distributed environment 100 showing an overlay or customer VCN hosted by CSPI according to certain embodiments. The distributed environment depicted in FIG. 1 includes multiple components in the overlay network. Distributed environment 100 depicted in FIG. 1 is merely an example and is not intended to unduly limit the scope of claimed embodiments. Many variations, alternatives, and modifications are possible. For example, in some implementations, the distributed environment depicted in FIG, 1 may have more or fewer systems or components than those shown in FIG. 1, may combine two or more systems, or may have a different configuration or arrangement of systems.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0064] As shown in the example depicted in FIG. 1, distributed environment 100 comprises CSPI 101 that provides sendees and resources that customers can subscribe to and use to build their virtual cloud networks (VCNs). In certain embodiments, CSPI 101 offers laaS services to subscribing customers. The data centers within CSPI 101 may be organized into one or more regions. One example region " Region US" 102 is shown in FIG. 1. A customer has configured a customer VCN 104 for region 102, The customer may deploy various compute instances on VCN 104, where the compute instances may include virtual machines or bare metal instances. Examples of instances include applications, database, load balancers, and the like.

[0065] In the embodiment depicted in FIG. 1, customer VCN 104 comprises two subnets, namely, " Subnet- 1 " and " Subnet-2", each subnet with its own CIDR IP address range. In FIG. 1, the overlay IP address range for Subnet- 1 is 10.0 / 16 and the address range for Subnet-2 is 10.1 / 16. A VCN Virtual Router 105 represents a logical gateway for the VCN that enables communications between subnets of the VCN 104, and with other endpoints outside the VCN. VCN VR 105 is configured to route traffic between VNICs in VCN 104 and gateways associated with VCN 104. VCN VR 105 provides a port for each subnet of VCN 104. For example, VR 105 may provide a port with IP address 10.0.0.1 for Subnet- 1 and a port with IP address 10.1.0.1 for Subnet-2.

[0066] Multiple compute instances may be deployed on each subnet, where the compute instances can be virtual machine instances, and / or bare metal instances. The compute instances in a subnet may be hosted by one or more host machines within CSPI 101. A compute instance participates in a subnet via a VNIC associated with the compute instance. For example, as shown in FIG. 1, a compute instance C1 is part of Subnet-1 via a VNIC associated with the compute instance. Likewise, compute instance C2 is part of Subnet- 1 via a VNIC associated with C2. In a similar manner, multiple compute instances, w’hich may be virtual machine instances or bare metal instances, may be part of Subnet- 1. Via its associated VNIC, each compute instance is assigned a private overlay IP address and a MAC address. For example, in FIG. 1, compute instance Cl has an overlay IP address of 10.0.0.2 and a MAC address of Ml, while compute instance C2 has a private overlay IP address of 10.0.0.3 and a MAC address of M2. Each compute instance in Subnet- 1, including compute instances Cl and C2, has a default route to VCN VR 105 using IP address 10.0.0, 1, which is the IP address for a port of VCN VR 105 for Subnet-1.

[0067] Subnet-2 can have multiple compute instances deployed on it, including virtual machine instances and / or bare metal instances. For example, as shown in FIG 1, computeAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) instances DI and D2 are part of Subnet-2 via VNICs associated with the respective compute instances. In the embodiment depicted in FIG. 1, compute instance DI has an overlay IP address of 10,1.0.2 and a MAC address of MM1, while compute instance D2 has a private overlay IP address of 10.1.0,3 and a MAC address of MM2. Each compute instance in Subnet-2, including compute instances D1 and D2, has a default route to VCN VR 105 using IP address 10.1.0.1, which is the IP address for a port of VCN VR 105 for Subnet-2.

[0068] VCN A 104 may also include one or more load balancers. For example, a load balancer may be provided for a subnet and may be configured to load balance traffic across multiple compute instances on the subnet. A load balancer may also be provided to load balance traffic across subnets in the VCN.

[0069] A particular compute instance deployed on V CN 104 can communicate with various different endpoints. These endpoints may include endpoints that are hosted by CSPI 200 and endpoints outside CSPI 200. Endpoints that are hosted by CSPI 101 may include: an endpoint on the same subnet as the particular compute instance (e.g., communications between two compute instances in Subnet-1); an endpoint on a different subnet but within the same VCN (e.g., communication between a compute instance in Subnet- 1 and a compute instance in Subnet-2); an endpoint in a different VCN in the same region (e.g., communications between a compute instance in Subnet- 1 and an endpoint in a VCN in the same region 106 or 110, communications between a compute instance in Subnet- 1 and an endpoint in service network 110 in the same region); or an endpoint in a VCN in a different region (e.g., communications between a compute instance in Subnet- 1 and an endpoint in a VCN in a different region 108). A compute instance in a subnet hosted by CSPI 101 may also communicate with endpoints that are not hosted by CSPI 101 (i.e., are outside CSPI 101). These outside endpoints include endpoints in the customer’s on-premise network 116, endpoints within other remote cloud hosted networks 118, public endpoints 114 accessible via a public network such as the Internet, and other endpoints.

[0070] Communications between compute instances on the same subnet are facilitated using VNICs associated with the source compute instance and the destination compute instance. For example, compute instance Cl in Subnet- 1 may want to send packets to compute instance C2 in Subnet- 1. For a packet originating at a source compute instance and whose destination is another compute instance in the same subnet, the packet is first processed by the VNIC associated with the source compute instance. Processing performed by the VNIC associated with the source computeAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) instance can include determining destination information for the packet from the packet headers, identifying any policies (e.g., security lists) configured for the VNIC associated with the source compute instance, determining a next hop for the packet, performing any packet encapsulation / decapsulation functions as needed, and then forwarding / routing the packet to the next hop with the goal of facilitating communication of the packet to its intended destination. When the destination compute instance is in the same subnet as the source compute instance, the VNIC associated with the source compute instance is configured to identify the VNIC associated with the destination compute instance and forward the packet to that VNIC for processing. The VNIC associated with the destination compute instance is then executed and forwards the packet to the destination compute instance.

[0071] For a packet to be communicated from a compute instance in a subnet to an endpoint in a different subnet in the same VCN, the communication is facilitated by the VNICs associated with the source and destination compute instances and the VCN VR For example, if compute instance Cl in Subnet-1 in FIG. 1 wants to send a packet to compute instance DI in Subnet-2, the packet is first processed by the VNIC associated with compute instance Cl. The VNIC associated with compute instance Cl is configured to route the packet to the VCN VR 105 using default route or port 10.0.0.1 of the VCN VR. VCN VR 105 is configured to route the packet to Subnet-2 using port 10.1.0.1. The packet is then received and processed by the VNIC associated with D 1 and the VNIC forwards the packet to compute instance DI.

[0072] For a packet to be communicated from a compute instance in VCN 104 to an endpoint that is outside VCN 104, the communication is facilitated by the VNIC associated with the source compute instance, VCN VR 105, and gateways associated with VCN 104. One or more types of gateways may be associated with VCN 104. A gateway is an interface between a VCN and another endpoint, where the another endpoint is outside the VCN. A gateway is a Layer-3 / IP layer concept and enables a VCN to communicate with endpoints outside the VCN. A gateway thus facilitates traffic flow between a VCN and other VCNs or networks. Various different types of gateways may be configured for a VCN to facilitate different types of communications with different types of endpoints. Depending upon the gateway, the communications may be over public networks (e.g., the Internet) or over private networks. Various communication protocols may be used for these communications.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0073] For example, compute instance Cl may want to communicate with an endpoint outside VCN 104. The packet may be first processed by the VNIC associated with source compute instance Cl. The VNIC processing determines that the destination for the packet is outside the Subnet- 1 of Cl. The VNIC associated with Cl may forward the packet to VCN VR 105 for VCN 104, VCN VR 105 then processes the packet and as part of the processing, based upon the destination for the packet, determines a particular gateway associated with VCN 104 as the next hop for the packet. VCN VR 105 may then forward the packet to the particular identified gateway. For example, if the destination is an endpoint within the customer's on-premise network, then the packet may be forwarded by VCN VR 105 to Dynamic Routing Gateway (DRG) gateway 122 configured for VCN 104. The packet may then be forwarded from the gateway to a next hop to facilitate communication of the packet to its final intended destination.

[0074] Various different types of gateways may be configured for a VCN. Examples of gateways that may be configured for a VCN are depicted in FIG. 1 and described below. Examples of gateways associated with a VCN are also depicted in FIGs. 12, 13, 14, and 15 (for example, gateways referenced by reference numbers 1234, 1236, 1238, 1334, 1336, 1338, 1434, 1436, 1438, 1534, 1536, and 1538) and described below. As shown in the embodiment depicted in FIG. 1, a Dynamic Routing Gateway (DRG) 122 may be added to or be associated with customer VCN 104 and provides a path for private network traffic communication between customer VCN 104 and another endpoint, where the another endpoint can be the customer's on-premise network 116, a VCN 108 in a different region of CSPI 101, or other remote cloud networks 118 not hosted by CSPI 101. Customer on-premise network 116 may be a customer network or a customer data center built using the customer’s resources. Access to customer on-premise network 116 is generally very restricted. For a customer that has both a customer on-premise network 116 and one or more VCNs 104 deployed or hosted in the cloud by CSPI 101, the customer may want their on-premise network 116 and their cloud-based VCN 104 to be able to communicate with each other. This enables a customer to build an extended hybrid environment encompassing the customer's VCN 104 hosted by CSPI 101 and their on-premises network 116. DRG 122 enables this communication. To enable such communications, a communication channel 124 is set up where one endpoint of the channel is in customer on-premise network 116 and the other endpoint is in CSPI 101 and connected to customer VCN 104. Communication channel 124 can be over public communication networks such as the Internet or private communication networks. VariousAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) different communication protocols may be used such as IPsec VPN technology over a public communication network such as the Internet, Oracle's FastConnect technology that uses a private network instead of a public network, and others. The device or equipment in customer on-premise network 116 that forms one end point for communication channel 124 is referred to as the customer premise equipment (CPE), such as CPE 126 depicted in FIG. 1, On the CSPI 101 side, the endpoint may be a host machine executing DRG 122.In certain embodiments, a Remote Peering Connection (RPC) can be added to a DRG, which allows a customer to peer one VCN with another VCN in a different region. Using such an RPC, customer VCN 104 can use DRG 122 to connect with a VCN 108 in another region. DRG 122 may also be used to communicate with other remote cloud networks 118, not hosted by CSPI 101 such as a Microsoft Azure cloud, / Xmazon AWS cloud, and others.

[0075] As shown in FIG. 1, an Internet Gateway (IGW) 120 may be configured for customer VCN 104 the enables a compute instance on VCN 104 to communicate with public endpoints 114 accessible over a public network such as the Internet. IGW 120 is a gateway that connects a VCN to a public network such as the Internet. IGW 120 enables a public subnet (where the resources in the public subnet have public overlay IP addresses) within a VCN, such as VCN 104, direct access to public endpoints 112 on a public network 114 such as the Internet. Using IGW 120, connections can be initiated from a subnet within VCN 104 or from the Internet.

[0076] A Network Address Translation (N AT) gateway 128 can be configured for customer's VCN 104 and enables cloud resources in the customer’s VCN, which do not have dedicated public overlay IP addresses, access to the Internet and it does so without exposing those resources to direct incoming Internet connections (e.g., L4-L7 connections). This enables a private subnet within a VCN, such as private Subnet-1 in VCN 104, with private access to public endpoints on the Internet. In NAT gateways, connections can be initiated only from the private subnet to the public Internet and not from the Internet to the private subnet.

[0077] In certain embodiments, a Service Gateway (SGW) 126 can be configured for customer VCN 104 and provides a path for private network traffic between VCN 104 and supported services endpoints in a service network 110, In certain embodiments, service network 110 may be provided by the CSP and may provide various services. An example of such a service network is Oracle’s Services Network, which provides various services that can be used by customers. For example, a compute instance (e.g., a database system) in a private subnet of customer VCN 104 can back upAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) data to a service endpoint (e.g., Object Storage) without needing public IP addresses or access to the Internet. In certain embodiments, a VCN can have only one SGW, and connections can only be initiated from a subnet within the VCN and not from service network 110. If a VCN is peered with another, resources in the other VCN typically cannot access the SGW. Resources in onpremises networks that are connected to a VCN with FastConnect or VPN Connect can also use the service gateway configured for that VCN.

[0078] In certain implementations, SGW 126 uses the concept of a service Classless InterDomain Routing (CIDR) label, which is a string that represents all the regional public IP address ranges for the service or group of services of interest. The customer uses the service CIDR label when they configure the SGW and related route rules to control traffic to the service. The customer can optionally utilize it when configuring security rules without needing to adjust them if the service's public I P addresses change in the future.

[0079] A Local Peering Gateway (LPG) 132 is a gateway that can be added to customer VCN 104 and enables VCN 104 to peer with another VCN in the same region. Peering means that the VCNs communicate using private IP addresses, without the traffic traversing a public network such as the Internet or without routing the traffic through the customer's on-premises network 116. In preferred embodiments, a VCN has a separate LPG for each peering it establishes. Local Peering or VCN Peering is a common practice used to establish network connectivity between different applications or infrastructure management functions.

[0080] Service providers, such as providers of services in service network 110, may provide access to services using different access models. According to a public access model, services may be exposed as public endpoints that are publicly accessible by compute instance in a customer VCN via a public network such as the Internet and or may be privately accessible via SGW 126. According to a specific private access model, services are made accessible as private IP endpoints in a private subnet in the customer's VCN. This is referred to as a Private Endpoint (PE) access and enables a service provider to expose their service as an instance in the customer's private network. A Private Endpoint resource represents a service within the customer's VCN. Each PE manifests as a VNIC (referred to as a PE- VNIC, with one or more private IPs) in a subnet chosen by the customer in the customer's VCN. A PE thus provides a way to present a service within a private customer VCN subnet using a VNIC. Since the endpoint is exposed as a VNIC, all theAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) features associates with a VNIC such as routing rules, security lists, etc., are now available for the PE VNIC.

[0081] A service provider can register their service to enable access through a PE, The provider can associate policies with the service that restricts the service's visibility to the customer tenancies. A provider can register multiple services under a single virtual IP address (VIP), especially for multi-tenant services. There may be multiple such private endpoints (in multiple VCNs) that represent the same service.

[0082] Compute instances in the private subnet can then use the PE VNIC's private IP address or the service DNS name to access the service. Compute instances in the customer VCN can access the service by sending traffic to the private IP address of the PE in the customer VCN. A Private Access Gateway (PAGW) 130 is a gateway resource that can be attached to a service provider VCN (e.g., a VCN in service network 110) that acts as an ingress / egress point for all traffic from / to customer subnet private endpoints. PAGW 130 enables a provider to scale the number of PE connections without utilizing its internal IP address resources. A provider needs only configure one PAGW for any number of services registered in a single VCN. Providers can represent a service as a private endpoint in multiple VCNs of one or more customers. From the customer's perspective, the PE VNIC, which, instead of being attached to a customer's instance, appears attached to the service with which the customer wishes to interact. The traffic destined to the private endpoint is routed via PAGW 130 to the service. These are referred to as customer- to-service private connections (C2S connections).

[0083] The PE concept can also be used to extend the private access for the service to customer's on-premises networks and data centers, by allowing the traffic to flow through FastConnect / IPsec links and the private endpoint in the customer VCN. Private access for the service can also be extended to the customer's peered VCNs, by allowing the traffic to flow between LPG 132 and the PE in the customer's VCN.

[0084] A customer can control routing in a V CN at the subnet level, so the customer can specify which subnets in the customer's VCN, such as VCN 104, use each gateway. A VCN's route tables are used to decide if traffic is allowed out of a VCN through a particular gateway. For example, in a particular instance, a route table for a public subnet within customer VCN 104 may send nonlocal traffic through IGW 120. The route table for a private subnet within the same customer V CNAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 104 may send traffic destined for CSP services through SGW 126. All remaining traffic may be sent via the NAT gateway 128. Route tables only control traffic going out of a VCN.

[0085] Security lists associated with a VCN are used to control traffic that comes into a VCN via a gateway via inbound connections. All resources in a subnet use the same route table and security lists. Security lists may be used to control specific types of traffic allowed in and out of instances in a subnet of a VCN. Security list rules may comprise ingress (inbound) and egress (outbound) rules. For example, an ingress rule may specify an allowed source address range, while an egress rule may specify an allowed destination address range. Security rules may specify a particular protocol (e.g., TCP, ICMP), a particular port (e.g., 22 for SSH, 3389 for Windows RDP), etc. In certain implementations, an instance's operating system may enforce its own firewall rules that are aligned with the security list rules. Rules may be stateful (e.g., a connection is tracked and the response is automatically allowed without an explicit security list rule for the response traffic) or stateless.

[0086] Access from a customer VCN (i.e., by a resource or compute instance deployed on VCN 104) can be categorized as public access, private access, or dedicated access. Public access refers to an access model where a public IP address or a N AT is used to access a public endpoint. Private access enables customer workloads in VCN 104 with private IP addresses (e.g., resources in a private subnet) to access sendees without traversing a public network such as the Internet. In certain embodiments, CSPI 101 enables customer VCN workloads with private IP addresses to access the (public service endpoints of) services using a service gateway. A service gateway thus offers a private access model by establishing a virtual link between the customer's VCN and the service's public endpoint residing outside the customer's private network.

[0087] Additionally, CSPI may offer dedicated public access using technologies such as FastConnect public peering where customer on-premises instances can access one or more services in a customer VCN using a FastConnect connection and without traversing a public network such as the Internet. CSPI also may also offer dedicated private access using FastConnect private peering where customer on-premises instances with private IP addresses can access the customer's VCN workloads using a FastConnect connection. FastConnect is a network connectivity alternative to using the public Internet to connect a customer's on-premise network to CSPI and its services. FastConnect provides an easy, elastic, and economical way to create a dedicated andAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) private connection with higher bandwidth options and a more reliable and consistent networking experience when compared to Internet-based connections.

[0088] FIG. 1 and the accompanying description above describes various virtualized components in an example virtual network. As described above, the virtual network is built on the underlying physical or substrate network. FIG. 2 depicts a simplified architectural diagram of the physical components in the physical network within CSPI 200 that provide the underlay for the virtual network according to certain embodiments. As shown, CSPI 200 provides a distributed environment comprising components and resources (e.g., compute, memory, and networking resources) provided by a cloud service provider (CSP). These components and resources are used to provide cloud services (e.g., IaaS services) to subscribing customers, i.e., customers that have subscribed to one or more services provided by the CSP. Based upon the services subscribed to by a customer, a subset of resources (e.g., compute, memory, and networking resources) of CSPI 200 are provisioned for the customer. Customers can then build their own cloud-based (i.e., CSPI-hosted) customizable and private virtual networks using physical compute, memory, and networking resources provided by CSPI 200. As previously indicated, these customer networks are referred to as virtual cloud networks (VCNs). A customer can deploy one or more customer resources, such as compute instances, on these customer VCNs. Compute instances can be in the form of virtual machines, bare metal instances, and the like. CSPI 200 provides infrastructure and a set of complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available hosted environment.

[0089] In the example embodiment depicted in FIG. 2, the physical components of CSPI 200 include one or more physical host machines or physical servers (e.g., 202, 206, 208), network virtualization devices (NVDs) (e.g., 210, 212), top-of-rack (TOR) switches (e.g., 214, 216), and a physical network (e.g., 218), and switches in physical network 218. The physical host machines or servers may host and execute various compute instances that participate in one or more subnets of a VCN. The compute instances may include virtual machine instances, and bare metal instances. For example, the various compute instances depicted in FIG. 1 may be hosted by the physical host machines depicted in FIG. 2, The virtual machine compute instances in a VCN may be executed by one host machine or by multiple different host machines. The physical host machines may also host virtual host machines, container-based hosts or functions, and the like. The VNICs and VCNAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) VR depicted in FIG. 1 may be executed by the NVDs depicted in FIG. 2. The gateways depicted in FIG. 1 may be executed by the host machines and / or by the NVDs depicted in FIG. 2.

[0090] The host machines or servers may execute a hypervisor (also referred to as a virtual machine monitor or VMM) that creates and enables a virtualized environment on the host machines. The virtualization or virtualized environment facilitates cloud-based computing. One or more compute instances may be created, executed, and managed on a host machine by a hypervisor on that host machine. The hypervisor on a host machine enables the physical computing resources of the host machine (e.g., compute, memory, and networking resources) to be shared between the various compute instances executed by the host machine.

[0091] For example, as depicted in FIG. 2, host machines 202 and 208 execute hypervisors 260 and 266, respectively. These hypervisors may be implemented using software, firmware, or hardware, or combinations thereof. Typically, a hypervisor is a process or a software layer that sits on top of the host machine's operating system (OS), which in turn executes on the hardware processors of the host machine. The hypervisor provides a virtualized environment by enabling the physical computing resources (e.g., processing resources such as processors / cores, memory resources, networking resources) of the host machine to be shared among the various virtual machine compute instances executed by the host machine. For example, m FIG. 2, hypervisor 260 may sit on top of the OS of host machine 202 and enables the computing resources (e.g., processing, memory, and networking resources) of host machine 202 to be shared between compute instances (e.g., virtual machines) executed by host machine 202. A virtual machine can have its own operating system (referred to as a guest operating system), which may be the same as or different from the OS of the host machine. The operating system of a virtual machine executed by a host machine may be the same as or different from the operating system of another virtual machine executed by the same host machine. A hypervisor thus enables multiple operating systems to be executed alongside each other while sharing the same computing resources of the host machine. The host machines depicted in FIG. 2 may have the same or different types of hypervisors.

[0092] A compute instance can be a virtual machine instance or a bare metal instance. In FIG.2, compute instances 268 on host machine 202 and 274 on host machine 208 are examples of virtual machine instances. Host machine 206 is an example of a bare metal instance that is provided to a customer.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0093] In certain instances, an entire host machine may be provisioned to a single customer, and all of the one or more compute instances (either virtual machines or bare metal instance) hosted by that host machine belong to that same customer. In other instances, a host machine may be shared between multiple customers (i.e., multiple tenants). In such a multi-tenancy scenario, a host machine may host virtual machine compute instances belonging to different customers. These compute instances may be members of different VCNs of different customers. In certain embodiments, a bare metal compute instance is hosted by a bare metal server without a hypervisor. When a bare metal compute instance is provisioned, a single customer or tenant maintains control of the physical CPU, memory, and network interfaces of the host machine hosting the bare metal instance and the host machine is not shared with other customers or tenants.

[0094] As previously described, each compute instance that is part of a VCN is associated with a VNIC that enables the compute instance to become a member of a subnet of the VCN. The VNIC associated with a compute instance facilitates the communication of packets or frames to and from the compute instance. A VNIC is associated with a compute instance when the compute instance is created. In certain embodiments, for a compute instance executed by a host machine, the VNIC associated with that compute instance is executed by an NVD connected to the host machine. For example, in FIG. 2, host machine 202 executes a virtual machine compute instance 268 that is associated with VNIC 276, and VNIC 276 is executed by NVD 210 connected to host machine 202. As another example, bare metal instance 272 hosted by host machine 206 is associated with VNIC 280 that is executed by NVD 212 connected to host machine 206. As yet another example, VNIC 284 is associated with compute instance 274 executed by host machine 208, and VNIC 284 is executed by NVD 212 connected to host machine 208.

[0095] For compute instances hosted by a host machine, an NVD connected to that host machine also executes VCN VRs corresponding to V CNs of which the compute instances are members. For example, in the embodiment depicted in FIG. 2, NVD 210 executes VCN VR 277 corresponding to the VCN of which compute instance 268 is a member. NVD 212 may also execute one or more VCN VRs 283 corresponding to VCNs corresponding to the compute instances hosted by host machines 206 and 208.

[0096] A host machine may include one or more network interface cards (NIC) that enable the host machine to be connected to other devices. A NIC on a host machine may provide one or more ports (or interfaces) that enable the host machine to be communicatively connected to anotherAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) device. For example, a host machine may be connected to an NVD using one or more ports (or interfaces) provided on the host machine and on the NAT). A host machine may also be connected to other devices such as another host machine,

[0097] For example, in FIG. 2, host machine 202 is connected to NVD 210 using link 220 that extends between a port 234 provided by a NIC 232 of host machine 202 and between a port 236 of NVD 210. Host machine 206 is connected to NVD 212 using link 224 that extends between a port 246 provided by a NIC 244 of host machine 206 and between a port 248 of NVD 212. Host machine 208 is connected to NVD 212 using link 226 that extends between a port 252 provided by a NIC 250 of host machine 208 and between a port 254 of NVD 212.

[0098] The NVDs are in turn connected via communication links to top-of-the-rack (TOR) switches, which are connected to physical network 218 (also referred to as the switch fabric). In certain embodiments, the links between a host machine and an NVD, and between an NVD and a TOR switch are Ethernet links. For example, in FIG. 2, NVDs 210 and 212 are connected to TOR switches 214 and 216, respectively, using links 228 and 230. In certain embodiments, the links 220, 224, 226, 228, and 230 are Ethernet links. The collection of host machines and NVDs that are connected to a TOR is sometimes referred to as a rack.

[0099] Physical network 218 provides a communication fabric that enables TOR switches to communicate with each other. Physical network 218 can be a multi-tiered network. In certain implementations, physical network 218 is a multi-tiered Clos network of switches, with TOR switches 214 and 216 representing the leaf level nodes of the multi-tiered and multi-node physical switching network 218. Different Clos network configurations are possible including but not limited to a 2-tier network, a 3-tier network, a 4-tier network, a 5-tier network, and in general a "n" -tiered network. An example of a Clos network is depicted in FIG. 5 and described below.

[0100] Various different connection configurations are possible between host machines and NVDs such as one-to-one configuration, many-to-one configuration, one-to-many configuration, and others. In a one-to-one configuration implementation, each host machine is connected to its own separate NVD. For example, in FIG. 2, host machine 202 is connected to NVD 210 via NIC 232 of host machine 202. In a many-to-one configuration, multiple host machines are connected to one NVD. For example, in FIG. 2, host machines 206 and 208 are connected to the same NVD 212 via NICs 244 and 250, respectively.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0101] In a one-to-many configuration, one host machine is connected to multiple NVDs. FIG.3 shows an example within CSPI 300 where a host machine is connected to multiple NVDs. As shown in FIG. 3, host machine 302 comprises a network interface card (NIC) 304 that includes multiple ports 306 and 308. Host machine 300 is connected to a first NAD 310 via port 306 and link 320, and connected to a second NVD 312 via port 308 and link 322. Ports 306 and 308 may be Ethernet ports and the links 320 and 322 between host machine 302 and NVDs 310 and 312 may be Ethernet links, NVD 310 is in turn connected to a first TOR switch 314 and NVD 312 is connected to a second TOR switch 316. The links between NVDs 310 and 312, and TOR switches 314 and 316 may be Ethernet links. TOR switches 314 and 316 represent the Tier-0 switching devices in multi-tiered physical network 318.

[0102] The arrangement depicted in FIG. 3 provides two separate physical network paths to and from physical switch network 318 to host machine 302: a first path traversing TOR switch 314 to NVD 310 to host machine 302, and a second path traversing TOR switch 316 to NVD 312 to host machine 302. The separate paths provide for enhanced availability (referred to as high availability) of host machine 302. If there are problems in one of the paths (e.g., a link in one of the paths goes down) or devices (e.g., a particular NVD is not functioning), then the other path may be used for communications to / from host machine 302.

[0103] In the configuration depicted in FIG. 3, the host machine is connected to two different NVDs using two different ports provided by a NIC of the host machine. In other embodiments, a host machine may include multiple NICs that enable connectivity of the host machine to multiple NVDs.

[0104] Referring back to FIG 2, an NVD is a physical device or component that performs one or more network and / or storage virtualization functions. An NVD may be any device with one or more processing units (e.g., CPUs, Network Processing Units (NPUs), FPGAs, packet processing pipelines, etc.), memory including cache, and ports. The various virtualization functions may be performed by software / firmware executed by the one or more processing units of the NVD.

[0105] An NVD may be implemented in various different forms. For example, in certain embodiments, an NAD is implemented as an interface card referred to as a smartNIC or an intelligent NIC with an embedded processor onboard. A smartNIC is a separate device from the NICs on the host machines. In FIG. 2, the NVDs 210 and 212 may be implemented as smartNICs that are connected to host machines 202, and host machines 206 and 208, respectively.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0106] A smartNIC is however just one example of an NVD implementation. Various other implementations are possible. For example, in some other implementations, an NVD or one or more functions performed by the NVD may be incorporated into or performed by one or more host machines, one or more TOR switches, and other components of CSPI 200, For example, an NVD may be embodied in a host machine where the functions performed by an NVD are performed by the host machine. As another example, an NAT) may be part of a TOR switch or a TOR switch may be configured to perform functions performed by an NAT) that enables the TOR switch to perform various complex packet transformations that are used for a public cloud. A TOR that performs the functions of an NVD is sometimes referred to as a smart TOR. In yet other implementations, where virtual machines (ViMs) instances, but not bare metal (BM) instances, are offered to customers, functions performed by an NAD may be implemented inside a hypervisor of the host machine. In some other implementations, some of the functions of the NVD may be offloaded to a centralized service running on a fleet of host machines.

[0107] In certain embodiments, such as when implemented as a smartNIC as shown in FIG. 2, an NVD may comprise multiple physical ports that enable it to be connected to one or more host machines and to one or more TOR switches. A port on an NVD can be classified as a host-facing port (also referred to as a "south port") or a network-facing or TOR-facing port (also referred to as a "north port"). A host-facing port of an NVD is a port that is used to connect the NVD to a host machine. Examples of host-facing ports in FIG. 2 include port 236 on NVD 210, and ports 248 and 254 on NVD 212. A network-facing port of an NVD is a port that is used to connect the NVD to a TOR switch. Examples of network-facing ports in FIG. 2 include port 256 on NVD 210, and port 258 on NVD 212. As shown in FIG. 2, NVD 210 is connected to TOR switch 214 using link 228 that extends from port 256 of NVD 210 to the TOR switch 214. Likewise, NVD 212 is connected to TOR switch 216 using link 230 that extends from port 258 of NVD 212 to the TOR switch 216.

[0108] An NVD receives packets and frames from a host machine (e.g., packets and frames generated by a compute instance hosted by the host machine) via a host-facing port and, after performing the necessary’ packet processing, may forward the packets and frames to a TOR switch via a network-facing port of the NVD. An NVD may receive packets and frames from a TOR switch via a network-facing port of the NVD and, after performing the necessary packetAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) processing, may forward the packets and frames to a host machine via a host-facing port of the NVD.

[0109] In certain embodiments, there may be multiple ports and associated links between an NVD and a TOR switch. These ports and links may be aggregated to form a link aggregator group of multiple ports or links (referred to as a LAG), Link aggregation allows multiple physical links between two end-points (e.g., between an NVD and a TOR switch) to be treated as a single logical link. All the physical links in a given LAG may operate in full-duplex mode at the same speed. LAGs help increase the bandwidth and reliability of the connection between two endpoints. If one of the physical links in the LAG goes down, traffic is dynamically and transparently reassigned to one of the other physical links in the LAG. The aggregated physical links deliver higher bandwidth than each individual link. The multiple ports associated with a LAG are treated as a single logical port. Traffic can be load-balanced across the multiple physical links of a LAG. One or more LAGs may be configured between two endpoints. The two endpoints may be between an NVD and a TOR switch, between a host machine and an NVD, and the like.

[0110] An N VD implements or performs network virtualization functions. These functions are performed by software / firmware executed by the NVD. Examples of network virtualization functions include without limitation: packet encapsulation and de-capsulation functions; functions for creating a VCN network; functions for implementing network policies such as VCN security list (firewall) functionality; functions that facilitate the routing and forwarding of packets to and from compute instances in a VCN; and the like. In certain embodiments, upon receiving a packet, an NVD is configured to execute a packet processing pipeline for processing the packet and determining how the packet is to be forwarded or routed. As part of this packet processing pipeline, the NVD may execute one or more virtual functions associated with the overlay network such as executing VNICs associated with CIs in the VCN, executing a Virtual Router (VR) associated with the VCN, the encapsulation and decapsulation of packets to facilitate forwarding or routing in the virtual network, execution of certain gateways (e.g., the Local Peering Gateway), the implementation of Security Lists, Network Security Groups, network address translation (NAT) functionality (e g., the translation of Public IP to Private IP on a host by host basis), throttling functions, and other functions.

[0111] In certain embodiments, the packet processing data path in an NVD may comprise multiple packet pipelines, each composed of a series of packet transformation stages. In certainAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) implementations, upon receiving a packet, the packet is parsed and classified to a single pipeline. The packet is then processed in a linear fashion, one stage after another, until the packet is either dropped or sent out over an interface of the NVD. These stages provide basic functional packet processing building blocks (e.g., validating headers, enforcing throttle, inserting new Layer-2 headers, enforcing L4 firewall, VCN encapsulation / decapsulation, etc.) so that new pipelines can be constructed by composing existing stages, and new functionality can be added by creating new stages and inserting them into existing pipelines.

[0112] An NVD may perform both control plane and data plane functions corresponding to a control plane and a data plane of a VCN. Examples of a VCN Control Plane are also depicted in FIGs. 12, 13, 14, and 15 (see references 1216, 1316, 1416, and 1516) and described below. Examples of a VCN Data Plane are depicted in FIGs. 12, 13, 14, and 15 (see references 1218, 1318, 1418, and 1518) and described below. The control plane functions include functions used for configuring a network (e.g., setting up routes and route tables, configuring VNICs, etc.) that controls how data is to be forwarded. In certain embodiments, a VCN Control Plane is provided that computes all the overlay-to-substrate mappings centrally and publishes them to the NVDs and to the virtual network edge devices such as various gateways such as the DRG, the SGW, the I GW, etc. Firewall rules may also be published using the same mechanism. In certain embodiments, an NVD only gets the mappings that are relevant for that NVD. The data plane functions include functions for the actual routing / forwarding of a packet based upon configuration set up using control plane. A VCN data plane is implemented by encapsulating the customer's network packets before they traverse the substrate network. The encapsulation / decapsulation functionality is implemented on the NVDs. In certain embodiments, an NVD is configured to intercept all network packets in and out of host machines and perform network virtualization functions.

[0113] As indicated above, an NVD executes various virtualization functions including VNICs and VCN VRs. An NVD may execute VNICs associated with the compute instances hosted by one or more host machines connected to the VNIC For example, as depicted in FIG. 2, NVD 210 executes the functionality' for VNIC 276 that is associated with compute instance 268 hosted by host machine 202 connected to NVD 210. As another example, NVD 212 executes VNIC 280 that is associated with bare metal compute instance 272 hosted by host machine 206, and executes VNIC 284 that is associated with compute instance 274 hosted by host machine 208. A host machine may host compute instances belonging to different VCNs, which belong to differentAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) customers, and the NVD connected to the host machine may execute the VNICs (i.e., execute VNICs-relate functionality) corresponding to the compute instances.

[0114] An NVD also executes VCN Virtual Routers corresponding to the VCNs of the compute instances. For example, in the embodiment depicted in FIG. 2, NVD 210 executes VCN VR 277 corresponding to the VCN to which compute instance 268 belongs, NVD 212 executes one or more VCN VRs 283 corresponding to one or more VCNs to which compute instances hosted by host machines 206 and 208 belong. In certain embodiments, the VCN VR corresponding to that VCN is executed by all the NVDs connected to host machines that host at least one compute instance belonging to that VCN. If a host machine hosts compute instances belonging to different VCNs, an NVD connected to that host machine may execute VCN VRs corresponding to those different VCNs.

[0115] In addition to VNICs and VCN VRs, an NVD may execute various software (e.g., daemons) and include one or more hardware components that facilitate the various network virtualization functions performed by the NVD. For purposes of simplicity, these various components are grouped together as "packet processing components" shown in FIG. 2. For example, NVD 210 comprises packet processing components 286 and NVD 212 comprises packet processing components 288. For example, the packet processing components for an NVD may include a packet processor that is configured to interact with the NVD's ports and hardware interfaces to monitor all packets received by and communicated using the NVD and store network information. The network information may, for example, include network flow information identifying different network flows handled by the VD and per flow information (e.g., per flow statistics). In certain embodiments, network flows information may be stored on a per VNIC basis. The packet processor may perform packet-by-packet manipulations as well as implement stateful NAT and L4 firewall (FW). As another example, the packet processing components may- include a replication agent that is configured to replicate information stored by the NVD to one or more different replication target stores. As yet another example, the packet processing components may include a logging agent that is configured to perform logging functions for the NVD. The packet processing components may also include software for monitoring the performance and health of the NVD and, also possibly of monitoring the state and health of other components connected to the NVD,Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0116] FIG. 1 shows the components of an example virtual or overlay network including a VCN, subnets within the VCN, compute instances deployed on subnets, VNICs associated with the compute instances, a VR for a VCN, and a set of gateways configured for the VCN. The overlay components depicted in FIG. 1 may be executed or hosted by one or more of the physical components depicted in FIG. 2. For example, the compute instances in a VCN may be executed or hosted by one or more host machines depicted m FIG. 2. For a compute instance hosted by a host machine, the VNIC associated with that compute instance is typically executed by an NVD connected to that host machine (i.e., the VNIC functionality is provided by the NVD connected to that host machine). The VCN VR function for a VCN is executed by all the NVDs that are connected to host machines hosting or executing the compute instances that are part of that VCN. The gateways associated with a VCN may be executed by one or more different types of NVDs. For example, certain gateways may be executed by smartNICs, while others may be executed by one or more host machines or other implementations of NVDs.

[0117] As described above, a compute instance in a customer VCN may communicate with various different endpoints, where the endpoints can be within the same subnet as the source compute instance, m a different subnet but within the same VCN as the source compute instance, or with an endpoint that is outside the VCN of the source compute instance. These communications are facilitated using VNICs associated with the compute instances, the VCN VRs, and the gateways associated with the VCNs.

[0118] For communications between two compute instances on the same subnet in a VCN, the communication is facilitated using VNICs associated with the source and destination compute instances. The source and destination compute instances may be hosted by the same host machine or by different host machines. A packet originating from a source compute instance may be forwarded from a host machine hosting the source compute instance to an NVD connected to that host machine. On the NVD, the packet is processed using a packet processing pipeline, which can include execution of the VNIC associated with the source compute instance. Since the destination endpoint for the packet is within the same subnet, execution of the ATTIC associated with the source compute instance results in the packet being forwarded to an NVD executing the VNIC associated with the destination compute instance, which then processes and forwards the packet to the destination compute instance. The VNICs associated with the source and destination compute instances may be executed on the same NVD (e.g., when both the source and destination computeAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) instances are hosted by the same host machine) or on different NVDs (e.g., when the source and destination compute instances are hosted by different host machines connected to different NVDs). The VNICs may use routing / forwarding tables stored by the NVD to determine the next hop for the packet.

[0119] For a packet to be communicated from a compute instance in a subnet to an endpoint in a different subnet in the same VCN, the packet originating from the source compute instance is communicated from the host machine hosting the source compute instance to the NVD connected to that host machine. On the NVD, the packet is processed using a packet processing pipeline, which can include execution of one or more VNICs, and the VR associated with the VCN. For example, as part of the packet processing pipeline, the NVD executes or invokes functionality corresponding to the VNIC (also referred to as executes the VNIC) associated with source compute instance. The functionality performed by the VNIC may include looking at the VLAN tag on the packet. Since the packet's destination is outside the subnet, the VCN VR functionality is next invoked and executed by the NVD. The VCN VR then routes the packet to the NVD executing the VNIC associated with the destination compute instance. The VNIC associated with the destination compute instance then processes the packet and forwards the packet to the destination compute instance. The VNICs associated with the source and destination compute instances may be executed on the same NVD (e.g., when both the source and destination compute instances are hosted by the same host machine) or on different NVDs (e.g., when the source and destination compute instances are hosted by different host machines connected to different NVDs).

[0120] If the destination for the packet is outside the V CN of the source compute instance, then the packet originating from the source compute instance is communicated from the host machine hosting the source compute instance to the NVD connected to that host machine. The NVD executes the VNIC associated with the source compute instance. Since the destination end point of the packet is outside the VCN, the packet is then processed by the VCN VR for that VCN. The NVD invokes the VCN VR functionality, w’hich may result in the packet being forwarded to an NVD executing the appropriate gateway associated with the VCN. For example, if the destination is an endpoint within the customer's on-premise network, then the packet may be forwarded by the VCN VR to the NVD executing the DRG gateway configured for the VCN. The V CN VR may¬ be executed on the same NVD as the NVD executing the VNIC associated with the source compute instance or by a different NVD, The gateway may be executed by an NVD, which may be aAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) smartNIC, a host machine, or other NVD implementation. The packet is then processed by the gateway and forwarded to a next hop that facilitates communication of the packet to its intended destination endpoint. For example, in the embodiment depicted in FIG. 2, a packet originating from compute instance 268 may be communicated from host machine 202 to NVD 210 over link 220 (using NIC 232). On NVD 210, VNIC 276 is invoked since it is the VNIC associated with source compute instance 268. VNIC 276 is configured to examine the encapsulated information in the packet, and determine a next hop for forwarding the packet with the goal of facilitating communication of the packet to its intended destination endpoint, and then forward the packet to the determined next hop.

[0121] A compute instance deployed on a VCN can communicate with various different endpoints. These endpoints may include endpoints that are hosted by CSPI 200 and endpoints outside CSPI 200. Endpoints hosted by CSPI 200 may include instances in the same VCN or other VCNs, which may be the customer's VCNs, or VCNs not belonging to the customer. Communications between endpoints hosted by CSPI 200 may be performed over physical network 218. A compute instance may also communicate with endpoints that are not hosted by CSPI 200, or are outside CSPI 200. Examples of these endpoints include endpoints within a customer’s on¬ premise network or data center, or public endpoints accessible over a public network such as the Internet. Communications with endpoints outside CSPI 200 may be performed over public networks (e.g., the Internet) (not shown in FIG. 2) or private networks (not shown in FIG. 2) using various communication protocols.

[0122] The architecture of CSPI 200 depicted in FIG. 2 is merely an example and is not intended to be limiting. Variations, alternatives, and modifications are possible in alternative embodiments. For example, in some implementations, CSPI 200 may have more or fewer systems or components than those shown in FIG. 2, may combine two or more systems, or may have a different configuration or arrangement of systems. The systems, subsystems, and other components depicted in FIG. 2 may be implemented in software (e.g., code, instructions, program) executed by one or more processing units (e.g., processors, cores) of the respective systems, using hardware, or combinations thereof. The software may be stored on a non-transitory storage medium (e.g., on a memory device).

[0123] FIG. 4 depicts connectivity between a host machine and an NVD for providing I / O virtualization for supporting multitenancy according to certain embodiments. As depicted in FIG.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 4, host machine 402 executes a hypervisor 404 that provides a virtualized environment. Host machine 402 executes two virtual machine instances, VM1 406 belonging to custom er / tenant #1 and VM2 408 belonging to customer / tenant #2. Host machine 402 comprises a physical NIC 410 that is connected to an NVD 412 via link 414. Each of the compute instances is attached to a VNIC that is executed by NVD 412. In the embodiment in FIG, 4, VM1 406 is attached to VNIC-VM1 420 and VM2 408 is attached to VNIC-VM2 422.

[0124] As shown in FIG. 4, NIC 410 comprises two logical NICs, logical NIC A 416 and logical NIC B 418. Each virtual machine is attached to and configured to work with its own logical NIC. For example, VM1 406 is attached to logical NIC A 416 and VM2 408 is attached to logical NIC B 418. Even though host machine 402 comprises only one physical NIC 410 that is shared by the multiple tenants, due to the logical NICs, each tenant’s virtual machine believes they have their own host machine and NIC.

[0125] In certain embodiments, each logical NIC is assigned to its own VLAN ID. Thus, a specific VLAN ID is assigned to logical NIC A 416 for Tenant #1 and a separate VLAN ID is assigned to logical NIC B 418 for Tenant #2. When a packet is communicated from VM1 406, a tag assigned to Tenant #1 is attached to the packet by the hypervisor and the packet is then communicated from host machine 402 to NVD 412 over link 414. In a similar manner, when a packet is communicated from VM2 408, a tag assigned to Tenant #2 is attached to the packet by the hypervisor and the packet is then communicated from host machine 402 to NVD 412 over link 414. Accordingly, a packet 424 communicated from host machine 402 to NVD 412 has an associated tag 426 that identifies a specific tenant and associated VM. On the NVD, for a packet 424 received from host machine 402, the tag 426 associated with the packet is used to determine whether the packet is to be processed by VNIC-VM1 420 or by VNIC-VM2 422. The packet is then processed by the corresponding VNIC. The configuration depicted in FIG. 4 enables each tenant's compute instance to believe that they own their own host machine and NIC. The setup depicted in FIG. 4 provides for I / O virtualization for supporting multi-tenancy.

[0126] FIG. 5 depicts a simplified block diagram of a physical network 500 according to certain embodiments. The embodiment depicted in FIG. 5 is structured as a Clos network. A Clos network is a particular type of network topology designed to provide connection redundancy while maintaining high bisection bandwidth and maximum resource utilization. A Clos network is a type of non-blocking, multistage or multi-tiered switching network, where the number of stages orAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) tiers can be two, three, four, five, etc. The embodiment depicted in FIG. 5 is a 3 -tiered network comprising tiers 1, 2, and 3. The TOR switches 504 represent Tier-0 switches in the Clos network. One or more NVDs are connected to the TOR switches. Tier-0 switches are also referred to as edge devices of the physical network. The Tier-0 switches are connected to Tier-1 switches, which are also referred to as leaf switches. In the embodiment depicted in FIG, 5, a set of "n" Tier-0 TOR switches are connected to a set of "n" Tier-1 switches and together form a pod. Each Tier-0 switch in a pod is interconnected to all the Tier-1 switches in the pod, but there is no connectivity of switches between pods. In certain implementations, two pods are referred to as a block. Each block is served by or connected to a set of "n" Tier-2 switches (sometimes referred to as spine switches). There can be several blocks in the physical network topology. The Tier-2 switches are in turn connected to "n" Tier-3 switches (sometimes referred to as super-spine switches). Communication of packets over physical network 500 is typically performed using one or more Layer-3 communication protocols. Typically, all the layers of the physical network, except for the TORs layer are n-ways redundant thus allowing for high availability. Policies may be specified for pods and blocks to control the visibility of switches to each other in the physical network so as to enable scaling of the physical network.

[0127] A feature of a Clos network is that the maximum hop count to reach from one Tier-0 switch to another Tier-0 switch (or from an NVD connected to a Tier-0- switch to another NVD connected to a Tier-0 switch) is fixed. For example, in a 3 - Tiered Clos network at most seven hops are needed for a packet to reach from one NVD to another N VD, where the source and target N VDs are connected to the leaf tier of the Clos network. Likewise, in a 4-tiered Clos network, at most nine hops are needed for a packet to reach from one N VD to another NVD, where the source and target NVDs are connected to the leaf tier of the Clos network. Thus, a Clos network architecture maintains consistent latency throughout the network, which is important for communication within and between data centers. A Clos topology scales horizontally and is cost effective. The bandwidth / throughput capacity of the network can be easily increased by adding more switches at the various tiers (e.g., more leaf and spine switches) and by increasing the number of links between the switches at adjacent tiers.

[0128] In certain embodiments, each resource within CSPI is assigned a unique identifier called a Cloud Identifier (CID). This identifier is included as part of the resource's information and canAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) be used to manage the resource, for example, via a Console or through APIs. An example syntax for a CID is:ocidl < RESOURCE TYPE>.< REALM>.[REGION][. FUTURE USE].< UNIQUE ID> where,ocid1: The literal string indicating the version of the CID;resource type: The type of resource (for example, instance, volume, VCN, subnet, user, group, and so on);realm: The realm the resource is in. Example values are "cl" for the commercial realm, "c2" for the Government Cloud realm, or "c3" for the Federal Government Cloud realm, etc. Each realm may have its own domain name;region: The region the resource is in. If the region is not applicable to the resource, this part might be blank;future use: Reserved for future use.unique ID: The unique portion of the ID. The format may vary depending on the type of resource or service.Network Fabrics- Scalability

[0129] Network fabrics for graphical processing units (GPUs) are high-bandwidth, low- latency interconnects (e.g., InfiniBand network fabric) that couple multiple GPUs for large-scale artificial intelligence or high-performance compute applications. In the context of networking, particularly in high-performance computing and data centers, the network fabric is typically scaled by communicatively coupling a plurality of switches / routers together. The level at which the network fabric is scaled may be determined by a radix of a switch i.e., the number of ports or connections a switch has. Higher radix switches can be beneficial because they reduce the number of hops (e.g., intermediate switches) the data needs to traverse to reach its destination. Deploying higher radix switches in the network fabrics thus leads to lower latency and improved performance.

[0130] The following description uses an InfiniBand™ (IB) network as an example for a high performance network. It will be apparent to those skilled in the art that other types of high performance networks can be used without limitation. Further, the topology of the IB network may be a fat-tree topology or other types of fabric topologies without limitation.

[0131] InfiniBand™ (IB) is an open standard lossless network technology developed by the InfiniBand™ Trade Association. The technology is based on a serial point-to-point full-duplexAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) interconnect that offers high throughput and low latency communication, geared particularly towards high-performance computing (HPC) applications and datacenters. The InfiniBand™ Architecture (IBA) supports a two-layer topological division. At the lower layer, IB networks are referred to as subnets, where a subnet can include a set of hosts interconnected using switches and point-to-point links. At the higher level, an IB fabric constitutes one or more subnets, which can be interconnected using routers.

[0132] Within a subnet, hosts can be connected using switches and point-to-point links. Additionally, there can be a master management entity, the subnet manager (SM), which resides on a designated subnet device in the subnet. The subnet manager is responsible for configuring, activating and maintaining the IB subnet. Additionally, the subnet manager (SM) can be responsible for performing routing table calculations in an IB fabric. For example, the routing of the IB network aims at proper load balancing between all source and destination pairs in the local subnet.

[0133] Scalability in GPU network fabrics is fundamentally about enabling thousands -or even tens of thousands -of GPUs to communicate with extremely low latency and very high bandwidth while maintaining near-linear performance scaling for distributed training and inference workloads. Unlike traditional data center traffic, GPU workloads (such as large-scale Al model training) generate intensive east-west traffic dominated by collective communication patterns like all-reduce, all-gather, and broadcast. If the fabric cannot sustain full bisection bandwidth with minimal congestion, training efficiency drops sharply as cluster size increases.

[0134] Modern GPU clusters often rely on high-performance interconnects such as InfiniBand and NVLink to provide scalable bandwidth within and across nodes. Within a server, NVLink enables GPUs to share memory coherently at very high speeds. Across servers, InfiniBand fabrics use features like Remote Direct Memory Access (RDMA), adaptive routing, and congestion control to minimize CPU overhead and reduce latency. Scalable topologies — often based on Clos or dragonfly architectures allow operators to expand clusters by adding additional tiers without disrupting existing workloads, preserving performance predictability as the system grows. However, the inclusion of additional tiers of switches in the network architecture (to achieve scalability) is not a cost effective solution and moreover increases the complexity of the control plane that manages the network fabric. Aspects of the present disclosure describe a newAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) architecture for network fabrics that is directed at developing multiplanar two-tier fabrics that achieve greater scalability than traditional network fabrics.

[0135] FIG. 6 depicts an exemplary rack 600 housing network resources, according to certain embodiments. The rack 600 includes a body (or frame) 605 that houses a plurality of compute trays (e.g,, compute trays 610, 615) and a plurality of switch trays (e.g., switch trays 620). In some implementations, the rack 600 includes a total of 18 compute trays and 9 switch trays. The switch trays 620 include one or more switches that communicatively couple the GPUs (housed in different compute trays, e.g., 610 and 615) across the rack 600.

[0136] Each compute tray (e.g., compute tray 610A) is a separate bare metal host which includes, for instance, 4 GPUs and 2 CPUs. Each GPU included in a compute tray is communicatively coupled via high speed bi-directional communication links to each switch included in the plurality of switch trays 620. A detailed architecture of a singular compute tray (e.g., compute tray 610A) and a switch tray (620A) are described below with reference to FIG. 7. Thus, in one implementation, the rack 600 of FIG. 6 provides for a total of 72 GPUs across 18 compute trays and provides for a total of 30 TB of unified memory. In order for customers (of a different cloud environment), it is appreciated that they will need to build and manage their GPU clusters, which implies that they will need the ability to manage the lifecycle of the underlying instances at the rack level.

[0137] Turning now to FIG. 7, there is illustrated an exemplary compute tray included in a rack, according to certain embodiments. The architecture 700 depicted in FIG. 7 illustrates a compute tray 701 that is coupled to a plurality of switch trays e.g., switch trays 710, 715. The compute tray 701 depicted in FIG. 7 can correspond to the compute tray 610A of FIG. 6. It is appreciated that the compute tray 701 and the plurality of switch trays (e.g., switch trays 710 and 715) are included in a single rack (e.g., rack 600 of FIG. 6).

[0138] The compute tray 701 includes a plurality of GPUs (e.g., GPUs 702, 703, 704, and 705) and a pair of CPUs 706A and 706B. Each CPU is coupled to a compute memory 721A and 721B, respectively. The compute tray 701 further includes a plurality of host network interface cards (i.e., host NICs) (e.g., 725A, 725B, 725C, 725D, and 726), and a pair of smart NICs 730A and 730B. Each switch tray includes a pair of switches and a switch controller. For instance, switch tray 710 includes a pair of switches (712A and 712B) and a switch controller 714, whereas switch tray 715 includes a pair of switches (717A and 717B) and a switch controller 718, Each GPU included inAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) the compute tray 701 is communicatively coupled to each switch included in each switch tray via a high-speed, low latency communication link (e.g, NV Link). It is noted that GPUs included in other compute trays of the rack are communicatively coupled to each switch included in each switch tray as described above. In this manner, the configuration of the compute tray and switch trays provides for each GPU being communicatively coupled to every other GPU in the rack thereby providing for a framework, where GPUs share memory resources (i.e., including CPU memory).

[0139] Further, as depicted in FIG. 7, the compute tray 701 is communicatively coupled with a compute network fabric 745 (i.e., network fabric where compute / hosts reside) via the pair of smartNICs 730A and 730B. Additionally, the compute tray is communicatively coupled to plurality of Tier–0 switches (e.g., 740A, 740B, 740C, and 740D) of a network fabric (e.g., InfiniBand network fabric) via the NICs 725A, 725B, 725C, and 725D respectively. It is appreciated that the plurality of Tier-0 switches forms a first layer of switches in a hierarchy of switch layers as shown in the network topology of the network fabric in FIG. 8B. Thus, it can be seen that communicatively coupling the compute tray 701 to the plurality of Tier-0 switches (e.g., 740 A, 740B, 740C, and 740D) of the network fabric, provisions scalability i.e., the compute rack 701 can be communicatively coupled to other compute racks via the network fabric i.e., the network can scale out.

[0140] FIG. 8A illustrates an exemplary switch included in a network fabric, according to certain embodiments. For instance, the switch depicted in FIG. 8A may correspond to switch 740A as depicted in FIG. 7. The switch 740A includes a first plurality of uplink ports e.g., 72 uplink ports labeled 815, and a second plurality of downlink ports e.g., 72 downlink ports labeled 820. Each port of the switch is configured to be operated at a certain bandwidth e.g. 800G. As depicted in FIG. 8A, the switch 740A includes four internal Application-Specific Integrated Circuit (ASICs) labeled 801, 802, 803, and 804. It is appreciated that an ASIC corresponds to a custom-designed microchip that is built to perform a specific task or set of tasks e.g., data center switches that use ASICs to forward packets at high switching speeds.

[0141] As depicted in FIG. 8A, each ASIC has 144 X 200G ports. Thus, when an 800G NIC is connected to the switch, the 800G "link" is internally split into 200G "planes". A plane is defined herein as a set of links (both physical and internal) of the switch which provide a path of connectivity between GPUs. It is noted that the planes are independent of one another. TheseAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) planes (shown by different shading in FIG. 8A) are disjoint within the switch. It is noted that each of the 800G interfaces is split into 4x200G channels which are spread across the four independent ASICs 801-804, Thus, the ASICs 801-804 provide the ability to logically partition a high-performance fabric into isolated domains, so that multiple workloads, tenants, or applications can share the same physical infrastructure without interfering with each other. However, it is noted that each of the 200G channels i.e., from the ASIC, is not physically separated. Specifically, an 800G channel is logically split across 4 ASICs (each having a 200G channel), where all the channels are physically routed to the same output port of the switch. In other words, all the four channels are routed from an egress port of the switch to the same ingress port of a higher level switch.

[0142] Turning to FIG. 8B, there is illustrated an exemplary architecture of a network fabric 850, according to certain embodiments. The architecture of the network fabric 850 includes a plurality of blocks e.g., block 1 (852) – block 72 (872). Each block includes a plurality of racks and a plurality of switches that form a first tier of switches (labeled as TO-tier) in the network fabric. For instance, referring to block I (852), it can be seen that this block includes a plurality of racks (i.e., rack 1-rack 4) labeled 854A-854D and a plurality of switches included in a first tier of switches e.g., switches labeled T0-R1 (856A), T0-R2 (856B), T0-R3 (856C), and T0-R4 (856D). Similarly, block labeled 872 includes a plurality of racks (i.e., rack 1-rack 4) labeled 874A-874D and a plurality of switches included in the first tier of switches (T0-tier) e.g., switches labeled T0-R285 (876A), T0-R286 (876B), T0-R287 (876C), and T0-R288 (876D).

[0143] Each switch included in Tier-0 layer of switches can correspond to the switch as shown in FIG. 8A. Specifically, each switch in the Tier-0 tier has 72 downlink ports and 72 uplink ports. The switches in the TO-tier are coupled to the plurality of racks included in the respective blocks via the downlink ports. Further, as will be described in greater detail below, the switches in the TO-tier are communicatively coupled to switches in the T1-tier of switches via their respective uplink ports (e.g., uplink port of switch T0-R1 labeled 857A). The network fabric 850 includes a plurality of switches in the T1-tier of switches e.g., switches labeled 862, 864, 882, and 884. The plurality of switches in the T1-tier is coupled via their respective downlink ports (e.g., downlink port of switch T1-R1 labeled 866A) to the uplink ports of switches in the T0-tier,

[0144] In some implementations, scalability is achieved in the network fabric 850 via partitioning the uplink ports of the TO-tier switches and the downlink ports of the Tl-tier switches.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) Specifically, an uplink port of the switch is partitioned into a first plurality of sub-ports. For instance, consider the first uplink port 857A of the T0-tier switch 856A. Block 880 depicts a detailed version of the partitioning of the ports of switch 856A. In the example depicted in FIG. 8B, it is noted that the uplink port of the switch is partitioned into four sub-ports. As shown in block 880, the uplink port of the switch 856A is partitioned into 4 sub-ports labeled 859A, 859B, 859C, and 859D. Each sub-port is uniquely shaded to correspond to the different planes as described previously with reference to FIG. 8A. It is appreciated that for each switch included in the Tl-tier of switches (e.g., switches 862, 864, 882, and 884), the downlink ports of each switch are partitioned in a manner similar to that as the uplink ports of switches included in the TO-tier of switches.

[0145] It is appreciated that each sub-port included in the plurality of sub-ports of an uplink port of a switch included in the first tier of switches is addressable via a unique network address. Similarly, it is noted that each sub-port included in the plurality of sub-ports of a downlink port of a switch included in the second tier of switches is addressable via another unique network address. In the network fabric 850 of FIG. 8B, the partitioning of uplink ports of the switches included in the TO-tier of switches, as well as the partitioning of downlink ports of the switches included in the T1-tier of switches can be achieved via the use of a shuffle cable. A shuffle cable may include one or more connectors that enable the partitioning of a port of a switch into multiple sub-ports. For example, the shuffle cable can include a first connector can be coupled to a subset of sub-ports of a port of the switch. For instance, the first connector can be coupled to a first sub-port and a second sub-port of the port of a switch, while a second connector (included in the shuffle cable) can be coupled to a different subset of sub-ports of the port of the switch e.g., the second connector can be coupled to third and fourth sub-ports of the port of the switch.

[0146] Each of the first and second connectors may correspond to multi-fiber push on (MPO) connectors that incorporate multiple optical fibers (i.e., links) within them. For example, connector 1 can include two links, while connector 2 includes additional two links. In this manner, the port of a switch can be partitioned into a plurality of sub-ports e.g., four sub-ports, where each sub-port may be communicatively coupled to a different entity (e.g., different Tl-tier switches in the network fabric configuration of FIG. 8B. The combination of links within the connectors is referred to herein as a shuffle cable i.e,, a cable that is connected at one end to the port of a switch,Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) while at the other end is connected to different entities (e.g., different switches in another layer of network fabric),

[0147] According to some embodiments, scalability is achieved in the network fabric of FIG.8B by communicatively coupling subsets of the sub-ports of an uplink port of a switch included in the TO-tier of switches to different switches included in the Tl-tier of switches. For example, consider the first uplink port (857A) of a first TO-tier switch (856A). It can be seen from the detailed depiction in box 880 that the uplink port is partitioned into four sub-ports (859A, 859B, 859C, and 859D). In such a setting, a first pair of sub-ports (e.g,, sub-ports 859A and 859B) of the first uplink port are communicatively coupled to a corresponding pair of sub-ports of a downlink port of a Tl-tier switch (e.g., switch 862). In other words, the sub-ports 859A and 859B are communicatively coupled to the first and second sub-ports of the downlink port 1 of switch 862. Further, a second pair of sub-ports of the first uplink port (e.g., sub-ports 859C and 859D) are communicatively coupled to another corresponding pair of sub-ports of a downlink port of another Tl-tier switch (e.g., switch 864). Specifically, the sub-ports 859C and 859D are communicatively coupled to the third and fourth sub-ports of the downlink port 1 of switch 864.

[0148] In this manner, each subset of sub-ports of a port of a switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches. As compared to a traditional means of interconnecting ports of switches in a network fabric i.e., where a single port (or sub-ports) of a switch is connected to a single downlink port of another switch (i.e., same port), it can be seen that the partitioning of uplink / downlink ports of the switches results in using 144 switches in the T1-tier of switches and 288 switches in the T0-tier of switches. This enables the network fabric 850 to achieve scalability while maintaining the tiered network fabric architecture to a two-tier network (e.g., two -tier CLOS network) as opposed to using a three tier network to achieve scalability. The partitioning of uplink ports of TO-tier switches and the downlink ports of T1 -tier switches as described above thus results in fewer overall network devices (switches) being used as illustrated in an exemplary comparison shown in Table I below:Two Tier Three TierComponent Difference(Using Shuffle Cables) CIos NetworkTO Switches 288 288 0T1 Switches 144 288 144 device savingsAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) T2 Switches N / A 144 144 device savings288 devices saved = 50% cheaperTable I: Comparison of switches used in two-tier and three-tier network fabrics.

[0149] Thus, it is appreciated that by incorporating shuffle cables to achieve partitioning of ports (i.e., at the TO and IT layer of switches), the two-tier architecture of FIG. 8B achieves higher scalability (as compared to a traditional 3-tier CLOS topology of fabrics), while reducing a total number of hardware switches employed in the fabric. Additionally, it is noted that compared to standard routing protocols that are employed in network fabrics, a control plane managing the network fabric of FIG. 8B, may be required to incorporate updated routing protocols e.g., multiplane routing protocol, unique local identifier (LID) based routing protocols (i.e., where each plane may be treated effectively as an independent set of LIDs) or the like. Moreover, it is noted that the specific numbers e.g., partitioning a port into four sub-ports used with reference to FIG. 8B are merely for explanatory’ purposes and not intended to limit the scope of the present disclosure. Rather, other variations of port breakouts are well within the scope of the present disclosure. For example, a first uplink port of a first switch included in the first tier of switches that operates at a speed of 800G can be partitioned into one of: (i) eight sub-ports, where each sub-port operates at a speed of 100G, (li) four sub-ports, where each sub-port operates at a speed of 200G, or (iii) two sub-ports, where each sub-port operates at a speed of 400G.

[0150] FIG. 9 depicts a flowchart illustrating steps performed m achieving scalability in the network fabric, according to certain embodiments. The processing depicted in FIG. 9 may be implemented in software (e.g., code, instructions, program) executed by one or more processing units (e.g., processors, cores) of the respective systems, hardware, or combinations thereof. The software may be stored on a non-transitory storage medium (e.g., on a memory device). The method presented in FIG. 9 and described below is intended to be illustrative and non-limiting. Although FIG. 9 depicts the various processing steps occurring in a particular sequence or order, this is not intended to be limiting. In certain alternative embodiments, the steps may be performed in some different order or some steps may also be performed in parallel.

[0151] The process commences in step 905, where for a network of switches included in a multi-tier network fabric, an uplink port of each switch included in a first tier of switches is partitioned into a first plurality of sub-ports. For example, as described with reference to FIG. 8BAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) and referring to block 880, an uplink port of a TO-switch may be partitioned into four independent sub-ports of the switch. This can be achieved via utilizing shuffle cables. It is noted that each subport included in the first plurality of sub-ports of the uplink port of the switch (included in the first tier of switches) is addressable via a unique network address. Thereafter, in step 910, partitioning, a downlink port of each switch included in a second tier of switches (i.e., Tl-tier), is partitioned into the first plurality of sub-ports. For instance, referring to FIG. 8B, downlink ports of each of the switches 862, 864, 882, and 884 are partitioned into four sub-ports. Each sub-port, included in the first plurality of sub-ports of the downlink port of the switch included in the second tier of switches is addressable via another unique network address.

[0152] The process in step 915 generates, for each uplink port of each switch included in the first tier of switches (TO-tier), a plurality of subsets of sub-ports. For instance, referring to FIG.8B, the uplink port is partitioned into four sub-ports. One can generate two subsets of sub-ports e.g., a first subset including the first and second sub-port, and a second subset including the third and fourth sub-ports. Each subset of sub-ports of the switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches. Upon configuring the network fabric as described above in steps 905-915, in step 920, a packet is transmitted from a first GPU coupled to a first switch that is included in the first tier of switches to a second GPU coupled to a second switch that is also included in the first tier of switches, via utilizing one of the sub-ports (e.g., planes) of the uplink port of the first switch.Example Cloud Infrastructure

[0153] As noted above, infrastructure as a service (laaS) is one particular type of cloud computing. laaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In an laaS 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 laaS 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, laaS users may be able to implement policies to drive load balancing to maintain application availability and performance.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0154] In some instances, laaS 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 laaS 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,

[0155] In most cases, a cloud computing model will 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) laaS. An entity might also opt to deploy a private cloud, becoming its own provider of infrastructure services.

[0156] In some examples, laaS 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, network hardware, 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.

[0157] In some examples, laaS 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.

[0158] In some cases, there are two different challenges for laaS 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 beAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) generated that creates and / or manages the different components described in the configuration files.

[0159] 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.

[0160] 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 geographic locations, sometimes spanning the entire world). However, in some examples, the infrastructure on which the code will be deployed must 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.

[0161] FIG. 10 is a block diagram 1000 illustrating an example pattern of an laaS architecture, according to at least one embodiment. Service operators 1002 can be communicatively coupled to a secure host tenancy 1004 that can include a virtual cloud network ( VCN) 1006 and a secure host subnet 1008. In some examples, the service operators 1002 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 LinuxAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 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 1006 and / or the Internet.

[0162] The VCN 1006 can include a local peering gateway (LPG) 1010 that can be communicatively coupled to a secure shell (SSH) VCN 1012 via an LPG 1010 contained in the SSH VCN 1012. The SSH VCN 1012 can include an SSH subnet 1014, and the SSH VCN 1012 can be communicatively coupled to a control plane VCN 1016 via the LPG 1010 contained in the control plane VCN 1016. Also, the SSH VCN 1012 can be communicatively coupled to a data plane VCN 1018 via an LPG 1010. The control plane VCN 1016 and the data plane VCN 1018 can be contained in a service tenancy 1019 that can be owned and / or operated by the laaS provider.

[0163] The control plane VCN 1016 can include a control plane demilitarized zone (DMZ) tier 1020 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 1020 can include one or more load balancer (LB) subnet(s) 1022, a control plane app tier 1024 that can include app subnet(s) 1026, a control plane data tier 1028 that can include database (DB) subnet(s) 1030 (e.g., frontend DB subnet(s) and / or backend DB subnet(s)). 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 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 and a network address translation (NAT) gateway 1038. The control plane VCN 1016 can include the service gateway 1036 and the NAT gateway 1038.

[0164] The control plane VCN 1016 can include a data plane mirror app tier 1040 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 that can execute a compute instance 1044. The compute instance 1044 can communicatively couple the app subnet(s) 1026 ofAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) the data plane mirror app tier 1040 to app subnet(s) 1026 that can be contained in a data plane app tier 1046.

[0165] The data plane VCN 1018 can include the data plane app tier 1046, a data plane DMZ tier 1048, and a data plane data tier 1050. The data plane DMZ tier 1048 can include LB subnet(s) 1022 that can be communicatively coupled to the app subnet(s) 1026 of the data plane app tier 1046 and the Internet gateway 1034 of the data plane VCN 1018. The app subnet(s) 1026 can be communicatively coupled to the service gateway 1036 of the data plane VCN 1018 and the NAT gateway 1038 of the data plane VCN 1018. The data plane data tier 1050 can also include the DB subnet(s) 1030 that can be communicatively coupled to the app subnet(s) 1026 of the data plane app tier 1046.

[0166] The Internet gateway 1034 of the control plane VCN 1016 and of the data plane VCN 1018 can be communicatively coupled to a metadata management service 1052 that can be communicatively coupled to public Internet 1054. Public Internet 1054 can be communicatively coupled to the NAT gateway 1038 of the control plane VCN 1016 and of the data plane VCN 1018. The service gateway 1036 of the control plane VCN 1016 and of the data plane VCN 1018 can be communicatively coupled to cloud services 1056.

[0167] In some examples, the service gateway 1036 of the control plane VCN 1016 or of the data plane VCN 1018 can make application programming interface (API) calls to cloud services 1056 without going through public Internet 1054. The API calls to cloud services 1056 from the service gateway 1036 can be one-way: the service gateway 1036 can make API calls to cloud services 1056, and cloud services 1056 can send requested data to the service gateway 1036. But, cloud services 1056 may not initiate API calls to the service gateway 1036.

[0168] In some examples, the secure host tenancy 1004 can be directly connected to the service tenancy 1019, which may be otherwise isolated. The secure host subnet 1008 can communicate with the SSH subnet 1014 through an LPG 1010 that may enable tw’O-way communication over an otherwise isolated system. Connecting the secure host subnet 1008 to the SSH subnet 1014 may give the secure host subnet 1008 access to other entities within the service tenancy 1019.

[0169] The control plane VCN 1016 may allow users of the service tenancy 1019 to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN 1016 may be deployed or otherwise used in the data plane VCN 1018. In some examples, the control plane VCN 1016 can be isolated from the data plane VCN 1018, and the data plane mirrorAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) app tier 1040 of the control plane VCN 1016 can communicate with the data plane app tier 1046 of the data plane VCN 1018 via VNICs 1042 that can be contained in the data plane mirror app tier 1040 and the data plane app tier 1046.

[0170] In some examples, users of the system, or customers, can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet 1054 that can communicate the requests to the metadata management service 1052. The metadata management service 1052 can communicate the request to the control plane VCN 1016 through the Internet gateway 1034, The request can be received by the LB subnet(s) 1022 contained in the control plane DMZ tier 1020. The LB subnet(s) 1022 may determine that the request is valid, and in response to this determination, the LB subnet(s) 1022 can transmit the request to app subnet(s) 1026 contained in the control plane app tier 1024. If the request is validated and requires a call to public Internet 1054, the call to public Internet 1054 may be transmitted to the NAT gateway 1038 that can make the call to public Internet 1054. Metadata that may be desired to be stored by the request can be stored in the DB subnet(s) 1030.

[0171] In some examples, the data plane mirror app tier 1040 can facilitate direct communication between the control plane VCN 1016 and the data plane VCN 1018. 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 1018. Via a VNIC 1042, the control plane VCN 1016 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 1018.

[0172] In some embodiments, the control plane VCN 1016 and the data plane VCN 1018 can be contained in the service tenancy 1019. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN 1016 or the data plane VCN 1018. Instead, the laaS provider may own or operate the control plane VCN 1016 and the data plane VCN 1018, both of which may be contained in the service tenancy 1019. 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 1054, which may not have a desired level of threat prevention, for storage.

[0173] In other embodiments, the LB subnet(s) 1022 contained in the control plane VCN 1016 can be configured to receive a signal from the service gateway 1036. In this embodiment, theAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) control plane VCN 1016 and the data plane VCN 1018 may be configured to be called by a customer of the laaS provider without calling public Internet 1054. Customers of the laaS provider may desire this embodiment since database(s) that the customers use may be controlled by the laaS provider and may be stored on the service tenancy 1019, which may be isolated from public Internet 1054.

[0174] FIG. 11 is a block diagram 1100 illustrating another example pattern of an laaS architecture, according to at least one embodiment. Service operators 1102 (e.g,, service operators 1002 of FIG. 10) can be communicatively coupled to a secure host tenancy 1104 (e.g,, the secure host tenancy 1004 of FIG 10) that can include a virtual cloud network (VCN) 1106 (e.g., the VCN 1006 of FIG 10) and a secure host subnet 1108 (e.g., the secure host subnet 1008 of FIG. 10). The VCN 1106 can include a local peering gateway (LPG) 1110 (e.g., the LPG 1010 of FIG. 10) that can be communicatively coupled to a secure shell (SSH) VCN 1112 (e.g., the SSH VCN 1012 of FIG. 10) via an LPG 1010 contained in the SSH VCN 1112. The SSH VCN 1112 can include an SSH subnet 1114 (e.g., the SSH subnet 1014 of FIG. 10), and the SSH VCN 1112 can be communicatively coupled to a control plane VCN 1116 (e.g., the control plane VCN 1016 of FIG.10) via an LPG 1110 contained in the control plane VCN 1116. The control plane VCN 1116 can be contained in a service tenancy 1119 (e.g., the service tenancy 1019 of FIG. 10), and the data plane VCN 1118 (e.g., the data plane VCN 1018 of FIG. 10) can be contained in a customer tenancy 1121 that may be owned or operated by users, or customers, of the system.

[0175] The control plane VCN 1116 can include a control plane DMZ tier 1120 (e.g., the control plane DMZ tier 1020 of FIG. 10) that can include LB subnet(s) 1122 (e.g., LB subnet(s) 1022 of FIG. 10), a control plane app tier 1124 (e.g., the control plane app tier 1024 of FIG. 10) that can include app subnet(s) 1126 (e.g., app subnet(s) 1026 of FIG. 10), a control plane data tier 1128 (e.g., the control plane data tier 1028 of FIG. 10) that can include database (DB) subnet(s) 1130 (e.g., similar to DB subnet(s) 1030 of FIG. 10). 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 an Internet gateway 1134 (e.g., the Internet gateway 1034 of FIG. 10) 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 a service gateway 1136 (e.g., the service gateway 1036 of FIG. 10) and a network addressAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) translation (NAT) gateway 1138 (e.g., the NAT gateway 1038 of FIG. 10). The control plane VCN 1116 can include the service gateway 1136 and the NAT gateway 1138.

[0176] The control plane VCN 1116 can include a data plane mirror app tier 1140 (e.g., the data plane mirror app tier 1040 of FIG. 10) that can include app subnet(s) 1126. The app subnet(s) 1126 contained in the data plane mirror app tier 1140 can include a virtual network interface controller (VNIC) 1142 (e.g,, the VNIC of 1042) that can execute a compute instance 1144 (e.g., similar to the compute instance 1044 of FIG, 10). The compute instance 1144 can facilitate communication between the app subnet(s) 1126 of the data plane mirror app tier 1140 and the app subnet(s) 1126 that can be contained in a data plane app tier 1146 (e.g., the data plane app tier 1046 of FIG. 10) via the VNIC 1142 contained in the data plane mirror app tier 1140 and the VNIC 1142 contained in the data plane app tier 1146.

[0177] The Internet gateway 1134 contained in the control plane VCN 1116 can be communicatively coupled to a metadata management service 1152 (e.g., the metadata management service 1052 of FIG. 10) that can be communicatively coupled to public Internet 1154 (e.g., public Internet 1054 of FIG. 10). Public Internet 1154 can be communicatively coupled to the NAT gateway 1138 contained in the control plane VCN 1116. The service gateway 1136 contained in the control plane VCN 1116 can be communicatively coupled to cloud services 1156 (e.g., cloud services 1056 of FIG. 10).

[0178] In some examples, the data plane VCN 1118 can be contained in the customer tenancy 1121. In this case, the laaS provider may provide the control plane VCN 1116 for each customer, and the laaS provider may, for each customer, set up a unique compute instance 1144 that is contained in the service tenancy 1119. Each compute instance 1144 may allow communication between the control plane VCN 1116, contained in the service tenancy 1119, and the data plane VCN 1118 that is contained in the customer tenancy 1121. The compute instance 1144 may allow resources, that are provisioned in the control plane VCN 1116 that is contained in the service tenancy 1119, to be deployed or otherwise used in the data plane VCN 1118 that is contained in the customer tenancy 1121.

[0179] In other examples, the customer of the laaS provider may have databases that live in the customer tenancy 1121. In this example, the control plane VCN 1116 can include the data plane mirror app tier 1140 that can include app subnet(s) 1126. The data plane mirror app tier 1140 can reside in the data plane VCN 1118, but the data plane mirror app tier 1140 may not live in theAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) data plane VCN 1118. That is, the data plane mirror app tier 1140 may have access to the customer tenancy 1121, but the data plane mirror app tier 1140 may not exist in the data plane VCN 1118 or be owned or operated by the customer of the TaaS provider. The data plane mirror app tier 1140 may be configured to make calls to the data plane VCN 1118 but may not be configured to make calls to any entity contained in the control plane VCN 1116. The customer may desire to deploy or otherwise use resources in the data plane VCN 1118 that are provisioned in the control plane VCN 1116, and the data plane mirror app tier 1140 can facilitate the desired deployment, or other usage of resources, of the customer.

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

[0181] In some embodiments, cloud services 1156 can be called by the service gateway 1136 to access services that may not exist on public Internet 1154, on the control plane VCN 1116, or on the data plane VCN 1118. The connection between cloud services 1156 and the control plane VCN 1116 or the data plane VCN 1118 may not be live or continuous. Cloud services 1156 may exist on a different network owned or operated by the laaS provider. Cloud services 1156 may be configured to receive calls from the service gateway 1136 and may be configured to not receive calls from public Internet 1154. Some cloud services 1156 may be isolated from other cloud services 1156, and the control plane VCN 1116 may be isolated from cloud services 1156 that may not be in the same region as the control plane VCN 1116. For example, the control plane VCN 1116 may be located in “Region 1,” and cloud service “Deployment 10,” may be located in Region 1 and in “Region 2.” If a call to Deployment 10 is made by the service gateway 1136 contained in the control plane VCN 1116 located in Region 1, the call may be transmitted to Deployment 10 in Region 1. In this example, the control plane VCN 1116, or Deployment 10 in Region 1, may not be communicatively coupled to, or otherwise in communication with. Deployment 10 in Region 2.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0182] FIG. 12 is a block diagram 1200 illustrating another example pattern of an laaS architecture, according to at least one embodiment. Service operators 1202 (e.g., service operators 1002 of FIG. 10) can be communicatively coupled to a secure host tenancy 1204 (e.g., the secure host tenancy 1004 ofFIG. 10)thatcan include a virtual cloud network (VCN) 1206 (e.g., the VCN 1006 ofFIG. 10) and a secure host subnet 1208 (e g., the secure host subnet 1008 ofFIG. 10). The VCN 1206 can include an LPG 1210 (e.g., the LPG 1010 ofFIG. 10) that can be communicatively coupled to an SSH VCN 1212 (e.g., the SSH VCN 1012 ofFIG. 10) 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 1014 of FIG. 10), and the SSH VCN 1212 can be communicatively coupled to a control plane VCN 1216 (e.g., the control plane VCN 1016 ofFIG. 10) via an LPG 1210 contained in the control plane VCN 1216 and to a data plane VCN 1218 (e.g., the data plane 1018 ofFIG. 10) 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 1019 of FIG. 10).

[0183] The control plane VCN 1216 can include a control plane DMZ tier 1220 (e.g., the control plane DMZ tier 1020 ofFIG. 10) that can include load balancer (LB) subnet(s) 1222 (e.g., LB subnet(s) 1022 ofFIG 10), a control plane app tier 1224 (e.g., the control plane app tier 1024 of FIG. 10) that can include app subnet(s) 1226 (e.g., similar to app subnet(s) 1026 of FIG. 10), a control plane data tier 1228 (e.g., the control plane data tier 1028 of FIG. 10) that can include DB subnet(s) 1230. 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 1034 of FIG. 10) 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 ofFIG. 10) and a network address translation (NAT) gateway 1238 (e.g., the NAT gateway 1038 ofFIG. 10). The control plane VCN 1216 can include the service gateway 1236 and the NAT gateway 1238.

[0184] The data plane VCN 1218 can include a data plane app tier 1246 (e.g., the data plane app tier 1046 ofFIG. 10), a data plane DMZ tier 1248 (e.g., the data plane DMZ tier 1048 ofFIG.10), and a data plane data tier 1250 (e.g., the data plane data tier 1050 ofFIG. 10). The data plane DMZ tier 1248 can include LB subnet(s) 1222 that can be communicatively coupled to trusted app subnet(s) 1260 and untrusted app subnet(s) 1262 of the data plane app tier 1246 and the InternetAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 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 sendee 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.

[0185] The untrusted app subnet(s) 1262 can include one or more primary VNICs 1264(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1266(1)-(N). Each tenant VM 1266(1)-(N) can be communicatively coupled to a respective app subnet 1267(1)-(N) that can be contained in respective container egress VCNs 1268(1 )-(N) that can be contained in respective customer tenancies 1270(l)-(N). 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 VCNs 1268(1 )-(N). Each container egress VCNs 1268(1)-(N) can include a NAT gateway 1238 that can be communicatively coupled to public Internet 1254 (e.g., public Internet 1054 of FIG. 10).

[0186] 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 1052 of FIG. 10) 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.

[0187] In some embodiments, the data plane VCN 1218 can be integrated with customer tenancies 1270. This integration can be useful or desirable for customers of the laaS 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 laaS provider may determine whether to run code given to the laaS provider by the customer.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

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

[0189] In some embodiments, the trusted app subnet(s) 1260 may run code that may be owned or operated by the laaS provider. In this embodiment, the trusted app subnet(s) 1260 may be communicatively coupled to the DB subnet] s) 1230 and be configured to execute CRUD operations in the DB subnet(s) 1230. The untrusted app subnet(s) 1262 may be communicatively coupled to the DB subnet(s) 1230, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s) 1230. The containers 1271(1)-(N) that can be contained in the VM 1266(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s) 1230.

[0190] In other embodiments, the control plane VCN 1216 and the data plane VCN 1218 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 1216 and the data plane VCN 1218. However, communication can occur indirectly through at least one method. An LPG 1210 may be established by the laaS provider that can facilitate communication between the control plane VCN 1216 and the data plane VCN 1218, In another example, the control plane VCN 1216 or the data plane VCN 1218 can make a call to cloud services 1256 via the service gateway 1236, For example, a call to cloud services 1256 from the control plane VCN 1216 can include a request for a service that can communicate with the data plane VCN 1218.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0191] FIG. 13 is a block diagram 1300 illustrating another example pattern of an laaS architecture, according to at least one embodiment. Service operators 1302 (e.g., service operators 1002 of FIG. 10) can be communicatively coupled to a secure host tenancy 1304 (e.g., the secure host tenancy 1004 ofFIG. 10)thatcan include a virtual cloud network (VCN) 1306 (e.g., the VCN 1006 ofFIG. 10) and a secure host subnet 1308 (e g., the secure host subnet 1008 ofFIG. 10). The VCN 1306 can include an LPG 1310 (e.g., the LPG 1010 ofFIG. 10) that can be communicatively coupled to an SSH VCN 1312 (e.g., the SSH VCN 1012 ofFIG. 10) via an LPG 1310 contained in the SSH VCN 1312. The SSH VCN 1312 can include an SSH subnet 1314 (e.g., the SSH subnet 1014 of FIG. 10), and the SSH VCN 1312 can be communicatively coupled to a control plane VCN 1316 (e.g., the control plane VCN 1016 ofFIG. 10) via an LPG 1310 contained in the control plane VCN 1316 and to a data plane VCN 1318 (e.g., the data plane 1018 ofFIG. 10) via an LPG 1310 contained in the data plane VCN 1318. The control plane VCN 1316 and the data plane VCN 1318 can be contained in a service tenancy 1319 (e.g., the service tenancy 1019 of FIG. 10).

[0192] The control plane VCN 1316 can include a control plane DMZ tier 1320 (e.g., the control plane DMZ tier 1020 of FIG. 10) that can include LB subnet(s) 1322 (e.g., LB subnet(s) 1022 ofFIG. 10), a control plane app tier 1324 (e.g., the control plane app tier 1024 ofFIG. 10) that can include app subnet(s) 1326 (e.g., app subnet(s) 1026 of FIG. 10), a control plane data tier 1328 (e.g., the control plane data tier 1028 ofFIG. 10) that can include DB subnet(s) 1330 (e.g., DB subnet(s) 1230 of FIG. 12). The LB subnet(s) 1322 contained in the control plane DMZ tier 1320 can be communicatively coupled to the app subnet(s) 1326 contained in the control plane app tier 1324 and to an Internet gateway 1334 (e.g., the Internet gateway 1034 ofFIG. 10) that can be contained in the control plane VCN 1316, and the app subnet(s) 1326 can be communicatively coupled to the DB subnet(s) 1330 contained in the control plane data tier 1328 and to a service gateway 1336 (e.g., the service gateway of FIG. 10) and a network address translation (NAT) gateway 1338 (e.g., the NAT gateway 1038 ofFIG. 10). The control plane VCN 1316 can include the service gateway 1336 and the NAT gateway 1338.

[0193] The data plane VCN 1318 can include a data plane app tier 1346 (e.g., the data plane app tier 1046 ofFIG. 10), a data plane DMZ tier 1348 (e.g., the data plane DMZ tier 1048 ofFIG.10), and a data plane data tier 1350 (e.g., the data plane data tier 1050 ofFIG. 10). The data plane DMZ tier 1348 can include LB subnet(s) 1322 that can be communicatively coupled to trusted app subnet(s) 1360 (e.g., trusted app subnet(s) 1260 ofFIG 12) and untrusted app subnet(s) 1362 (e.g.,Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) untrusted app subnet(s) 1262 of FIG. 12) of the data plane app tier 1346 and the Internet gateway 1334 contained in the data plane VCN 1318. The trusted app subnet(s) 1360 can be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318, the NAT gateway 1338 contained in the data plane VCN 1318, and DB subnet(s) 1330 contained in the data plane data tier 1350. The untrusted app subnet(s) 1362 can be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318 and DB subnet(s) 1330 contained in the data plane data tier 1350, The data plane data tier 1350 can include DB subnet(s) 1330 that can be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318.

[0194] The untrusted app subnet(s) 1362 can include primary VNICs 1364(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1366(1)-(N) residing within the untrusted app subnet(s) 1362. Each tenant VM 1366(1)-(N) can run code in a respective container 1367(1 )-(N), and be communicatively coupled to an app subnet 1326 that can be contained in a data plane app tier 1346 that can be contained in a container egress VCN 1368. Respective secondary VNICs 1372(1)-(N) can facilitate communication between the untrusted app subnet(s) 1362 contained in the data plane VCN 1318 and the app subnet contained in the container egress VCN 1368. The container egress VCN can include a NAT gateway 1338 that can be communicatively coupled to public Internet 1354 (e.g., public Internet 1054 of FIG. 10).

[0195] The Internet gateway 1334 contained in the control plane VCN 1316 and contained in the data plane VCN 1318 can be communicatively coupled to a metadata management service 1352 (e.g., the metadata management system 1052 of FIG. 10) that can be communicatively coupled to public Internet 1354. Public Internet 1354 can be communicatively coupled to the NAT gateway 1338 contained in the control plane VCN 1316 and contained in the data plane VCN 1318. The service gateway 1336 contained in the control plane VCN 1316 and contained in the data plane VCN 1318 can be communicatively coupled to cloud services 1356.

[0196] In some examples, the pattern illustrated by the architecture of block diagram 1300 of FIG. 13 may be considered an exception to the pattern illustrated by the architecture of block diagram 1200 of FIG. 12 and may be desirable for a customer of the TaaS provider if the laaS provider cannot directly communicate with the customer (e.g., a disconnected region). The respective containers 1367(1)-(N) that are contained in the VMs 1366(1)-(N) for each customer can be accessed in real-time by the customer. The containers 1367(1)-(N) may be configured toAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) make calls to respective secondary VNICs 1372(1)-(N) contained in app subnet(s) 1326 of the data plane app tier 1346 that can be contained in the container egress VCN 1368. The secondary VNICs 1372(1)-(N) can transmit the calls to the NAT gateway 1338 that may transmit the calls to public Internet 1354. In this example, the containers 1367(1 )-(N) that can be accessed in real-time by the customer can be isolated from the control plane VCN 1316 and can be isolated from other entities contained in the data plane VCN 1318. The containers 1367(1)-(N) may also be isolated from resources from other customers,

[0197] In other examples, the customer can use the containers 1367(1 )-(N) to call cloud services 1356. In this example, the customer may run code in the containers 1367(1)-(N) that requests a service from cloud services 1356. The containers 1367(1)-(N) can transmit this request to the secondary VNICs 1372(1 )-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet 1354. Public Internet 1354 can transmit the request to LB subnet(s) 1322 contained in the control plane VCN 1316 via the Internet gateway 1334. In response to determining the request is valid, the LB subnet(s) can transmit the request to app subnet(s) 1326 that can transmit the request to cloud services 1356 via the service gateway 1336.

[0198] It should be appreciated that laaS architectures 1000, 1100, 1200, 1300 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 laaS 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.

[0199] In certain embodiments, the laaS 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 laaS system is the Oracle Cloud Infrastructure (OCI) provided by the present assignee.

[0200] FIG. 14 illustrates an example computer system 1400, in which various embodiments may be implemented. The system 1400 may be used to implement any of the computer systems described above. As shown in the figure, computer system 1400 includes a processing unit 1404 that communicates with a number of peripheral subsystems via a bus subsystem 1402. These peripheral subsystems may include a processing acceleration unit 1406, an I / O subsystem 1408, aAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) storage subsystem 1418 and a communications subsystem 1424. Storage subsystem 1418 includes tangible computer- readable storage media 1422 and a system memory 1410.

[0201] Bus subsystem 1402 provides a mechanism for letting the various components and subsystems of computer system 1400 communicate with each other as intended. Although bus subsystem 1402 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1402 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.

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

[0203] In various embodiments, processing unit 1404 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) 1404 and / or in storage subsystem 1418. Through suitable programming, processor(s) 1404 can provide various functionalities described above. Computer system 1400 may additionally include a processing acceleration unit 1406, which can include a digital signal processor (DSP), a special-purpose processor, and / or the like.

[0204] I / O subsystem 1408 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,Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 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.

[0205] 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.

[0206] User interface output devices may include a display subsystem, indicator lights, or nonvisual 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 ciystal 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 1400 to a user or other computer. For example, user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio / video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.

[0207] Computer system 1400 may comprise a storage subsystem 1418 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 canAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) include programs, code modules, instructions, scripts, etc., that when executed by one or more cores or processors of processing unit 1404 provide the functionality described above. Storage subsystem 1418 may also provide a repository for storing data used in accordance with the present disclosure,

[0208] As depicted in the example in FIG. 14, storage subsystem 1418 can include various components including a system memory 1410, computer-readable storage media 1422, and a computer readable storage media reader 1420. System memory 1410 may store program instructions that are loadable and executable by processing unit 1404. System memory 1410 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 1410 including but not limited to client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), virtual machines, containers, etc.

[0209] System memory 1410 may also store an operating system 1416. Examples of operating system 1416 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 1400 executes one or more virtual machines, the virtual machines along with their guest operating systems (GOSs) may be loaded into system memory 1410 and executed by one or more processors or cores of processing unit 1404.

[0210] System memory 1410 can come in different configurations depending upon the type of computer system 1400. For example, system memory 1410 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 1410 may include a basic input / output system (BIOS) containing basic routines that help to transfer information between elements within computer system 1400, such as during start-up.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0211] Computer-readable storage media 1422 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 1400 including instructions executable by processing unit 1404 of computer system 1400.

[0212] Computer-readable storage media 1422 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.

[0213] By way of example, computer-readable storage media 1422 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 1422 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 1422 may also include, solid-state drives (SSD) based on non-volatile memory such as flashmemory 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-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for computer system 1400.

[0214] Machine-readable instructions executable by one or more processors or cores of processing unit 1404 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 mediaAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) (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.

[0215] Communications subsystem 1424 provides an interface to other computer systems and networks. Communications subsystem 1424 serves as an interface for receiving data from and transmitting data to other systems from computer system 1400, For example, communications subsystem 1424 may enable computer system 1400 to connect to one or more devices via the Internet, In some embodiments communications subsystem 1424 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 1424 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.

[0216] In some embodiments, communications subsystem 1424 may also receive input communication in the form of structured and / or unstructured data feeds 1426, event streams 1428, event updates 1430, and the like on behalf of one or more users who may use computer system 1400.

[0217] By way of example, communications subsystem 1424 may be configured to receive data feeds 1426 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.

[0218] Additionally, communications subsystem 1424 may also be configured to receive data in the form of continuous data streams, which may include event streams 1428 of real-time events and / or event updates 1430, 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.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0219] Communications subsystem 1424 may also be configured to output the structured and / or unstructured data feeds 1426, event streams 1428, event updates 1430, 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 1400,

[0220] Computer system 1400 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.

[0221] Due to the ever-changing nature of computers and networks, the description of computer system 1400 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.

[0222] 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 the present 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.

[0223] 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 toAttorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834) 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.

[0224] 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.

[0225] 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 methods described 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 m the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.

[0226] 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.Attorney Docket No. 088325-1543445 (519000PC)Client Ref. No. ORC25139881-WO-PCT (laaS #834)

[0227] 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,

[0228] 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.

[0229] 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 IS1. A method comprising:for a network of switches included in a multi-tier network fabric, partitioning, for each switch included in a first tier of switches, an uplink port of the switch into a first plurality of subports;partitioning, for each switch included in a second tier of switches, a downlink port of the switch into the first plurality of sub-ports;generating, for each uplink port of each switch included in the first tier of switches, a plurality of subsets of sub-ports, wherein each subset of sub-ports of the switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches; andtransmitting a packet from a first GPU coupled to a first switch included in the first tier of switches to a second GPU coupled to a second switch included in the first tier of switches via utilizing one of the sub-ports of the uplink port of the first switch.

2. The method of claim 1, wherein each sub-port included in the first plurality of sub-ports of the uplink port of the switch included in the first tier of switches is addressable via a unique network address.

3. The method of claim 2, wherein each sub-port included in the first plurality of sub-ports of the downlink port of the switch included in the second tier of switches is addressable via another unique network address.

4. The method of claim 1, wherein the multi-tier network fabric is a two-tier CLOS network comprising the first tier of switches and the second tier of switches, wherein each switch in the first tier of switches is connected to a plurality of GPU racks at one end and to a plurality of switches included in the second tier of switches at another end.

5. The method of claim 1, wherein the multi-tier network fabric is an InfiniBand network fabric.

6. The method of claim 1, wherein a first uplink port of the first switch included in the first tier of switches operates at a speed of 800G, and wherein the first port is partitioned into four sub-ports, where each sub-port operates at a speed of 200G.

7. The method of claim 1, wherein a first uplink port of a first switch included in the first tier of switches is partitioned into four sub-ports, wherein a first pair of sub-ports of the first uplink port are communicatively coupled to a corresponding pair of sub-ports of the downlink port of a second switch included in the second tier of switches, and wherein a second pair of sub-ports of the first uplink port are communicatively coupled to another corresponding pair of sub-ports of the downlink port of a third switch included in the second tier of switches, the third switch being different from the second switch.

8. The method of claim 1, wherein a first number of switches included in the first tier of switches in the multi-tier network fabric is greater than a second number of switches included in the second tier of switches in the multi-tier network fabric.

9. A computer readable medium storing specific computer-executable instructions that, when executed by a processor, cause a computer system for:for a network of switches included in a multi-tier network fabric, partitioning, for each switch included in a first tier of switches, an uplink port of the switch into a first plurality of subports;partitioning, for each switch included in a second tier of switches, a downlink port of the switch into the first plurality of sub-ports;generating, for each switch included in the first tier of switches, a plurality of subsets of sub-ports, wherein each subset of sub-ports of the uplink port of the switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches; andtransmitting a packet from a first GPU coupled to a first switch included in the first tier of switches to a second GPU coupled to a second switch included in the first tier of switches via the multi-tier network fabric.

10. The computer readable medium storing specific computer-executable instructions of claim 9, wherein each sub-port included in the first plurality of sub-ports of the uplink port of the switch included in the first tier of switches is addressable via a unique network address.

11. The computer readable medium storing specific computer-executable instructions of claim 10, wherein each sub-port included m the first plurality of sub-ports of the downlink port of the switch included in the second tier of switches is addressable via another unique network address.

12. The computer readable medium storing specific computer-executable instructions of claim 9, wherein the multi-tier network fabric is a two-tier CLOS network comprising the first tier of switches and the second tier of switches, wherein each switch in the first tier of switches is connected to a plurality of GPU racks at one end and to a plurality of switches included in the second tier of switches at another end.

13. The computer readable medium storing specific computer- executable instructions of claim 9, wherein the multi-tier network fabric is an InfiniBand network fabric,14. The computer readable medium storing specific computer-executable instructions of claim 9, wherein a first uplink port of the first switch included in the first tier of switches operates at a speed of 800G, and wherein the first port is partitioned into four sub-ports, where each sub-port operates at a speed of 200G.

15. The computer readable medium storing specific computer-executable instructions of claim 9, wherein a first uplink port of a first switch included in the first tier of switches is partitioned into four sub-ports, wherein a first pair of sub-ports of the first uplink port are communicatively coupled to a corresponding pair of sub-ports of the downlink port of a second switch included in the second tier of switches, and wherein a second pair of sub-ports of the first uplink port are communicatively coupled to another corresponding pair of sub-ports of the downlink port of a third switch included in the second tier of switches, the third switch being different from the second switch.

16. The computer readable medium storing specific computer-executable instructions of claim 9, wherein a first number of switches included in the first tier of switches in the multitier network fabric is greater than a second number of switches included in the second tier of switches in the multi-tier network fabric.

17. A computing device comprising:a processor; anda memory including instructions that, when executed with the processor, cause the computing device to, at least:for a network of switches included in a multi-tier network fabric, partition, for each switch included in a first tier of switches, an uplink port of the switch into a first plurality of sub-ports;partition, for each switch included in a second tier of switches, a downlink port of the switch into the first plurality of sub-ports;generate, for each switch included in the first tier of switches, a plurality of subsets of sub-ports, wherein each subset of sub-ports of the uplink port of the switch included in the first tier of switches is communicatively coupled to a different switch included in the second tier of switches; andtransmit a packet from a first GPU coupled to a first switch included in the first tier of switches to a second GPU coupled to a second switch included in the first tier of switches via the multi-tier network fabric.

18. The computing device of claim 17, wherein a first uplink port of the first switch included in the first tier of switches operates at a speed of 800G, and wherein the first port is partitioned into four sub-ports, where each sub-port operates at a speed of 200G.

19. The computing device of claim 17, wherein each sub-port included in the first plurality of sub-ports of the uplink port of the switch included in the first tier of switches is addressable via a unique network address, and wherein each sub-port included in the first plurality of sub-ports of the downlink port of the switch included in the second tier of switches is addressable via another unique network address.

20. The computing device of claim 17, wherein a first number of switches included in the first tier of switches in the multi-tier network fabric is greater than a second number of switches included in the second tier of switches in the multi-tier network fabric.

Images