WO2022271991A1 - Politiques de routage pour unités de traitement graphique - Google Patents

Politiques de routage pour unités de traitement graphique Download PDF

Info

Publication number
WO2022271991A1
WO2022271991A1 PCT/US2022/034789 US2022034789W WO2022271991A1 WO 2022271991 A1 WO2022271991 A1 WO 2022271991A1 US 2022034789 W US2022034789 W US 2022034789W WO 2022271991 A1 WO2022271991 A1 WO 2022271991A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
link
packet
vcn
network
Prior art date
Application number
PCT/US2022/034789
Other languages
English (en)
Inventor
Jagwinder Singh Brar
David Dale Becker
Lukasz Sulek
Jacob Robert UECKER
Original Assignee
Oracle International Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US17/734,865 external-priority patent/US20220417139A1/en
Application filed by Oracle International Corporation filed Critical Oracle International Corporation
Priority to EP22747186.9A priority Critical patent/EP4360280A1/fr
Priority to JP2023579266A priority patent/JP2024524992A/ja
Priority to CN202280045088.1A priority patent/CN117597894A/zh
Publication of WO2022271991A1 publication Critical patent/WO2022271991A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H04L45/7453—Address table lookup; Address filtering using hashing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/28—Routing or path finding of packets in data switching networks using route fault recovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/38—Flow based routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/12—Avoiding congestion; Recovering from congestion
    • H04L47/125—Avoiding congestion; Recovering from congestion by balancing the load, e.g. traffic engineering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/15—Interconnection of switching modules
    • H04L49/1553—Interconnection of ATM switching modules, e.g. ATM switching fabrics
    • H04L49/1569—Clos switching fabrics
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath

