Traffic-aware strategy engine

By introducing a Traffic Aware Policy Engine (TAPE), the complexity of managing different layers of the network stack in a cloud computing environment is solved, enabling simplified management and efficient execution of cross-layer policies.

CN123125837APending Publication Date: 2026-11-17ORACLE INT CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202580029351.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-09-03
Filing Date
2025-04-21
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In cloud computing environments, existing technologies struggle to effectively create and maintain rules and policies at different layers of the network stack, resulting in complex and time-consuming management.

Method used

The Traffic Aware Policy Engine (TAPE) is introduced, which integrates different layers of the network stack, allowing users to create simple policies across layers and enforce identity and permission verification within the network, reducing the need to create separate rules for each layer.

Benefits of technology

With TAPE, administrators can simplify policy management, improve network management efficiency, reduce time and resource consumption, and achieve cross-level policy enforcement.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125837A_ABST
    Figure CN123125837A_ABST
Patent Text Reader

Abstract

This paper describes techniques for processing packets and enforcing network policies / rules across different network layers. Instead of having to create rules and policies for each of the different network layers and manually specify where and which devices should enforce those rules / policies, the techniques described herein aim to allow users to create simple policies that integrate different network layers. In some examples, the different network layers are defined by the Open Systems Interconnection (OSI) model.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. non-provisional application No. 18 / 823,339 entitled “TRAFFIC AWARE POLICY ENGINE”, which claims priority to U.S. provisional patent application No. 63 / 639,236 entitled “Traffic Aware Policy Engine”, filed April 26, 2024, the entire disclosure of which is hereby incorporated herein by reference for all purposes. Background Technology

[0003] Cloud computing environments are large and complex systems, comprising many different components and related products / services. Protecting data going to / from these cloud environments, as well as data traveling within them, can be challenging. For example, it is important for companies to control what traffic enters and leaves their networks. However, this can be very difficult given the many different ways to connect the environment and the components within it. Skilled network administrators / technicians create numerous rules and different policies using existing solutions in an attempt to protect their data and networks.

[0004] A further challenge arises from the need to design and create rules and policies to enforce them at each different layer of the network stack. For example, the Open Systems Interconnection (OSI) model breaks down communication into seven distinct layers: Physical Layer 1, Data Link Layer 2, Network Layer 3, Transport Layer 4, Session Layer 5, Presentation Layer 6, and Application Layer 7. Creating rules for each of these different layers can be extremely challenging. Furthermore, after creating and deploying the rules, significant time and money can be spent keeping them up-to-date based on changing network conditions and requirements. Summary of the Invention

[0005] This disclosure generally relates to a Traffic Aware Policy Engine (TAPE) that integrates different layers of the network stack, thereby allowing users to create policies that can enforce simple Layer 2 (L2) rules up to complex pattern and payload verification, as well as advanced authentication of identity and permissions enforced at different points within the network. More specifically, novel techniques for enforcing policies / rules that can be associated with any of the different network layers are described. Using the techniques described herein, instead of having to create different rules and policies for each of the different network layers, a single policy that integrates any / all network layers can be created and enforced by components / devices that include the TAPE throughout the network. As used herein, “TAPE,” “TAPE device,” or “TAPE component” can refer to one or more components / devices (virtual and / or physical) that perform the processing associated with enforcing policies that integrate any / all different network layers.

[0006] In some examples, TAPE can be deployed with network devices involved in intra-network data transfer. In some configurations, TAPE can be deployed with gateways, smartNICs, instances, and other types of network devices. Using TAPE, an administrator or another user can create simple policies that can be enforced across different network layers (e.g., L2-L7+ identities) without requiring the administrator to specify specific rules for each layer. Example policies could be as simple as "Allow only traffic to services A, B, and D from the lease to the service gateway" or "Check payload pattern validation." The specified policy determines how traffic flows across one or more networks.

[0007] This document describes various embodiments to illustrate various features. These embodiments include various methods, systems, non-transitory computer-readable storage media that store programs, code, or instructions executable by one or more processors, etc.

[0008] At least one embodiment relates to a computer-implemented method. Another embodiment relates to a computing device including one or more processors and instructions, which, when executed by the one or more processors, cause the computing device to perform any suitable combination of the methods(one or more) disclosed herein. Yet another embodiment relates to a non-transitory computer-readable medium storing computer-executable instructions, which, when executed by one or more processors of a computing cluster, cause the computing cluster to perform any suitable combination of the methods(one or more) disclosed herein.

[0009] The foregoing, along with other features and embodiments, will become clearer with reference to the following description, claims, and drawings. Attached Figure Description

[0010] To facilitate identification of any discussion of a particular element or action, the most significant one or more digits in the figure references indicate the figure number in which the element was first introduced.

[0011] Figure 1 This is a high-level diagram illustrating a distributed environment of a virtual or overlay cloud network hosted by a cloud service provider infrastructure, according to certain embodiments.

[0012] Figure 2 A simplified architecture diagram of the physical components in the physical network within the CSPI according to certain embodiments is depicted.

[0013] Figure 3 An example arrangement within CSPI according to certain embodiments is shown, in which a host machine is connected to multiple network virtualization devices (NVDs).

[0014] Figure 4 The connectivity between the host machine and the NVD, according to certain embodiments, is described to provide I / O virtualization to support multitenancy.

[0015] Figure 5 A simplified block diagram of a physical network provided by CSPI according to certain embodiments is depicted.

[0016] Figure 6 This is a simplified block diagram illustrating an environment that uses TAPE to enforce network policies / rules in one or more networks according to certain embodiments.

[0017] Figure 7 This is a simplified block diagram illustrating an environment that uses TAPE to enforce network policies / rules in one or more networks according to certain embodiments.

[0018] Figure 8 An example flowchart illustrating a method for processing packets using TAPE according to certain embodiments is shown.

[0019] Figure 9 An example flowchart illustrating a method for processing packets using TAPE according to certain embodiments is shown.

[0020] Figure 10 This is a block diagram illustrating a graphical user interface according to at least one embodiment, the graphical user interface including user interface elements associated with policies, metrics, and logs.

[0021] Figure 11 This is a block diagram illustrating an example pattern of an IaaS architecture according to at least one embodiment.

[0022] Figure 12This is a block diagram illustrating another example pattern of IaaS architecture according to at least one embodiment.

[0023] Figure 13 This is a block diagram illustrating another example pattern of IaaS architecture according to at least one embodiment.

[0024] Figure 14 This is a block diagram illustrating another example pattern of IaaS architecture according to at least one embodiment.

[0025] Figure 15 This is a block diagram illustrating an example computer system according to at least one embodiment. Detailed Implementation

[0026] Example Virtual Networking Architecture

[0027] The term cloud service generally refers to services provided by a cloud service provider (CSP) to users or customers on demand (e.g., via a subscription model) using systems and infrastructure (cloud infrastructure) provided by the CSP. Typically, the servers and systems that make up the CSP's infrastructure are separate from the customer's own on-premises servers and systems. Therefore, customers can utilize cloud services provided by the CSP without having to purchase separate hardware and software resources for the service. Cloud services are designed to provide subscribers with simple, scalable access to applications and computing resources without requiring customers to invest in the infrastructure used to provide the service.

[0028] Several cloud service providers offer various types of cloud services. There are various different types or models of cloud services, including Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), etc.

[0029] A customer can subscribe to one or more cloud services provided by a CSP. A customer can be any entity, such as an individual, organization, or enterprise. When a customer subscribes to or registers for a service provided by a CSP, a lease or account is created for that customer. The customer can then access one or more subscribed cloud resources associated with that account.

[0030] As mentioned above, Infrastructure as a Service (IaaS) is a specific type of cloud computing service. In the IaaS model, a CSP provides customers with infrastructure (called Cloud Service Provider Infrastructure or CSPI) that they can use to build their own customizable networks and deploy customer resources. Therefore, the customer's resources and network are hosted in a distributed environment by the infrastructure provided by the CSP. This differs from traditional computing, where the customer's resources and network are hosted by the infrastructure provided by the customer.

[0031] CSPI can include interconnected high-performance computing resources forming a physical network, including various host machines, memory resources, and network resources. This physical network is also known as the base network or underlying network. Resources in the CSPI can be distributed across one or more data centers, which may be geographically distributed across one or more geographic regions. Virtualization software can be executed by these physical resources to provide a virtualized distributed environment. Virtualization creates overlay networks (also known as software-based networks, software-defined networks, or virtual networks) on the physical network. The CSPI physical network provides the underlying foundation for creating one or more overlay or virtual networks on top of the physical network. The physical network (or base network or underlying network) includes physical network devices such as physical switches, routers, computers, and host machines. An overlay network is a logical (or virtual) network that runs on top of the physical base network. A given physical network can support one or more overlay networks. Overlay networks typically use encapsulation techniques to distinguish traffic belonging to different overlay networks. Virtual or overlay networks are also known as Virtual Cloud Networks (VCNs). Virtual networks are created using software virtualization technologies (e.g., hypervisors, virtualization functions implemented by network virtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR) switches, intelligent TORs that implement one or more functions performed by NVDs, and other mechanisms) to create a layer of network abstraction that can run on top of a physical network. Virtual networks can take many forms, including peer-to-peer networks, IP networks, etc. Virtual networks are typically 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. Examples of protocols developed for virtual networks include IP-in-IP (or Generic Routing Encapsulation (GRE)), Virtual Extensible LAN (VXLAN—IETF RFC 7348), Virtual Private Networks (VPNs) (e.g., MPLS Layer 3 Virtual Private Network (RFC 4364)), VMware's NSX, GENEVE (Generic Network Virtualization Encapsulation), etc.

[0032] For IaaS, the infrastructure provided by a CSP (Center for Service Providers) can be configured to offer virtualized computing resources over a public network (e.g., the Internet). In the IaaS model, cloud service providers can host infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., hypervisor layer), etc.). In some cases, IaaS providers can also provision various services accompanying those infrastructure components (e.g., billing, monitoring, logging, security, load balancing, and clustering, etc.). Therefore, since these services can be policy-driven, IaaS users can implement policies to drive load balancing to maintain application availability and performance. CSPI provides a collection of infrastructure and 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 provides high-performance computing resources and capabilities, as well as storage capacity, in a flexible virtual network securely accessible from various networked locations, such as the customer's on-premises network. When a customer subscribes to or enrolls in an IaaS service provided by a CSP, the lease created for that customer is a secure and isolated partition within the CSP, where the customer can create, organize, and manage their cloud resources.

[0033] Customers can build their own virtual networks using the compute, storage, and networking resources provided by CSPI. One or more customer resources or workloads, such as compute instances, can be deployed on these virtual networks. For example, a customer can use resources provided by CSPI to build one or more customizable and private virtual networks, called Virtual Cloud Networks (VCNs). A customer can deploy one or more customer resources, such as compute instances, on a customer VCN. Compute instances can take the form of virtual machines, bare metal instances, etc. Therefore, CSPI provides a collection of infrastructure and complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available, virtually managed environment. Customers do not manage or control the underlying physical resources provided by CSPI, but they have control over the operating system, storage, and deployed applications; and may also have limited control over selected networking components, such as firewalls.

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

[0035] CSPI can support single-tenant or multi-tenant architectures. In a single-tenant architecture, software (e.g., applications, databases) or hardware components (e.g., host machines or servers) serve a single customer or tenant. In a multi-tenant architecture, the software or hardware components serve multiple customers or tenants. Therefore, in a multi-tenant architecture, CSPI resources are shared among multiple customers or tenants. In a multi-tenant scenario, precautions and safeguards are implemented in CSPI to ensure that each tenant's data is isolated and invisible to other tenants.

[0036] In a physical network, a network endpoint is a computing device or system that connects to and communicates with the physical network. Network endpoints in a physical network can connect to a Local Area Network (LAN), a Wide Area Network (WAN), or other types of physical networks. Examples of traditional endpoints in a physical network include modems, hubs, bridges, switches, routers and other networking devices, physical computers (or host machines), etc. Each physical device in a 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), etc. In a virtualized environment or virtual network, endpoints can include various virtual endpoints, such as virtual machines hosted by components of the physical network (e.g., hosted by physical host machines). These endpoints in a virtual network are addressed using 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 provide flexibility by allowing network administrators to move between overlay addresses associated with network endpoints using software management (e.g., via software implementing a control plane for virtual networks). Correspondingly, unlike physical networks, in virtual networks, overlay addresses (e.g., overlay IP addresses) can be moved from one endpoint to another using network management software. Since virtual networks are built on top of physical networks, communication between components within a virtual network involves both the virtual network and the underlying physical network. To facilitate this communication, CSPI components are configured to learn and store mappings that map overlay addresses in the virtual network to actual physical addresses in the base network, and vice versa. These mappings are then used to facilitate communication. Client traffic is encapsulated to facilitate routing within the virtual network.

[0037] Accordingly, physical addresses (e.g., physical IP addresses) are associated with components in a physical network, and overlay addresses (e.g., overlay IP addresses) are associated with entities in a virtual or overlay network. A physical IP address is an IP address associated with a physical device (e.g., a network device) in the underlying or physical network. For example, each NVD has an associated physical IP address. An overlay IP address is an overlay address associated with an entity in the overlay network, such as a compute instance in a customer's Virtual Cloud Network (VCN). Two different customers or tenants (each with its own private VCN) can potentially use the same overlay IP address in their VCNs without knowing about each other. Both physical IP addresses and overlay IP addresses are types of real IP addresses. These addresses are separate from virtual IP addresses. A virtual IP address is typically a single IP address that represents or maps to multiple real IP addresses. Virtual IP addresses provide a one-to-many mapping between virtual IP addresses and multiple real IP addresses. For example, a load balancer can use a VIP to map to or represent multiple servers, each with its own real IP address.

[0038] Cloud infrastructure, or CSPI, is physically hosted in one or more data centers in one or more regions of the world. CSPI may include components in the physical or underlying network and virtualized components (e.g., virtual networks, compute instances, virtual machines, etc.) in virtual networks built on top of the physical network components. In some embodiments, CSPI is organized and hosted in domains, regions, and availability domains. A region is typically a localized geographical area containing one or more data centers. Regions are generally independent of each other and can be geographically distant, for example, spanning countries or even continents. For example, one region might be in Australia, another in Japan, another in India, and so on. CSPI resources are partitioned between regions, such that each region has its own independent subset of CSPI resources. Each region can provide a collection of core infrastructure services and resources, such as compute resources (e.g., bare metal servers, virtual machines, containers, and related infrastructure); 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-premises networks), database resources; edge networking resources (e.g., DNS); and access management and monitoring resources, etc. Each region typically has multiple paths connecting it to other regions within the domain.

[0039] Generally, applications are deployed in the areas where they are used most frequently (i.e., on the infrastructure associated with that area) because using nearby resources is faster than using resources far away. Applications may also be deployed in different areas for various reasons, such as redundancy to mitigate the risk of events within a region (such as large weather systems or earthquakes), or to meet different requirements such as legal jurisdiction, tax domain, and other business or social standards.

[0040] Data centers within a region can be further organized and subdivided into Availability Domains (ADs). An Availability Domain can correspond to one or more data centers located within the region. A region can consist of one or more Availability Domains. In this distributed environment, CSPI resources are either region-specific, such as Virtual Cloud Networks (VCNs), or Availability Domain-specific, such as compute instances.

[0041] Availability Zones (ADs) within a region are isolated from each other, fault-tolerant, and configured to make simultaneous failures highly unlikely. This is achieved by ensuring that ADs do not share critical infrastructure resources (such as networking, physical cabling, cable paths, cable entry points, etc.), making a failure at one AD within a region unlikely to affect the availability of other ADs in the same region. ADs within the same region can be interconnected via low-latency, high-bandwidth networks, enabling highly available connectivity to other networks (e.g., the internet, customer on-premises networks, etc.) and allowing for replication systems across multiple ADs to achieve both high availability and disaster recovery. Cloud services use multiple ADs to ensure high availability and prevent resource failures. As the infrastructure provided by the IaaS provider grows, more regions and ADs, along with additional capacity, can be added. Traffic between availability domains is typically encrypted.

[0042] In some embodiments, regions are grouped into domains. A domain is a logical set of regions. Domains are isolated from each other and do not share any data. Regions within the same domain can communicate with each other, but regions in different domains cannot. A customer's lease or account with the CSP resides in a single domain and can be distributed across one or more regions belonging to that domain. Typically, when a customer subscribes to an IaaS service, a lease or account is created for that customer in a region within the domain that the customer designates (called the "primary" region). A customer can extend their lease to one or more other regions within the domain. A customer cannot access regions that are not within the domain where their lease resides.

[0043] IaaS providers can offer multiple domains, each catering to the needs of a specific set of customers or users. For example, a business domain can be offered for business customers. As another example, a domain can be offered for customers within a specific country. As yet another example, a government domain can be offered for governments, and so on. For instance, a government domain can meet the needs of a specific government and may have a higher level of security than a business domain. For example, Oracle Cloud Infrastructure (OCI) currently offers domains for its business cloud region and two domains (e.g., FedRAMP licensed and IL5 licensed) for its government cloud region.

[0044] In some embodiments, an Active Directory (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 these instances do not reside on the same physical hardware within a single AD. This is known as anti-affinity. A fault domain refers to a collection of hardware components (computers, switches, etc.) that share a single point of failure. Compute pools are logically divided into fault domains. Therefore, a hardware failure or compute hardware maintenance event affecting one fault domain does not affect instances in other fault domains. Depending on the embodiment, the number of fault domains per AD can vary. For example, in some embodiments, each AD contains three fault domains. Fault domains act as logical data centers within the AD.

[0045] When a customer subscribes to IaaS services, resources from CSPI are provisioned to the customer and associated with the customer's lease. Customers can use these provisioned resources to build private networks and deploy resources on those networks. Customer networks hosted in the cloud by CSPI are called Virtual Cloud Networks (VCNs). Customers can use the CSPI resources allocated to them to set up one or more VCNs. A VCN is a virtual or software-defined private network. Customer resources deployed in a customer's VCN can include compute instances (e.g., virtual machines, bare metal instances) and other resources. These compute instances can represent various customer workloads, such as applications, load balancers, databases, etc. Compute instances deployed on a VCN can communicate with publicly accessible endpoints (“public endpoints”) via public networks (such as the Internet), with other instances in the same VCN or other VCNs (e.g., other VCNs belonging to the customer or VCNs not belonging to the customer), with the customer's on-premises data center or network, and with service endpoints and other types of endpoints.

[0046] CSPs can use CSPIs to provide various services. In some cases, CSPI clients can act as service providers themselves and use CSPI resources to provide services. Service providers can expose service endpoints characterized by identification information such as IP addresses, DNS names, and ports. Client resources (e.g., compute instances) can access a specific service by visiting the service endpoints exposed by the service for that specific service. These service endpoints are generally publicly accessible to users via public communication networks such as the Internet using the public IP addresses associated with the endpoints. Publicly accessible network endpoints are sometimes also called public endpoints.

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

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

[0049] A VCN can be subdivided into one or more subnets, such as one or more subnets. Therefore, a subnet is a configurable unit or subdivision that can be created within a VCN. A VCN can have one or more 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), which do not overlap with other subnets within that VCN and represent a subset of the VCN's address space.

[0050] Each compute instance is associated with a Virtual Network Interface Card (VNIC), which enables the compute instance to participate in subnets within a VCN. A VNIC is the logical representation of a physical network interface card (NIC). Generally, a VNIC is the interface between an entity (e.g., a compute instance, a service) and a virtual network. A VNIC exists within a subnet and has one or more associated IP addresses, along with associated security rules or policies. A VNIC is equivalent to a Layer 2 port on a switch. A VNIC is attached to both the compute instance and the subnet within the VCN. The VNIC associated with a compute instance enables the compute instance to be part of a VCN's subnet and allows the compute instance to communicate (e.g., send and receive packets) with endpoints on the same subnet as the compute instance, with endpoints in different subnets within the VCN, or with endpoints outside the VCN. Therefore, the VNIC associated with a compute instance determines how the compute instance connects to endpoints inside and outside the VCN. When a compute instance is created and added to a subnet within a VCN, a VNIC is created for the compute instance and associated with that compute instance. For a subnet that includes a set of compute instances, the subnet contains a VNIC corresponding to that set of compute instances, with each VNIC attached to a compute instance within that set of compute instances.

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

[0052] In some embodiments, in addition to a private overlay IP address, a compute instance may optionally be assigned additional overlay IP addresses, such as one or more public IP addresses, for example, if in a public subnet. These multiple addresses are assigned either on the same VNIC or on multiple VNICs associated with the compute instance. However, each instance has a primary VNIC, which is created during instance startup and associated with the overlay private IP address assigned to that instance—this primary VNIC cannot be removed. Additional VNICs, called secondary VNICs, can be added to an existing instance in the same availability domain as the primary VNIC. All VNICs are in the same availability domain as the instance. The secondary VNIC can be located in a subnet within the same VCN as the primary VNIC, or in a different subnet within the same VCN or different VCNs.

[0053] If a compute instance is in a public subnet, it can optionally be assigned a public IP address. When creating a subnet, it can be specified as either a public or private subnet. A private subnet means that resources within the subnet (such as compute instances) and associated VNICs cannot have public overriding IP addresses. A public subnet means that resources within the subnet and associated VNICs can have public IP addresses. Customers can specify that a subnet exists within a single availability domain or across multiple availability domains in a region or domain.

[0054] As described above, a VCN can be subdivided into one or more subnets. In some embodiments, a virtual router (VR) configured for a VCN (referred to as a VCN VR or simply VR) enables communication between the subnets of the VCN. For a subnet within a VCN, the VR represents a logical gateway for that subnet, enabling that subnet (i.e., compute instances on that subnet) to communicate with endpoints on other subnets within the VCN as well as with other endpoints outside the VCN. The VCN VR is a logical entity configured to route traffic between the VNIC within the VCN and the virtual gateway (“gateway”) associated with the VCN. The following section discusses… Figure 1Further description of the gateway. A VCN VR is a Layer 3 / IP layer concept. In one embodiment, there exists a VCN VR for a VCN, where the VCN VR potentially has an unlimited number of ports addressable via IP addresses, one port for each subnet of the VCN. In this way, the VCN VR has a different IP address for each subnet within the VCN to which the VCN VR is attached. The VR also connects to various gateways configured for the VCN. In some embodiments, a specific overlay IP address within a range of overlay IP addresses for a subnet is reserved for the port of the VCN VR for that subnet. For example, consider a VCN with two subnets, associated with address ranges 10.0 / 16 and 10.1 / 16. For the first subnet in the VCN with an address range of 10.0 / 16, addresses within this range are reserved for the port of the VCN VR for that subnet. In some cases, the first IP address within the range can be reserved for the VCN VR. For example, for a subnet with an overlay IP address range of 10.0 / 16, the IP address 10.0.0.1 could be reserved for the port of the VCN VR for that subnet. For a second subnet within the same VCN with an address range of 10.1 / 16, the VCN VR can have a port with IP address 10.1.0.1 for the second subnet. The VCN VR has a different IP address for each subnet within the VCN.

[0055] In some other embodiments, each subnet within a VCN may have its own associated VR, which can be addressed by the subnet using a reserved or default IP address associated with the VR. For example, the reserved or default IP address may be the first IP address in the range of IP addresses associated with the subnet. The VNICs within the subnet can use this default or reserved IP address to communicate with the VR associated with the subnet (e.g., send and receive packets). In this embodiment, the VR is the ingress / egress point of the subnet. The VR associated with a subnet within the VCN can communicate with other VRs associated with other subnets within the VCN. The VR can also communicate with the gateway associated with the VCN. The VR functionality of a subnet runs on or is performed by one or more NVDs that perform the VNIC functionality of the VNICs within the subnet.

[0056] You can configure routing tables, security rules, and DHCP options for a VCN. A routing table is a virtual routing table used by the VCN and contains rules that route traffic from subnets within the VCN to destinations outside the VCN via gateways or specially configured instances. The VCN's routing table can be customized to control how packets are forwarded / routed to and from the VCN. DHCP options refer to configuration information automatically provided to the instance when it starts up.

[0057] Security rules configured for a VCN represent overlay firewall rules used by the VCN. Security rules can include ingress and egress rules, specifying the types of traffic allowed to enter and exit instances within the VCN (e.g., based on protocol and port). Clients can choose whether a given rule is stateful or stateless. For example, a client can set up a stateful ingress rule with source CIDR 0.0.0.0 / 0 and destination TCP port 22 to allow a set of incoming SSH traffic from anywhere to an instance. 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 resources within that group. A security list, on the other hand, includes rules applicable to all resources in any subnet using that security list. A default security list with default security rules can be provided to the VCN. DHCP options configured for the VCN provide configuration information that is automatically provided to instances within the VCN at instance startup.

[0058] In some embodiments, configuration information for a VCN is determined and stored by the VCN control plane. For example, the configuration information for a VCN may include information about: the address range associated with the VCN, subnets and associated information within the VCN, one or more VRs associated with the VCN, compute instances and associated VNICs within the VCN, the NVD performing various virtualized network functions associated with the VCN (e.g., VNICs, VRs, gateways), status information for the VCN, and other VCN-related information. In some embodiments, the VCN distribution service publishes the configuration information or portions thereof stored by the VCN control plane to the NVD. The distributed information can be used to update information stored by the NVD and used to forward packets to and from compute instances within the VCN (e.g., forwarding tables, routing tables, etc.).

[0059] In some embodiments, the creation of VCNs and subnets is handled by the VCN control plane (CP), and the initiation of compute instances is handled by the compute control plane. The compute control plane is responsible for allocating physical resources to the compute instances and then invoking the VCN control plane to create VNICs and attach them to the compute instances. The VCN CP also maps VCN data to the VCN data plane, which is configured to perform packet forwarding and routing functions. In some embodiments, the VCN CP provides a distribution service responsible for providing updates to the VCN data plane. Examples of VCN control planes are also available in... Figure 10 , Figure 11 , Figure 12 and Figure 13 The figures are depicted (see reference numerals 1016, 1116, 1216 and 1316) and described below.

[0060] Customers can create one or more VCNs using resources hosted by CSPI. Compute instances deployed on a customer's VCN can communicate with different endpoints. These endpoints can include endpoints hosted by CSPI and endpoints outside of CSPI.

[0061] Various architectures are used to implement cloud-based services using CSPI. Figure 1 , Figure 2 , Figure 3 , Figure 4 , Figure 5 It is described in the text and further described below. Figure 1 This is a high-level diagram of a distributed environment 100, illustrating an overlay or client VCN hosted by CSPI according to certain embodiments. Figure 1 The distributed environment described includes multiple components in the overlay network. Figure 1 The distributed environment 100 depicted herein is merely an example and is not intended to unduly limit the scope of the claimed embodiments. Many variations, substitutions, and modifications are possible. For example, in some implementations, Figure 1 The distributed environment described in the text can have more than Figure 1 The more or fewer systems or components shown can be combined into two or more systems, or can have different system configurations or arrangements.

[0062] like Figure 1 As illustrated in the example, distributed environment 100 includes a CSPI 101 that provides services and resources that customers can subscribe to and use to build their Virtual Cloud Network (VCN). In some embodiments, CSPI 101 provides IaaS services to subscribing customers. Data centers within CSPI 101 can be organized into one or more regions. Figure 1 The example shown is a region "Region US" 102. The customer has already configured customer VCN 104 for region 102. The customer can deploy various compute instances on VCN 104, which can include virtual machines or bare metal instances. Examples of instances include applications, databases, load balancers, etc.

[0063] exist Figure 1 In the embodiment depicted, customer VCN 104 includes two subnets, namely "Subnet-1" and "Subnet-2", each with its own CIDR IP address range. Figure 1In this configuration, subnet-1 covers the IP address range of 10.0 / 16, and subnet-2 covers the address range of 10.1 / 16. VCN Virtual Router 105 represents a logical gateway for the VCN, enabling communication between subnets within VCN 104 and with other endpoints outside the VCN. VCN VR 105 is configured to route traffic between the VNICs within VCN 104 and the gateway associated with VCN 104. VCN VR 105 provides a port for each subnet of VCN 104. For example, VR 105 could 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.

[0064] Multiple compute instances can be deployed on each subnet, where compute instances can be virtual machine instances and / or bare metal instances. Compute instances within a subnet can be hosted by one or more host machines within CSPI 101. Compute instances participate in the subnet via a VNIC associated with the compute instance. For example, as... Figure 1 As shown, compute instance C1 becomes part of subnet-1 via the VNIC associated with it. Similarly, compute instance C2 becomes part of subnet-1 via the VNIC associated with it. In a similar manner, multiple compute instances (which can be virtual machine instances or bare metal instances) can be part of subnet-1. Each compute instance is assigned a private overlay IP address and MAC address via its associated VNIC. For example, in... Figure 1 In this context, compute instance C1 has an overlay IP address of 10.0.0.2 and a MAC address of M1, while compute instance C2 has a private overlay IP address of 10.0.0.3 and a MAC address of M2. Each compute instance in subnet-1 (including compute instances C1 and C2) has a default route to VCN VR 105 using IP address 10.0.0.1, which is the IP address of the port used by VCN VR 105 in subnet-1.

[0065] Multiple compute instances, including virtual machine instances and / or bare metal instances, can be deployed on subnet-2. For example, such as Figure 1 As shown, compute instances D1 and D2 become part of subnet-2 via the VNIC associated with the respective compute instance. Figure 1 In the illustrated embodiment, compute instance D1 has an overlay IP address of 10.1.0.2 and a MAC address of MM1, while compute instance D2 has a private overlay IP address of 10.1.0.3 and a MAC address of MM2. Each compute instance in subnet-2 (including compute instances D1 and D2) has a default route to VCN VR 105 using IP address 10.1.0.1, which is the IP address of the port of VCN VR105 in subnet-2.

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

[0067] A specific compute instance deployed on VCN 104 can communicate with a variety of different endpoints. These endpoints can include endpoints hosted by CSPI 200 and endpoints outside of CSPI 200. Endpoints hosted by CSPI 101 can include: endpoints on the same subnet as the specific compute instance (e.g., communication between two compute instances in subnet-1); endpoints on different subnets but within the same VCN (e.g., communication between a compute instance in subnet-1 and a compute instance in subnet-2); endpoints in different VCNs within the same region (e.g., communication between a compute instance in subnet-1 and endpoints in VCNs in the same region 106 or 110, or communication between a compute instance in subnet-1 and endpoints in service network 110 within the same region); or endpoints in VCNs in different regions (e.g., communication between a compute instance in subnet-1 and endpoints in VCNs in different regions 108). Compute instances in subnets hosted by CSPI 101 can also communicate with endpoints not hosted by CSPI 101 (i.e., outside of CSPI 101). These external endpoints include endpoints in the customer’s on-premises network 116, endpoints in other remote cloud-hosted networks 118, public endpoints 114 that are accessible via public networks such as the Internet, and other endpoints.

[0068] VNICs associated with source and destination compute instances facilitate communication between compute instances on the same subnet. For example, compute instance C1 in subnet-1 might want to send packets to compute instance C2 in subnet-1. For packets originating from the source compute instance and destined for 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 may include determining the packet's destination information from the packet header, identifying any policies (e.g., security lists) configured for the VNIC associated with the source compute instance, determining the packet's next hop, performing any packet encapsulation / decapsulation functions as needed, and then forwarding / routing the packet to the next hop to facilitate communication to its intended destination. When the destination compute instance is in the same subnet as the source compute instance, the VNIC associated with the source compute instance is configured to identify the VNIC associated with the destination compute instance and forward packets to that VNIC for processing. The VNIC associated with the destination compute instance then performs the necessary actions and forwards the packets to the destination compute instance.

[0069] For packets to be transferred from compute instances in a subnet to endpoints in different subnets within the same VCN, communication is facilitated by the VNIC associated with the source and destination compute instances, as well as the VCN VR. For example, if Figure 1 If compute instance C1 in subnet-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 VCN VR 105 using the 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. Then, the VNIC associated with D1 receives and processes the packet and forwards it to compute instance D1.

[0070] For packets to be transferred from a compute instance in VCN 104 to an endpoint outside VCN 104, communication is facilitated by the VNIC associated with the source compute instance, VCN VR 105, and the gateway associated with VCN 104. One or more types of gateways can be associated with VCN 104. A gateway is an interface between a VCN and another endpoint located outside the VCN. A gateway is a Layer 3 / IP concept and enables a VCN to communicate with endpoints outside the VCN. Therefore, a gateway facilitates traffic flow between a VCN and other VCNs or networks. Various different types of gateways can be configured for a VCN to facilitate different types of communication with different types of endpoints. Depending on the gateway, communication can be conducted over a public network (e.g., the Internet) or over a private network. Various communication protocols can be used for these communications.

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

[0072] Various types of gateways can be configured for a VCN. Examples of gateways that can be configured for a VCN are available in [link / details]. Figure 1 It is depicted in [the text] and described below. Examples of gateways associated with VCNs are also [described in the text]. Figure 10 , Figure 11 , Figure 12 and Figure 13 The gateways are depicted (e.g., referenced by reference numerals 1034, 1036, 1038, 1134, 1136, 1138, 1234, 1236, 1238, 1334, 1336, and 1338) and are described below. Figure 1As depicted in the embodiments, a Dynamic Routing Gateway (DRG) 122 can be added to or associated with a customer VCN 104 and provides a path for private network traffic communication between the customer VCN 104 and another endpoint, which can be the customer's on-premises network 116, a VCN 108 in a different region of CSPI 101, or another remote cloud network 118 not hosted by CSPI 101. The customer's on-premises network 116 can be a customer network or customer data center built using the customer's resources. Access to the customer's on-premises network 116 is generally very restricted. For customers who have both a customer's on-premises network 116 and one or more VCNs 104 deployed or hosted in the cloud by CSPI 101, the customer may want their on-premises network 116 and their cloud-based VCN 104 to be able to communicate with each other. This allows customers to build extended hybrid environments encompassing the customer's VCN 104 hosted by CSPI 101 and their on-premises network 116. The DRG 122 enables this communication. To enable this type of communication, a communication channel 124 is set up, with one endpoint located in the customer's on-premises network 116 and the other endpoint located in CSPI 101 and connected to the customer's VCN 104. Communication channel 124 can be over a public communication network (such as the Internet) or a private communication network. Various communication protocols can be used, such as IPsec VPN technology over a public communication network (such as the Internet), Oracle's FastConnect technology using a private network instead of a public network, etc. The device or equipment forming one endpoint of communication channel 124 in the customer's on-premises network 116 is referred to as customer premises equipment (CPE), such as... Figure 1 The CPE126 is depicted in the diagram. On the CSPI 101 side, the endpoint can be a host machine executing DRG 122.