Definitions

  • HPC High performance compute
  • Cloud infrastructure service providers offer newer and faster CPUs and graphical processing units (GPUs) to address the requirements of HPC applications.
  • GPUs graphical processing units
  • a virtual topology is constructed in order to provision the various GPUs that are hosted on the several host machines to communicate with one another.
  • the present disclosure relates generally to routing mechanisms for graphical processing units (GPUs) that are hosted on several host machines in a cloud environment.
  • GPUs graphical processing units
  • 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.
  • One embodiment of the present disclosure is directed to a method comprising: for a packet transmitted by a graphical processing unit (GPU) of a host machine and received by a network device, determining, by the network device, an incoming port-link of the network device on which the packet was received; identifying, by the network device, based on a GPU routing policy, an outgoing port-link corresponding to the incoming port-link, wherein the GPU routing policy is preconfigured prior to receiving the packet and establishes a mapping of each incoming port-link of the network device to a unique outgoing port-link of the network device; and forwarding, by the network device, the packet on the outgoing port-link of the network device.
  • GPU graphical processing unit
  • An aspect of the present disclosure provides for a system comprising one or more data processors, and a non-transitory computer readable storage medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform part or all of one or more methods disclosed herein.
  • 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.
  • 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.
  • FIG. 2 depicts a simplified architectural diagram of the physical components in the physical network within CSPI according to certain embodiments.
  • FIG. 3 shows an example arrangement within CSPI where a host machine is connected to multiple network virtualization devices (NVDs) according to certain embodiments.
  • NDVs network virtualization devices
  • FIG. 4 depicts connectivity between a host machine and an NVD for providing I/O virtualization for supporting multitenancy according to certain embodiments.
  • FIG.5 depicts a simplified block diagram of a physical network provided by a CSPI according to certain embodiments.
  • FIG. 6 depicts a simplified block diagram of a cloud infrastructure incorporating a CLOS network arrangement, according to certain embodiments.
  • FIG. 7 depicts an exemplary scenario depicting a flow collision in the cloud infrastructure of FIG. 6, according to certain embodiments.
  • FIG. 8 depicts a policy based routing mechanism implemented in the cloud infrastructure, according to certain embodiments. [0019] FIG.
  • FIG. 9 depicts a block diagram of a cloud infrastructure illustrating different types of connections in the cloud infrastructure, according to certain embodiments.
  • FIG. 10 illustrates an exemplary configuration of a rack included in the cloud infrastructure, according to certain embodiments.
  • FIG. 11A illustrates a flowchart depicting steps performed by a network device in routing a packet, according to certain embodiments.
  • FIG. 11B illustrates another flowchart depicting steps performed by a network device in routing a packet, according to certain embodiments.
  • FIG. 12 is a block diagram illustrating one pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment. [0024] FIG.
  • FIG. 13 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 14 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 15 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 16 is a block diagram illustrating an example computer system, according to at least one embodiment. DETAILED DESCRIPTION [0028]
  • 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.
  • 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.
  • CSP cloud services provider
  • systems and infrastructure cloud infrastructure
  • 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.
  • cloud service providers that offer various types of cloud services.
  • cloud services including Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), and others.
  • SaaS Software-as-a-Service
  • PaaS Platform-as-a-Service
  • IaaS Infrastructure-as-a-Service
  • a customer can subscribe to one or more cloud services provided by a CSP.
  • the customer can be any entity such as an individual, an organization, an enterprise, and the like.
  • infrastructure as a service is one particular type of cloud computing service.
  • 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.
  • CSPI cloud services provider infrastructure
  • 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.
  • 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 of virtual or overlay networking is often referred to as virtual or overlay Layer-3 networking.
  • CSPI Generic Routing Encapsulation
  • VXLAN Virtual Extensible LAN
  • VXLAN Virtual Extensible LAN
  • VPNs Virtual Private Networks
  • RRC 4364 Virtual Private Networks
  • VMware's NSX GENEVE (Generic Network Virtualization Encapsulation)
  • CSPI the infrastructure
  • public network e.g., the Internet
  • 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).
  • an IaaS provider may also supply a variety of services to accompany those infrastructure components (e.g., billing, monitoring, logging, security, load balancing and clustering, etc.).
  • these services may be policy-driven, IaaS 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.
  • a customer subscribes to or registers for an IaaS 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.
  • 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.
  • 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).
  • VCNs virtual cloud networks
  • 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 over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., firewalls).
  • 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.
  • the console provides a web-based user interface that can be used to access and manage CSPI.
  • CSPI may support single-tenancy or multi-tenancy architectures.
  • a software e.g., an application, a database
  • a hardware component e.g., a host machine or a server
  • a software or a hardware component serves multiple customers or tenants.
  • CSPI resources are shared between multiple customers or tenants.
  • 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.
  • a network 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.
  • 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).
  • 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).
  • an overlay address (e.g., an overlay IP address) can be moved from 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.
  • physical addresses e.g., physical IP addresses
  • overlay addresses e.g., overlay IP addresses
  • 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.
  • 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.
  • 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.
  • 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 e.g., edge networking resources (e.g., DNS); and access management and monitoring resources, and others.
  • edge networking resources e.g., DNS
  • ADs availability domains
  • 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.
  • CSPI resources are either region-specific, such as a virtual cloud network (VCN), or availability domain-specific, such as a compute instance.
  • VCN virtual cloud network
  • ADs within a region are isolated from each other, fault tolerant, and are configured such that they are very unlikely to fail simultaneously.
  • 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.
  • 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.
  • 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.
  • An IaaS provider can provide multiple realms, each realm catered to a particular set of customers or users.
  • a commercial realm may be provided for commercial customers.
  • a realm may be provided for a specific country for customers within that country.
  • a government realm may be provided for a government, and the like.
  • the government realm may be catered for a specific government and may have a heightened level of security than a commercial realm.
  • Oracle Cloud Infrastructure currently offers a realm for commercial regions and two realms (e.g., FedRAMP authorized and IL5 authorized) for government cloud regions.
  • 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.
  • the number of fault domains for each AD 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.
  • VCNs virtual cloud networks
  • a customer can set up one or more virtual cloud networks (VCNs) using CSPI resources allocated for the customer.
  • 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.
  • the CSP may provide various services using the CSPI.
  • 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 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.
  • 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.
  • a service endpoint provided for a service can be accessed by multiple customers that intend to consume that service.
  • a dedicated service endpoint may be provided for a customer such that only that customer can access the service using that dedicated service endpoint.
  • CIDR Classless Inter-Domain Routing
  • 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.
  • 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 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.
  • 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.
  • VNIC virtual network interface card
  • a VNIC is a logical representation of physical Network Interface Card (NIC).
  • NIC Network Interface Card
  • a VNIC is an interface 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.
  • the subnet 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a VCN may be subdivided into one or more subnets.
  • 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.
  • 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.
  • 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.
  • 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.
  • IP address 10.0.0.1 may be reserved for a port of the VCN VR for that subnet.
  • the VCN VR may have a port for that second subnet with IP address 10.1.0.1.
  • the VCN VR has a different IP address for each of the subnets in the VCN.
  • each subnet within a VCN 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.
  • 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.
  • 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.
  • 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.
  • 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 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 VCN 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • distributed environment 100 comprises CSPI 101 that provides services and resources that customers can subscribe to and use to build their virtual cloud networks (VCNs).
  • CSPI 101 offers IaaS 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.
  • customer VCN 104 comprises two subnets, namely, "Subnet-1" and "Subnet-2", each subnet with its own CIDR IP address range.
  • 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.
  • 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.
  • 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.
  • a compute instance C1 is part of Subnet-1 via a VNIC associated with the compute instance.
  • compute instance C2 is part of Subnet-1 via a VNIC associated with C2.
  • each compute instance may be virtual machine instances or bare metal instances, may be part of Subnet-1.
  • each compute instance Via its associated VNIC, each compute instance is assigned a private overlay IP address and a MAC address.
  • compute instance C1 has an overlay IP address of 10.0.0.2 and a MAC address of M1
  • 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 C1 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.
  • Subnet-2 can have multiple compute instances deployed on it, including virtual machine instances and/or bare metal instances.
  • compute instances D1 and D2 are part of Subnet-2 via VNICs associated with the respective compute instances.
  • compute instance D1 has an overlay IP address of 10.1.0.2 and a MAC address of MM1
  • compute instance D2 has an 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.
  • VCN A 104 may also include one or more load balancers.
  • 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.
  • a particular compute instance deployed on VCN 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).
  • 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.,
  • 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 C1 in Subnet-1 may want to send packets to compute instance C2 in Subnet-1.
  • the packet 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 compute 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.
  • policies e.g., security lists
  • 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.
  • the communication is facilitated by the VNICs associated with the source and destination compute instances and the VCN VR. For example, if compute instance C1 in Subnet-1 in FIG. 1 wants to send a packet to compute instance D1 in Subnet-2, the packet is first processed by the VNIC associated with compute instance C1.
  • the VNIC associated with compute instance C1 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 D1 and the VNIC forwards the packet to compute instance D1.
  • 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.
  • the communications may be over public networks (e.g., the Internet) or over private networks.
  • Various communication protocols may be used for these communications.
  • compute instance C1 may want to communicate with an endpoint outside VCN 104.
  • the packet may be first processed by the VNIC associated with source compute instance C1.
  • the VNIC processing determines that the destination for the packet is outside the Subnet-1 of C1.
  • the VNIC associated with C1 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 it final intended destination.
  • DGW Dynamic Routing Gateway
  • 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.
  • 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.
  • 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.
  • Various 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.
  • CPE customer premise equipment
  • the endpoint may be a host machine executing DRG 122.
  • 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.
  • RPC Remote Peering Connection
  • 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, Amazon AWS cloud, and others.
  • 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 1120 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.
  • a Network Address Translation (NAT) 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).
  • NAT Network Address Translation
  • 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.
  • 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.
  • a compute instance in a private subnet of customer VCN 104 can back up data to a service endpoint (e.g., Object Storage) without needing public IP addresses or access to the Internet.
  • 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 on-premises networks that are connected to a VCN with FastConnect or VPN Connect can also use the service gateway configured for that VCN.
  • SGW 126 uses the concept of a service Classless Inter- Domain 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 IP addresses change in the future.
  • 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.
  • LPG Local Peering Gateway
  • VCN 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.
  • 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.
  • 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.
  • a Private Endpoint (PE) access 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • C2S connections customer-to-service private connections
  • 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.
  • a customer can control routing in a VCN 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 non-local traffic through IGW 120. The route table for a private subnet within the same customer VCN 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.
  • 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.
  • 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.
  • 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 NAT 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 services without traversing a public network such as the Internet.
  • 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.
  • 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.
  • 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.
  • 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.
  • cloud services e.g., IaaS services
  • VCNs virtual cloud networks
  • 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.
  • 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.
  • 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 VCN 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.
  • 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.
  • host machines 202 and 208 execute hypervisors 260 and 266, respectively.
  • hypervisors may be implemented using software, firmware, or hardware, or combinations thereof.
  • 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.
  • OS operating system
  • 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.
  • 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.
  • a compute instance can be a virtual machine instance or a bare metal instance.
  • 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.
  • 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.
  • a host machine may be shared between multiple customers (i.e., multiple tenants).
  • 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.
  • a bare metal compute instance is hosted by a bare metal server without a hypervisor.
  • 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.
  • the VNIC associated with that compute instance is executed by an NVD connected to the host machine. For example, in FIG.
  • 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.
  • VNIC 276 is executed by NVD 210 connected to host machine 202.
  • 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.
  • 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.
  • an NVD connected to that host machine also executes VCN VRs corresponding to VCNs of which the compute instances are members. For example, in the embodiment depicted in FIG.
  • 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.
  • a host machine may include one or more network interface cards (NIC) that enable the host machine to be connected to other devices.
  • NIC network interface cards
  • a NIC on a host machine may provide one or more ports (or interfaces) that enable the host machine to be communicatively connected to another device.
  • a host machine may be connected to an NVD using one or more ports (or interfaces) provided on the host machine and on the NVD.
  • a host machine may also be connected to other devices such as another host machine.
  • 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.
  • 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).
  • TOR top-of-the-rack
  • the links between a host machine and an NVD, and between an NVD and a TOR switch are Ethernet links.
  • NVDs 210 and 212 are connected to TOR switches 214 and 216, respectively, using links 228 and 230.
  • 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.
  • 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.
  • 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.
  • each host machine is connected to its own separate NVD.
  • host machine 202 is connected to NVD 210 via NIC 232 of host machine 202.
  • multiple host machines are connected to one NVD.
  • host machines 206 and 208 are connected to the same NVD 212 via NICs 244 and 250, respectively.
  • a one-to-many configuration one host machine is connected to multiple NVDs.
  • FIG. 1 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.
  • host machine 302 comprises a network interface card (NIC) 304 that includes multiple ports 306 and 308.
  • NIC network interface card
  • Host machine 300 is connected to a first NVD 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.
  • 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.
  • 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.
  • An NVD may be implemented in various different forms. For example, in certain embodiments, an NVD 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.
  • a smartNIC is however just one example of an NVD implementation.
  • 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.
  • an NVD may be embodied in a host machine where the functions performed by an NVD are performed by the host machine.
  • an NVD may be part of a TOR switch or a TOR switch may be configured to perform functions performed by an NVD 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.
  • functions performed by an NVD may be implemented inside a hypervisor of the host machine.
  • some of the functions of the NVD may be offloaded to a centralized service running on a fleet of host machines.
  • 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.
  • NVD 210 is connected to TOR switch 214 using link 228 that extends from port 256 of NVD 210 to the TOR switch 214.
  • NVD 212 is connected to TOR switch 216 using link 230 that extends from port 258 of NVD 212 to the TOR switch 216.
  • 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.
  • a host machine e.g., packets and frames generated by a compute instance hosted by the host machine
  • An NVD may receive packets and frames from a TOR switch via a network-facing port of the NVD and, after performing the necessary packet processing, may forward the packets and frames to a host machine via a host-facing port of the NVD.
  • 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 NVD implements or performs network virtualization functions. These functions are performed by software/firmware executed by the NVD.
  • 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.
  • an NVD upon receiving a packet, is configured to execute a packet processing pipeline for processing the packet and determining how the packet is to be forwarded or routed.
  • 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.
  • the packet processing data path in an NVD may comprise multiple packet pipelines, each composed of a series of packet transformation stages.
  • the packet 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.
  • 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.
  • 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 IGW, etc. Firewall rules may also be published using the same mechanism.
  • 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.
  • an NVD is configured to intercept all network packets in and out of host machines and perform network virtualization functions.
  • 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.
  • NVD 210 executes the functionality for VNIC 276 that is associated with compute instance 268 hosted by host machine 202 connected to NVD 210.
  • 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 different customers, and the NVD connected to the host machine may execute the VNICs (i.e., execute VNICs-relate functionality) corresponding to the compute instances.
  • An NVD also executes VCN Virtual Routers corresponding to the VCNs of the compute instances.
  • 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.
  • 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.
  • 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.
  • NVD 210 comprises packet processing components 286 and NVD 212 comprises packet processing components 288.
  • 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 NVD 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).
  • 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.
  • 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.
  • 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.
  • the compute instances in a VCN may be executed or hosted by one or more host machines depicted in FIG.2.
  • 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.
  • 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, in 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.
  • 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 VNIC 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 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).
  • 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.
  • 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.
  • 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).
  • 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, which 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 VCN 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 a 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.
  • a packet originating from compute instance 268 may be communicated from host machine 202 to NVD 210 over link 220 (using NIC 232).
  • 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.
  • 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.
  • public networks e.g., the Internet
  • 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).
  • FIG. 4 depicts connectivity between a host machine and an NVD for providing I/O virtualization for supporting multitenancy according to certain embodiments.
  • host machine 402 executes a hypervisor 404 that provides a virtualized environment.
  • Host machine 402 executes two virtual machine instances, VM1 406 belonging to customer/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.
  • VM1406 is attached to VNIC-VM1420 and VM2408 is attached to VNIC-VM2422.
  • 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.
  • VM1406 is attached to logical NIC A 416
  • VM2408 is attached to logical NIC B 418.
  • 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.
  • each logical NIC is assigned its own VLAN ID.
  • 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.
  • a packet is communicated from VM1406, 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.
  • 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.
  • a packet 424 communicated from host machine 402 to NVD 412 has an associated tag 426 that identifies a specific tenant and associated VM.
  • the tag 426 associated with the packet is used to determine whether the packet is to be processed by VNIC-VM1420 or by VNIC-VM2422. 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.
  • FIG. 5 depicts a simplified block diagram of a physical network 500 according to certain embodiments. The embodiment depicted in FIG.
  • a Clos network 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 or 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.
  • 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.
  • 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).
  • 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.
  • 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 NVD, where the source and target NVDs are connected to the leaf tier of the Clos network.
  • 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.
  • each resource within CSPI is assigned a unique identifier called a Cloud Identifier (CID).
  • CID Cloud Identifier
  • This identifier is included as part of the resource's information and can be used to manage the resource, for example, via a Console or through APIs.
  • An example syntax for a CID is: ocid1. ⁇ 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 "c1" 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.
  • FIG.6 depicts a block diagram of a cloud infrastructure 600 incorporating a CLOS network arrangement, according to certain embodiments.
  • the cloud infrastructure 600 includes a plurality of racks (e.g., rack 1 610 ...rack M, 620).
  • Each rack includes a plurality of host machines (also referred to herein as hosts).
  • rack 1610 includes a plurality of hosts (e.g., K host machines) host 1-A, 612 to host 1-K, 614, and rack M includes K host machines i.e., Host M-A, 622 to Host M-K, 624.
  • hosts e.g., K host machines
  • rack M includes K host machines i.e., Host M-A, 622 to Host M-K, 624.
  • FIG.6 i.e., each rack including the same number of host machines e.g., K host machines
  • rack M, 620 may have a higher or lower number of host machines as compared to the number of host machines included in rack 1, 610.
  • Each host machine includes a plurality of graphical processing units (GPUs). For example, as shown in FIG.
  • GPUs graphical processing units
  • Host machine 1-A 612 includes N GPUs e.g., GPU 1, 613. Moreover, it is appreciated that the illustration in FIG.6 (of having each host machine including the same number of GPUs, i.e., N GPUs), is intended to be illustrative and non-limiting i.e., each host machine can include a different number of GPUs. Each rack includes a top of rack (TOR) switch that is communicatively coupled with the GPUs hosted on the host machines.
  • TOR top of rack
  • rack 1 610 includes a TOR switch (i.e., TOR 1) 616 that is communicatively coupled to Host 1-A, 612 and Host 1-K, 614
  • rack M 620 includes a TOR switch (i.e., TOR M) 626 that is communicatively coupled to Host M-A, 622 and Host M-K, 624.
  • TOR switches depicted in FIG. 6 i.e., TOR 1616, and TOR M 626
  • each include N ports that are used to communicatively couple the TOR switch to the N GPUs hosted on each host machine included in the rack.
  • the TOR switch may have a plurality of ports, each of which corresponds to a GPU on each host machine i.e., a GPU on a host machine may be connected to a unique port of the TOR via a communication link.
  • traffic received by a network device e.g., TOR 1 616) is characterized herein as traffic received on a particular incoming port-link of the network device. For example, when GPU 1613 of Host 1-A 612 transmits a data packet to TOR 1616 (using link 617), the data packet is received on port 619 of the TOR 1 switch.
  • TOR 1 616 characterizes this data packet as information received on a first incoming port-link of the TOR. It is appreciated that a similar notion can be applied to all outgoing port-links of the TOR.
  • the TOR switches from each rack are communicatively coupled to a plurality of spine switches e.g., spine switch 1, 630 and spine switch P 640. As shown in FIG. 6, TOR 1, 616 is connected to spine switch 1630 via two links, and to spine switch P 640 via another two links, respectively.
  • Information transmitted from a particular TOR switch to a spine switch is referred to herein as communication conducted via uplinks, whereas information transmitted from a spine switch to a TOR switch is referred to herein as communication conducted via downlinks.
  • the TOR switches and the spine switches are connected in a CLOS network arrangement (e.g., a multi-stage switching network), where each TOR switch forms a ‘leaf’ node in the CLOS network.
  • the GPUs included in the host machines execute tasks related to machine learning. In such a setting, a single task may be performed/spread across a large number of GPUs (e.g., 64) that in turn could be spread across multiple host machines and across multiple racks. Since all these GPUs are working on the same task (i.e., a workload), they all need to communicate with each other in a time synchronized manner.
  • the GPUs are either in one of a compute mode or a communication mode i.e., GPUs talk to one another at roughly the same time instant.
  • the speed of the workload is determined by the speed of the slowest GPU.
  • a source GPU e.g., GPU 1, 613 of Host 1-A 612
  • a destination GPU e.g., GPU 1, 623 of Host M-A 622
  • equal cost multipath (ECMP) routing is utilized.
  • ECMP routing when there are multiple equal cost paths available for routing traffic from a sender to a receiver, a selection technique is used to select a particular path.
  • a selection algorithm is used to select an outgoing link to be used for forwarding the traffic from the network device on a next hop to another network device.
  • a hash-based selection algorithm is a widely used ECMP selection technique, where the hash may be based upon a 4-tuple of a packet (e.g., source port, destination port, source IP, destination IP).
  • ECMP routing is a flow aware routing technique, where each flow (i.e., a stream of data packets) is hashed to a particular path for the duration of the flow.
  • packets in a flow are forwarded from a network device using a particular outgoing port/link. This is typically done in order to ensure that packets in a flow arrive in order i.e., no re-ordering of packets is required.
  • ECMP routing is bandwidth (or throughput) unaware. In other words, the TOR and spine switches perform statistical flow-aware (throughput unaware) ECMP load balancing of flows on parallel links. [0135] In standard ECMP routing (i.e., only flow aware routing), a problem is that flows received by a network device over two separate incoming links may get hashed to the same outgoing link, thereby resulting in a flow collision.
  • FIG. 7 illustrates an exemplary scenario of a flow collision 700.
  • flow 1710 which is directed from a first GPU of the host machine host 1-A, 612 to the TOR switch 616 (depicted by solid line)
  • flow 2720 which is directed from another GPU on the same host machine 612 to the TOR switch 616 (depicted by dashed line).
  • the two flows are directed to the TOR switch 616 on separate links i.e., separate incoming port-links of the TOR. It is assumed that all links depicted in FIG.7 have a capacity (i.e., bandwidth) of 100G.
  • the TOR switch 616 performs ECMP routing algorithm, it is possible that the two flows get hashed to use the same outgoing port-link of the TOR e.g., port of the TOR connected to link 730, which connects the TOR switch 616 to spine switch 630. In this case, there is a collision between the two flows (represented by ‘X’ mark), which results in packets being dropped. [0137] Such a collision scenario is generally problematic for all types of traffic irrespective of the protocol.
  • TCP is intelligent in that when a packet gets dropped and the sender does not get an acknowledgment for that dropped packet, the packet is re-transmitted.
  • RDMA remote direct memory access
  • RDMA networks do not use TCP for a variety of reasons (e.g., TCP has a complex logic that does not lend well to low latency and high performance).
  • RDMA networks use protocols such as RDMA over Infiniband or RDMA over converged Ethernet (RoCE).
  • RoCE there is a congestion control algorithm, wherein when a sender identifies the occurrence of a congestion or dropped packets, the sender slows down the transmission of packets.
  • a network with no oversubscription is one where bandwidth of incoming links to a device (e.g., TOR, spine switch) is the same as bandwidth of outgoing links. Note that if all links have the same bandwidth capacity, then the number of incoming links is the same as the number of outgoing links.
  • a GPU based policy routing mechanism also referred to herein as a GPU-based Traffic Engineering mechanism
  • ECMP routing mechanism a modified ECMP routing mechanism.
  • the cloud infrastructure 800 includes a plurality of racks e.g., rack 1810 to rack M 820.
  • Each rack includes a host machine including a plurality of GPUs.
  • rack 1810 includes a host machine i.e., Host 1-A 812
  • rack M 820 includes a host machine i.e., Host M-A 822.
  • Each rack includes a TOR switch e.g., rack 1810 includes TOR 1 switch 814 and rack M 820 includes TOR M switch 824.
  • the host machine in each rack is communicatively coupled to the respective TOR switch in the rack.
  • the TOR switches i.e., TOR switch 1, 814 and TOR switch M 824 are in turn communicatively coupled to the spine switches i.e. spine switch 830 and spine switch 840.
  • the cloud infrastructure 800 is depicted as including a single host machine per rack. However, it is appreciated that each rack in the infrastructure may have more than one host machine.
  • data packets from a sender to a receiver are routed in the network on a hop-by-hop basis.
  • a routing policy is configured at each network device that ties an incoming port-link to an outgoing port-link.
  • the network device could be a TOR switch or the spine switch.
  • FIG.8 there are depicted two flows: flow 1 from GPU 1 on host machine 812 whose intended destination is GPU 1 on host machine 822, and flow 2 from GPU N on host machine 812 whose intended destination is GPU N on host machine 822.
  • the network devices i.e., TOR 1 814, spine 1 830, TOR M 824, and spine P 840 are configured to tie (or match) an incoming port-link to an outgoing port-link.
  • a matching of the incoming port-links to outgoing port-links is maintained (e.g., in a policy table) at each network device.
  • each network device is configured to tie an incoming port/link to an outgoing port/link in order to avoid collisions.
  • the TOR 1814 receives a first data packet (corresponding to flow 1) on link 850, and receives a second data packet (corresponding to flow 2) on link 870.
  • TOR 1814 is configured to forward data packets received on incoming link/port 850 to outgoing link/port 855, and to forward data packets received on incoming link/port 870 to outgoing link/port 875, it is ensured that the first and second data packets will not collide.
  • the network device is configured to switch its routing policy from the GPU policy based routing to a standard ECMP routing to obtain a new available output link (from various available output links) and send the flow down that new output link. It is noted that in this case, one may incur flow collision resulting in congestion.
  • the infrastructure 900 includes a plurality of racks e.g., rack 1910, rack D 920, and rack M, 930.
  • Racks 910 and 930 include a plurality of host machines.
  • rack 1910 includes a plurality of hosts (e.g., K host machines) Host 1-A, 912 to Host 1-K, 914
  • rack M includes K host machines i.e., Host M-A, 932 to Host M-K, 934.
  • Rack D 920 includes one or more host machines 922, each of which include a plurality of CPUs i.e., the host machine 922 is a non- GPU host machine.
  • Each of the racks 910, 920, and 930 include a TOR switch i.e., TOR 1, 916, TOR D 926, and TOR M 936, respectively that are communicatively coupled to the host machines in the respective racks.
  • the TOR switches 916, 926, and 936 are communicatively coupled to a plurality of spine switches i.e., spine switches 940 and 950. [0145] As shown in FIG.
  • connection 1 a first connection (i.e., connection 1 depicted by dashed lines) exists from a GPU host (i.e., Host 1-A 912) to another GPU host (i.e., Host M-A 932), and a second connection (i.e., connection 2 depicted by dotted lines) exists from a GPU host (i.e., Host 1-K 914) to a non-GPU host (i.e., Host D 922).
  • connection 1 data packets associated with the flow are routed on a hop-by-hop basis by configuring each intermediate network device based on the GPU based policy routing mechanism as described previously in FIG.8.
  • connection 1 is routed along the dashed links depicted in FIG. 9. i.e., from host 1-A to TOR 1, from TOR 1 to spine switch 1, from spine switch 1 to TOR M, and eventually from TOR M to host M-A.
  • Each of the network devices is configured to tie an incoming link-port to an outgoing link-port of the network device.
  • connection 2 is from a GPU based host (i.e., Host 1-K 914) to a non- GPU based host (i.e., Host D 922).
  • TOR 1916 is configured to tie an incoming link-port i.e., port and link (971) on which it receives data packets from a GPU based host to an outgoing link-port i.e., an output port and link 972 connected to the output port.
  • TOR 1 forwards the data packets to spine switch 1 940 using the outgoing link 972.
  • spine switch 1940 does not utilize the policy based routing mechanism to forward the packets to TOR D. Rather, spine switch 1940 utilizes the ECMP routing mechanism to select one of the available links 980 to forward the packets to TOR D, which then forwards the data packets to Host D 922.
  • the flow collision described previously with reference to FIG. 7 is avoided by network devices of the cloud infrastructures described herein by implementing a modified version of ECMP routing.
  • the ECMP hash algorithm is modified such that, traffic coming over a particular incoming port-link of a network device is hashed (and directed) to a same outgoing port-link of the network device.
  • each network device implements a modified ECMP algorithm to determine an output port-link to be used for forwarding the packet, wherein per the modified ECMP algorithm, any packet received over a particular incoming port-link always hashes to the same outgoing port-link.
  • the network device is configured to implement the modified ECMP algorithm where the network device transmits the first packet and the second packet on a first outgoing port-link of the network device, and transmits the third packet and the fourth packet on a second outgoing port-link of the network device, where the first incoming port-link of the network device is different than the second incoming port- link of the network device, and the first outgoing port-link of the network device is different than the second outgoing port-link of the network device.
  • the information stored in a forwarding information database can be modified to enable the above stated functionality.
  • a forwarding information database e.g., forwarding tables, ECMP tables, etc.,
  • the rack 1000 includes two host machines i.e., host machine 1010 and host machine 1020. It is appreciated that although rack 1000 is depicted as including two host machines, the rack 1000 may include more number of host machines. Each host machine includes a plurality of GPUs and a plurality of CPUs.
  • the host machine 1010 includes a plurality of CPUs 1012 and a plurality of GPUs 1014, whereas the host machine 1020 includes a plurality of CPUs 1022 and a plurality of GPUs 1024.
  • the host machines are communicatively coupled to different network fabrics via different TOR switches.
  • host machines 1010 and 1020 are communicatively coupled to a network fabric (referred to herein as a front-end network of the rack 1000) via a TOR switch i.e., TOR 1 switch 1050.
  • the front-end network may correspond to an external network.
  • the host machine 1010 is connected to the front-end network, via a network interface card (NIC) 1030 and a network virtualization device (NVD) 1035, which is coupled to the TOR 1 switch 1050.
  • the host machine 1020 is connected to the front-end network via a NIC 1040 and a NVD 1045, which is coupled to the TOR 1 switch 1050.
  • the CPUs of each host machine may communicate with the front-end network via the NIC, NVD, and TOR switch.
  • CPUs 1012 of host machine 1010 may communicate with the front-end network via NIC 1030, NVD 1035, and TOR 1 switch 1050.
  • the host machines 1010 and 1020 are connected to a quality of service (QoS) enabled backend network on the other side.
  • the (QoS) enabled backend network is referred to herein as a backend network that corresponds to a GPU cluster network as shown in FIG. 6.
  • Host machine 1010 is connected via another NIC 1065 to a TOR 2 switch 1060 which communicatively couples the host machine 1010 to the backend network.
  • host machine 1020 is connected via NIC 1080 to the TOR 2 switch 1060, which communicatively couples the host machine 1020 to the backend network.
  • FIG. 11A depicts an exemplary flowchart 1100 depicting steps performed by a network device in routing a packet, according to certain embodiments.
  • the processing depicted in FIG. 11A 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).
  • a non-transitory storage medium e.g., on a memory device.
  • the method presented in FIG. 11A and described below is intended to be illustrative and non-limiting. Although FIG. 11A 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.
  • the process commences in step 1105 where a network device receives a data packet transmitted by a graphical processing unit (GPU) of a host machine.
  • the network device determines an incoming port/link that the packet was received on.
  • GPU graphical processing unit
  • the network device identifies an outgoing port/link corresponding to the incoming port/link (on which the packet was received) based on a policy routing information.
  • the policy routing information corresponds to a pre-configured GPU routing table for the network device that ties each incoming port-link of the network device to a unique outgoing link-port of the network device.
  • the process then moves to step 1120, where a query is performed to determine whether the outgoing port-link is in a functioning state e.g., the outgoing link is active.
  • step 1125 the network device utilizes the outgoing port-link (identified in step 1115) to forward the received data packet to another network device.
  • step 1130 the network device obtains flow information of the data packet e.g., the flow information may correspond to a 4-tuple associated with the packet (i.e., source port, destination port, source IP address, destination IP address).
  • FIG. 11B depicts another exemplary flowchart 1150 depicting steps performed by a network device in routing a packet, according to certain embodiments.
  • the processing depicted in FIG. 11B 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).
  • a non-transitory storage medium e.g., on a memory device.
  • the method presented in FIG. 11B and described below is intended to be illustrative and non-limiting. Although FIG. 11B 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.
  • the process commences in step 1155, where a network device receives a data packet transmitted by a graphical processing unit (GPU) of a host machine.
  • the network device determines flow information of the received packet.
  • GPU graphical processing unit
  • the flow information may correspond to 4-tuple associated with the packet (i.e., source port, destination port, source IP address, destination IP address).
  • the network device computes an outgoing port-link by implementing a modified version of the ECMP routing. Per the modified ECMP algorithm, any packet received over a particular incoming port-link is always hashed to be transmitted on the same outgoing port-link. [0156] The process then moves to step 1170, where a query is performed to determine whether the outgoing port-link (determined in step 1165) is in a functioning state e.g., the outgoing link is active.
  • step 1175 the network device utilizes the outgoing port-link (identified in step 1165) to forward the received data packet to another network device.
  • the identified outgoing port-link of step 1165) is determined to be in an inactive state, then the process moves to step 1180.
  • step 1180 the network device implements ECMP routing (i.e., standard ECMP routing) to identify a new outgoing port-link.
  • IaaS infrastructure as a service
  • IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet).
  • 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).
  • an IaaS provider may also supply a variety of services to accompany those infrastructure components (e.g., billing, monitoring, logging, security, load balancing and clustering, etc.).
  • these services may be policy-driven, IaaS users may be able to implement policies to drive load balancing to maintain application availability and performance.
  • IaaS customers may access resources and services through a wide area network (WAN), such as the Internet, and can use the cloud provider's services to install the remaining elements of an application stack.
  • WAN wide area network
  • the user can log in to the IaaS platform to create virtual machines (VMs), install operating systems (OSs) on each VM, deploy middleware such as databases, create storage buckets for workloads and backups, and even install enterprise software into that VM.
  • VMs virtual machines
  • OSs install operating systems
  • middleware such as databases
  • storage buckets for workloads and backups
  • enterprise software 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.
  • 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) IaaS.
  • An entity might also opt to deploy a private cloud, becoming its own provider of infrastructure services.
  • IaaS deployment is the process of putting a new application, or a new version of an application, onto a prepared application server or the like. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed by the cloud provider, below the hypervisor layer (e.g., the servers, storage, network hardware, and virtualization).
  • IaaS provisioning may refer to acquiring computers or virtual hosts for use, and even installing needed libraries or services on them. In most cases, deployment does not include provisioning, and the provisioning may need to be performed first.
  • IaaS provisioning there are two different challenges for IaaS provisioning. First, there is the initial challenge of provisioning the initial set of infrastructure before anything is running. Second, there is the challenge of evolving the existing infrastructure (e.g., adding new services, changing services, removing services, etc.) once everything has been provisioned.
  • 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.
  • VPCs virtual private clouds
  • VMs virtual machines
  • 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.
  • 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.
  • 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.
  • FIG. 12 is a block diagram 1200 illustrating an example pattern of an IaaS architecture, according to at least one embodiment.
  • Service operators 1202 can be communicatively coupled to a secure host tenancy 1204 that can include a virtual cloud network (VCN) 1206 and a secure host subnet 1208.
  • VCN virtual cloud network
  • the service operators 1202 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.
  • the client computing devices can be general purpose personal computers including, by way of example, personal computers and/or laptop computers running various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems.
  • the client computing devices can be workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems, including without limitation the variety of GNU/Linux operating systems, such as for example, Google Chrome OS.
  • 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 1206 and/or the Internet.
  • the VCN 1206 can include a local peering gateway (LPG) 1210 that can be communicatively coupled to a secure shell (SSH) VCN 1212 via an LPG 1210 contained in the SSH VCN 1212.
  • the SSH VCN 1212 can include an SSH subnet 1214, and the SSH VCN 1212 can be communicatively coupled to a control plane VCN 1216 via the LPG 1210 contained in the control plane VCN 1216.
  • the SSH VCN 1212 can be communicatively coupled to a data plane VCN 1218 via an LPG 1210.
  • the control plane VCN 1216 and the data plane VCN 1218 can be contained in a service tenancy 1219 that can be owned and/or operated by the laaS provider.
  • the control plane VCN 1216 can include a control plane demilitarized zone (DMZ) tier 1220 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 security breaches contained.
  • the DMZ tier 1220 can include one or more load balancer (LB) subnet(s) 1222, a control plane app tier 1224 that can include app subnet(s) 1226, a control plane data tier 1228 that can include database (DB) subnet(s) 1230 (e.g., frontend DB subnet(s) and/or backend DB subnet(s)).
  • LB load balancer
  • 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 an internet gateway 1234 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 a sendee gateway 1236 and a network address translation (NAT) gateway 1238.
  • the control plane VCN 1216 can include the service gateway 1236 and the NAT gateway 1238.
  • the control plane VCN 1216 can include a data plane mirror app tier 1240 that can include app subnet(s) 1226,
  • the app subnet(s) 1226 contained in the data plane mirror app tier 1240 can include a virtual network interface controller (VNIC) 1242 that can execute a compute instance 1244.
  • the compute instance 1244 can communicatively couple the app subnet(s) 1226 of the data plane mirror app tier 1240 to app subnet(s) 1226 that can be contained in a data plane app tier 1246.
  • the data plane VCN 1218 can include the data plane app tier 1246, a data plane DMZ tier 1248, and a data plane data tier 1250.
  • the data plane DMZ tier 1248 can include LB subnet(s) 1222 that can be communicatively coupled to the app subnet( s) 1226 of the data plane app tier 1246 and the Internet gateway 1234 of the data plane VCN 1218.
  • the app subnet(s) 1226 can be communicatively coupled to the service gateway 1236 of the data plane V CN 1218 and the NAT gateway 1238 of the data plane VCN 1218.
  • the data plane data tier 1250 can also include the DB subnet(s) 1230 that can be communicatively coupled to the app subnet(s) 1226 of the data plane app tier 1246.
  • the Internet gateway 1234 of the control plane VCN 1216 and of the data plane VCN 1218 can be communicatively coupled to a metadata management service 1252 that can be communicatively coupled to public Internet 1254.
  • Public Internet 1254 can be communicatively coupled to the NAT gateway 1238 of the control plane VCN 1216 and of the data plane VCN 1218.
  • the service gateway 1236 of the control plane VCN 1216 and of the data plane VCN 1218 can be communicatively couple to cloud services 1256.
  • the service gateway 1236 of the control plane VCN 1216 or of the data plane VCN 1218 can make application programming interface (API) calls to cloud services 1256 without going through public Internet 1254.
  • the API calls to cloud services 1256 from the service gateway 1236 can be one-way: the service gateway 1236 can make API calls to cloud services 1256, and cloud services 1256 can send requested data to the service gateway 1236. But, cloud services 1256 may not initiate API calls to the service gateway 1236.
  • the secure host tenancy 1204 can be directly connected to the service tenancy 1219, which may be otherwise isolated.
  • the secure host subnet 1208 can communicate with the SSH subnet 1214 through an LPG 1210 that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet 1208 to the SSH subnet 1214 may give the secure host subnet 1208 access to other entities within the service tenancy 1219.
  • the control plane VCN 1216 may allow users of the service tenancy 1219 to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN 1216 may be deployed or otherwise used in the data plane VCN 1218.
  • control plane VCN 1216 can be isolated from the data plane VCN 1218, and the data plane mirror app tier 1240 of the control plane VCN 1216 can communicate with the data plane app tier 1246 of the data plane VCN 1218 via VNICs 1242 that can be contained in the data plane mirror app tier 1240 and the data plane app tier 1246.
  • users of the system, or customers can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet 1254 that can communicate the requests to the metadata management service 1252.
  • the metadata management service 1252 can communicate the request to the control plane VCN 1216 through the Internet gateway 1234.
  • the request can be received by the LB subnet(s) 1222 contained in the control plane DMZ tier 1220.
  • the LB subnet(s) 1222 may determine that the request is valid, and in response to this determination, the LB subnet(s) 1222 can transmit the request to app subnet(s) 1226 contained in the control plane app tier 1224. If the request is validated and requires a call to public Internet 1254, the call to public Internet 1254 may be transmitted to the NAT gateway 1238 that can make the call to public Internet 1254.
  • Memory that may be desired to be stored by the request can be stored in the DB subnet(s) 1230.
  • the data plane mirror app tier 1240 can facilitate direct communication between the control plane VCN 1216 and the data plane VCN 1218. 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 1218.
  • the control plane VCN 1216 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 1218.
  • the control plane VCN 1216 and the data plane VCN 1218 can be contained in the service tenancy 1219. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN 1216 or the data plane VCN 1218.
  • the IaaS provider may own or operate the control plane VCN 1216 and the data plane VCN 1218, both of which may be contained in the service tenancy 1219.
  • 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 1254, which may not have a desired level of security, for storage.
  • the LB subnet(s) 1222 contained in the control plane VCN 1216 can be configured to receive a signal from the service gateway 1236.
  • FIG. 13 is a block diagram 1300 illustrating another example pattern of an IaaS architecture, according to at least one embodiment.
  • Service operators 1302 e.g. service operators 1202 of FIG.12
  • a secure host tenancy 1304 e.g. the secure host tenancy 1204 of FIG.
  • the VCN 1306 can include a local peering gateway (LPG) 1310 (e.g. the LPG 1210 of FIG.12) that can be communicatively coupled to a secure shell (SSH) VCN 1312 (e.g. the SSH VCN 1212 of FIG. 12) via an LPG 1310 contained in the SSH VCN 1312.
  • LPG local peering gateway
  • SSH secure shell
  • the SSH VCN 1312 can include an SSH subnet 1314 (e.g. the SSH subnet 1214 of FIG.
  • the SSH VCN 1312 can be communicatively coupled to a control plane VCN 1316 (e.g. the control plane VCN 1216 of FIG. 12) via an LPG 1310 contained in the control plane VCN 1316.
  • the control plane VCN 1316 can be contained in a service tenancy 1319 (e.g. the service tenancy 1219 of FIG.12), and the data plane VCN 1318 (e.g. the data plane VCN 1218 of FIG.12) can be contained in a customer tenancy 1321 that may be owned or operated by users, or customers, of the system.
  • the control plane VCN 1316 can include a control plane DMZ tier 1320 (e.g.
  • control plane DMZ tier 1220 of FIG.12 that can include LB subnet(s) 1322 (e.g. LB subnet(s) 1222 of FIG.12), a control plane app tier 1324 (e.g. the control plane app tier 1224 of FIG.12) that can include app subnet(s) 1326 (e.g. app subnet(s) 1226 of FIG. 12), a control plane data tier 1328 (e.g. the control plane data tier 1228 of FIG. 12) that can include database (DB) subnet(s) 1330 (e.g. similar to DB subnet(s) 1230 of FIG.12).
  • DB database
  • 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 an Internet gateway 1334 (e.g. the Internet gateway 1234 of FIG. 12) 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 a service gateway 1336 (e.g. the service gateway of FIG. 12) and a network address translation (NAT) gateway 1338 (e.g. the NAT gateway 1238 of FIG. 12).
  • the control plane VCN 1316 can include the service gateway 1336 and the NAT gateway 1338.
  • the control plane VCN 1316 can include a data plane mirror app tier 1340 (e.g. the data plane mirror app tier 1240 of FIG. 12) that can include app subnet(s) 1326.
  • the app subnet(s) 1326 contained in the data plane mirror app tier 1340 can include a virtual network interface controller (VNIC) 1342 (e.g. the VNIC of 1242) that can execute a compute instance 1344 (e.g. similar to the compute instance 1244 of FIG. 12).
  • VNIC virtual network interface controller
  • the compute instance 1344 can facilitate communication between the app subnet(s) 1326 of the data plane mirror app tier 1340 and the app subnet(s) 1326 that can be contained in a data plane app tier 1346 (e.g.
  • the Internet gateway 1334 contained in the control plane VCN 1316 can be communicatively coupled to a metadata management service 1352 (e.g. the metadata management service 1252 of FIG. 12) that can be communicatively coupled to public Internet 1354 (e.g. public Internet 1254 of FIG. 12).
  • Public Internet 1354 can be communicatively coupled to the NAT gateway 1338 contained in the control plane VCN 1316.
  • the service gateway 1336 contained in the control plane VCN 1316 can be communicatively couple to cloud services 1356 (e.g. cloud services 1256 of FIG. 12).
  • the data plane VCN 1318 can be contained in the customer tenancy 1321.
  • the IaaS provider may provide the control plane VCN 1316 for each customer, and the IaaS provider may, for each customer, set up a unique compute instance 1344 that is contained in the service tenancy 1319.
  • Each compute instance 1344 may allow communication between the control plane VCN 1316, contained in the service tenancy 1319, and the data plane VCN 1318 that is contained in the customer tenancy 1321.
  • the compute instance 1344 may allow resources, which are provisioned in the control plane VCN 1316 that is contained in the service tenancy 1319, to be deployed or otherwise used in the data plane VCN 1318 that is contained in the customer tenancy 1321.
  • the customer of the IaaS provider may have databases that live in the customer tenancy 1321.
  • the control plane VCN 1316 can include the data plane mirror app tier 1340 that can include app subnet(s) 1326.
  • the data plane mirror app tier 1340 can reside in the data plane VCN 1318, but the data plane mirror app tier 1340 may not live in the data plane VCN 1318. That is, the data plane mirror app tier 1340 may have access to the customer tenancy 1321, but the data plane mirror app tier 1340 may not exist in the data plane VCN 1318 or be owned or operated by the customer of the IaaS provider.
  • the data plane mirror app tier 1340 may be configured to make calls to the data plane VCN 1318 but may not be configured to make calls to any entity contained in the control plane VCN 1316.
  • the customer may desire to deploy or otherwise use resources in the data plane VCN 1318 that are provisioned in the control plane VCN 1316, and the data plane mirror app tier 1340 can facilitate the desired deployment, or other usage of resources, of the customer.
  • the customer of the IaaS provider can apply filters to the data plane VCN 1318.
  • the customer can determine what the data plane VCN 1318 can access, and the customer may restrict access to public Internet 1354 from the data plane VCN 1318.
  • the IaaS provider may not be able to apply filters or otherwise control access of the data plane VCN 1318 to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN 1318, contained in the customer tenancy 1321, can help isolate the data plane VCN 1318 from other customers and from public Internet 1354.
  • cloud services 1356 can be called by the service gateway 1336 to access services that may not exist on public Internet 1354, on the control plane VCN 1316, or on the data plane VCN 1318.
  • the connection between cloud services 1356 and the control plane VCN 1316 or the data plane VCN 1318 may not be live or continuous. Cloud services 1356 may exist on a different network owned or operated by the IaaS provider.
  • Cloud services 1356 may be configured to receive calls from the service gateway 1336 and may be configured to not receive calls from public Internet 1354. Some cloud services 1356 may be isolated from other cloud services 1356, and the control plane VCN 1316 may be isolated from cloud services 1356 that may not be in the same region as the control plane VCN 1316. For example, the control plane VCN 1316 may be located in “Region 1,” and cloud service “Deployment 12,” may be located in Region 1 and in “Region 2.” If a call to Deployment 12 is made by the service gateway 1336 contained in the control plane VCN 1316 located in Region 1, the call may be transmitted to Deployment 12 in Region 1.
  • FIG. 14 is a block diagram 1400 illustrating another example pattern of an IaaS architecture, according to at least one embodiment.
  • Service operators 1402 e.g. service operators 1202 of FIG.12
  • a secure host tenancy 1404 e.g. the secure host tenancy 1204 of FIG. 12
  • VCN virtual cloud network
  • secure host subnet 1408 e.g. the secure host subnet 1208 of FIG. 12
  • the VCN 1406 can include an LPG 1410 (e.g. the LPG 1210 of FIG. 12) that can be communicatively coupled to an SSH VCN 1412 (e.g. the SSH VCN 1212 of FIG. 12) via an LPG 1410 contained in the SSH VCN 1412.
  • the SSH VCN 1412 can include an SSH subnet 1414 (e.g. the SSH subnet 1214 of FIG. 12), and the SSH VCN 1412 can be communicatively coupled to a control plane VCN 1416 (e.g. the control plane VCN 1216 of FIG.12) via an LPG 1410 contained in the control plane VCN 1416 and to a data plane VCN 1418 (e.g. the data plane 1218 of FIG.
  • the control plane VCN 1416 can include a control plane DMZ tier 1420 (e.g. the control plane DMZ tier 1220 of FIG. 12) that can include load balancer (LB) subnet(s) 1422 (e.g. LB subnet(s) 1222 of FIG. 12), a control plane app tier 1424 (e.g. the control plane app tier 1224 of FIG. 12) that can include app subnet(s) 1426 (e.g.
  • LB load balancer
  • a control plane data tier 1428 (e.g. the control plane data tier 1228 of FIG. 12) that can include DB subnet(s) 1430.
  • the LB subnet(s) 1422 contained in the control plane DMZ tier 1420 can be communicatively coupled to the app subnet(s) 1426 contained in the control plane app tier 1424 and to an Internet gateway 1434 (e.g. the Internet gateway 1234 of FIG. 12) that can be contained in the control plane VCN 1416, and the app subnet(s) 1426 can be communicatively coupled to the DB subnet(s) 1430 contained in the control plane data tier 1428 and to a service gateway 1436 (e.g.
  • the control plane VCN 1416 can include the service gateway 1436 and the NAT gateway 1438.
  • the data plane VCN 1418 can include a data plane app tier 1446 (e.g. the data plane app tier 1246 of FIG. 12), a data plane DMZ tier 1448 (e.g. the data plane DMZ tier 1248 of FIG. 12), and a data plane data tier 1450 (e.g. the data plane data tier 1250 of FIG. 12).
  • the data plane DMZ tier 1448 can include LB subnet(s) 1422 that can be communicatively coupled to trusted app subnet(s) 1460 and untrusted app subnet(s) 1462 of the data plane app tier 1446 and the Internet gateway 1434 contained in the data plane VCN 1418.
  • the trusted app subnet(s) 1460 can be communicatively coupled to the service gateway 1436 contained in the data plane VCN 1418, the NAT gateway 1438 contained in the data plane VCN 1418, and DB subnet(s) 1430 contained in the data plane data tier 1450.
  • the untrusted app subnet(s) 1462 can be communicatively coupled to the service gateway 1436 contained in the data plane VCN 1418 and DB subnet(s) 1430 contained in the data plane data tier 1450.
  • the data plane data tier 1450 can include DB subnet(s) 1430 that can be communicatively coupled to the service gateway 1436 contained in the data plane VCN 1418.
  • the untrusted app subnet(s) 1462 can include one or more primary VNICs 1464(1)- (N) that can be communicatively coupled to tenant virtual machines (VMs) 1466(1)-(N).
  • Each tenant VM 1466(1)-(N) can be communicatively coupled to a respective app subnet 1467(1)- (N) that can be contained in respective container egress VCNs 1468(1)-(N) that can be contained in respective customer tenancies 1470(1)-(N).
  • Respective secondary VNICs 1472(1)-(N) can facilitate communication between the untrusted app subnet(s) 1462 contained in the data plane VCN 1418 and the app subnet contained in the container egress VCNs 1468(1)-(N).
  • Each container egress VCNs 1468(1)-(N) can include a NAT gateway 1438 that can be communicatively coupled to public Internet 1454 (e.g. public Internet 1254 of FIG.12).
  • the Internet gateway 1434 contained in the control plane VCN 1416 and contained in the data plane VCN 1418 can be communicatively coupled to a metadata management service 1452 (e.g. the metadata management system 1252 of FIG. 12) that can be communicatively coupled to public Internet 1454.
  • Public Internet 1454 can be communicatively coupled to the NAT gateway 1438 contained in the control plane VCN 1416 and contained in the data plane VCN 1418.
  • the service gateway 1436 contained in the control plane VCN 1416 and contained in the data plane VCN 1418 can be communicatively couple to cloud services 1456.
  • the data plane VCN 1418 can be integrated with customer tenancies 1470.
  • This integration can be useful or desirable for customers of the IaaS provider in some cases such as a case that may desire support when executing code.
  • the customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects.
  • the IaaS provider may determine whether to run code given to the IaaS provider by the customer. [0193]
  • the customer of the IaaS provider may grant temporary network access to the IaaS provider and request a function to be attached to the data plane tier app 1446. Code to run the function may be executed in the VMs 1466(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN 1418.
  • Each VM 1466(1)-(N) may be connected to one customer tenancy 1470.
  • Respective containers 1471(1)-(N) contained in the VMs 1466(1)-(N) may be configured to run the code.
  • there can be a dual isolation e.g., the containers 1471(1)-(N) running code, where the containers 1471(1)-(N) may be contained in at least the VM 1466(1)-(N) that are contained in the untrusted app subnet(s) 1462), which may help prevent incorrect or otherwise undesirable code from damaging the network of the IaaS provider or from damaging a network of a different customer.
  • the containers 1471(1)-(N) may be communicatively coupled to the customer tenancy 1470 and may be configured to transmit or receive data from the customer tenancy 1470.
  • the containers 1471(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN 1418.
  • the IaaS provider may kill or otherwise dispose of the containers 1471(1)-(N).
  • the trusted app subnet(s) 1460 may run code that may be owned or operated by the IaaS provider.
  • the trusted app subnet(s) 1460 may be communicatively coupled to the DB subnet(s) 1430 and be configured to execute CRUD operations in the DB subnet(s) 1430.
  • the untrusted app subnet(s) 1462 may be communicatively coupled to the DB subnet(s) 1430, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s) 1430.
  • the containers 1471(1)-(N) that can be contained in the VM 1466(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s) 1430.
  • the control plane VCN 1416 and the data plane VCN 1418 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 1416 and the data plane VCN 1418.
  • FIG. 15 is a block diagram 1500 illustrating another example pattern of an IaaS architecture, according to at least one embodiment.
  • Service operators 1502 e.g.
  • a secure host tenancy 1504 e.g. the secure host tenancy 1204 of FIG. 12
  • a secure host tenancy 1504 e.g. the secure host tenancy 1204 of FIG. 12
  • the VCN 1506 can include an LPG 1510 (e.g. the LPG 1210 of FIG. 12) that can be communicatively coupled to an SSH VCN 1512 (e.g. the SSH VCN 1212 of FIG. 12) via an LPG 1510 contained in the SSH VCN 1512.
  • the SSH VCN 1512 can include an SSH subnet 1514 (e.g. the SSH subnet 1214 of FIG. 12), and the SSH VCN 1512 can be communicatively coupled to a control plane VCN 1516 (e.g. the control plane VCN 1216 of FIG.12) via an LPG 1510 contained in the control plane VCN 1516 and to a data plane VCN 1518 (e.g. the data plane 1218 of FIG. 12) via an LPG 1510 contained in the data plane VCN 1518.
  • the control plane VCN 1516 and the data plane VCN 1518 can be contained in a service tenancy 1519 (e.g. the service tenancy 1219 of FIG. 12).
  • the control plane VCN 1516 can include a control plane DMZ tier 1520 (e.g. the control plane DMZ tier 1220 of FIG.12) that can include LB subnet(s) 1522 (e.g. LB subnet(s) 1222 of FIG.12), a control plane app tier 1524 (e.g. the control plane app tier 1224 of FIG.12) that can include app subnet(s) 1526 (e.g. app subnet(s) 1226 of FIG. 12), a control plane data tier 1528 (e.g. the control plane data tier 1228 of FIG. 12) that can include DB subnet(s) 1530 (e.g. DB subnet(s) 1430 of FIG. 14).
  • a control plane DMZ tier 1520 e.g. the control plane DMZ tier 1220 of FIG.12
  • LB subnet(s) 1522 e.g. LB subnet(s) 1222 of FIG.12
  • the LB subnet(s) 1522 contained in the control plane DMZ tier 1520 can be communicatively coupled to the app subnet(s) 1526 contained in the control plane app tier 1524 and to an Internet gateway 1534 (e.g. the Internet gateway 1234 of FIG. 12) that can be contained in the control plane VCN 1516, and the app subnet(s) 1526 can be communicatively coupled to the DB subnet(s) 1530 contained in the control plane data tier 1528 and to a service gateway 1536 (e.g. the service gateway of FIG.12) and a network address translation (NAT) gateway 1538 (e.g. the NAT gateway 1238 of FIG. 12).
  • a service gateway 1536 e.g. the service gateway of FIG.12
  • NAT network address translation
  • the control plane VCN 1516 can include the service gateway 1536 and the NAT gateway 1538.
  • the data plane VCN 1518 can include a data plane app tier 1546 (e.g. the data plane app tier 1246 of FIG. 12), a data plane DMZ tier 1548 (e.g. the data plane DMZ tier 1248 of FIG. 12), and a data plane data tier 1550 (e.g. the data plane data tier 1250 of FIG. 12).
  • the data plane DMZ tier 1548 can include LB subnet(s) 1522 that can be communicatively coupled to trusted app subnet(s) 1560 (e.g. trusted app subnet(s) 1460 of FIG.
  • untrusted app subnet(s) 1562 e.g. untrusted app subnet(s) 1462 of FIG. 14
  • the trusted app subnet(s) 1560 can be communicatively coupled to the service gateway 1536 contained in the data plane VCN 1518, the NAT gateway 1538 contained in the data plane VCN 1518, and DB subnet(s) 1530 contained in the data plane data tier 1550.
  • the untrusted app subnet(s) 1562 can be communicatively coupled to the service gateway 1536 contained in the data plane VCN 1518 and DB subnet(s) 1530 contained in the data plane data tier 1550.
  • the data plane data tier 1550 can include DB subnet(s) 1530 that can be communicatively coupled to the service gateway 1536 contained in the data plane VCN 1518.
  • the untrusted app subnet(s) 1562 can include primary VNICs 1564(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1566(1)-(N) residing within the untrusted app subnet(s) 1562.
  • VMs virtual machines
  • Each tenant VM 1566(1)-(N) can run code in a respective container 1567(1)-(N), and be communicatively coupled to an app subnet 1526 that can be contained in a data plane app tier 1546 that can be contained in a container egress VCN 1568.
  • Respective secondary VNICs 1572(1)-(N) can facilitate communication between the untrusted app subnet(s) 1562 contained in the data plane VCN 1518 and the app subnet contained in the container egress VCN 1568.
  • the container egress VCN can include a NAT gateway 1538 that can be communicatively coupled to public Internet 1554 (e.g. public Internet 1254 of FIG.12).
  • public Internet 1554 e.g. public Internet 1254 of FIG.12
  • the Internet gateway 1534 contained in the control plane VCN 1516 and contained in the data plane VCN 1518 can be communicatively coupled to a metadata management service 1552 (e.g. the metadata management system 1252 of FIG. 12) that can be communicatively coupled to public Internet 1554.
  • Public Internet 1554 can be communicatively coupled to the NAT gateway 1538 contained in the control plane VCN 1516 and contained in the data plane VCN 1518.
  • the service gateway 1536 contained in the control plane VCN 1516 and contained in the data plane VCN 1518 can be communicatively couple to cloud services 1556.
  • the pattern illustrated by the architecture of block diagram 1500 of FIG.15 may be considered an exception to the pattern illustrated by the architecture of block diagram 1400 of FIG. 14 and may be desirable for a customer of the IaaS provider if the IaaS provider cannot directly communicate with the customer (e.g., a disconnected region).
  • the respective containers 1567(1)-(N) that are contained in the VMs 1566(1)-(N) for each customer can be accessed in real-time by the customer.
  • the containers 1567(1)-(N) may be configured to make calls to respective secondary VNICs 1572(1)-(N) contained in app subnet(s) 1526 of the data plane app tier 1546 that can be contained in the container egress VCN 1568.
  • the secondary VNICs 1572(1)-(N) can transmit the calls to the NAT gateway 1538 that may transmit the calls to public Internet 1554.
  • the containers 1567(1)-(N) that can be accessed in real-time by the customer can be isolated from the control plane VCN 1516 and can be isolated from other entities contained in the data plane VCN 1518.
  • the containers 1567(1)-(N) may also be isolated from resources from other customers.
  • the customer can use the containers 1567(1)-(N) to call cloud services 1556.
  • the customer may run code in the containers 1567(1)-(N) that requests a service from cloud services 1556.
  • the containers 1567(1)-(N) can transmit this request to the secondary VNICs 1572(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet 1554.
  • Public Internet 1554 can transmit the request to LB subnet(s) 1522 contained in the control plane VCN 1516 via the Internet gateway 1534.
  • the LB subnet(s) can transmit the request to app subnet(s) 1526 that can transmit the request to cloud services 1556 via the service gateway 1536.
  • IaaS architectures 1200, 1300, 1400, 1500 depicted in the figures may have other components than those depicted. Further, the embodiments shown in the figures are only some examples of a cloud infrastructure system that may incorporate an embodiment of the disclosure. In some other embodiments, the IaaS systems may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration or arrangement of components.
  • the IaaS systems described herein may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner.
  • An example of such an IaaS system is the Oracle Cloud Infrastructure (OCI) provided by the present assignee.
  • FIG. 16 illustrates an example computer system 1600, in which various embodiments may be implemented. The system 1600 may be used to implement any of the computer systems described above. As shown in the figure, computer system 1600 includes a processing unit 1604 that communicates with a number of peripheral subsystems via a bus subsystem 1602.
  • peripheral subsystems may include a processing acceleration unit 1606, an I/O subsystem 1608, a storage subsystem 1618 and a communications subsystem 1624.
  • Storage subsystem 1618 includes tangible computer-readable storage media 1622 and a system memory 1610.
  • Bus subsystem 1602 provides a mechanism for letting the various components and subsystems of computer system 1600 communicate with each other as intended. Although bus subsystem 1602 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1602 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.
  • 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.
  • Processing unit 1604 which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 1600.
  • processors may be included in processing unit 1604. These processors may include single core or multicore processors.
  • processing unit 1604 may be implemented as one or more independent processing units 1632 and/or 1634 with single or multicore processors included in each processing unit. In other embodiments, processing unit 1604 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip. [0208] In various embodiments, processing unit 1604 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) 1604 and/or in storage subsystem 1618. Through suitable programming, processor(s) 1604 can provide various functionalities described above.
  • Computer system 1600 may additionally include a processing acceleration unit 1606, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.
  • I/O subsystem 1608 may include user interface input devices and user interface output devices.
  • User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices.
  • User interface input devices may include, for example, motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands.
  • User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®).
  • 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.
  • 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.
  • User interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc.
  • the display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like.
  • CTR cathode ray tube
  • LCD liquid crystal display
  • plasma display a projection device
  • touch screen a touch screen
  • output device is intended to include all possible types of devices and mechanisms for outputting information from computer system 1600 to a user or other computer.
  • 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.
  • Computer system 1600 may comprise a storage subsystem 1618 that comprises software elements, shown as being currently located within a system memory 1610.
  • System memory 1610 may store program instructions that are loadable and executable on processing unit 1604, as well as data generated during the execution of these programs.
  • system memory 1610 may be volatile (such as random access memory (RAM)) and/or non-volatile (such as read-only memory (ROM), flash memory, etc.)
  • RAM random access memory
  • ROM read-only memory
  • flash memory etc.
  • the RAM typically contains data and/or program modules that are immediately accessible to and/or presently being operated and executed by processing unit 1604.
  • system memory 1610 may include multiple different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • a basic input/output system containing the basic routines that help to transfer information between elements within computer system 1600, such as during start-up, may typically be stored in the ROM.
  • system memory 1610 also illustrates application programs 1612, which may include client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), etc., program data 1614, and an operating system 1616.
  • operating system 1616 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® 16 OS, and Palm® OS operating systems.
  • Storage subsystem 1618 may also provide a tangible computer-readable storage medium for storing the basic programming and data constructs that provide the functionality of some embodiments.
  • Software programs, code modules, instructions that when executed by a processor provide the functionality described above may be stored in storage subsystem 1618.
  • Storage subsystem 1618 may also provide a repository for storing data used in accordance with the present disclosure.
  • Storage subsystem 1600 may also include a computer-readable storage media reader 1620 that can further be connected to computer-readable storage media 1622. Together and, optionally, in combination with system memory 1610, computer-readable storage media 1622 may comprehensively represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, transmitting, and retrieving computer-readable information.
  • Computer-readable storage media 1622 containing code, or portions of code can also 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.
  • computer-readable storage media 1622 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 1622 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 1622 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • SSD solid-state drives
  • 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.
  • Communications subsystem 1624 provides an interface to other computer systems and networks. Communications subsystem 1624 serves as an interface for receiving data from and transmitting data to other systems from computer system 1600. For example, communications subsystem 1624 may enable computer system 1600 to connect to one or more devices via the Internet.
  • communications subsystem 1624 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.
  • RF radio frequency
  • communications subsystem 1624 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.
  • communications subsystem 1624 may also receive input communication in the form of structured and/or unstructured data feeds 1626, event streams 1628, event updates 1630, and the like on behalf of one or more users who may use computer system 1600.
  • communications subsystem 1624 may be configured to receive data feeds 1626 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.
  • RSS Rich Site Summary
  • communications subsystem 1624 may also be configured to receive data in the form of continuous data streams, which may include event streams 1628 of real- time events and/or event updates 1630 that may be continuous or unbounded in nature with no explicit end.
  • 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.
  • Communications subsystem 1624 may also be configured to output the structured and/or unstructured data feeds 1626, event streams 1628, event updates 1630, 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 1600.
  • Computer system 1600 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.
  • 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
  • PC personal computer system
  • workstation e.g., a workstation
  • mainframe e.g., a mainframe
  • kiosk e.g., a server rack
  • server rack e.g., a server rack
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un mécanisme de routage pour des unités de traitement graphique (GPU) qui sont hébergées sur plusieurs machines hôtes dans un environnement en nuage. Pour un paquet transmis par une GPU d'une machine hôte et reçu par un dispositif réseau, le dispositif réseau détermine un port-lien d'entrée du dispositif réseau sur lequel le paquet a été reçu. Le dispositif réseau obtient des informations de flux associées au paquet et calcule, sur la base des informations de flux, un port-lien de sortie du dispositif réseau selon un algorithme de hachage. L'algorithme de hachage est configuré pour hacher des paquets reçus sur un port-lien d'entrée particulier du dispositif réseau et destinés à être transmis sur un même port-lien de sortie du dispositif réseau. Le dispositif réseau transfère le paquet sur le port-lien de sortie du dispositif réseau.
PCT/US2022/034789 2021-06-25 2022-06-23 Politiques de routage pour unités de traitement graphique WO2022271991A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP22747186.9A EP4360280A1 (fr) 2021-06-25 2022-06-23 Politiques de routage pour unités de traitement graphique
JP2023579266A JP2024524992A (ja) 2021-06-25 2022-06-23 グラフィック処理ユニットのルーティングポリシー
CN202280045088.1A CN117597894A (zh) 2021-06-25 2022-06-23 用于图形处理单元的路由策略

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202163215264P 2021-06-25 2021-06-25
US63/215,264 2021-06-25
US17/734,865 US20220417139A1 (en) 2021-06-25 2022-05-02 Routing policies for graphical processing units
US17/734,865 2022-05-02

Publications (1)

Publication Number Publication Date
WO2022271991A1 true WO2022271991A1 (fr) 2022-12-29

Family

ID=82694001

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2022/034789 WO2022271991A1 (fr) 2021-06-25 2022-06-23 Politiques de routage pour unités de traitement graphique

Country Status (3)

Country Link
EP (1) EP4360280A1 (fr)
JP (1) JP2024524992A (fr)
WO (1) WO2022271991A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190097914A1 (en) * 2016-05-27 2019-03-28 Huawei Technologies Co., Ltd. Data forwarding method and device
US20190230025A1 (en) * 2018-01-19 2019-07-25 Vmware, Inc. Methods and apparatus to configure and manage network resources for use in network-based computing
EP3531633A1 (fr) * 2018-02-21 2019-08-28 Intel Corporation Technologies pour l'équilibrage de charge d'un réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190097914A1 (en) * 2016-05-27 2019-03-28 Huawei Technologies Co., Ltd. Data forwarding method and device
US20190230025A1 (en) * 2018-01-19 2019-07-25 Vmware, Inc. Methods and apparatus to configure and manage network resources for use in network-based computing
EP3531633A1 (fr) * 2018-02-21 2019-08-28 Intel Corporation Technologies pour l'équilibrage de charge d'un réseau

Also Published As

Publication number Publication date
EP4360280A1 (fr) 2024-05-01
JP2024524992A (ja) 2024-07-09

Similar Documents

Publication Publication Date Title
US11777848B2 (en) Scalable routing and forwarding of packets in cloud infrastructure
US12074791B2 (en) Packet flow control in a header of a packet
US11637770B2 (en) Invalidating cached flow information in a cloud infrastructure
US11876710B2 (en) Dynamic IP routing in a cloud environment
US11929976B2 (en) Virtual network routing gateway that supports address translation for dataplane as well as dynamic routing protocols (control plane)
US20220417139A1 (en) Routing policies for graphical processing units
US12015562B2 (en) Port addressing via packet header modification
US20230222007A1 (en) Publishing physical topology network locality information for graphical processing unit workloads
US20230224223A1 (en) Publishing physical topology network locality for general workloads
US20240126581A1 (en) Implementing communications within a container environment
US20240152409A1 (en) Routing in a gpu super-cluster
US12086625B2 (en) Multiple top-of-rack (TOR) switches connected to a network virtualization device
US20230246956A1 (en) Invalidating cached flow information in a cloud infrastructure
WO2022271991A1 (fr) Politiques de routage pour unités de traitement graphique
WO2023136964A1 (fr) Publication d'informations de localité de réseau de topologie physique pour charges de travail d'unité de traitement graphique
WO2022271990A1 (fr) Politiques d'acheminement pour unités de traitement graphique
WO2023136965A1 (fr) Publication de localité de réseau de topologie physique pour charges de travail générales
WO2024039520A1 (fr) Mise en œuvre de commutateur double de niveau supérieur pour un nuage de régions dédié au niveau d'un client
WO2024039519A1 (fr) Multiples commutateurs de haut de bâti (tor) connectés à un dispositif de virtualisation de réseau
WO2024039521A1 (fr) Fourniture de services de résistance aux défaillances dans un nuage de régions dédiées au niveau d'un client

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22747186

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202347084377

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2023579266

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 202280045088.1

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2022747186

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022747186

Country of ref document: EP

Effective date: 20240125