[0073] In some embodiments, a remote peering connection (RPC) can be added to the DRG, which allows a customer to peer one VCN with another VCN in a different region. Using such an RPC, customer VCN 104 can use DRG 122 to connect to VCN 108 in another region. DRG 122 can also be used to communicate with other remote cloud networks 118 not hosted by CSPI 101, such as Microsoft Azure Cloud, Amazon AWS Cloud, etc.

[0074] like Figure 1As shown, an Internet Gateway (IGW) 120 can be configured for customer VCN 104, enabling compute instances on VCN 104 to communicate with a public endpoint 114 accessible via a public network, such as the Internet. IGW 120 is a gateway connecting the VCN to a public network, such as the Internet. IGW 120 enables public subnets within the VCN (such as VCN 104), where resources have publicly overridden IP addresses, to directly access a public endpoint 112 on the public network 114 (such as the Internet). Using IGW 120, connections can be initiated from subnets within VCN 104 or from the Internet.

[0075] Network Address Translation (NAT) gateway 128 can be configured for a customer's VCN 104, enabling cloud resources within the customer's VCN that do not have dedicated public overlay IP addresses to access the Internet, and it does so without exposing those resources to directly incoming Internet connections (e.g., L4-L7 connections). This allows private subnets within the VCN (such as private subnet-1 in VCN 104) to privately access public endpoints on the Internet. In a NAT gateway, connections can only be initiated from a private subnet to the public Internet, and not from the Internet to a private subnet.

[0076] In some embodiments, a Service Gateway (SGW) 126 may be configured for a customer's VCN 104 and provide a path for private network traffic between VCN 104 and service endpoints supported in Service Network 110. In some embodiments, Service Network 110 may be provided by a CSP and may offer a variety of services. An example of such a service network is Oracle's service network, which provides a variety of services available to customers. For example, compute instances (e.g., database systems) in a private subnet of customer VCN 104 may back up data to service endpoints (e.g., object storage) without requiring a public IP address or access to the Internet. In some embodiments, a VCN may have only one SGW, and connections may only originate from subnets within the VCN, not from Service Network 110. If a VCN is peered to another, resources in the other VCN typically cannot access the SGW. Resources in an on-premises network connected to a VCN using FastConnect or VPN Connect may also use the Service Gateway configured for that VCN.

[0077] In some implementations, the SGW 126 uses the concept of a Service Classless Inter-Domain Routing (CIDR) label, which is a string representing the range of all regional public IP addresses used for the service or group of services of interest. Customers use the Service CIDR label when configuring the SGW and associated routing rules to control traffic to the service. Customers can optionally use it when configuring security rules without needing to adjust the security rules if the public IP addresses of the service change in the future.

[0078] Local peering gateway (LPG) 132 is a gateway that can be added to customer VCN 104 and enable VCN 104 to peer with another VCN in the same area. Peering refers to VCNs communicating using private IP addresses without traffic traversing public networks (such as the Internet) or routing traffic through the customer's on-premises network 116. In a preferred embodiment, a VCN has a separate LPG for each peering it establishes. Local peering, or VCN peering, is a common practice for establishing network connectivity between different applications or infrastructure management functions.

[0079] Service providers (such as service providers in service network 110) can offer access to services using different access models. Under the public access model, a service can be exposed as a public endpoint accessible to compute instances within a customer's VCN via a public network (such as the Internet), and / or privately accessible via SGW 126. Under a specific private access model, a service can be accessed as a private IP endpoint within a private subnet of the customer's VCN. This is called Private Endpoint (PE) access and enables service providers to expose their services as instances within the customer's private network. A private endpoint resource represents a service within the customer's VCN. Each PE is represented as a VNIC (called a PE-VNIC, with one or more private IPs) within the customer's VCN in a subnet chosen by the customer. Thus, the PE provides a way to present services within a private customer VCN subnet using a VNIC. Because the endpoint is exposed as a VNIC, all characteristics associated with the VNIC (such as routing rules, security lists, etc.) are now available for the PE VNIC.

[0080] Service providers can register their services to enable access via PE. Providers can associate policies with services, which restricts the visibility of services to customer leases. Providers can register multiple services under a single Virtual IP address (VIP), especially for multi-tenant services. Multiple such private endpoints (across multiple VCNs) can represent the same service.

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

[0082] The PE concept can also be used to extend private access to services to a customer's on-premises network and data center by allowing traffic to flow through FastConnect / IPsec links and private endpoints within the customer's VCN. Private access to services can also be extended to the customer's peering VCN by allowing traffic to flow between the LPG 132 and the PE within the customer's VCN.

[0083] Customers can control routing within a VCN at the subnet level, allowing them to specify which subnets within a customer's VCN (such as VCN104) use each gateway. The VCN's routing table is used to determine whether traffic is allowed to leave the VCN via a specific gateway. For example, in a given instance, the routing table for public subnets within customer VCN 104 might send non-local traffic via IGW 120. The routing table for private subnets within the same customer VCN 104 might send traffic destined for CSP services via SGW 126. All remaining traffic might be sent via NAT gateway 128. The routing table only controls traffic leaving the VCN.

[0084] Security lists associated with a VCN are used to control traffic entering the VCN via a gateway through inbound connections. All resources within a subnet use the same routing tables and security lists. Security lists can be used to control specific types of traffic allowed to enter or leave instances within a subnet of the VCN. Security list rules can include inbound and outbound rules. For example, inbound rules can specify allowed source address ranges, while outbound rules can specify allowed destination address ranges. Security rules can specify specific protocols (e.g., TCP, ICMP), specific ports (e.g., port 22 for SSH, port 3389 for Windows RDP), etc. In some implementations, the instance's operating system can enforce its own firewall rules that conform to the security list rules. Rules can be stateful (e.g., tracking connections and automatically allowing responses without explicit security list rules for response traffic) or stateless.

[0085] Access from a customer's VCN (i.e., through resources or compute instances deployed on VCN 104) can be categorized as public access, private access, or dedicated access. Public access refers to an access model that uses a public IP address or NAT to access a public endpoint. Private access enables customer workloads with private IP addresses within VCN 104 (e.g., resources in a private subnet) to access services without traversing a public network such as the Internet. In some embodiments, CSPI 101 enables customer VCN workloads with private IP addresses to access the service's (public service endpoint) using a service gateway. Thus, the service gateway provides a private access model by establishing a virtual link between the customer's VCN and the public endpoint of the service residing outside the customer's private network.

[0086] Furthermore, CSPI can provide private public access using technologies such as FastConnect public peering, where on-premises instances can access one or more services within a customer's VCN using FastConnect connections without traversing public networks such as the internet. CSPI can also provide private private access using FastConnect private peering, where on-premises instances with private IP addresses can access a customer's VCN workloads using FastConnect connections. FastConnect is a network connectivity alternative to using the public internet to connect a customer's on-premises network to CSPI and its services. Compared to internet-based connections, FastConnect offers a simple, flexible, and cost-effective way to create private and private connections with higher bandwidth options and a more reliable and consistent network experience.

[0087] Figure 1The accompanying description above describes the various virtualized components in the example virtual network. As mentioned above, the virtual network is built on the underlying physical or base network. Figure 2 A simplified architecture diagram of the physical components within the physical network of the CSPI 200, which provides the underlying layer for virtual networks according to certain embodiments, is depicted. As shown, the CSPI 200 provides a distributed environment including components and resources (e.g., compute, storage, and network resources) provided by a cloud service provider (CSP). These components and resources are used to provide cloud services (e.g., IaaS services) to subscribed customers (i.e., customers who have subscribed to one or more services provided by the CSP). Based on the services subscribed to by the customer, a subset of the resources of the CSPI 200 (e.g., compute, storage, and network resources) is provisioned to the customer. The customer can then use the physical compute, storage, and networking resources provided by the CSPI 200 to build their own cloud-based (i.e., CSPI-hosted) customizable and private virtual networks. As indicated above, these customer networks are referred to as Virtual Cloud Networks (VCNs). Customers can deploy one or more customer resources, such as compute instances, on these customer VCNs. Compute instances can take the form of virtual machines, bare metal instances, etc. The CSPI 200 provides a collection of infrastructure and complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available managed environment.

[0088] exist Figure 2 In the example embodiment depicted, 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), as well as switches within physical network 218. The physical host machines or servers can host and execute various compute instances participating in one or more subnets of the VCN. Compute instances can include virtual machine instances and bare metal instances. For example, Figure 1 The various computational examples described in the text can be derived from... Figure 2 The physical host machine described in the diagram is used for hosting virtual machine compute instances in a VCN. Virtual machine compute instances in a VCN can be executed by one host machine or multiple different host machines. A physical host machine can also host virtual host machines, container-based hosts, or functions, etc. Figure 1 The VNIC and VCN VR described in the text can be generated by Figure 2 The NVD execution described in the text. Figure 1 The gateway described herein can be a host machine and / or Figure 2 The NVD execution described in [the document / document].

[0089] A host machine or server can execute a hypervisor (also known as a virtual machine monitor or VMM) that creates and enables virtualized environments on the host machine. Virtualized or virtualized environments facilitate cloud-based computing. One or more compute instances can be created, executed, and managed on the host machine by a hypervisor on that host machine. The hypervisor on the host machine enables the host machine's physical computing resources (e.g., compute, storage, and network resources) to be shared among various compute instances executed by the host machine.

[0090] For example, such as Figure 2 As depicted, host machines 202 and 208 execute hypervisors 260 and 266, respectively. These hypervisors can be implemented using software, firmware, or hardware, or a combination thereof. Typically, a hypervisor is a process or software layer residing above the host machine's operating system (OS), which in turn executes on the host machine's hardware processor. Hypervisors provide a virtualized environment by enabling the host machine's physical computing resources (e.g., processing resources such as processors / cores, memory resources, network resources) to be shared among various virtual machine computing instances executed by the host machine. For example, in... Figure 2 In this configuration, the hypervisor 260 can reside on top of the operating system of the host machine 202 and enable the computing resources (e.g., processing, memory, and network resources) of the host machine 202 to be shared among computing instances (e.g., virtual machines) executed by the host machine 202. Virtual machines can have their own operating systems (called guest operating systems), which can be the same as or different from the host machine's operating system. The operating system of a virtual machine executed by the host machine can be the same as or different from the operating system of another virtual machine executed by the same host machine. Therefore, the hypervisor enables multiple operating systems to be executed simultaneously, while sharing the same computing resources of the host machine. Figure 2 The host machines described in the text may have the same or different types of management programs.

[0091] A compute instance can be a virtual machine instance or a bare metal instance. Figure 2 In the diagram, compute instance 268 on host machine 202 and compute instance 274 on host machine 208 are examples of virtual machine instances. Host machine 206 is an example of a bare metal instance provided to a customer.

[0092] In some cases, an entire host machine can be provisioned to a single customer, and one or more compute instances (or virtual machines or bare metal instances) hosted by that host machine all belong to the same customer. In other cases, the host machine can be shared among multiple customers (i.e., multiple tenants). In this multi-tenancy scenario, the host machine can host virtual machine compute instances belonging to different customers. These compute instances can be members of different VCNs for different customers. In some embodiments, bare metal compute instances are hosted by bare metal servers without a hypervisor. When provisioning a bare metal compute instance, a single customer or tenant maintains control over the physical CPU, memory, and network interfaces of the host machine hosting that bare metal instance, and the host machine is not shared with other customers or tenants.

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

[0094] For compute instances hosted by a host machine, NVDs connected to that host machine also execute VCN VR corresponding to the VCN where the compute instance is a member. For example, in Figure 2 In the embodiment depicted, NVD 210 executes VCN VR 277 corresponding to the VCN of compute instance 268, which is a member of NVD 212. NVD 212 may also execute one or more VCN VR 283 corresponding to the VCNs of compute instances hosted by host machines 206 and 208.

[0095] The host machine may include one or more network interface cards (NICs) that enable the host machine to connect to other devices. The NIC on the host machine may provide one or more ports (or interfaces) that allow the host machine to communicatively connect to another device. For example, the host machine may connect to the NVD using one or more ports (or interfaces) provided on the host machine and the NVD. The host machine may also connect to other devices, such as another host machine.

[0096] For example, in Figure 2 In this configuration, host machine 202 is connected to NVD 210 via link 220, which extends between port 234 provided by NIC 232 of host machine 202 and port 236 of NVD 210. Host machine 206 is connected to NVD 212 via link 224, which extends between port 246 provided by NIC 244 of host machine 206 and port 248 of NVD 212. Host machine 208 is connected to NVD 212 via link 226, which extends between port 252 provided by NIC 250 of host machine 208 and port 254 of NVD 212.

[0097] The NVD is then connected to top-of-rack (TOR) switches via communication links, which are connected to physical network 218 (also known as the switching architecture). In some embodiments, the links between the host machine and the NVD, and between the NVD and the TOR switches, are Ethernet links. For example, in Figure 2 In this configuration, NVDs 210 and 212 are connected to TOR switches 214 and 216 via links 228 and 230, respectively. In some embodiments, links 220, 224, 226, 228, and 230 are Ethernet links. The set of host machines connected to the TOR and the NVDs is sometimes referred to as a rack.

[0098] Physical network 218 provides a communication architecture that enables TOR switches to communicate with each other. Physical network 218 can be a multi-layer network. In some implementations, physical network 218 is a multi-layer Clos network of switches, where TOR switches 214 and 216 represent leaf-level nodes of the multi-layer and multi-node physical switching network 218. Different Clos network configurations are possible, including but not limited to Layer 2 networks, Layer 3 networks, Layer 4 networks, Layer 5 networks, and general "n"-layer networks. Examples of Clos networks are provided in... Figure 5 It is depicted in the middle and described below.

[0099] Various connection configurations can exist between the host machine and the NVD, such as one-to-one, many-to-one, and one-to-many configurations. In a one-to-one configuration, each host machine connects to its own individual NVD. For example, in... Figure 2 In this configuration, host machine 202 connects to NVD 210 via its NIC 232. In a many-to-one configuration, multiple host machines connect to a single NVD. For example, in... Figure 2 In this configuration, host machines 206 and 208 are connected to the same NVD 212 via NICs 244 and 250, respectively.

[0100] In a one-to-many configuration, a host machine connects to multiple NVDs. Figure 3 An example within the CSPI 300 is shown, where a host machine is connected to multiple NVDs. (Example follows) Figure 3 As shown, host machine 302 includes a network interface card (NIC) 304, which includes multiple ports 306 and 308. Host machine 300 is connected to a first NVD 310 via port 306 and link 320, and to a second NVD 312 via port 308 and link 322. Ports 306 and 308 may be Ethernet ports, and links 320 and 322 between host machine 302 and NVDs 310 and 312 may be Ethernet links. NVD 310 is further connected to a first TOR switch 314, and NVD 312 is connected to a second TOR switch 316. Links between NVDs 310 and 312 and TOR switches 314 and 316 may be Ethernet links. TOR switches 314 and 316 represent Layer 0 switching devices in a multi-layer physical network 318.

[0101] Figure 3 The layout depicted provides two separate physical network paths between physical switch network 318 and host machine 302: the first path goes through TOR switch 314 to NVD 310 and then to host machine 302, and the second path goes through TOR switch 316 to NVD 312 and then to host machine 302. These separate paths provide enhanced availability (referred to as high availability) for host machine 302. If one of the paths (e.g., a link in one of the paths breaks) or a device (e.g., a particular NVD is not running) experiences a problem, the other path can be used for communication to / from host machine 302.

[0102] exist Figure 3 In the configuration depicted, the host machine connects to two different NVDs using two different ports provided by the host machine's NIC. In other embodiments, the host machine may include multiple NICs that enable the host machine to connect to multiple NVDs.

[0103] Go back to reference Figure 2An NVD is a physical device or component that performs one or more network and / or storage virtualization functions. An NVD can be any device with one or more processing units (e.g., CPU, Network Processing Unit (NPU), FPGA, packet processing pipeline, etc.), memory including cache, and ports. Various virtualization functions can be executed by software / firmware performed by one or more processing units of the NVD.

[0104] NVDs can be implemented in various different forms. For example, in some embodiments, an NVD is implemented as an interface card called a smartNIC or a smart NIC with an onboard embedded processor. A smartNIC is a device separate from the NIC on the host machine. Figure 2 In this context, NVD 210 and 212 can be implemented as smartNICs connected to host machine 202 and host machines 206 and 208, respectively.

[0105] However, smartNIC is just one example of an NVD implementation. Various other implementations are possible. For example, in some other implementations, the NVD, or one or more functions performed by the NVD, may be integrated into or performed by one or more host machines, one or more TOR switches, and other components of the CSPI 200. For example, the NVD may be implemented within a host machine, where the functions performed by the NVD are performed by the host machine. As another example, the NVD may be part of a TOR switch, or the TOR switch may be configured to perform functions performed by the NVD, enabling the TOR switch to perform various complex packet transformations for public clouds. TORs performing the functions of the NVD are sometimes referred to as smart TORs. In other implementations that serve virtual machine (VM) instances rather than bare metal (BM) instances to customers, the functions performed by the NVD may be implemented within the hypervisor of the host machine. In some other implementations, some of the functions of the NVD may be offloaded to a centralized service running on a set of host machines.

[0106] In some embodiments, such as when implemented as Figure 2 As shown in the smartNIC diagram, the NVD can include multiple physical ports that enable it to connect to one or more host machines and one or more TOR switches. Ports on the NVD can be classified as host-facing ports (also known as "south ports") or network-facing or TOR-facing ports (also known as "north ports"). The host-facing ports of the NVD are those used to connect the NVD to the host machine. Figure 2 Examples of host-facing ports include port 236 on the NVD 210 and ports 248 and 254 on the NVD 212. Network-facing ports on the NVD are used to connect the NVD to a TOR switch. Figure 2 Examples of network-facing ports include port 256 on the NVD 210 and port 258 on the NVD 212. Figure 2 As shown, NVD 210 is connected to TOR switch 214 via link 228, which extends from port 256 of NVD 210 to TOR switch 214. Similarly, NVD 212 is connected to TOR switch 216 via link 230, which extends from port 258 of NVD 212 to TOR switch 216.

[0107] The NVD receives packets and frames from the host machine (e.g., packets and frames generated by compute instances hosted by the host machine) via its host-facing port, and after performing the necessary packet processing, can forward the packets and frames to the TOR switch via its network-facing port. The NVD can also receive packets and frames from the TOR switch via its network-facing port, and after performing the necessary packet processing, can forward the packets and frames to the host machine via its host-facing port.

[0108] In some embodiments, there can be multiple ports and associated links between the NVD and TOR switches. These ports and links can be aggregated to form a link aggregation group (called a LAG) of multiple ports or links. Link aggregation allows multiple physical links between two endpoints (e.g., between the NVD and TOR switches) to be treated as a single logical link. All physical links in a given LAG can operate at the same speed in full-duplex mode. LAGs help increase the bandwidth and reliability of the connection between two endpoints. If one of the physical links in the LAG fails, traffic will be dynamically and transparently reassigned to one of the other physical links in the LAG. Aggregated physical links deliver higher bandwidth than each individual link. Multiple ports associated with an LAG are treated as a single logical port. Traffic can be load balanced across multiple physical links in the LAG. One or more LAGs can be configured between two endpoints. These endpoints can be located between the NVD and TOR switches, between a host machine and the NVD, etc.

[0109] The NVD implements or performs network virtualization functions. These functions are performed by software / firmware executed by the NVD. Examples of network virtualization functions include, but are not limited to: packet encapsulation and decapsulation functions; functions for creating VCN networks; functions for implementing network policies, such as VCN security list (firewall) functionality; functions for facilitating the routing and forwarding of packets to and from compute instances in the VCN; and so on. In some embodiments, upon receiving a packet, the NVD is configured to execute a packet processing pipeline for processing the packet and determining how to forward or route the packet. As part of this packet processing pipeline, the NVD may perform one or more virtual functions associated with the overlay network, such as executing VNICs associated with compute instances in the VCN, executing virtual routers (VRs) associated with the VCN, packet encapsulation and decapsulation to facilitate forwarding or routing in the virtual network, execution of certain gateways (e.g., local peer gateways), implementation of security lists, network security groups, Network Address Translation (NAT) functionality (e.g., host-by-host translation of public IPs to private IPs), throttling functions, and other functions.

[0110] In some embodiments, the packet processing data path in the NVD may include multiple packet pipelines, each consisting of a series of packet transformation stages. In some implementations, upon receiving a packet, the packet is parsed and classified into a single pipeline. The packet is then processed linearly, stage by stage, until the packet is dropped or sent out through the NVD's interface. These stages provide basic functional packet processing building blocks (e.g., header verification, throttling, insertion of new Layer 2 headers, L4 firewall enforcement, VCN encapsulation / decapsulation, etc.) so that new pipelines can be built by combining existing stages, and new functionality can be added by creating new stages and inserting them into existing pipelines.

[0111] NVD can perform control plane and data plane functions corresponding to those of VCN's control plane and data plane. An example of the VCN control plane is also available in... Figure 11 , Figure 12 , Figure 13 and Figure 14 The VCN data plane is depicted (see reference numerals 1116, 1216, 1316, and 1416) and described below. An example of the VCN data plane is shown in... Figure 11 , Figure 12 , Figure 13 and Figure 14The diagram is depicted in Figures 1118, 1218, 1318, and 1418 and described below. Control plane functions include features for configuring the network (e.g., setting routes and routing tables, configuring VNICs, etc.) and how network control data is forwarded. In some embodiments, a VCN control plane is provided that centrally computes all overlay mappings to the base layer and publishes them to the NVD and virtual network edge devices (such as various gateways, such as DRGs, SGWs, IGWs, etc.). Firewall rules can also be published using the same mechanism. In some embodiments, the NVD only receives mappings associated with that NVD. Data plane functions include the ability to actually route / forward packets based on the configuration set using the control plane. The VCN data plane is implemented by encapsulating client network packets before they traverse the base network. Encapsulation / decapsulation functionality is implemented on the NVD. In some embodiments, the NVD is configured to intercept all network packets entering and leaving the host machine and perform network virtualization functions.

[0112] As indicated above, NVD performs various virtualization functions, including VNIC and VCN VR. NVD can execute VNICs associated with compute instances hosted on one or more host machines connected to the VNIC. For example, as... Figure 2 As depicted, NVD 210 performs the functionality of VNIC 276 associated with compute instance 268 hosted by host machine 202 connected to NVD 210. As another example, NVD 212 performs VNIC 280 associated with bare-metal compute instance 272 hosted by host machine 206, and VNIC 284 associated with compute instance 274 hosted by host machine 208. Host machines can host compute instances belonging to different VCNs (which belong to different customers), and NVDs connected to host machines can perform VNICs corresponding to compute instances (i.e., perform VNIC-related functionality).

[0113] NVD also executes a VCN virtual router corresponding to the VCN of the compute instance. For example, in Figure 2 In the embodiments depicted, NVD 210 executes VCN VR 277 corresponding to the VCN to which compute instance 268 belongs. NVD 212 executes one or more VCN VR 283 corresponding to one or more VCNs to which compute instances hosted by host machines 206 and 208 belong. In some embodiments, the VCN VR corresponding to a VCN is executed by all NVDs connected to host machines hosting at least one compute instance belonging to that VCN. If a host machine hosts compute instances belonging to different VCNs, then NVDs connected to that host machine can execute VCN VR corresponding to those different VCNs.

[0114] In addition to VNIC and VCN VR, NVD can execute various software (e.g., daemons) and includes one or more hardware components that facilitate various network virtualization functions performed by NVD. For simplicity, these various components are grouped together as... Figure 2 The term "packet processing component" is shown in the diagram. For example, NVD 210 includes packet processing component 286 and NVD 212 includes packet processing component 288. For instance, a packet processing component for an NVD may include a packet processor configured to interact with the NVD's ports and hardware interfaces to monitor all packets received by and transmitted using the NVD and to store network information. This network information may include, for example, network flow information identifying different network flows handled by the NVD and per-flow information (e.g., per-flow statistics). In some embodiments, network flow information may be stored on a per-VNIC basis. The packet processor may perform per-packet manipulation and implement stateful NAT and L4 firewall (FW). As another example, a packet processing component may include a replication agent configured to replicate information stored by the NVD to one or more different replication target repositories. As yet another example, a packet processing component may include a logging agent configured to perform logging functions of the NVD. The packet processing component may also include software for monitoring the performance and health of the NVD and may also monitor the status and health of other components connected to the NVD.

[0115] Figure 1 The components of an example virtual or overlay network are shown, including a VCN, subnets within the VCN, compute instances deployed on the subnets, VNICs associated with the compute instances, VRs for the VCN, and a collection of gateways configured for the VCN. Figure 1 The overlay component described in the text can be made by Figure 2 One or more executions or hosts are described in the physical components. For example, a compute instance in a VCN can be executed or managed by... Figure 2 The VNIC described herein is executed or hosted by one or more host machines. For a compute instance hosted by a host machine, the VNIC associated with that compute instance is typically executed by an NVD connected to that host machine (i.e., VNIC functionality is provided by an NVD connected to that host machine). The VCN VR functionality for a VCN is executed by all NVDs connected to the host machine hosting or executing a compute instance as part of that VCN. The gateway associated with a VCN can be executed by one or more different types of NVDs. For example, some gateways can be executed by smartNICs, while others can be executed by one or more host machines or other implementations of NVDs.

[0116] As described above, compute instances in a client VCN can communicate with various endpoints, which may be in the same subnet as the source compute instance, in a different subnet but within the same VCN as the source compute instance, or outside the source compute instance's VCN. These communications are facilitated using VNICs, VCN VRs, and gateways associated with the VCNs.

[0117] For communication between two compute instances on the same subnet within a VCN, a VNIC associated with both the source and destination compute instances facilitates the communication. The source and destination compute instances can be hosted by the same host machine or different host machines. Packets originating from the source compute instance can be forwarded from the host machine hosting the source compute instance to an NVD connected to that host machine. On the NVD, packets are processed using a packet processing pipeline, which may include the execution of the VNIC associated with the source compute instance. Because the destination endpoint of the packet is within the same subnet, the execution of the VNIC associated with the source compute instance results in the packet being forwarded to the NVD executing the VNIC associated with the destination compute instance, which then processes the packet and forwards it to the destination compute instance. The VNIC associated with the source and destination compute instances can execute on the same NVD (e.g., when 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 VNIC can use a routing / forwarding table stored by the NVD to determine the next hop for the packet.

[0118] For packets destined for endpoints in different subnets within the same VCN, the packet originating from the source compute instance is forwarded from the host machine hosting the source compute instance to the NVD connected to that host machine. On the NVD, the packet is processed using a packet processing pipeline, which may include the execution of one or more VNICs and the VR associated with the VCN. For example, as part of the packet processing pipeline, the NVD executes or invokes a function corresponding to the VNIC associated with the source compute instance (also known as executing the VNIC). Functions executed by the VNIC may include viewing VLAN tags on the packet. Since the packet's destination is outside the subnet, the VCN VR function is then 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 it to the destination compute instance. The VNICs associated with the source and destination compute instances may execute on the same NVD (e.g., when 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).

[0119] If the packet's destination is outside the source compute instance's VCN, the packet originating from the source compute instance is forwarded 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 packet's destination endpoint is outside the VCN, the packet is subsequently processed by the VCN VR used by that VCN. The NVD invokes VCN VR functionality, which may result in the packet being forwarded to the NVD executing the appropriate gateway associated with the VCN. For example, if the destination is an endpoint within a customer's on-premises network, the packet may be forwarded by the VCN VR to the NVD executing the DRG gateway configured for the VCN. The VCN VR may execute on the same NVD as the NVD executing the VNIC associated with the source compute instance, or it may be executed by a different NVD. The gateway may be executed by the NVD, which can be a smartNIC, a host machine, or another NVD implementation. The packet is then processed by the gateway and forwarded to the next hop, which facilitates the packet's delivery to its intended destination endpoint. For example, in Figure 2 In the embodiment depicted, packets originating from compute instance 268 can be transmitted from host machine 202 to NVD 210 via link 220 (using NIC 232). On NVD 210, VNIC 276 is invoked because it is the VNIC associated with the source compute instance 268. VNIC 276 is configured to examine the information encapsulated in the packet and determine the next hop for forwarding the packet, with the aim of facilitating the transmission of the packet to its intended destination endpoint, and then forwarding the packet to the determined next hop.

[0120] Compute instances deployed on a VCN can communicate with a variety of endpoints. These endpoints can include endpoints hosted by CSPI 200 and endpoints outside of CSPI 200. Endpoints hosted by CSPI 200 can include instances within the same VCN or other VCNs, which can be the customer's VCN or a VCN not belonging to the customer. Communication between endpoints hosted by CSPI 200 can be performed via physical network 218. Compute instances can also communicate with endpoints not hosted by CSPI 200 or outside of CSPI 200. Examples of these endpoints include endpoints within the customer's on-premises network or data center, or public endpoints accessible via public networks such as the Internet. Communication with endpoints outside of CSPI 200 can use various communication protocols over public networks (e.g., the Internet). Figure 2 (not shown in the image) or a dedicated network ( Figure 2 (Not shown in the image) to execute.

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

[0122] Figure 4 The connectivity between the host machine and the NVD, according to certain embodiments, is described for providing I / O virtualization to support multi-tenancy. For example... Figure 4 As depicted, 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 includes a physical NIC 410 connected to NVD 412 via link 414. Each compute instance is attached to a VNIC executed by NVD 412. Figure 4 In one embodiment, VM1 406 is attached to VNIC-VM1 420 and VM2 408 is attached to VNIC-VM2 422.

[0123] like Figure 4 As shown, NIC 410 includes two logical NICs, logical NIC A 416 and logical NIC B 418. Each virtual machine is attached to its own logical NIC and configured to work with its own logical NIC. For example, VM1 406 is attached to logical NIC A 416 and VM2 408 is attached to logical NIC B 418. Although host machine 402 includes only one physical NIC 410 shared by multiple tenants, each tenant's virtual machines believe they have their own host machine and network interface card due to the logical NICs.

[0124] In some embodiments, each logical NIC is assigned its own VLAN ID. Thus, a specific VLAN ID is assigned to logical NIC A 416 for tenant #1, and a different VLAN ID is assigned to logical NIC B 418 for tenant #2. When a packet is transmitted from VM1 406, the hypervisor appends a tag assigned to tenant #1 to the packet, and the packet is then transmitted from host machine 402 to NVD 412 via link 414. Similarly, when a packet is transmitted from VM2 408, the hypervisor appends a tag assigned to tenant #2 to the packet, and the packet is then transmitted from host machine 402 to NVD 412 via link 414. Accordingly, the packet 424 transmitted from host machine 402 to NVD 412 has an associated tag 426 identifying the specific tenant and the associated VM. On the NVD, for a packet 424 received from the host machine 402, the tag 426 associated with the packet is used to determine whether the packet is processed by VNIC-VM1 420 or VNIC-VM2 422. The packet is then processed by the corresponding VNIC. Figure 4 The configuration described in [the document] enables each tenant's compute instance to believe that it owns its own host machine and NIC. Figure 4 The setup described in [the document] provides I / O virtualization to support multi-tenancy.

[0125] Figure 5 A simplified block diagram of a physical network 500 according to certain embodiments is depicted. Figure 5 The embodiments depicted are structured as Clos networks. Clos networks are a specific type of network topology designed to provide connectivity redundancy while maintaining high bandwidth and maximum resource utilization. Clos networks are non-blocking, multi-stage or multi-layer switching networks, where the number of stages or layers can be two, three, four, five, etc. Figure 5 The embodiment depicted is a Layer 3 network, including Layer 1, Layer 2, and Layer 3. TOR switch 504 represents a Layer 0 switch in a Clos network. One or more NVDs are connected to the TOR switch. Layer 0 switches are also referred to as edge devices of the physical network. Layer 0 switches are connected to Layer 1 switches, also known as leaf switches. Figure 5In the embodiments depicted, a set of "n" Layer 0 TOR switches is connected to a set of "n" Layer 1 switches and together forms a pod. Each Layer 0 switch in the pod is interconnected to all Layer 1 switches in that pod, but there is no switch connectivity between pods. In some implementations, two pods are referred to as blocks. Each block is served by or connected to a set of "n" Layer 2 switches (sometimes called backbone switches). There can be several blocks in the physical network topology. The Layer 2 switches are then connected to "n" Layer 3 switches (sometimes called super backbone switches). Packet communication on the physical network 500 is typically performed using one or more Layer 3 communication protocols. Typically, all layers of the physical network (except the TOR layer) are n-way redundant, thus allowing high availability. Policies can be specified for pods and blocks to control the visibility of switches to each other in the physical network, thereby enabling scaling of the physical network.

[0126] A key characteristic of Clos networks is that the maximum number of hops from one Layer 0 switch to another (or from an NVD connected to a Layer 0 switch to another NVD connected to a Layer 0 switch) is fixed. For example, in a Layer 3 Clos network, a packet takes a maximum of seven hops to reach another NVD, where the source and destination NVDs are connected to the leaf layers of the Clos network. Similarly, in a Layer 4 Clos network, a packet takes a maximum of nine hops to reach another NVD, where the source and destination NVDs are connected to the leaf layers of the Clos network. Therefore, the Clos network architecture maintains consistent latency throughout the network, which is important for communication within and between data centers. Clos topologies are horizontally scalable and cost-effective. Network bandwidth / throughput capacity can be easily increased by adding more switches at each layer (e.g., more leaf switches and backbone switches) and by increasing the number of links between switches in adjacent layers.

[0127] In some implementations, each resource within CSPI is assigned a unique identifier called a Cloud Identifier (CID). This identifier is included as part of the resource's information and can be used to manage the resource, for example, via a console or API. An example syntax for a CID is:

[0128] in, ocid1: A text string indicating the version of the CID; resource type: The type of resource (e.g., instance, volume, VCN, subnet, user, group, etc.); realm: The realm where the resource resides. 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 can have its own domain name; region: The region where the resource is located. This section may be empty if the region is not applicable to the resource. future use: to be reserved for future use.

[0129] uniqueID: The unique part of the ID. The format may vary depending on the type of resource or service.

[0130] Example Traffic Awareness Policy Engine (TAPE)

[0131] Figure 6 This is a simplified block diagram illustrating an environment 600 that uses TAPE 640 to enforce network policies / rules in one or more networks according to certain embodiments. Environment 600 includes multiple systems communicatively coupled to each other. Figure 6 The system includes traffic service 602, instance 610, computing device 620, gateway 630, and service 606. Traffic service 602 includes tape manager 604, monitoring service 606, and data 608. Although tape manager 604 and monitoring service 606 are shown as part of traffic service 602, one or more of these components may be outside of traffic service 602. Computing device 620, which may be referred to herein as "server 620" or "server computing device 620," may include a hypervisor (HV) (not shown) capable of hosting virtual machines (VMs) such as instance 610.

[0132] Figure 6 The environment 600 depicted herein is merely an example and is not intended to unduly limit the scope of the claimed embodiments. Many variations, alternatives, and modifications are possible. For example, in some embodiments, environment 600 may have a greater... Figure 6 The systems or components shown may include more or fewer systems or components, and may combine two or more systems, or may have different system configurations or arrangements. Figure 6 The systems, subsystems, and other components described herein may be implemented using software (e.g., code, instructions, programs) executed by one or more processing units (e.g., processors, cores) of the respective systems, using hardware or a combination thereof. The software may be stored on a non-transitory storage medium (e.g., on a memory device).

[0133] exist Figure 6The embodiments described herein present a novel technique for enforcing network policies / rules across different network layers. Instead of having to create rules and policies for each of the different network layers and manually specify where and which devices should enforce the rules / policies, the technique described herein aims to allow users to create simple policies that integrate policies / rules across any / all layers of different network layers. In some examples, the different network layers are defined by the Open Systems Interconnection (OSI) model. In other examples, different network models (e.g., the five-layer TCP / IP model) can be used with the technique described herein. As briefly discussed above, the OSI model defines seven different layers, including Physical Layer 1, Data Link Layer 2, Network Layer 3, Transport Layer 4, Session Layer 5, Presentation Layer 6, and Application Layer 7. In some configurations, identity policies are enforced by a layer that TAPE may refer to herein as "Layer 8".

[0134] After a policy is created, it is enforced across the network by TAPE 640s distributed across different network points. In some examples, the user does not need to specify which devices are used to enforce the policy or where those devices are located. Instead, traffic service 602 or some other component can deploy and / or instruct different TAPE devices 640 to enforce the policy. In some examples, TAPE 640 can be deployed with all or some of the network devices involved in transmitting data within one or more networks. For example, TAPE 640 can be deployed with gateway 630, smart NIC, instance 610, and other types of network devices.

[0135] Using TAPE 640, an administrator or other authorized user can create simple policies that can be enforced across different network layers (e.g., L2-L7+ identities) without having to specify specific rules for each layer. For example, policies could be as simple as "Block traffic to IP 10.10.10.240", "Allow only traffic to services A, B, and D from the lease to the service gateway", "Check payload pattern validation", "For traffic from identity principles, enforce on resources from lease X to resources (A, X, Z)", etc. These policies / rules can be stored as Policy / Rule 608B within data repository 608, and / or in another location. Figure 10 The diagram illustrates more example strategies.

[0136] In some configurations, traffic service 602 communicates with different tapes 640 within the network. According to some examples, traffic service 602 provides instructions to different tapes 640 indicating which policies / rules to enforce. Individual tapes 640 can also communicate with traffic service 602 to request policies from policies / rules 608B, store data in recorded data 608A, provide resource data (e.g., CPU, storage, etc.), etc.

[0137] According to some examples, traffic service 602, tape manager 604, monitoring service 606, or some other device / component can identify what packet processing to perform based on the available resources of the computing device currently hosting tape 640. According to some examples, traffic service 602 or some other component or device can access monitoring data provided by monitoring service 606 and determine whether there are sufficient available resources within a particular computing device 620 to perform processing related to the enforcement of some / all policies. In some configurations, monitoring service 606 monitors resources such as, but not limited to, CPU usage, memory usage, I / O usage, etc.

[0138] In some configurations, the TAPE 640 sits in front of network devices (e.g., gateways, instances, smartNICs) across the network and is configured to perform processing on each received packet. As will be described in more detail, the TAPE 640 can perform many different types of processing. Figure 6 The illustration shows a Tape 640 deployed in front of gateways (e.g., service gateways 630B and 630C, internet gateways 630D and gateway 630A) and instances 610A and 610B.

[0139] As discussed herein, virtual networks are implemented using software virtualization technologies (e.g., hypervisors, virtualization functions implemented by network virtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR) switches, smart TORs that implement one or more functions performed by the NVD, and other mechanisms) to create a layer of network abstraction that can run on top of the physical network. For example, in some embodiments, the NVD is implemented as an interface card called a smartNIC or a smart NIC with an onboard embedded processor. A smartNIC is a separate device from the NIC on the host machine (such as computing device 620 hosting instance 610). Depending on some configurations, smartNICs within the network include TAPE 640. Other NVDs may also include TAPE 640. For example, in some other embodiments, the NVD or one or more functions performed by the NVD may be incorporated into or performed by one or more computing devices 620, one or more TOR switches, and other components of CSPI 200. For example, in cases where virtual machine (VM) instances are provided to customers but not bare metal (BM) instances, the functions performed by the NVD may be implemented within the hypervisor of the host machine. In some other implementations, some of the NVD's functionality can be offloaded to a centralized service running on a host machine cluster.

[0140] Go back to reference Figure 6 Placing the TAPE 640D in front of the Service Gateway (SGW) 630C allows cloud service clients to connect to the Data Plane (DP) 632, or private endpoints, and also allows connection to the Control Plane (CP) 634 to access service 606. The TAPE 640E can also be placed in front of the Internet Gateway 630D to process network traffic flowing to / from the cloud network, such as traffic flowing to / from device 622. In this example, the TAPE 640D enforces ingress / egress control in both the Control Plane (CP) 634 and the Data Plane (DP) 632. The TAPE 640D can also restrict access to service 606 without requiring service 606 to implement separate rules / policies. This allows for granular filtering of traffic to specific services or to cloud services.

[0141] In some examples, upon receiving a packet, the TAPE 640 is configured to execute a packet processing pipeline to process the packet and determine how it should be processed. As part of this packet processing pipeline, the TAPE 640 can perform one or more virtual functions (such as packet encapsulation and decapsulation – see [link to documentation]). Figure 7 This facilitates the processing of policies / rules, as well as other functions.

[0142] In some embodiments, the packet processing data path in a device including the TAPE 640 may include multiple packet pipelines, each consisting of a series of packet transformation stages. In some implementations, upon receiving a packet, the packet may be decrypted, parsed, and classified into a single pipeline. The packet is then processed linearly, stage by stage, until the packet is either discarded, stored / recorded, or transmitted on an interface associated with the TAPE device.

[0143] Figure 6 Gateway 630 in the diagram can be any type of gateway, such as, but not limited to, Dynamic Routing Gateway (DRG), Internet Gateway (IGW), Network Address Translation (NAT) gateway, Local Peer Gateway (LPG), Serving Gateway (SGW), etc. A DRG, acting as a virtual router, provides a path for traffic between your on-premises network and the VCN, and can also be used to route traffic between VCNs. An IGW enables compute instances on a VCN to communicate with public endpoints accessible on public networks such as the Internet. A NAT gateway can be configured for a customer's VCN, enabling cloud resources within that customer's VCN that do not have dedicated public overlay IP addresses to access the Internet without exposing those resources to direct inbound Internet connections (e.g., L4-L7 connections). An LPG is a gateway that can be added to a VCN and enables the VCN to peer with another VCN in the same area. An SGW can be configured for a VCN and provides a path for private network traffic between the VCN and supported service endpoints in the serving network.

[0144] Figure 7 This is a simplified block diagram illustrating an environment 700 that enforces network policies / rules in one or more networks using TAPE 640 according to an embodiment. Environment 700 includes multiple systems communicatively coupled to each other. Figure 7 The system includes TAPE 640, control plane 708, data 712, and device 710. Traffic 640 includes policy engine 702, packet engine 704, intrusion detection system (IDS) / intrusion protection system (IPS) engine 714, plug-in engine 716, (one or more) custom plug-ins 718, (one or more) protocol inspection plug-ins 720, logging component 722, identity engine 724, and encryption / decryption engine 706.

[0145] Figure 7 The environment 700 depicted herein is merely an example and is not intended to unduly limit the scope of the claimed embodiments. Many variations, alternatives, and modifications are possible. For example, in some embodiments, environment 700 may have a greater... Figure 7The systems or components shown may include more or fewer systems or components, and may combine two or more systems, or may have different system configurations or arrangements. Figure 7 The systems, subsystems, and other components described herein may be implemented using software (e.g., code, instructions, programs) executed by one or more processing units (e.g., processors, cores) of the respective systems, using hardware or a combination thereof. The software may be stored on a non-transitory storage medium (e.g., on a memory device).

[0146] Depending on the configuration, the TAPE 640 can be configured to perform many different functions based on the policies being enforced by the TAPE 640. In some examples, the policy engine 702 is configured to manage the enforcement of policies / rules associated with received packets. For example, the TAPE 640E can use the policy engine 702 to perform IDS / IPS operations (e.g., using the IDS / IPS engine 714 to communicate with the IDS / IPS service), use the plug-in engine 716 to perform plug-ins, use the identity engine 724 to perform identity operations to restrict / allow access to specified identities, use the logging engine 722 to log data, use the packet engine 704 to store packet data, and perform other packet processing related to one or more policies.

[0147] exist Figure 7 In the examples depicted, TAPE 640 can run on any network device (virtual or physical) that includes at least a portion of the computing resources necessary to perform processes associated with the enforcement of one or more policies / rules across different network layers. In some configurations, one or more TAPE 640s may be associated with a network device. For example, TAPE 640 may be associated with each instance (such as VM 610) within a cloud environment. In some examples, a network device may / may not include TAPE 640. For example, device 710 may include TAPE 640F, or may not include TAPE 640F. In some cases, devices that send / receive packets may include TAPE 640. In other cases, some devices that send / receive packets may not include TAPE 640. For example, TAPE manager 604 may determine which network devices include TAPE 640 based on the available resources of the network devices (e.g., determined by monitoring service 606), whether the network devices are being or will be involved in the enforcement of one or more policies, etc. In some configurations, Traffic Service 602, Tape Manager 604, or some other component / device are deployed / activated along with any instance / device that will process packets associated with one or more policies / rules.

[0148] As shown in the diagram, the TAPE 640E receives / sends packets to / from devices such as device 710. In some cases, the received packets can be encrypted. Depending on the configuration, the TAPE 640 is configured to use the encryption / decryption engine 706 to decrypt and encrypt traffic as it flows. In some examples, network users / clients authorize the TAPE 640 to decrypt / encrypt traffic. In these cases, the TAPE may be able to access a private key to encrypt / decrypt packets.

[0149] The packet engine 704 is coupled to the policy engine 702. The packet engine includes a packet capture component configured to record / store specified packets. For example, the packet capture engine can be configured to store one percent of all received packets. The packet capture engine can also be configured to store packets that fail inspection performed by the plug-in engine, the IDS / IPS engine, and / or some other functionality included within the packet capture engine.

[0150] As briefly discussed above, TAPE can use plugins or some other provided executable code to support functionality provided by trusted users. For example, plugins can be developed to perform packet checks to determine if data follows a specific pattern, whether data is encrypted, or whether packets originate from an authorized location. Generally, plugins or other executable code can perform analytics associated with any of the layers 1-7 and / or perform operations involving identity verification.

[0151] In some examples, the TAPE 640 associated with different network devices can communicate with one or more services / components outside the TAPE-enabled device. For example, the policy engine 702 can communicate with the IDS / IPS service using the IDS / IPS engine 714, with the identity service using the identity engine 724, and so on.

[0152] Depending on the configuration, TAPE 640 can communicate with traffic service 602 to receive instructions / code / functionality to be executed. For example, traffic service 602 can instruct TAPE 640 within the smartNIC to perform lower-level network layer checks (e.g., L2-L4), while gateway 630 can be instructed to perform other tasks (e.g., L2-L7, identity). In this way, policy-associated packet processing can be distributed across different TAPE devices that inspect traffic associated with a specific policy. In some examples, TAPE devices can perform processing associated with all different network layers.

[0153] The packet capture engine 704 is configured to record / store packets. For example, the packet capture engine 704 can store a predetermined portion (e.g., 1%, 2%, 5%, etc.) of received packets within a data repository (such as data repository 712). In some configurations, the packet capture engine 704 stores packets based on one or more policies / rules. For example, a user can specify to record a specified percentage of packets, packets that pass / fail a specified test, etc. Authorized users can then access the stored packets to perform one or more other actions, such as packet analysis.

[0154] The plugin engine 716 can be configured to execute plugins that perform packet-related processing. For example, the plugin engine 716 can execute one or more custom plugins provided by a client or another authorized user, or other plugins such as one or more protocol inspection plugins 720. Instead of being limited to inspecting a single protocol for unencrypted data using previous solutions, many different types of protocol inspections (for both encrypted and unencrypted data) can be performed by the TAPE 640 using the techniques described herein. As an example, the protocol inspection plugin can be configured to inspect many different protocols, such as, but not limited to, TCP / IP (Transmission Control Protocol / Internet Protocol), UDP / IP (User Datagram Protocol / Internet Protocol), HTTP (Hypertext Transfer Protocol), HTTPS (Secure Hypertext Transfer Protocol), FTP (File Transfer Protocol), etc.

[0155] In some examples, one or more plugins can be developed to determine whether a packet conforms to a pattern. For example, whether the packet's data includes data specified by the pattern. When the data does not conform to the pattern, the plugin engine 716 can notify the policy engine 702 and / or perform other actions, such as storing the packet in a data repository, preventing the packet from flowing through the network, generating a notification indicating failure, logging the error, etc. In some examples, packet checks (e.g., protocol, pattern, etc.) can be performed at TAPE 640 at a network point specific to the traffic egress / ingress. Generally, the plugin engine 716 can be configured to execute any trusted code to perform packet processing.

[0156] Log engine 716 can be configured to log data related to grouping processes involving enforced policies. For example, log engine 716 can be configured to log data related to times when protocol checks fail, plugin mode checks fail, etc. In other examples, log engine 716 can be configured to log other types of data.

[0157] The Identity Engine 724 can be configured to perform identity operations associated with policies. TAPE 640 not only supports network, protocol, and pattern policies, but it also includes the power of identity to define traffic from an identity perspective, rather than focusing on specific network characteristics. For example, the Identity Engine 724 can be configured to control which / which identities can access specific cloud resources, which identities can transfer data to a specific location, which identities can receive data, etc. 1. Generally, policies can specify "who" should be able to move data and can specify what resources can be accessed on the authenticated data plane.

[0158] Figure 8 The illustration shows an example method 800 for processing packets using TAPE 640, based on various aspects. Method 800 can be derived from... Figure 1-7 The method is executed by one or more components of 11-15. A computer-readable storage medium comprising computer-readable instructions, which, when executed by one or more processors of a computing device, cause the computing device to perform method 800. Method 800 may be executed in any suitable order. It should be appreciated that method 800 may include more than Figure 8 The larger or smaller number of steps described in the text.

[0159] At position 802, packets are received. As discussed above, packets can be received at network devices / components including TAPE 640. Received packets can be encrypted and / or decrypted.

[0160] At point 804, a determination is made regarding whether the packet is encrypted. If the packet is encrypted, the procedure proceeds to point 806. If the packet is not encrypted, the procedure proceeds to point 808.

[0161] At 806, the packet is decrypted. As discussed above, when authorized, the encryption / decryption engine 706, as part of TAPE 640, decrypts the packet. For example, the encryption / decryption engine 706 may have access to a key that allows decryption of the packet or some other security device. In some cases, the packet is not unencrypted when the processing associated with the policy does not require the packet to be unencrypted.

[0162] At point 808, the policy to be enforced is determined. As discussed above, traffic service 602, policy engine 702, or some other device / component can determine which policy to enforce. In some examples, traffic service 602 accesses policies / rules 608B in data repository 608 to determine the policies / rules associated with the received packets. Depending on some configurations, the policy is based on where the packet originated and / or the packet's destination and / or some other data.

[0163] At 810, processing is performed. As discussed above, traffic service 602 and / or some other device / component can determine what rules the network device receiving the packet should enforce. In other examples, tape 640, which receives the packet, can determine the policy to enforce. In some configurations, each tape 640 can be configured to perform processing on received packets. In other examples, different NVDs can perform different types of processing. For example, a smartNIC can perform lower-level processing, while a gateway can perform higher-level processing. See [link to documentation] for further details. Figure 9 And related discussions.

[0164] Figure 9 The illustration shows an example method 900 for processing groups using TAPE based on various aspects. Method 900 can be derived from... Figure 1-7 The method is executed by one or more components of 11-15. A computer-readable storage medium comprising computer-readable instructions, which, when executed by one or more processors of a computing device, cause the computing device to perform method 900. Method 900 may be executed in any suitable order. It should be appreciated that method 900 may include more than Figure 9 The larger or smaller number of steps described in the text.

[0165] At position 902, identify the rules associated with the policy to be enforced at the network device. As discussed above, rules can be associated with controlling the flow of traffic across the network or performing some other type of processing.

[0166] At 904, a determination is made regarding whether to store the packet. As discussed above, TAPE 640 can be configured to store the packet within the data repository. When a received packet is to be stored, the process proceeds to 906.

[0167] At 906, packets are stored. As discussed above, packet engine 704 can store received packets in data repository 712. As mentioned above, packet engine 704 can store a predetermined number of packets (e.g., 1%, 5%, ...) and / or store received packets based on some other condition.

[0168] At 908, a determination is made regarding whether one or more plugins should perform processing on the group. As discussed above, the plugin engine 716 can be configured to execute plugins that perform group-related processing. When a plugin is to be executed, the process proceeds to 910.

[0169] At 910, the plugin is executed. As discussed above, the plugin engine 716 executes the plugin. This plugin can be a customer plugin 718 supplied by a client of the network, or a plugin developed by another entity. As an example, a customer could provide a custom plugin 718 to check whether the data within received packets conforms to a pattern. As another example, the plugin could be part of a set of underlying plugins for performing operations, such as protocol inspection plugins, logging plugins, etc.

[0170] At 912, a determination is made regarding whether to perform protocol checks. As discussed above, the plugin engine 716 can be configured to execute plugins that perform protocol checks related to packets. When a plugin is to be executed, the process proceeds to 910.

[0171] At position 914, a protocol check is performed. As discussed above, in some examples, the plugin engine at position 716 executes one or more plugins to perform the protocol check.

[0172] At point 916, a determination is made regarding whether to perform an IDS / IPS operation. As discussed above, the IDS / IPS engine 714 can be configured to perform operations related to the IDS / IPS to be executed. When an IDS / IPS operation is to be performed, the process proceeds to point 918.

[0173] At position 918, IDS / IPS operations are performed. As discussed above, in some examples, IDS / IPS engine 716 enables the performance of IDS / IPS operations.

[0174] Figure 10 This is a block diagram illustrating a graphical user interface 1000 that includes user interface elements associated with policies, metrics, and logs. Figure 10 The illustration shows an example control plane illustrating the policies 1010, metrics 1020, and log data 1030 within the graphical user interface (GUI) 1000.

[0175] Using GUI 1000, customers can select instances, gateways (i.e., service gateways, internet gateways, etc.), and apply the created policies / plugins. Metrics 1020 allows users to view information associated with policy enforcement. Logs 1030 allow users to view data related to the execution of different rules / policies.

[0176] Example CSPI architecture for providing cloud services

[0177] As noted above, Infrastructure as a Service (IaaS) is a specific type of cloud computing. IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In the IaaS model, cloud providers can host infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., hypervisor layer), etc.). In some cases, IaaS providers can also provision various services to accompany these infrastructure components (example services include billing software, monitoring software, logging software, load balancing software, and clustering software, etc.). Therefore, because these services may be policy-driven, IaaS users can implement policies to drive load balancing to maintain application availability and performance.

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

[0179] In most cases, cloud computing models will require the involvement of cloud providers. Cloud providers can, but are not necessarily, third-party providers specializing in (e.g., provisioning, renting, selling) IaaS services. Entities may also choose to deploy private clouds, thus becoming their own infrastructure service providers.

[0180] In some examples, IaaS deployment is the process of placing a new application or a new version of an application onto a prepared application server, etc. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is typically managed by the cloud provider, below the hypervisor layer (e.g., servers, storage devices, network hardware, and virtualization). Therefore, the customer can be responsible for disposing of the operating system (OS), middleware, and / or application deployment (e.g., on self-service virtual machines, etc., which can be started on demand).

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

[0182] In some cases, IaaS provisioning presents two distinct challenges. First, there's the initial challenge of provisioning the initial infrastructure set before anything is operational. Second, once everything is provisioned, there's the challenge of evolving the existing infrastructure (e.g., adding new services, changing services, removing services, etc.). In some cases, both challenges can be addressed by enabling configuration that declaratively defines the infrastructure. In other words, the infrastructure (e.g., which components are needed and how they interact) can be defined by one or more configuration files. Therefore, the overall topology of the infrastructure (e.g., which resources depend on which resources and how they work together) can be described declaratively. In some instances, once the topology is defined, workflows for creating and / or managing the different components described in the configuration files can be generated.

[0183] In some examples, the infrastructure can have many interconnected components. For example, one or more Virtual Private Clouds (VPCs) (e.g., potential on-demand pools of configurable and / or shared computing resources), also known as the core network, may exist. In some examples, one or more inbound / outbound traffic group rules may also be supplied to define how inbound / outbound traffic to the network and one or more virtual machines (VMs) will be configured. Other infrastructure elements, such as load balancers, databases, etc., may also be supplied. The infrastructure can evolve incrementally as more and / or additional infrastructure elements are desired.

[0184] In some instances, continuous deployment techniques can be used to enable the deployment of infrastructure code across various virtual computing environments. Furthermore, the described techniques enable infrastructure management within these environments. In some examples, service teams may write code that they expect to deploy to one or more, but often many, different production environments (e.g., across various geographical locations, sometimes spanning the entire world). However, in some examples, the infrastructure on which the code will be deployed must first be set up. In some instances, provisioning can be done manually, resources can be provisioned using provisioning tools, and / or once the infrastructure is provisioned, the code can be deployed using deployment tools.

[0185] Figure 11This is a block diagram 1100 illustrating an example pattern of an IaaS architecture according to at least one embodiment. Service operator 1102 may be communicatively coupled to a secure host lease 1104, which may include a virtual cloud network (VCN) 1106 and a secure host subnet 1108. In some examples, service operator 1102 may use one or more client computing devices, which may be portable handheld devices (e.g., iPhone®, cellular phone, iPad®, computing tablet, personal digital assistant (PDA)) or wearable devices (e.g., Google Glass® head-mounted display), running software (such as Microsoft Windows Mobile®) and / or various mobile operating systems (such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, etc.), and supporting the Internet, email, short message service (SMS), Blackberry®, or other communication protocols. Alternatively, client computing devices may be general-purpose personal computers, including, for example, personal computers and / or laptops running various versions of Microsoft Windows®, Apple Macintosh®, and / or Linux operating systems. Client computing devices can be workstation computers running a variety of commercially available UNIX® or UNIX-like operating systems, including but not limited to any of the various GNU / Linux operating systems (such as, for example, Google Chrome OS). Alternatively or additionally, client computing devices can be any other electronic device, such as thin client computers, internet-enabled gaming systems (e.g., Microsoft Xbox game consoles with or without Kinect® gesture input devices), and / or personal messaging devices capable of communicating over a network that can access VCN 1106 and / or the internet.

[0186] VCN 1106 may include a local peering gateway (LPG) 1110, which may be communicatively coupled to a secure shell (SSH) VCN 1112 via LPG 1110 contained in SSH VCN 1112. SSH VCN 1112 may include an SSH subnet 1114, and SSH VCN 1112 may be communicatively coupled to a control plane VCN 1116 via LPG 1110 contained in control plane VCN 1116. Furthermore, SSH VCN 1112 may be communicatively coupled to a data plane VCN 1118 via LPG 1110. Control plane VCN 1116 and data plane VCN 1118 may be contained in a service lease 1119 that may be owned and / or operated by an IaaS provider.

[0187] The control plane VCN 1116 may include a control plane demilitarized zone (DMZ) layer 1120 that acts as a peripheral network (e.g., a portion of a corporate network between a corporate intranet and an external network). DMZ-based servers can have limited responsibilities and help deter security intrusions. Furthermore, the DMZ layer 1120 may include one or more load balancer (LB) subnets 1122, a control plane application layer 1124 that may include one or more application subnets 1126, and a control plane data layer 1128 that may include one or more database (DB) subnets 1130 (e.g., one or more front-end DB subnets and / or one or more back-end DB subnets). One or more LB subnets 1122 contained in the control plane DMZ layer 1120 may be communicatively coupled to one or more application subnets 1126 contained in the control plane application layer 1124 and an Internet gateway 1134 that may be contained in the control plane VCN 1116. The application subnets 1126 may be communicatively coupled to one or more DB subnets 1130 contained in the control plane data layer 1128, as well as a service gateway 1136 and a Network Address Translation (NAT) gateway 1138. The control plane VCN 1116 may include the service gateway 1136 and the NAT gateway 1138.

[0188] The control plane VCN 1116 may include a data plane mirror application layer 1140, which may include one or more application subnets 1126. The one or more application subnets 1126 included in the data plane mirror application layer 1140 may include a virtual network interface controller (VNIC) 1142 capable of executing a compute instance 1144. The compute instance 1144 may communicatively couple the one or more application subnets 1126 of the data plane mirror application layer 1140 to the one or more application subnets 1126 that may be included in the data plane application layer 1146.

[0189] Data plane VCN 1118 may include data plane application layer 1146, data plane DMZ layer 1148, and data plane data layer 1150. Data plane DMZ layer 1148 may include one or more LB subnets 1122 communicatively coupled to one or more application subnets 1126 of data plane application layer 1146 and Internet gateway 1134 of data plane VCN 1118. One or more application subnets 1126 communicatively coupled to service gateway 1136 and NAT gateway 1138 of data plane VCN 1118. Data plane data layer 1150 may also include one or more DB subnets 1130 communicatively coupled to one or more application subnets 1126 of data plane application layer 1146.

[0190] The Internet gateway 1134 of control plane VCN 1116 and data plane VCN 1118 can be communicatively coupled to metadata management service 1152, and metadata management service 1152 can be communicatively coupled to public Internet 1154. Public Internet 1154 can be communicatively coupled to NAT gateway 1138 of control plane VCN 1116 and data plane VCN 1118. Service gateway 1136 of control plane VCN 1116 and data plane VCN 1118 can be communicatively coupled to cloud service 1156.

[0191] In some examples, service gateway 1136, either control plane VCN 1116 or data plane VCN 1118, can make application programming interface (API) calls to cloud service 1156 without traversing the public internet 1154. API calls from service gateway 1136 to cloud service 1156 can be unidirectional: service gateway 1136 can make API calls to cloud service 1156, and cloud service 1156 can send requested data to service gateway 1136. However, cloud service 1156 may not initiate API calls to service gateway 1136.

[0192] In some examples, secure host lease 1104 can be directly connected to service lease 1119, which would otherwise be isolated. Secure host subnet 1108 can communicate with SSH subnet 1114 via LPG 1110, which enables bidirectional communication between otherwise isolated systems. Connecting secure host subnet 1108 to SSH subnet 1114 allows secure host subnet 1108 to access other entities within service lease 1119.

[0193] Control plane VCN 1116 may allow users of service lease 1119 to configure or otherwise provision desired resources. Desired resources provisioned in control plane VCN 1116 may be deployed or otherwise used in data plane VCN 1118. In some examples, control plane VCN 1116 may be isolated from data plane VCN 1118, and the data plane mirror application layer 1140 of control plane VCN 1116 may communicate with the data plane application layer 1146 of data plane VCN 1118 via VNIC 1142, which may be included in both the data plane mirror application layer 1140 and the data plane application layer 1146.

[0194] In some examples, users or clients of the system can make requests, such as create, read, update, or delete (CRUD) operations, via the public internet 1154, which can transmit requests to the metadata management service 1152. The metadata management service 1152 can transmit requests to the control plane VCN 1116 via internet gateway 1134. Requests can be received by one or more LB subnets 1122 contained in the control plane DMZ layer 1120. The LB subnets 1122 can determine that the request is valid, and in response to this determination, they can transmit the request to one or more application subnets 1126 contained in the control plane application layer 1124. If the request is validated and requires a call to the public internet 1154, the call to the public internet 1154 can be transmitted to a NAT gateway 1138 that can make calls to the public internet 1154. The request may expect stored metadata to be stored in one or more DB subnets 1130.

[0195] In some examples, the data plane mirroring application layer 1140 can facilitate direct communication between the control plane VCN 1116 and the data plane VCN 1118. For example, it may be desirable to apply configuration changes, updates, or other appropriate modifications to resources contained in the data plane VCN 1118. Through VNIC 1142, the control plane VCN 1116 can communicate directly with the resources contained in the data plane VCN 1118, and thus can perform configuration changes, updates, or other appropriate modifications.

[0196] In some embodiments, control plane VCN 1116 and data plane VCN 1118 may be contained within service lease 1119. In this case, the system's users or customers may not own or operate control plane VCN 1116 or data plane VCN 1118. Alternatively, the IaaS provider may own or operate control plane VCN 1116 and data plane VCN 1118, both of which may be contained within service lease 1119. This embodiment can achieve network isolation that may prevent users or customers from interacting with resources from other users or customers. Furthermore, this embodiment can allow users or customers of the system to privately store databases without relying on the public internet 1154, which may not have the desired level of threat protection for storage.

[0197] In other embodiments, one or more LB subnets 1122 included in the control plane VCN 1116 may be configured to receive signals from the service gateway 1136. In this embodiment, the control plane VCN 1116 and the data plane VCN 1118 may be configured to be invoked by the IaaS provider's customers without invoking the public internet 1154. The IaaS provider's customers may expect this embodiment because the database(s) used by the customer can be controlled by the IaaS provider and can be stored on service lease 1119, which may be isolated from the public internet 1154.

[0198] Figure 12 This is a block diagram 1200 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 1202 (e.g., Figure 11 Service provider 1102) can communicatively couple to secure host lease 1204 (e.g., Figure 11 Secure hosting lease 1104), the secure hosting lease 1204 may include a virtual cloud network (VCN) 1206 (e.g., Figure 11 VCN 1106) and Secure Host Subnet 1208 (e.g., Figure 11 The secure host subnet 1108). VCN 1206 may include a local peering gateway (LPG) 1210 (e.g., Figure 11 The LPG 1110, which can be communicatively coupled to the Secure Shell (SSH) VCN 1212 (e.g., LPG 1110 contained in the SSH VCN 1212) Figure 11 SSH VCN 1112). SSH VCN 1212 can include SSH subnet 1214 (e.g., Figure 11 SSH subnet 1114), and SSH VCN 1212 can be communicatively coupled to control plane VCN 1216 via LPG 1210 included in control plane VCN 1216 (e.g., Figure 11 Control plane VCN 1116). Control plane VCN 1216 may be included in service lease 1219 (e.g., Figure 11 In the service lease 1119), and the data plane VCN 1218 (e.g., Figure 11 The data plane VCN 1118 may be included in a customer lease 1221 that may be owned or operated by the system’s users or customers.

[0199] The control plane VCN 1216 may include one or more LB subnets 1222 (e.g., Figure 11 The control plane DMZ layer 1220 of (one or more) LB subnets 1122) (e.g., Figure 11 The control plane DMZ layer 1120 may contain one or more application subnets 1226 (e.g., Figure 11 The control plane application layer 1224 of (one or more) application subnets 1126 (e.g., Figure 11 The control plane application layer 1124) may contain one or more database (DB) subnets 1230 (e.g., similar to...). Figure 11 The control plane data layer 1228 of (one or more) DB subnets 1130 (e.g., Figure 11 The control plane data layer 1128). One or more LB subnets 1222 contained in the control plane DMZ layer 1220 can be communicatively coupled to one or more application subnets 1226 contained in the control plane application layer 1224 and an Internet gateway 1234 that can be contained in the control plane VCN 1216 (e.g., Figure 11 Internet gateway 1134), and application subnet(s) 1226 can communicatively couple to DB subnet(s) 1230 contained in control plane data layer 1228 and service gateway 1236 (e.g., Figure 11 Service gateway 1136) and Network Address Translation (NAT) gateway 1238 (e.g., Figure 11 (NAT gateway 1138). The control plane VCN 1216 may include the service gateway 1236 and the NAT gateway 1238.

[0200] The control plane VCN 1216 may include a data plane mirror application layer 1240 that may contain one or more application subnets 1226 (e.g., Figure 11 The data plane mirror application layer 1140). One or more application subnets 1226 contained in the data plane mirror application layer 1240 may include computational instances 1244 (e.g., similar to...). Figure 11 The virtual network interface controller (VNIC) 1242 (e.g., the VNIC of 1142) of the computing instance 1144. The computing instance 1244 may facilitate the mirroring of the application subnet(s) 1226 of the application layer 1240 in the data plane and may be included in the application layer 1246 in the data plane (e.g., Figure 11 Communication between one or more application subnets 1226 in the data plane application layer 1146 via VNIC 1242 contained in the data plane mirror application layer 1240 and VNIC 1242 contained in the data plane application layer 1246.

[0201] The Internet gateway 1234 included in the control plane VCN 1216 can be communicatively coupled to the metadata management service 1252 (e.g., Figure 11Metadata management service 1252), which can communicatively couple to public Internet 1254 (e.g., Figure 11 The public internet 1254 can communicatively couple to a NAT gateway 1238 contained in a control plane VCN 1216. The service gateway 1236 contained in the control plane VCN 1216 can communicatively couple to a cloud service 1256 (e.g., ...). Figure 11 Cloud services (1156).

[0202] In some examples, data plane VCN 1218 may be included in customer lease 1221. In this case, the IaaS provider may provide control plane VCN 1216 for each customer, and the IaaS provider may set up a unique compute instance 1244 for each customer, included in service lease 1219. Each compute instance 1244 may allow communication between control plane VCN 1216 included in service lease 1219 and data plane VCN 1218 included in customer lease 1221. Compute instance 1244 may allow resources provisioned in control plane VCN 1216 included in service lease 1219 to be deployed or otherwise used in data plane VCN 1218 included in customer lease 1221.

[0203] In other examples, an IaaS provider's customer may have a database residing in customer lease 1221. In this example, control plane VCN 1216 may include data plane mirror application layer 1240, which may include one or more application subnets 1226. Data plane mirror application layer 1240 may reside in data plane VCN 1218, but may not reside in data plane VCN 1218. That is, data plane mirror application layer 1240 may have access to customer lease 1221, but may not reside in data plane VCN 1218 or be owned or operated by an IaaS provider's customer. Data plane mirror application layer 1240 may be configured to invoke data plane VCN 1218, but may not be configured to invoke any entity contained in control plane VCN 1216. Customers may expect to deploy or otherwise use resources provisioned in the control plane VCN 1216 in the data plane VCN 1218, and the data plane mirroring application layer 1240 can facilitate the customer's expected deployment or other use of resources.

[0204] In some embodiments, an IaaS provider's customer may apply filters to data plane VCN 1218. In this embodiment, the customer may determine what data plane VCN 1218 can access, and the customer may restrict access from data plane VCN 1218 to the public Internet 1254. The IaaS provider may not be able to apply filters or otherwise control data plane VCN 1218's access to any external networks or databases. Applying filters and controls to data plane VCN 1218 contained in customer lease 1221 helps isolate data plane VCN 1218 from other customers and the public Internet 1254.

[0205] In some embodiments, cloud service 1256 may be invoked by service gateway 1236 to access services that may not exist on public internet 1254, control plane VCN 1216, or data plane VCN 1218. The connection between cloud service 1256 and control plane VCN 1216 or data plane VCN 1218 may not be real-time or continuous. Cloud service 1256 may reside on different networks owned or operated by an IaaS provider. Cloud service 1256 may be configured to receive calls from service gateway 1236 and may be configured not to receive calls from public internet 1254. Some cloud services 1256 may be isolated from other cloud services 1256, and control plane VCN 1216 may be isolated from cloud services 1256 that may not be in the same region as control plane VCN 1216. For example, control plane VCN 1216 may be located in "Region 1," and cloud service "Deployment 11" may be located in both "Region 1" and "Region 2." If the service gateway 1236, contained in the control plane VCN 1216 located in region 1, makes a call to deployment 11, then that call can be transmitted to deployment 11 in region 1. In this example, the control plane VCN 1216 or deployment 11 in region 1 may not be communicatively coupled to or otherwise communicate with deployment 11 in region 2.

[0206] Figure 13 This is a block diagram 1300 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 1302 (e.g., Figure 11 Service provider 1102) can communicatively couple to secure host lease 1304 (e.g., Figure 11 Secure hosting lease 1104), the secure hosting lease 1304 may include a virtual cloud network (VCN) 1306 (e.g., Figure 11 VCN 1106) and Secure Host Subnet 1308 (e.g., Figure 11 The secure host subnet 1108). VCN 1306 may include LPG 1310 (e.g., Figure 11 The LPG 1110), which can be communicatively coupled to the SSH VCN 1312 via the LPG 1310 included in the SSH VCN 1312 (e.g., Figure 11 SSH VCN 1112). SSH VCN 1312 can include SSH subnet 1314 (e.g., Figure 11 SSH subnet 1114), and SSH VCN 1312 can be communicatively coupled to control plane VCN 1316 via LPG 1310 contained in control plane VCN 1316 (e.g., Figure 11 The control plane VCN 1116) and coupled to the data plane VCN 1318 via the LPG 1310 contained in the data plane VCN 1318 (e.g., Figure 11 Data plane 1118). Control plane VCN 1316 and data plane VCN 1318 may be included in service lease 1319 (e.g., Figure 11 In the service rental (1119).

[0207] The control plane VCN 1316 may include one or more load balancer (LB) subnets 1322 (e.g., Figure 11 The control plane DMZ layer 1320 of (one or more) LB subnets 1122) (e.g., Figure 11 The control plane DMZ layer 1120 may contain one or more application subnets 1326 (e.g., similar to...). Figure 11 The control plane application layer 1324 of (one or more) application subnets 1126 (e.g., Figure 11 The control plane application layer 1124), and the control plane data layer 1328, which may contain one or more DB subnets 1330, for example, Figure 11 The control plane data layer 1128). One or more LB subnets 1322 contained in the control plane DMZ layer 1320 can be communicatively coupled to one or more application subnets 1326 contained in the control plane application layer 1324 and an Internet gateway 1334 that can be contained in the control plane VCN 1316 (e.g., Figure 11 Internet gateway 1134), and application subnet(s) 1326 can communicatively couple to DB subnet(s) 1330 contained in control plane data layer 1328 and service gateway 1336 (e.g., Figure 11 The service gateway) and Network Address Translation (NAT) gateway 1338 (e.g., Figure 11 (NAT gateway 1138). The control plane VCN 1316 may include the service gateway 1336 and the NAT gateway 1338.

[0208] Data plane VCN 1318 may include data plane application layer 1346 (e.g., Figure 11 Data plane application layer 1146), data plane DMZ layer 1348 (e.g., Figure 11 Data plane DMZ layer 1148), and data plane data layer 1350 (e.g., Figure 11 The data plane data layer 1150). The data plane DMZ layer 1348 may include one or more trusted application subnets 1360 and one or more untrusted application subnets 1362 that can be communicatively coupled to the data plane application layer 1346, and one or more LB subnets 1322 of the Internet gateway 1334 contained in the data plane VCN 1318. The one or more trusted application subnets 1360 may be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318, the NAT gateway 1338 contained in the data plane VCN 1318, and one or more DB subnets 1330 contained in the data plane data layer 1350. The one or more untrusted application subnets 1362 may be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318 and the one or more DB subnets 1330 contained in the data plane data layer 1350. The data plane data layer 1350 may include one or more DB subnets 1330 that can be communicatively coupled to the service gateway 1336 contained in the data plane VCN 1318.

[0209] One or more untrusted application subnets 1362 may include one or more primary VNICs 1364(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1366(1)-(N). Each tenant VM 1366(1)-(N) may be communicatively coupled to a corresponding application subnet 1367(1)-(N) that may be contained in a corresponding container egress VCN 1368(1)-(N), which may be contained in a corresponding customer lease 1370(1)-(N). A corresponding secondary VNIC 1372(1)-(N) may facilitate communication between one or more untrusted application subnets 1362 contained in data plane VCN 1318 and application subnets contained in container egress VCN 1368(1)-(N). Each container exit VCN 1368(1)-(N) may include a NAT gateway 1338, which may communicatively couple to the public Internet 1354 (e.g., Figure 11 The public internet (1154).

[0210] Internet gateway 1334, contained in control plane VCN 1316 and data plane VCN 1318, can be communicatively coupled to metadata management service 1352 (e.g., Figure 11 A metadata management system 1152, which is communicatively coupled to the public internet 1354, is also communicatively coupled to a NAT gateway 1338 contained in a control plane VCN 1316 and a data plane VCN 1318. A service gateway 1336 contained in both the control plane VCN 1316 and the data plane VCN 1318 is communicatively coupled to a cloud service 1356.

[0211] In some embodiments, the data plane VCN 1318 may be integrated with the customer lease 1370. Such integration may be useful or desired by the IaaS provider's customer in certain situations, such as when support may be expected during code execution. A customer may provide code that could be destructive, might communicate with other customer resources, or might otherwise cause undesirable effects. In response, the IaaS provider may determine whether to run the code provided by the customer to the IaaS provider.

[0212] In some examples, an IaaS provider's customer may grant the IaaS provider temporary network access and request that functionality be attached to the data plane application layer 1346. The code running this functionality may execute in VMs 1366(1)-(N) and may not be configured to run anywhere else on the data plane VCN 1318. Each VM 1366(1)-(N) may be connected to a customer lease 1370. A corresponding container 1371(1)-(N) contained in VMs 1366(1)-(N) may be configured to run the code. In this case, dual isolation may exist (e.g., container 1371(1)-(N) runs the code, where container 1371(1)-(N) may be contained in at least one or more untrusted application subnets 1362 containing VMs 1366(1)-(N)), which can help prevent incorrect or otherwise unintended code from corrupting the IaaS provider's network or the networks of different customers. Containers 1371(1)-(N) may be communicatively coupled to customer lease 1370 and may be configured to transmit or receive data from customer lease 1370. Containers 1371(1)-(N) may not be configured to transmit or receive data from any other entity in data plane VCN 1318. After the code execution is complete, the IaaS provider may terminate or otherwise dispose of containers 1371(1)-(N).

[0213] In some embodiments, one or more trusted application subnets 1360 may run code that can be owned or operated by an IaaS provider. In this embodiment, one or more trusted application subnets 1360 may be communicatively coupled to one or more database subnets 1330 and configured to perform CRUD operations in one or more database subnets 1330. One or more untrusted application subnets 1362 may be communicatively coupled to one or more database subnets 1330, but in this embodiment, one or more untrusted application subnets may be configured to perform read operations in one or more database subnets 1330. Containers 1371(1)-(N) that may be contained in each customer's VM 1366(1)-(N) and may run code from the customer may not be communicatively coupled to one or more database subnets 1330.

[0214] In other embodiments, the control plane VCN 1316 and the data plane VCN 1318 may be coupled without direct communication. In this embodiment, there may be no direct communication between the control plane VCN 1316 and the data plane VCN 1318. However, communication can occur indirectly through at least one method. The LPG 1310 may be established by an IaaS provider, which can facilitate communication between the control plane VCN 1316 and the data plane VCN 1318. In another example, either the control plane VCN 1316 or the data plane VCN 1318 may invoke the cloud service 1356 via the service gateway 1336. For example, an invocation of the cloud service 1356 from the control plane VCN 1316 may include a request for a service that can communicate with the data plane VCN 1318.

[0215] Figure 14 This is a block diagram 1400 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 1402 (e.g., Figure 11 Service provider 1102) can communicatively couple to secure host lease 1404 (e.g., Figure 11 Secure hosting lease 1104), the secure hosting lease 1404 may include a virtual cloud network (VCN) 1406 (e.g., Figure 11 VCN 1106) and Secure Host Subnet 1408 (e.g., Figure 11 The secure host subnet 1108). VCN 1406 may include LPG 1410 (e.g., Figure 11 The LPG 1110), the LPG 1410 can be accessed via SSH VCN 1412 (e.g., LPG 1110), Figure 11The LPG 1410 in SSH VCN 1112 is communicatively coupled to SSH VCN 1412. SSH VCN 1412 may include SSH subnet 1414 (e.g., Figure 11 SSH subnet 1114), and SSH VCN 1412 can be communicatively coupled to control plane VCN 1416 via LPG 1410 contained in control plane VCN 1416 (e.g., Figure 11 The control plane VCN 1116) and coupled to the data plane VCN 1418 via the LPG 1410 contained in the data plane VCN 1418 (e.g., Figure 11 Data plane 1118). Control plane VCN 1416 and data plane VCN 1418 may be contained in service lease 1419 (e.g., Figure 11 In the service rental (1119).

[0216] The control plane VCN 1416 may include one or more LB subnets 1422 (e.g., Figure 11 The control plane DMZ layer 1420 of (one or more) LB subnets 1122) (e.g., Figure 11 The control plane DMZ layer 1120 may contain one or more application subnets 1426 (e.g., Figure 11 The control plane application layer 1424 of (one or more) application subnets 1126 (e.g., Figure 11 The control plane application layer 1124) may contain one or more DB subnets 1430 (e.g., Figure 13 The control plane data layer 1428 of (one or more) DB subnets 1330 (e.g., Figure 11 The control plane data layer 1128). One or more LB subnets 1422 contained in the control plane DMZ layer 1420 can be communicatively coupled to one or more application subnets 1426 contained in the control plane application layer 1424 and an Internet gateway 1434 that can be contained in the control plane VCN 1416 (e.g., Figure 11 Internet gateway 1134), and application subnet(s) 1426 can communicatively couple to DB subnet(s) 1430 contained in control plane data layer 1428 and service gateway 1436 (e.g., Figure 11 The service gateway) and Network Address Translation (NAT) gateway 1438 (e.g., Figure 11 (NAT gateway 1138). The control plane VCN 1416 may include the service gateway 1436 and the NAT gateway 1438.

[0217] Data plane VCN 1418 may include data plane application layer 1446 (e.g., Figure 11 Data plane application layer 1146), data plane DMZ layer 1448 (e.g., Figure 11 Data plane DMZ layer 1148), and data plane data layer 1450 (e.g., Figure 11 The data plane data layer 1150). The data plane DMZ layer 1448 may include one or more trusted application subnets 1460 that can be communicatively coupled to the data plane application layer 1446 (e.g., Figure 13 (one or more) trusted application subnets 1360 and (one or more) untrusted application subnets 1462 (e.g., Figure 13 The data plane VCN 1418 may include one or more untrusted application subnets 1362 and one or more LB subnets 1422. One or more trusted application subnets 1460 may be communicatively coupled to a service gateway 1436, a NAT gateway 1438, and a DB subnet 1430, all contained in the data plane VCN 1418. One or more untrusted application subnets 1462 may be communicatively coupled to a service gateway 1436 and a DB subnet 1430, both contained in the data plane VCN 1418 and the data plane data layer 1450. The data plane data layer 1450 may include one or more DB subnets 1430 that may be communicatively coupled to a service gateway 1436, contained in the data plane VCN 1418.

[0218] One or more untrusted application subnets 1462 may include a primary VNIC 1464(1)-(N) communicatively coupled to tenant virtual machines (VMs) 1466(1)-(N) residing within one or more untrusted application subnets 1462. Each tenant VM 1466(1)-(N) may run code in a corresponding container 1467(1)-(N) and is communicatively coupled to an application subnet 1426 that may be contained in a data plane application layer 1446 contained in a container egress VCN 1468. A corresponding secondary VNIC 1472(1)-(N) may facilitate communication between one or more untrusted application subnets 1462 contained in a data plane VCN 1418 and the application subnets contained in a container egress VCN 1468. The container egress VCN may include a public internet 1454 (e.g., Figure 11 The public internet (1154) uses NAT gateway 1438.

[0219] Internet gateway 1434, contained in control plane VCN 1416 and data plane VCN 1418, can be communicatively coupled to metadata management service 1452 (e.g., Figure 11 A metadata management system 1452 (the metadata management service 1452) can be communicatively coupled to the public internet 1454. The public internet 1454 can be communicatively coupled to a NAT gateway 1438 contained in a control plane VCN 1416 and a data plane VCN 1418. A service gateway 1436 contained in a control plane VCN 1416 and a data plane VCN 1418 can be communicatively coupled to a cloud service 1456.

[0220] In some examples, Figure 14 The architecture shown in block diagram 1400 can be considered as... Figure 13 This is an exception to the pattern shown in the architecture of block diagram 1300, and this pattern may be what the IaaS provider's customers would expect if the IaaS provider cannot communicate directly with the customer (e.g., in a disconnected region). The customer can access in real time the corresponding container 1467(1)-(N) contained in each customer's VM 1466(1)-(N). Container 1467(1)-(N) can be configured to invoke the corresponding auxiliary VNIC 1472(1)-(N) contained in one or more application subnets 1426 of the data plane application layer 1446, which may be contained in the container egress VCN 1468. The auxiliary VNIC 1472(1)-(N) can transmit the call to NAT gateway 1438, which can then transmit the call to the public internet 1454. In this example, containers 1467(1)-(N), which can be accessed by clients in real time, can be isolated from the control plane VCN 1416 and from other entities contained in the data plane VCN 1418. Containers 1467(1)-(N) can also be isolated from resources from other clients.

[0221] In other examples, a client may use container 1467(1)-(N) to invoke cloud service 1456. In this example, the client may run code within container 1467(1)-(N) requesting a service from cloud service 1456. Container 1467(1)-(N) may transmit the request to auxiliary VNIC 1472(1)-(N), which may transmit the request to a NAT gateway, which may then transmit the request to the public internet 1454. The public internet 1454 may then transmit the request via internet gateway 1434 to one or more LB subnets 1422 contained in control plane VCN 1416. In response to determining that the request is valid, one or more LB subnets may transmit the request to one or more application subnets 1426, which may then transmit the request to cloud service 1456 via service gateway 1436.

[0222] It should be recognized that the IaaS architectures 1100, 1200, 1300, and 1400 depicted in the figures may have other components besides those depicted. Furthermore, the embodiments shown in the figures are merely some examples of cloud infrastructure systems that can be incorporated into embodiments of this disclosure. In some other embodiments, the IaaS system may have more or fewer components than shown in the figures, may combine two or more components, or may have different configurations or component arrangements.

[0223] In some embodiments, the IaaS system described herein may include application suites, middleware, and database service offerings delivered to customers 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 this assignee.

[0224] Figure 15 An example computer system 1500, in which various embodiments can be implemented, is illustrated. System 1500 can be used to implement any of the computer systems described above. As shown, computer system 1500 includes a processing unit 1504 that communicates with a plurality of peripheral subsystems via a bus subsystem 1502. These peripheral subsystems may include a processing acceleration unit 1506, an I / O subsystem 1508, a storage subsystem 1518, and a communication subsystem 1524. Storage subsystem 1518 includes a tangible computer-readable storage medium 1522 and system memory 1510.

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

[0226] A processing unit 1504, which may be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of the computer system 1500. One or more processors may be included in the processing unit 1504. These processors may include single-core or multi-core processors. In some embodiments, the processing unit 1504 may be implemented as one or more independent processing units 1532 and / or 1534, wherein each processing unit includes a single-core or multi-core processor. In other embodiments, the processing unit 1504 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.

[0227] In various embodiments, processing unit 1504 can execute various 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 reside in processor(s) 1504 and / or storage subsystem 1518. With appropriate programming, processor(s) 1504 can provide the various functionalities described above. Computer system 1500 may additionally include processing acceleration unit 1506, which may include digital signal processor (DSP), dedicated processor, etc.

[0228] I / O subsystem 1508 may include user interface input devices and user interface output devices. User interface input devices may include keyboards, pointing devices such as mice or trackballs, touchpads or touchscreens integrated into a display, scroll wheels, click wheels, dials, buttons, switches, keypads, 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 motion sensor of Microsoft Kinect®, which enables users to control and interact with input devices such as game controllers for the Microsoft Xbox® 360 via a natural user interface using gestures and voice commands. User interface input devices may also include eye posture recognition devices, such as the Google Glass® blink detector, which detects eye activity from the user (e.g., “blinking” when taking a photo and / or making menu selections) and translates the eye posture into input in an input device (e.g., Google Glass®). Furthermore, user interface input devices may include voice recognition sensing devices that enable users to interact with a voice recognition system (e.g., the Siri® navigator) via voice commands.

[0229] User interface input devices may also include, but are not limited to, 3D mice, joysticks or pointing sticks, game panels and drawing tablets, as well as audio / visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode readers, 3D scanners, 3D printers, laser rangefinders, and eye-tracking devices. Furthermore, user interface input devices may include, for example, medical imaging input devices such as computed tomography (CT), magnetic resonance imaging (MRI), positron emission tomography (PET), and medical ultrasound equipment. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments, etc.

[0230] User interface output devices may include display subsystems, indicator lights, or non-visual displays such as audio output devices. Display subsystems may be cathode ray tubes (CRTs), flat panel devices such as those using liquid crystal displays (LCDs) or plasma displays, projection devices, touchscreens, and so on. Generally, the term "output device" is intended to encompass all possible types of devices and mechanisms for outputting information from computer system 1500 to a user or other computer. For example, user interface output devices may include, but are not limited to, various display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, car navigation systems, plotters, voice output devices, and modems.

[0231] Computer system 1500 may include storage subsystem 1518, which provides a tangible, non-transitory, computer-readable storage medium for storing software and data constructs that provide the functionality of the embodiments described in this disclosure. The software may include programs, code modules, instructions, scripts, etc., which, when executed by one or more cores or processors of processing unit 1504, provide the aforementioned functionality. Storage subsystem 1518 may also provide a repository for storing data used according to this disclosure.

[0232] like Figure 15 As depicted in the example, storage subsystem 1518 may include various components, including system memory 1510, computer-readable storage medium 1522, and computer-readable storage medium reader 1520. System memory 1510 may store program instructions that can be loaded and executed by processing unit 1504. System memory 1510 may also store data used during the execution of instructions and / or data generated during the execution of program instructions. Various types of programs may be loaded into system memory 1510, including but not limited to client applications, web browsers, middleware applications, relational database management systems (RDBMS), virtual machines, containers, etc.

[0233] System memory 1510 may also store operating system 1516. Examples of operating system 1516 may include various versions of Microsoft Windows®, Apple Macintosh® and / or Linux operating systems, various commercially available UNIX® or UNIX-like operating systems (including, but not limited to, various GNU / Linux operating systems, Google Chrome® OS, etc.) and / or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® OS and Palm® OS. In some implementations of computer system 1500 that execute one or more virtual machines, the virtual machine, along with its guest operating system (GOS), may be loaded into system memory 1510 and executed by one or more processors or cores of processing unit 1504.

[0234] System memory 1510 can be configured differently depending on the type of computer system 1500. For example, system memory 1510 can be volatile memory (such as random access memory (RAM)) and / or non-volatile memory (such as read-only memory (ROM), flash memory, etc.). Different types of RAM configurations can be provided, including static random access memory (SRAM), dynamic random access memory (DRAM), etc. In some implementations, system memory 1510 may include a basic input / output system (BIOS), which contains basic routines that facilitate the transfer of information between components within computer system 1500 (such as during startup).

[0235] Computer-readable storage medium 1522 may represent a remote, local, fixed and / or removable storage device and a storage medium for temporarily and / or more permanently containing and storing computer-readable information (including instructions executable by the processing unit 1504 of the computer system 1500) for use by the computer system 1500.

[0236] Computer-readable storage medium 1522 may include any suitable medium known or used in the art, including storage and communication media, such as, but not limited to, volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing and / or transmitting information. This may include tangible computer-readable storage media such as RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical storage devices, magnetic tape cassettes, magnetic tape, disk storage devices or other magnetic storage devices, or other tangible computer-readable media.

[0237] As an example, computer-readable storage medium 1522 may include hard disk drives that read from or write to non-removable non-volatile magnetic media, disk drives that read from or write to removable non-volatile magnetic disks, and optical disc drives that read from or write to removable non-volatile optical discs (such as CD-ROMs, DVDs, and Blu-ray® discs or other optical media). Computer-readable storage medium 1522 may include, but is not limited to, Zip® drives, flash memory cards, Universal Serial Bus (USB) flash memory drives, Secure Digital (SD) cards, DVD discs, digital video tapes, and the like. Computer-readable storage medium 1522 may also include solid-state drives (SSDs) based on non-volatile memory (such as flash memory-based SSDs, enterprise flash drives, solid-state ROMs, etc.), volatile memory-based SSDs (such as solid-state RAM, dynamic RAM, static RAM), DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs using a combination of DRAM-based and flash memory-based SSDs. Disk drives and their associated computer-readable media can provide non-volatile storage for computer-readable instructions, data structures, program modules and other data for computer system 1500.

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

[0239] The communication subsystem 1524 provides an interface to other computer systems and networks. The communication subsystem 1524 serves as an interface for receiving data from other systems and sending data from computer system 1500 to other systems. For example, the communication subsystem 1524 enables computer system 1500 to connect to one or more devices via the Internet. In some embodiments, the communication subsystem 1524 may include radio frequency (RF) transceiver components (e.g., advanced data network technologies using cellular telephone technology, such as 3G, 4G, or EDGE (Enhanced Data Rates for Global Evolution), WiFi (IEEE 802.11 series standards), or other mobile communication technologies, or any combination thereof), a global positioning system (GPS) receiver component, and / or other components for accessing wireless voice and / or data networks. In some embodiments, as an addition to or alternative to the wireless interface, the communication subsystem 1524 may provide a wired network connection (e.g., Ethernet).

[0240] In some embodiments, the communication subsystem 1524 may also represent one or more users who can use the computer system 1500 to receive input communications in the form of structured and / or unstructured data feeds 1526, event streams 1528, event updates 1530, etc.

[0241] As an example, the communication subsystem 1524 can be configured to receive data feeds 1526 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.

[0242] Furthermore, the communication subsystem 1524 can also be configured to receive data in the form of a continuous data stream, which may include event streams 1528 and / or event updates 1530 that are essentially continuous or unbounded real-time events without a clearly defined termination. Examples of applications that generate continuous data may include, for example, sensor data applications, financial quote machines, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, vehicle traffic monitoring, and so on.

[0243] The communication subsystem 1524 can also be configured to output structured and / or unstructured data feeds 1526, event streams 1528, event updates 1530, etc. to one or more databases, which can communicate with one or more streaming data source computers coupled to the computer system 1500.

[0244] The computer system 1500 can be one of a variety of types, including handheld portable devices (e.g., iPhone® cellular phones, iPad® computing tablets, PDAs), wearable devices (e.g., Google® Glass head-mounted displays), PCs, workstations, mainframes, information stations, server racks, or any other data processing system.

[0245] Due to the ever-evolving nature of computers and networks, the description of the computer system 1500 depicted in the figures is intended only as a specific example. Many other configurations with more or fewer components than the system depicted in the figures are possible. For example, custom hardware may also be used and / or specific elements may be implemented using hardware, firmware, software (including small applications), or a combination thereof. Additionally, connections to other computing devices, such as network input / output devices, may also be employed. Based on the disclosure and teachings provided herein, those skilled in the art will recognize other ways and / or methods for implementing the various embodiments.

[0246] While specific embodiments have been described, various modifications, alterations, alternative constructions, and equivalents are also included within the scope of this disclosure. The embodiments are not limited to operation within certain specific data processing environments, but can be freely operated within multiple data processing environments. Furthermore, although the embodiments have been described using a specific series of transactions and steps, those skilled in the art will understand that the scope of this disclosure is not limited to the described series of transactions and steps. Various features and aspects of the above embodiments can be used individually or in combination.

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

[0248] Accordingly, the specification and drawings are intended to be illustrative rather than restrictive. However, it will be apparent that additions, omissions, deletions, and other modifications and alterations may be made thereto without departing from the broader spirit and scope set forth in the claims. Thus, while specific disclosed embodiments have been described, they are not intended to be limiting. Various modifications and equivalents are within the scope of the following claims.

[0249] In the context of describing the disclosed embodiments (especially in the context of the following claims), the terms “a,” “an,” and “the,” and similar designations, are to be interpreted as encompassing both singular and plural, unless otherwise indicated herein or clearly contradicted by the context. Unless otherwise stated, the terms “comprising,” “having,” “including,” and “containing” are to be interpreted as open-ended terms (i.e., meaning “including but not limited to”). The term “connected” should be interpreted as partially or wholly contained in, attached to, or joined together, even if something exists in between. Unless otherwise indicated herein, the enumeration of value ranges herein is intended only as a shorthand method for individually referencing each individual value falling within that range, and each individual value is incorporated into the specification as if it were individually enumerated herein. Unless otherwise indicated herein or clearly contradicted by the context, all methods described herein can be performed in any suitable order. The use of any and all examples or exemplary language (e.g., “such as”) provided herein is intended only to better illustrate the embodiments and does not constitute a limitation on the scope of this disclosure, unless otherwise defined by the claims. Nothing in the specification should be construed as indicating that any unclaimed element is essential to the practice of this disclosure.

[0250] Disjunctive language, such as the phrase “at least one of X, Y, or Z”, is intended to be understood in the context in which items, terms, etc., can be X, Y, or Z, or any combination thereof (e.g., X, Y, and / or Z), unless otherwise expressly stated. Therefore, such disjunctive language is generally not intended to, and should not, imply that certain embodiments require the presence of at least one of X, at least one of Y, or at least one of Z, each individually.

[0251] This document describes preferred embodiments of the present disclosure, including the best modes known for carrying out the present disclosure. Variations of those preferred embodiments may become apparent to those skilled in the art upon reading the foregoing description. Those skilled in the art should be able to suitably employ such variations and may practice the present disclosure in ways different from those specifically described herein. Accordingly, the present disclosure includes all modifications and equivalents to the subject matter recited in the appended claims, where permitted by applicable law. Furthermore, unless otherwise indicated herein, the present disclosure includes any combination of the foregoing elements in all its possible variations.

[0252] All references cited in this article, including publications, patent applications and patents, are incorporated into this article by reference to the same extent as if each reference individually and specifically indicated to be incorporated by reference and elaborated in full in this article.

[0253] In the foregoing specification, various aspects of this disclosure have been described with reference to specific embodiments thereof, but those skilled in the art will recognize that this disclosure is not limited thereto. The various features and aspects of the foregoing disclosure may be used individually or in combination. Furthermore, embodiments may be used in any number of settings and applications other than those described herein without departing from the broader spirit and scope of this specification. Accordingly, this specification and the accompanying drawings should be considered illustrative rather than restrictive.

Claims

1. A method for performing grouping processing associated with one or more policies, the method comprising: Receive packets at network devices that include a Traffic Aware Policy Engine (TAPE); A policy that accesses at least one of how specified traffic flows through the network or how traffic is processed within the network, wherein the policy integrates different network layers including at least a second data link layer and a seventh application layer. The processing to be performed on packets at the network device is determined at least in part based on the policy. as well as The processing is performed on packets at the network device using TAPE.

2. The method of claim 1, further comprising deploying TAPE to a network device within the network, wherein the network device includes a network virtualization device (NVD) containing a smartNIC and a virtual interface containing a gateway.

3. The method of claim 2, wherein the network device performs the processing across any one of the first physical layer, the second data link layer, the third network layer, the fourth transport layer, the fifth session layer, the sixth presentation layer, or the seventh application layer.

4. The method of claim 2, wherein the network device executes a first portion of the rule associated with the policy and one or more other network devices execute a second portion of the rule.

5. The method of claim 1, wherein performing the processing includes storing the group in a data repository.

6. The method of claim 5, wherein the policy specifies one or more identities authorized to access one or more resources.

7. The method of claim 1, further comprising decrypting the packet before performing the processing and encrypting the packet before transmitting the packet.

8. The method of claim 1, wherein performing processing on the groups includes analyzing the groups to determine if the groups conform to a specified pattern.

9. The method of claim 1, wherein processing the packets includes analyzing the packets to determine if the packets conform to a specified protocol.

10. The method of claim 1, wherein performing processing on the packet includes one or more of the following: causing the execution of IDS / IPS services, the execution of one or more plugins provided by a client of the network, or the execution of one or more identity rules.

11. A system comprising: The network includes network devices; A strategy that specifies at least one of how traffic flows through the network or how traffic is processed within the network, wherein the strategy integrates different network layers including the second data link layer and the seventh application layer. One or more processors; as well as A non-transitory computer-readable medium storing an instruction set, which, when executed by the one or more processors, causes processing to be performed, including: Receive packets at network devices that include a Traffic Aware Policy Engine (TAPE); The processing to be performed on packets at the network device is determined at least in part based on the policy; and The processing is performed on packets at the network device using TAPE.

12. The system of claim 11, wherein the network device includes a network virtualization device (NVD) comprising a smartNIC and a virtual interface comprising a gateway.

13. The system of claim 12, wherein the network device performs the processing across any one of the first physical layer, the second data link layer, the third network layer, the fourth transport layer, the fifth session layer, the sixth presentation layer, or the seventh application layer.

14. The system of claim 12, wherein the network device executes a first portion of a rule associated with the policy, and one or more other network devices execute a second portion of the rule.

15. The system of claim 11, wherein performing the process includes storing the packets in a data repository.

16. The system of claim 11, wherein the policy specifies one or more identities authorized to access one or more resources.

17. The system of claim 11, wherein performing processing on packets includes analyzing packets to determine if the packets conform to a specified pattern or analyzing packets to determine if the packets conform to a specified protocol, at least one of these.

18. The system of claim 11, wherein performing processing on a packet includes one or more of the following: causing the execution of an IDS / IPS service, the execution of one or more plugins provided by a client of the network, or the execution of one or more identity rules.

19. The system of claim 11, wherein TAPE is located in front of the control plane and data plane associated with one or more network services.

20. A computer-readable medium including instructions that, when executed, cause one or more processors to perform operations, comprising: A policy that accesses at least one of how specified traffic flows through the network or how traffic is processed within the network, wherein the policy integrates different network layers including the second data link layer and the seventh application layer. Receive packets at network devices that include a Traffic Aware Policy Engine (TAPE); The processing to be performed on packets at the network device is determined at least in part based on the policy. as well as The processing is performed on packets at the network device using a Traffic Aware Policy Engine (TAPE) associated with the network device.