providing, via the second cloud service provider, metrics associated with the private cloud network available from the first cloud service provider

Abstract

Techniques are disclosed for providing metrics associated with a private cloud network available from a first cloud service provider via a second cloud service provider. Cross-cloud services can be provisioned and managed between the cloud service provider's private cloud and between the cloud service provider's private clouds. First observability data associated with cloud services provisioned from the first cloud environment in the second cloud environment is obtained. The first observability data is processed into second observability data compatible with the observability data format of the second cloud environment, and the second observability data is provided to the second cloud environment.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit and priority of U.S. Provisional Application No. 63 / 604,722, filed November 30, 2023, the entire contents of which are incorporated herein by reference for all purposes. Background Technology

[0003] Over the past few years, we have seen a dramatic increase in the adoption of cloud services, and this trend is only going to grow. Different cloud service providers (CSPs) offer a variety of different cloud environments, each providing a set of one or more cloud services. This set of cloud services provided by a cloud environment can include one or more different types of services, including but not limited to Software as a Service (SaaS), Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and so on.

[0004] While various cloud environments are currently available, each provides a closed ecosystem for its subscribers. Therefore, customers of a cloud environment are limited to using the services provided by that specific cloud environment. For customers subscribed to a cloud environment offered by a CSP, there is no easy way to access services offered by different CSPs through that cloud environment. The embodiments discussed herein address these and other issues. Summary of the Invention

[0005] Techniques for providing metrics associated with a private cloud network available from a first cloud service provider via a second cloud service provider are disclosed.

[0006] In some embodiments, a method includes: obtaining first observability data associated with a cloud service supplied by the first cloud environment in a second cloud environment from a first cloud environment; processing the first observability data by the first cloud environment to generate second observability data, wherein the second observability data is compatible with the observability data format of the second cloud environment; and providing the second observability data from the first cloud environment to the second cloud environment.

[0007] In some embodiments, the first observability data includes one or more metrics and / or one or more events associated with the execution of the cloud service.

[0008] In some embodiments, processing the first observability data to generate the second observability data includes identifying a schema associated with the second cloud environment; and converting the format of the first observability data to the observability data format of the second cloud environment based on the schema.

[0009] In some embodiments, the pattern is derived from manifest information retrieved from a second cloud environment.

[0010] In some embodiments, the method further includes creating one or more targets configured to receive the first observable data in an observable data plane within a first cloud environment before obtaining the first observable data.

[0011] In some embodiments, the method further includes identifying a first identifier associated with a customer and a first private cloud in a first cloud environment and a second identifier associated with the customer and a second private cloud in a second cloud environment; storing the association between the first identifier, the second identifier, and a resource identifier associated with a cloud service in an observability control plane within the first cloud environment; identifying the resource identifier associated with the first observability data after obtaining the first observability data; and identifying the customer, the second cloud environment, and one or more resource details based on the resource identifier and the association stored in the observability control plane.

[0012] In some embodiments, providing second observability data to a second cloud environment includes providing the second observability data from an observability data plane within a first cloud environment to an agent configured to communicate with an observability data repository within a second cloud environment.

[0013] Some embodiments include a system comprising one or more processing systems and one or more computer-readable media storing instructions that, when executed by the one or more processing systems, cause the system to perform some or all of the operations and / or methods disclosed herein.

[0014] Some embodiments include one or more non-transitory computer-readable media storing instructions that, when executed by one or more processing systems, cause the systems to perform some or all of the operations and / or methods disclosed herein.

[0015] The techniques described above and below can be implemented in a variety of ways and in a variety of contexts. Several example implementations and contexts are provided with reference to the following figures, which are described in more detail below. However, the following implementations and contexts are only a few of many implementations and contexts. Attached Figure Description

[0016] The features, embodiments, and advantages of this disclosure can be better understood by reading the following detailed description with reference to the accompanying drawings.

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

[0018] Figure 2 A simplified architecture diagram of physical components in the physical network within a Cloud Service Provider Infrastructure (CSPI) according to certain embodiments is depicted.

[0019] 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).

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

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

[0022] Figure 6 A simplified high-level diagram of a distributed environment comprising multiple cloud environments provided by different cloud service providers (CSPs) is depicted according to certain embodiments.

[0023] Figure 7 An exemplary physical architecture for providing cross-cloud services based on infrastructure distributed across multiple CSPs, according to some embodiments, is described.

[0024] Figure 8 An exemplary virtual architecture for providing cross-cloud services based on infrastructure distributed across multiple CSPs is described according to some embodiments.

[0025] Figure 9 Exemplary virtual resources provided by a first CSP to a customer of a second CSP, according to some embodiments, are described.

[0026] Figure 10 An exemplary architecture for provisioning and managing cross-cloud services based on infrastructure distributed across multiple CSPs, according to some embodiments, is described.

[0027] Figure 11 An exemplary user experience flow for supplying resources, according to some embodiments, is described.

[0028] Figure 12 An exemplary control plane supply process according to some embodiments is described.

[0029] Figure 13 Examples of architectures, including resource management mechanisms for provisioning and managing cross-cloud services across multiple cloud environments, are described according to some embodiments.

[0030] Figure 14This is a simplified block diagram illustrating an exemplary data streaming environment, according to some embodiments, for providing observability data from a first cloud environment to a second cloud environment.

[0031] Figure 15 This is a simplified block diagram illustrating an exemplary observability data delivery environment 1500, according to some embodiments, for providing observability data from a first cloud environment to a second cloud environment using an agent.

[0032] Figure 16 Example processing for providing observable data across cloud services in multiple cloud environments, according to some embodiments, is described.

[0033] Figure 17 This is a block diagram illustrating a pattern for implementing a cloud infrastructure-as-a-service system according to certain embodiments.

[0034] Figure 18 This is a block diagram illustrating another style of implementing a cloud infrastructure-as-a-service system according to certain embodiments.

[0035] Figure 19 This is a block diagram illustrating another style of implementing a cloud infrastructure-as-a-service system according to certain embodiments.

[0036] Figure 20 This is a block diagram illustrating another style of implementing a cloud infrastructure-as-a-service system according to certain embodiments.

[0037] Figure 21 This is a block diagram illustrating an example computer system according to certain embodiments. Detailed Implementation

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

[0039] This disclosure generally relates to improved cloud architectures, and more specifically to techniques for providing services based on infrastructure distributed across multiple cloud service providers (CSPs). In the example, the first cloud service provider (CSP) (e.g., Oracle) ®Cloud infrastructure (OCI) provides primary services (e.g., database services, such as Exadata services available from Oracle), some of which are available from the primary cloud service provider infrastructure (CSPI) of the primary CSP. Secondary CSPs (e.g., Microsoft...) ® Azure, Google Cloud™, Amazon WebServices – AWS ® The first service (e.g., Azure Virtual Machines) is provided, some of which may be available from the second cloud service provider infrastructure (CSPI) of the second CSP. At least one of these first services may be made available to the second CSP's customers via the second CSPI. In the example, the hardware and / or software configured by the first CSPI to provide the first service is deployed at the second CSPI.

[0040] For example, at the physical level, the second CSPI may include a first set of computing resources of the first CSPI (e.g., racks of servers optimized for the services of the first CSPI). The first CSPI may include a second set of computing resources of the first CSPI (e.g., servers within a region). The second CSPI may also include a third set of computing resources of the second CSPI (e.g., servers within an availability zone). The first set of computing resources may be connected to the second and third sets of computing resources.

[0041] At the virtual tier, the first and second sets of resources can host a first cloud for a customer utilizing the first CSP. Conversely, the third set of resources can host a second cloud for the same customer utilizing the second CSP. These two clouds can be connected (e.g., via a peering connection using a virtual router). The service provided by the first CSP to the customer can have the first resources hosted in the first set of computing resources and the second resources hosted in the second set of computing resources. This service can be made available to the customer via the second cloud. The use of the first resources enables reduced latency. Providing services from the first CSP via the second CSP can enable a better experience by extending the service to customers of the second CSP (who may be more familiar with configuring and managing clouds using the second CSP).

[0042] To illustrate, consider an example of the Exadata service (i.e., the OCI database service) made available via Azure. In this example, at the physical tier, the OCI child site, belonging to the OCI region, is co-located in an Azure datacenter. The OCI child site is connected to the Azure datacenter via a FastConnect router (and a Microsoft MeetMe ToR router on the Azure side). The OCI child site is also connected to the parent OCI region via a Fibre Channel connection. At the virtual tier, the Azure datacenter hosts the customer cloud (e.g., VNET), while the parent region and child site of OCI co-host the customer virtual cloud network (VCN). Latency-critical resources used for the OCI service (e.g., data plane resources used for the Exadata service) are hosted in the child site, while other supporting resources (e.g., control plane resources, customer-facing console resources, etc.) are hosted in the parent region.

[0043] On the OCI side, VNET and VCN are connected via virtual routers (e.g., a Dynamic Routing Gateway (DRG) supporting FastConnect and a virtual router provided by Azure supporting MeetMe). Within VNET, delegated subnets can be configured. Within VCN, Exadata service subnets can be configured. Both subnets use the same Internet Protocol (IP) address range. VNET can store mapping information that maps IP addresses used within the IP address range in VNET to IP addresses of the Exadata service at VCN. Given a one-to-one IP address mapping, traffic to that IP address (e.g., compute instances from VNET) is sent from VNET to VCN.

[0044] Therefore, from the customer's perspective, the customer perceives the Exadata service as being within a VNET with an IP address. However, the Exadata service is actually located within the VCN at that IP address. Furthermore, by hosting at least a portion of the Exadata service (e.g., the data plane) in a subsite, the latency associated with the Exadata service can be reduced.

[0045] Referring back to the architecture described above, the first group of computing resources can be referred to as belonging to the sub-site, while the second group of computing resources can be referred to as belonging to the parent site. The third group of computing resources can be referred to as data center resources. The sub-sites of the first CSP are deployed in the data center (or second CSPI) of the second CSP. In contrast, the parent site of the first CSP is deployed in the first CSPI of the first CSP.

[0046] Subsites allow the low-latency services of the first CSP to be provisioned to customers via a second CSP. However, deployment mechanisms may be needed to control the deployment of resources of the first CSP in both the subsite and parent sites.

[0047] Embodiments of this disclosure relate to a deployment mechanism in which a control plane of a first CSP is not hosted in a subsite. Customer input at a second CSPI can be received by the control plane and mapped to a customer ID at the first CSPI. Based on this customer ID, the control plane can provision resources at the first CSPI, such as by creating a cloud network for the customer and creating associated connectivity resources (e.g., a Dynamic Routing Gateway – DRG) for that cloud network. The cloud network can also be connected to a cluster of virtual machines (VMs) hosting services. The VM cluster can be hosted in a subsite, while other resources of the cloud network can be hosted in a parent site. The control plane can then interconnect this cloud network to the customer's cloud network at the second CSP, thus interconnecting the customer's two cloud networks. As part of this interconnection, the control plane can provide the second CSPI with the Internet Protocol (IP) addresses of the VM clusters and possible corresponding DNS records, making these IP addresses and possible DNS records available to the customer at the customer's cloud network at the second CSP.

[0048] To illustrate, consider the OCI and Azure example again. Azure customer input (e.g., selecting their VNET and subnet) is received from Azure Resource Manager (ARM). The Oracle Resource Provider (ORP) can transform this input into an OCI ID for the customer and pass that information to the control plane. The control plane performs two main processes. The first is provisioning the relevant OCI resources. The second is connecting these resources to the customer's VNET.

[0049] In the first processing step, the control plane creates the customer's VCN in the customer's lease (e.g., at the parent site) and creates subnets (and possible backup subnets) within the VCN. The Azure and OCI subnets (one in the customer's Azure VNET, and one in the customer's OCI VCN) use the same Classless Inter-Domain Routing (CIDR). The control plane also creates a DRG in the customer's lease and attaches the DRG to the VCN. It also establishes routing information for the DRG and VCN (enabling these two resources to interconnect). The ORP can also be provisioned to a cluster of VMs (e.g., at the subsite). The IP addresses of this VM cluster(s) come from the CIDR and are mapped to the corresponding DNS records.

[0050] In the second process, the control plane registers these IP addresses with Azure (on the MeetMe router). It also creates a virtual circuit between the DRG and the MeetMe router and sends DNS records, enabling the establishment of a private DNS zone in Azure.

[0051] For clarity of explanation, embodiments of this disclosure are described in conjunction with specific CSPs (e.g., Oracle and Microsoft) and services (e.g., Exadata services). However, the embodiments are not limited thereto, but are similarly and equivalently applicable to any CSP, CSPI, and service in a multi-cloud environment.

[0052] Examples of cloud networks

[0053] The term cloud service generally refers to services provided by a service provider (CSP) to users or customers on demand (e.g., via a subscription model) using systems and infrastructure (e.g., cloud infrastructure) provided by the CSP. Typically, the servers and systems that make up the CSP's infrastructure are separate from the customer's own on-premise systems and servers. 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 a set of computing resources without requiring customers to invest in the infrastructure used to provide the service.

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

[0055] 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 cloud resources associated with that account through the subscription.

[0056] As mentioned above, IaaS is a specific type of cloud computing service. In the IaaS model, a CSP provides customers with the 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.

[0057] CSPI can include interconnected high-performance computing resources, including various host machines, memory resources, and network resources forming a physical network, also known as a substrate network or underlay network. Resources in 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 top of the physical network (or substrate network or underlay network). The physical network provides the underlying foundation for creating one or more overlay or virtual networks on top of it. The physical network includes physical network devices such as physical switches, routers, computers, host machines, etc. An overlay network is a logical (or virtual) network that runs on top of the physical substrate 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 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 network abstraction layer 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.

[0058] For IaaS, CSPI provided by a CSP can be configured to provide a virtualized set of 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 to accompany 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 infrastructure and a complementary set of cloud services, enabling 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.

[0059] 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 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 the infrastructure and a complementary set of cloud services that enable customers to build and run a wide range of applications and services in a highly available, virtualized 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 chosen networking components, such as firewalls.

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

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

[0062] 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 around the overlay addresses associated with network endpoints using software management (e.g., via software implementing a control plane for virtual networks). Therefore, unlike physical networks, in virtual networks, network management software can be used to move overlay addresses (e.g., overlay IP addresses) from one endpoint to another. 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 underlying network, and vice versa. These mappings are then used to facilitate communication. Client traffic is encapsulated to facilitate routing within the virtual network.

[0063] Therefore, 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 an overlay network, such as an overlay address associated with a compute instance in a customer's VCN. Two different customers or tenants, each with their own private VCN, can potentially use the same overlay IP address in their VCN without knowing about each other. Both physical IP addresses and overlay IP addresses are types of real IP addresses. They 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. A virtual IP address provides 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 or represent multiple servers, each with its own real IP address.

[0064] 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 so that each region has its own independent subset of CSPI resources. Each region can provide a set 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., VCN, load balancing resources, connectivity to on-premises networks); database resources; edge networking resources (e.g., DNS); access management and monitoring resources, etc. Each region typically has multiple paths connecting it to other regions within the domain.

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

[0066] 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 VCNs, or Availability Domain-specific, such as compute instances.

[0067] 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 IaaS providers grows, more regions and ADs, along with additional capacity, can be added. Traffic between availability domains is typically encrypted.

[0068] In some embodiments, regions are grouped into domains. A domain is a logical collection 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.

[0069] 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. 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, OCI currently offers domains for its business region and two domains for its government cloud region (e.g., FedRAMP licensed and IL5 licensed).

[0070] 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 group 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.

[0071] 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 these networks. A customer network hosted in the cloud by CSPI is called a VCN. A customer can use the CSPI resources allocated to them to establish 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.

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

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

[0074] 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. The 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 the VCN to enable communication to and from different types of endpoints.

[0075] A VCN can be subdivided into one or more subnets or subnetworks. 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) that do not overlap with other subnets within that VCN and represent a subset of the VCN's address space.

[0076] 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 become part of a VCN 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 it. For a subnet that includes a set of compute instances, the subnet contains a VNIC corresponding to that set of compute instances, and each VNIC is attached to a compute instance within that set of compute instances.

[0077] A private overlay IP address is assigned to each compute instance via the VNIC associated with it. This private overlay network 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.

[0078] 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 deleted. 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. Secondary VNICs can reside in a subnet within the same VCN as the primary VNIC, or in a different subnet within the same VCN or different VCNs.

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

[0080] 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., the compute instances on that subnet) to communicate with endpoints on other subnets within the VCN and with other endpoints outside the VCN. The VCN VR is a logical entity configured to route traffic between the VNIC within the VCN and the virtual gateway (“gateway”) associated with the VCN. The VCN VR is a Layer 3 / IP concept. In one embodiment, there is one VCN VR for a VCN, where the VCN VR potentially has an unlimited number of ports addressed by 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 the overlay IP address range 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 within the VCN with the address range 10.0 / 16, addresses within this range are reserved for ports on the VCN VR for that subnet. In some cases, the first IP address in the range can be reserved for the VCN VR. For example, for a subnet covering the 10.0 / 16 address range, the IP address 10.0.0.1 could be reserved for ports on the VCN VR for that subnet. For the second subnet within the same VCN with the address range 10.1 / 16, the VCN VR could have a port with the IP address 10.1.0.1 for the second subnet. The VCN VR has a different IP address for each subnet within the VCN.

[0081] 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 VNIC in the subnet can use this default or reserved IP address to communicate with the VR associated with the subnet (e.g., send and receive data 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 the subnet runs on or is performed by one or more NVDs that perform the VNIC functionality of the VNICs in the subnet.

[0082] 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. You can customize the VCN's routing table 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.

[0083] 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 allow incoming SSH traffic from anywhere to a set of instances by setting a stateful ingress rule with source CIDR 0.0.0.0 / 0 and destination TCP port 22. Security rules can be implemented using network security groups or security lists. A network security group consists of a set of security rules that apply only to 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 when the instance starts.

[0084] In some embodiments, configuration information for a VCN is determined and stored by the VCN control plane (CP). For example, 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, NVDs (e.g., VNICs, VRs, gateways) performing various virtualization network functions associated with the VCN, status information for the VCN, and other VCN-related information. In some embodiments, a VCN distribution service publishes the configuration information or portions thereof stored by the VCN CP to the NVD. The distributed information can be used to update information stored by the NVD and used to forward data packets to and from compute instances within the VCN (e.g., forwarding tables, routing tables, etc.).

[0085] In some embodiments, the creation of the VCN and subnet is handled by the VCN CP, and the startup of the compute instance is handled by the compute CP. The compute CP is responsible for allocating physical resources to the compute instance and then invoking the VCN CP to create the VNIC and attach the VNIC to the compute instance. 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.

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

[0087] Various architectures are used to implement cloud-based services using CSPI. Figures 1-12 and Figures 17-21 It is depicted in the text and 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.

[0088] like Figure 1 As illustrated in the example, distributed environment 100 includes CSPI 101, which provides services and resources that customers can subscribe to and use to build their 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 Region US 102. The customer has already configured a customer VCN c / o Oracle International 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.

[0089] exist Figure 1In the embodiment depicted, customer VCN 104 includes two subnets, namely "Subnet-1" and "Subnet-2", each with its own CIDR IP address range. Figure 1 In 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, VCN 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.

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

[0091] 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 1In 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.

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

[0093] 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 an endpoint in a VCN within the same region, or communication between a compute instance in subnet-1 and an endpoint 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 an endpoint in a VCN in a different region). 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 networks 118, public endpoints 112 that are accessible via public networks such as the Internet, and other endpoints.

[0094] 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 a packet to compute instance C2 in subnet-1. For a packet 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. The 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 the packet to that VNIC for processing. The VNIC associated with the destination compute instance then performs the forwarding and forwarding of the packet to the destination compute instance.

[0095] For data packets to be transmitted from a compute instance in a subnet to an endpoint in a different subnet 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 data 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.

[0096] For data packets to be transmitted 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.

[0097] For example, compute instance C1 might want to communicate with an endpoint outside of VCN 104. The data 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 the 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 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.

[0098] Various types of gateways can be configured for a VCN. Examples of gateways that can be configured for a VCN are available in [link to example]. Figure 1 It is depicted in the diagram and described below. An example of a gateway associated with a VCN is also included. Figures 17-20 The gateways are depicted in the figures (e.g., referenced by reference numerals 1734, 1736, 1738, 1834, 1836, 1838, 1934, 1936, 1938, 2034, 2036, and 2038) and described below. Figure 1As illustrated in the embodiments depicted, DRG 122 can be added to or associated with customer VCN 104 and provides a path for private network traffic communication between customer VCN 104 and another endpoint, which can be customer's on-premises network 116, VCN 108 in a different region of CSPI 101, or another remote cloud network 118 not hosted by CSPI 101. Customer on-premises network 116 can be a customer network or customer data center built using customer resources. Access to customer on-premises network 116 is generally very restricted. For customers who have both customer 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 customer VCNs 104 hosted by CSPI 101 and their on-premises network 116. DRG 122 enables this communication. To enable this type of communication, a communication channel 124 is established, 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 called a 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.

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

[0100] 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 112 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 allows public subnets within the VCN (such as VCN 104), where resources have publicly overriding IP addresses, to directly access the 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.

[0101] 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 direct inbound 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 private subnets to the public Internet, and not from the Internet to private subnets.

[0102] In some embodiments, a Service Gateway (SGW) 126 may be configured for a client 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 clients. For example, compute instances (e.g., database systems) in a private subnet of client 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 the on-premises network of a VCN connected using FastConnect or VPN Connect may also use the service gateway configured for that VCN.

[0103] 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 those rules if the public IP addresses of the service change in the future.

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

[0105] 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 the VNIC. Because the endpoint is exposed as a VNIC, all features associated with the VNIC (such as routing rules, security lists, etc.) are now available to the PE VNIC.

[0106] Service providers can register their services to enable access via a Virtual Private Server (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.

[0107] 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 allows 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).

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

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

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

[0111] 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 (e.g., resources in a private subnet) with private IP addresses within VCN 104 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.

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

[0113] 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, memory, and networking resources) provided by the CSP. These components and resources are used to provide cloud services (e.g., IaaS services) to subscribing 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, memory, and networking resources) is provisioned to the customer. The customer can then use the physical compute, memory, 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 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 infrastructure and a complementary set of cloud services that enable customers to build and run a wide range of applications and services in a highly available managed environment.

[0114] 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), 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 a... Figure 2 The NVD execution described in [the document / document].

[0115] 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 a set of physical computing resources (e.g., compute, memory, and networking resources) of the host machine to be shared among various compute instances executed by the host machine.

[0116] 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 that sits 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 a set of physical computing resources on the host machine (e.g., processing resources such as processors / cores, memory resources, networking resources) to be shared among various virtual machine computing instances executed by the host machine. For example, in... Figure 2 In this configuration, hypervisor 260 can reside on top of the operating system of host machine 202 and enable a set of computing resources (e.g., processing, memory, and networking resources) of host machine 202 to be shared among computing instances (e.g., virtual machines) running on 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 running on the host machine can be the same as or different from the operating system of another virtual machine running on the same host machine. Therefore, the hypervisor enables multiple operating systems to be executed simultaneously, sharing the same set of 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.

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

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

[0119] 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 of packets or frames to and from the compute instance. The VNIC is associated with the compute instance when the compute instance 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.

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

[0121] 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 use one or more ports (or interfaces) provided on the host machine and the NVD to connect to the NVD. The host machine may also connect to other devices, such as another host machine.

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

[0123] The NVD is then connected to 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 collection of host machines and NVDs connected to the ToR is sometimes referred to as a rack.

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

[0125] 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 2In 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.

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

[0127] Figure 3 The layout depicted provides two separate physical network paths from physical switch network 318 to 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.

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

[0129] Return 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.), cached memory, and ports. Various virtualization functions can be executed by software / firmware running on one or more processing units of the NVD.

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

[0131] 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 instance, 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. A ToR performing the functions of the NVD is sometimes referred to as a smart ToR. 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 cluster of host machines.

[0132] In some embodiments, such as when implemented as Figure 2 As shown in the smartNIC diagram, an 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 an NVD can be categorized as host-facing ports (also known as "south ports") or network-facing or ToR-facing ports (also known as "north ports"). Host-facing ports on an NVD are those used to connect the NVD to host machines. 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 the 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.

[0133] 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 the NVD's 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 the NVD's host-facing port.

[0134] In some embodiments, there can be multiple ports and associated links between the NVD and the ToR switch. 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 the ToR switch) 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 is 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 the ToR switch, between a host machine and the NVD, etc.

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

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

[0137] NVD can perform both control plane and data plane functions corresponding to the control plane and data plane of VCN. Examples of VCN CP are also available. Figures 17-20 The data plane VCN is depicted in (see reference numerals 1716, 1816, 1916, and 2016) and described below. Figures 17-20The following describes the data plane functionality (see reference numerals 1718, 1818, 1918, and 2018). Control plane functions include features for configuring how control data is forwarded on the network (e.g., setting routes and routing tables, configuring VNICs, etc.). In some embodiments, a VCN CP is provided, which centrally computes all overlay mappings to the underlying 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 established using the control plane. The VCN data plane is implemented by encapsulating client network packets before they traverse the underlying 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.

[0138] 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).

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

[0140] 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 “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 example, a packet processing component for an NVD may include a packet processor configured to interact with the NVD’s ports and hardware interface to monitor all packets received by and transmitted using the NVD and to store network information. 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 copy 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.

[0141] 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, a VR for the VCN, and a set 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.

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

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

[0144] For packets destined for endpoints in different subnets within the same VCN, the packets originating from the source compute instance are routed from the host machine hosting the source compute instance to an NVD connected to that host machine. On the NVD, the packets are 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 functionality corresponding to the VNIC associated with the source compute instance (also known as executing the VNIC). Functionality executed by the VNIC may include viewing VLAN tags on the packets. Since the packet's destination is outside the subnet, the VCN VR functionality is then invoked and executed by the NVD. The VCN VR then routes the packets to the NVD executing the VNIC associated with the destination compute instance. The VNIC associated with the destination compute instance then processes the packets and forwards them 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).

[0145] If the destination of a data packet is outside the VCN of the source compute instance, the packet originating from the source compute instance is transmitted from the host machine hosting the source compute instance to the NVD connected to that host machine. The NVD executes the VNIC associated with the source compute instance. Since the destination endpoint of the packet is outside the VCN, the packet is subsequently processed by the VCN VR used by that VCN. The NVD invokes the 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 may 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 delivery of the packet to its intended destination endpoint. For example, in Figure 2In the embodiment depicted, data 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 data packets and determine the next hop for forwarding the data packets, with the aim of facilitating the transmission of the data packets to their intended destination endpoint, and then forwarding the data packets to the determined next hop.

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

[0147] Figure 2 The 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 a more advanced architecture 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).

[0148] 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 4As 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.

[0149] 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 NIC due to the logical NICs.

[0150] 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. Therefore, 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 data packet 424 received from the host machine 402, the tag 426 associated with the data packet is used to determine whether the data packet is processed by VNIC-VM1 420 or VNIC-VM2 422. The data packet is then processed by the corresponding VNIC. Figure 4 The configuration described in the document allows 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.

[0151] Figure 5A 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 Layers 1, 2, and 3. The 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 5 In the embodiments depicted, a group of "n" Layer 0 ToR switches are connected to a group of "n" Layer 1 switches, forming a pod (cluster). Each Layer 0 switch in a pod is interconnected to all Layer 1 switches within 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 group 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). Communication of packets 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 for high availability. Policies can be specified for pods and blocks to control the visibility of switches to each other within the physical network, thereby enabling scaling of the physical network.

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

[0153] 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:

[0154] ocid1.<RESOURCE TYPE> . <realm>[REGION][FUTURE USE].<UNIQUE ID> in,

[0155] ocid1: A text string indicating the version of the CID;

[0156] Resource Type: The type of resource (e.g., instance, volume, VCN, subnet, user, group, etc.).

[0157] Realm: The domain in which the resource resides (example values ​​are "c1" for the commercial domain, "c2" for the government cloud domain, or "c3" for the federal government cloud domain, etc. Each domain can have its own domain name).

[0158] Region: The region where the resource is located (this part may be empty if the region is not applicable to the resource).

[0159] Future use: (Reserved for future use); and

[0160] Unique ID: The unique part of the ID (the format may vary depending on the type of resource or service).

[0161] partly cloudy

[0162] Figure 6 A simplified high-level diagram 600 depicts a distributed environment comprising multiple cloud environments provided by different CSPs. (See diagram 600.) Figure 6 As described herein, various cloud environments (also referred to as "clouds") can be provided by different CSPs, and each cloud environment or cloud provision can be one or more cloud services subscribed to by one or more customers of the corresponding CSP. The set of cloud services provided by a cloud environment offered by a CSP can include one or more different types of cloud services, including but not limited to SaaS services, IaaS services, PaaS services, Database-as-a-Service (DBaaS) services, and other services. Examples of cloud environments provided by various CSPs include OCI, Azure, Google Cloud, AWS, etc. The cloud services provided by a particular cloud environment can differ from the set of cloud services provided by another cloud environment.

[0163] In a typical cloud environment, a CSP provides a Cloud Service Provider Interface (CSPI), which is used to offer its customers a set of cloud services provided by that cloud environment. The CSPI provided by the CSP can include various types of hardware and software resources, including computing resources, storage resources, networking resources, consoles for accessing cloud services, etc. Customers of a cloud environment provided by a CSP can subscribe to one or more cloud services offered by that cloud environment. The CSP can offer various subscription models to its customers. After a customer subscribes to a cloud service provided by the cloud environment, one or more users can be associated with that subscribed customer, and such users can use the cloud services subscribed to by that customer. In some implementations, when a customer subscribes to a cloud service provided by a particular cloud environment, a customer account or customer lease is created for that customer. One or more users can then be associated with that customer lease, and such users can then use the services subscribed to by that customer lease. Information about the services subscribed to by the customer, the users associated with the customer lease, etc., is typically stored within the cloud environment and associated with the customer lease.

[0164] For example, Figure 6 The document describes two different cloud environments provided by two different CSPs (but different numbers of cloud environments are possible). These include cloud environment A (Cloud A) 610 provided by CSP A and cloud environment B (Cloud B) 640 provided by CSP B.

[0165] Cloud A 610 includes infrastructure CSPI_A 612 provided by CSP A. This infrastructure CSPI_A 612 can be used to provide a set of in-cloud services 615 supplied by Cloud A 610. One or more customers (e.g., Cust_A1 616-1, Cust_A2 616-2) can subscribe to one or more of these services. One or more users 618-1 can be associated with customer Cust_A1 616-1 and can use the services subscribed to by customer Cust_A1 616-1 in Cloud A 610. Similarly, one or more users 618-2 can be associated with customer Cust_A2 616-2 and can use the services subscribed to by customer Cust_A2 616-2 in Cloud A 610. In various use cases, the services subscribed to by customer Cust_A1 616-1 may differ from the services subscribed to by customer Cust_A2 616-2.

[0166] Similarly, Cloud B 640 includes infrastructure CSPI_B 642 provided by CSP B. This infrastructure CSPI_B 642 can be used to provide a set of services 644 provided by Cloud B 640 (which may, but are not necessarily, different from, the services provided by Cloud A 610). One or more customers (e.g., Cust_B1 646-1) can subscribe to one or more services in this set of services 644. One or more users 648-1 can be associated with customer Cust_B1 646-1 and can use the services subscribed to by customer Cust_B1 646-1 in Cloud B 640.

[0167] like Figure 6 As described, customer Cust_A1 616-1 is also a customer of CSP B and has subscribed to services available from CSPI_B642. Therefore, customer Cust_A1 616-1 has leases in both Cloud B 640 and Cloud A 610.

[0168] In some embodiments, CSP A and CSP B may agree to provide their respective cross-cloud services. Figure 6 As described, CSP A provides one or more of its services (referred to herein as cross-cloud services) to CSP B's customers via CSPI_B 642. These cross-cloud services include, for example, database services, storage services, compute services, etc. Thus, customer Cust_A1 616-1 (a customer of both Cloud A and Cloud B) can request, subscribe to, use, and / or manage one or more cross-cloud services of the CSPA through its lease at CSPI_B 642. In contrast, customer Cust_B1 646-1 does not have a lease at CSPI_A 612. Therefore, CSP A's cross-cloud services may be unavailable to customer Cust_B1 646-1 unless customer Cust_B1 646-1 requests a lease provided by the CSPA. This request can be submitted and managed through the portal of Cloud B 640, as further described in the following diagram.

[0169] To enable cross-cloud service provisioning and availability of CSP A via Cloud B 640, Cloud A 610 can implement Inter-Cloud Service 614. Inter-Cloud Service 614 can, among other things, be configured to enable the use of CSP A's cross-cloud services via Cloud B. For example, Inter-Cloud Service 614 can communicate with Service 644 of Cloud B 640 and translate such communication into information suitable for use by Cloud A's intra-cloud services 615. More specifically, this set of services 644 enables the implementation of a portal for CSP B and the deployment and management of resources for CSP B's customers within Cloud B 640. Through this portal, cross-cloud services of CSP A can be provisioned. Thus, CSP B's customers (e.g., customer Cust_A1 616-1) can subscribe to and request cross-cloud services of CSP A via this portal. Such subscription and cloud operation requests can be received by Inter-Cloud Service 614, which then translates them into information specific to Cloud A 610. This type of information can be passed to one or more cloud services 615 that then provide the service. Information fed back from cloud service 615 can be transformed by inter-cloud service 614 and sent to cloud service 644 for its use.

[0170] In some embodiments, the requested cross-cloud service can be provisioned by one or more cloud services in cloud service 615 across resources in both cloud A 610 and cloud B 640. This can support latency-sensitive operations (or at least reduce processing latency).

[0171] As shown in the figure, the infrastructure CSPI_A 612 of Cloud A 610 includes infrastructure 624 for customer Cust_A1 616-1's private cloud in Cloud A 610 (e.g., for a VCN as part of the customer's lease at Cloud A 610), infrastructure 626 for customer Cust_A2 616-2's private cloud in Cloud A 610, and other infrastructure 620. Each of these infrastructures includes hardware and / or software provided by CSP A and installed at a location (organized as a region) under the control of CSP A.

[0172] In contrast, the infrastructure CSPI_B 642 of Cloud B 640 includes infrastructure 644 for customer Cust_A1 616-1's private cloud in Cloud A (e.g., for a VCN as part of the customer's lease at Cloud A 610), infrastructure 646 for customer Cust_A1 616-1's private cloud in Cloud B 640 (e.g., for a VNET as part of the customer's lease at Cloud B 640), infrastructure 648 for customer Cust_B1 646-1's private cloud in Cloud B 640, and other infrastructure 650. Infrastructure 644 includes hardware and / or software (e.g., co-located with components of CSPI_B 642) provided by CSP A and installed at a location (organized as a region) under the control of CSP B. In contrast, infrastructures 646, 648, and 650 include hardware and / or software provided by CSP B and installed at a location (organized as a region) under the control of CSP B.

[0173] Infrastructures 644 and 646 can be networked together, allowing customer Cust_A1 616-1 to access its private cloud at CSP A via its private cloud at CSP B, where the private cloud at CSP A is distributed between CSPI_A 612 and CSPI_B 642. This communication coupling of the private clouds can be initiated by inter-cloud service 614 and executed by one or more intra-cloud services in intra-cloud service 615. In this way, customer A 616-1 has two leases: the first at CSP A, which includes a first private cloud (e.g., VCN) distributed between CSPI_A 612 and CSPI_B 642, and the second at CSP B, which includes a second private cloud (e.g., VNET) local to CSPI_B 642.

[0174] The requested cross-cloud service may actually be hosted on a first private cloud (e.g., at least partially on infrastructure 644 within CSPI_B 642, and possibly in infrastructure 624 within CSPI_A 612) and accessible via a second private cloud (e.g., for workflow access hosted by infrastructure 646). This distribution of components will be further described in the following diagrams, enabling the first private cloud of the first CSP to be hosted at least partially by and linked to the second private cloud hosted by the second CSP.

[0175] Figure 7 An exemplary physical architecture for providing cross-cloud services based on infrastructure distributed across multiple CSPs, according to some embodiments, is described. Figure 7 In this embodiment, the second CSP's customer will manage the lifecycle of the cross-cloud service developed by the first CSP. For illustrative purposes, the Exadata service (also referred to herein as the Oracle DB service) and the Oracle and Microsoft clouds are described. In this description, Oracle corresponds to the first CSP, and Microsoft corresponds to the second CSP, while the Exadata service corresponds to the cross-cloud service provided by the first CSP via the second CSP's cloud. However, the embodiment is not limited to this, but is similarly applicable to other CSPIs, CSPs, and / or cross-cloud services.

[0176] A second CSP's customer (e.g., an Azure customer) can create and manage virtual resources (e.g., infrastructure and / or VM clusters) within the first CSP's cloud via the second CSP's portal (e.g., the Azure portal). These virtual resources can be provisioned to offer cross-cloud services. This can be at least partially utilized. Figure 6 Cloud services 614 are used to support such provisioning. Furthermore, the infrastructure supporting virtual resources can be distributed between the CSPIs of two CSPs (e.g., between an Azure data center and an OCI region). Specifically, a first portion of the infrastructure provided by the first CSP is installed at the CSPI of the second CSP, while the remaining second portion of the infrastructure provided by the first CSP is installed at the CSPI of the first CSP. The first portion may be referred to as being included within the cloud of the second CSP or forming a subsite within the cloud of the second CSP. The second portion may be referred to as being included or forming a parent-child region for that subsite, wherein the parent region is within the cloud of the first CSP.

[0177] exist Figure 7 On the left, a second CSPI_B 750 of the second CSP is shown. This CSPI_B 750 may, for example, represent the data center of the second CSP (e.g., an Azure data center). Within the CSPI_B 750, a base network 730 is available and provided by the second CSP. The base network 730 includes a set of computing resources, such as routers 732A, 732B, etc. (In the case of an Azure data center, these routers may include MeetMe ToRs supporting the MeetMe protocol for peer-to-peer connections). The CSPI_B 750 also includes a subsite 720 (which is a set of computing resources, such as server blades, racks, or other physical hardware of the first CSP that execute the software of the CSP). Subsite 720 includes, among others, routers 722A, 722B, etc. (in the case of OCI, these routers may include FastConnect routers that support the FastConnect protocol for connecting peers), connectivity architecture 724 (e.g., physical architecture, such as JFAB, which provides connectivity to other physical architectures and components), and physical resources 726 (e.g., racks, such as OCI server blades optimized for cross-cloud services, such as Exadata services).

[0178] exist Figure 7 On the right, a first CSPI_A 700 of the first CSP is shown. This CSPI_A 700 may, for example, represent the data center of the first CSP (e.g., an OCI data center). Within CSPI_A 700, a parent region 710 is illustrated. The parent region 710 may include a base network with multiple components. Among these components is a connectivity architecture 712 (e.g., a physical architecture, such as JFAB). The connectivity architecture 712 is connected to a connectivity architecture 724, enabling the child site 720 to be communicatively coupled to the parent region 710. Optionally, the parent region 710 is located in a region physically adjacent to the child site 720 (or equivalently, CSPI_B 750), thereby reducing network latency for communication between the child site 720 and the parent region 710.

[0179] Router 732 within the base network 730 can be interconnected (e.g., via Ethernet cable) to router 722 within subsite 720. The connectivity architecture 724 of subsite 720 provides interconnectivity between router 722 and physical resources 726. Furthermore, this connectivity architecture 724 is connected to the connectivity architecture 714 of parent area 710 (e.g., using fiber optic cables, such as dark fiber), enabling data connectivity between subsite 720 and parent area 710.

[0180] The base network 730 can host a set of resources for a second CSP for customers (e.g., to provide a VNET containing compute instances with access to the Exadata service, as further illustrated in the following diagram). These second CSP resources can be part of a neighboring group within a certain latency (e.g., 100µs) of the cross-cloud service.

[0181] Subsite 720 can host latency-critical resources of the first CSP, where these resources support cross-cloud services (e.g., subsite 720 can host OCI database resources and data plane resources supporting the Exadata service). Parent region 720 can host other resources that support cross-cloud services (e.g., Figure 6 (This includes cloud-to-cloud services 614 and cloud-within-cloud services 715). (For example, for the Exadata service, parent region 720 can host ORP, OCI tools, OCI metrics and logging, the OCI control plane, regional OCI services, and a customer-facing console.) Some of these resources (e.g., OCI database resources and data plane resources) can be deployed as part of the customer's first private cloud at the first CSP (e.g., as a VCN in the case of OCI) and can be perceived by the customer as being available via the customer's second private cloud at the second CSP (e.g., VNET in the case of Azure). This perception is possible by using the same IP address range in both private clouds used for cross-cloud services.

[0182] In the example, a customer may have multiple private clouds (e.g., multiple VNETs and / or multiple VCNs) at each CSP. In the case of multiple private clouds at the first CSP, the underlying physical resources may not be co-located in the same CSPI at the second CSP, but may instead be included in different subsites or formed as different subsites. In this case, these resources may not be directly interconnected (e.g., there may be no direct physical connection between different subsites). Alternatively, indirect connections may exist via a parent region, where each subsite in the different subsites is physically (e.g., via fiber optic) connected to the parent region, and where data flows between the two subsites through the parent region.

[0183] Furthermore, Subsite 720 can support multi-tenant architectures. Specifically, multiple customers can each have one or more private clouds (e.g., one or more VNETs and one or more VCNs) at each CSP. Each such customer can have individual access to the corresponding cross-cloud services via Subsite 720.

[0184] Figure 8 An exemplary virtual architecture for providing cross-cloud services based on infrastructure distributed across multiple CSPs, according to some embodiments, is described. Figure 8 In this context, a customer’s first private cloud 810 at the first CSP (e.g., a VCN hosted by OCI) and the customer’s second cloud 820 at the second CSP (e.g., a VNET hosted by Azure) can be provisioned to provide cross-cloud services of the first CSP to the cloud via the second CSP (e.g., Exadata services provided by Oracle and available to Azure customers via Azure).

[0185] In the example, the second private cloud 820 (e.g., VNET) is hosted by the physical compute resources (e.g., Azure data center) of the second CSP's CSPI_B 850. The second private cloud 820 may include compute instances (not shown) with access to cross-cloud services. The second private cloud 820 includes a subnet 822. Subnet 822 uses an IP address range. This range can be specified based on customer input via the second CSP's portal (e.g., the Azure portal). IP addresses can be assigned from this IP address range to each compute instance (e.g., a VM belonging to a VM cluster and providing a database instance) launched to provide cross-cloud services to customers. These compute instances may be hosted by the first private cloud 810 (in... Figure 8 More generally, these are displayed as virtual resources 814A, 814B, 814C, and 814D. Figure 8 The diagram illustrates four computational examples, indicated by rectangles labeled NIC 824A, 824B, 824C, and 824D (or collectively referred to as NIC 824). While NIC stands for Network Interface Card, Figure 8 The NIC 824 itself is not like that. Instead, the NIC 824 represents mapping information used to map each IP address to the corresponding compute instance across cloud services. This mapping information can be stored as part of the configuration information of the second private cloud 820. If a compute instance of the second private cloud 820 uses an IP address to send or request traffic, and that IP address corresponds to a NIC, then the mapping information indicates that the traffic will be sent to or received from the first private cloud 810 (e.g., VCN) and that the traffic is cross-cloud service traffic.

[0186] The first private cloud 810 (e.g., VCN) can be hosted by the physical computing resources of the first CSP, such as physical computing resources including subsites and parent regions (similar to...). Figure 7 The diagram illustrates physical computing resources. The first private cloud 810 may include subnets 812 using the same IP address range. Each compute instance launched to provide cross-cloud services (e.g., each of virtual resources 814A, 814B, 814C, and 814D, collectively referred to as virtual resource 814) is hosted by a set of physical computing resources of the first CSP. This set of physical computing resources for the compute instance may include physical computing resources in subsites and physical computing resources in the parent region. The computing resources of the subsites may include, for example, hardware (e.g., racks) that performs operations such as... Figure 7 The software shown here is for cross-cloud services and provides latency-critical virtual resources (e.g., database resources, data plane resources, etc.). The physical computing resources of the parent region may include, for example, servers, server clusters, network virtualization devices, etc., that provide non-latency-critical virtual resources (e.g., control plane resources, tool resources, etc.).

[0187] Each compute instance can have an IP address from this IP address range. There is a one-to-one mapping between compute instances in the first private cloud 810 (e.g., virtual resource 814) and NIC 824 in the second private cloud 820. Thus, using this one-to-one mapping, cross-cloud service traffic can be sent from the second private cloud 820 to the first private cloud 810 and vice versa.

[0188] The second private cloud 820 can be connected to the first private cloud 810 via one or more virtual routers (e.g., coupling the underlying network of the second CSP to the subsites), gateways (e.g., for coupling the subsites to the parent region, implementing gateway 826 at the subsites and gateway 816 at the parent region, such as through various parts of a connectivity architecture), and connectivity protocols (e.g., MeetMe and FastConnect protocols) (e.g., peer-to-peer connections). Overall, gateways 816 and 826 can represent dynamic routing gateways.

[0189] From the customer's perspective, the customer does not need to know the underlying physical architecture and interconnects. Instead, it may be sufficient for the customer to have visibility at the virtual tier, thereby enabling the customer to perceive and manage their private clouds 810 and 820 (e.g., their network configuration). Management of the second private cloud 820 can be via a second portal of the second CSP. Management of the first private cloud 810 can be via a second portal of the second CSP or a first portal of the first CSP. In this embodiment, changes and / or operations related to cross-cloud services are enabled only via the second CSP (e.g., via the second CSP, a customer can expand or shrink, remove, terminate, add, etc., virtual resources at the first private cloud 810 launched for cross-cloud services). In contrast, changes and / or operations unrelated to cross-cloud services may (only) be enabled via the first CSP (e.g., via the first CSP, a customer can expand or shrink, remove, terminate, add, etc., virtual resources at the first private cloud 810 launched for non-cross-cloud services).

[0190] Figure 9 Exemplary virtual resources provided to a client according to some embodiments are described. Figure 9 The right side shows the first resource (e.g., OCI resource) of the first CSP deployed for the customer. Figure 9 The left side shows a second resource (e.g., for an Azure data center) deployed for a second CSP for a customer. The first CSP (shown as CSP A) provides cross-cloud services (e.g., Exadata services) available in the cloud via the second CSP (shown as CSP B).

[0191] The first resource (which may be a combination of physical and virtual resources) may include a private cloud 920, a service lease 910, a VM cluster 926, and a gateway 928. The private cloud 920 (e.g., a VCN) may correspond to a lease held by a customer at a first CSP and may include a primary subnet 922 with an IP range (e.g., a Classless Inter-Domain Routing (CIDR) range) and, optionally, a backup subnet 924 using the same IP range. The service lease 910 may be available to multiple customers of the first CSP and may include a gateway 912. The VM cluster 926 includes a number of VMs (or compute instances) launched for clients to provide cross-cloud services. The VM cluster 926 may be hosted on physical resources within a subsite. The gateway 928 (e.g., a service gateway) connects the virtual resources of the primary subnet 922 (and, similarly, the backup subnet 924) hosted on physical resources within a parent region to the VM cluster 926. In contrast, the gateway 912 connects such virtual resources to a private cloud 960 held by a customer at a second CSP. Gateway 912 can be implemented as a DRG attached to a private cloud 920 in a customer lease. This connection can be via gateway / router 914. Gateway / router 914 can be provided at least partially in a subsite and connects the subsite to the parent region via a first connection protocol (e.g., FastConnect) (thus providing gateway functionality) and to the underlying network of a second CSP via a second connection protocol (e.g., MeetMe) (thus providing routing functionality). For example, gateway / router 914 can represent a FastConnect virtual circuit resource in service lease 910 for connecting the DRG to an Azure MeetMe router (example router 968).

[0192] The second resource (which may be a combination of physical and virtual resources) may include a private cloud 960 and a router 968. The private cloud 960 may include a main subnet 922 with an IP range, and optionally a backup subnet 964 using the same IP range. This IP range may be the same as the IP range of the main subnet 922. The router 968 may be connected to a gateway / router 914 to provide data connectivity from the main subnet 962 (e.g., and the backup subnet 964) to the private cloud 920. The main subnet 962 may include NICs 966A to 966K connected to the router 968.

[0193] The first CSP (e.g., its inter-cloud or intra-cloud service) can select IP addresses from this IP range to provide services to different virtual resources across clouds. The first CSP (e.g., its inter-cloud or intra-cloud service) can create Domain Name System (DNS) records corresponding to these IP addresses, which can then be provided to Private Cloud 960. These DNS records can be used to establish private DNS zones for customers, which can be used in conjunction with Private Cloud 960.

[0194] For illustration, subnets 922, 924, 962, and 964 use IP addresses from 10.0.10.0 / 24. Each NIC 966 has an IP address from this range (e.g., NIC A 966 A uses 10.0.10.10, and NIC K 966 K uses 10.0.10.11). VMs in the VM cluster use the same IP addresses (e.g., the first VM uses 10.0.10.10, while the second VM uses 10.0.10.11).

[0195] Figure 10 An exemplary architecture for provisioning and managing cross-cloud services based on infrastructure distributed across multiple CSPs, according to some embodiments, is described. Figure 10 In this example, the customer of the second CSP (shown as CSP B) will manage the lifecycle of a cross-cloud service developed by the first CSP (shown as CSP A). For clarity and illustrative purposes, OCI and Azure are described as examples of CSPI, and the Exadata service is described as an example of a cross-cloud service. However, the embodiment is not limited to this, but is similarly applicable to other CSPs and / or cross-cloud services.

[0196] A customer (e.g., an Azure customer) can operate customer device 1000 to create and manage a set of virtual resources (e.g., Oracle DB infrastructure resources) across cloud services via a second CSP's portal (displayed as CSP_B portal 1052). In the example, portal 1052 interacts with one or more services of the second CSP (displayed as CSP_B service 1054, examples of which may include Azure Resource Manager (ARM) that exposes APIs for managing the lifecycle of Oracle DB infrastructure resources (DB infrastructure resources include Exadata infrastructure and cloud VM clusters); other examples include Azure Resource Provider as a Service (RPaaS) to simplify the development and operation of Azure resource providers, such as asynchronous operations and their progress updates). To manage the resources (DB Home, databases, pluggable databases) built on top of the set of virtual resources, CSP_B service 1054 interacts with the first CSP's inter-cloud service 1012, causing the customer to be redirected to inter-cloud service 1012 (e.g., ORP in the case of OCI).

[0197] Inter-cloud service 1012 is configured to: i. handle the transformation (including identity, resource ID, and subscription ID) of an identifier assigned by a second CSP (e.g., an Azure identifier) ​​to an identifier assigned by a first CSP (e.g., an OCI identifier); ii. handle the transformation of a second CSP state (e.g., an Azure state) to a first CSP state (e.g., an OCI state) and vice versa; and / or iii. delegate requests to an in-cloud service 1014 of the first CSP for execution (e.g., delegate to a resource control plane 1016, such as the OCI DBaaS control plane). Inter-cloud service 1012 is also configured to coordinate any second CSP-specific integrations with other second CSP services (e.g., with Azure resource providers). Inter-cloud service 1012 may also be configured to perform or cause other in-cloud services 1014 to perform operations, including linking cloud accounts, publishing observability information, and issuing vending tokens to access other cloud customer environments.

[0198] Cloud service 1014 can provide a portal for the first CSP (displayed as CSP_A portal 1018), which can be accessed by the customer's client device 1000 to manage other services provided by the customer to the first CSP. The two portals 1052 and 1018 can enable similar functionality (e.g., by presenting input and output fields), but are still different. For example, portal 1052 (e.g., the Azure portal) can have a presentation format controlled by the second CSP. Furthermore, in addition to functionality related to cross-cloud services, portal 1052 can also enable functionality specific to the second CSP and unrelated to the first CSP. In contrast, portal 1018 (e.g., the OCI portal) can have a presentation format controlled by the first CSP. Furthermore, in addition to functionality related to cross-cloud services, portal 1018 can also enable functionality specific to the first CSP and unrelated to the second CSP. Regarding cross-cloud services, portal 1052 can expose information available from the second CSP, which can be provided by inter-cloud service 1012.

[0199] In the OCI and Azure use case examples, Cloud Service 1012 exposes the Oracle DB product. Cloud Service 1012 can register with ARM via RPaaS and is configured to implement Azure Resource Provider Contracts (RPCs), a set of operations supported by all Azure resource providers. Azure RPaaS internal services are used to support most of the RPC operations.

[0200] Generally, Cloud Service 1012 can be configured to have a second CSP identity (e.g., an Azure RP identity equivalent to an OCI service principal) and the ability to operate on a second CSP customer environment using second CSP processes (e.g., Azure OBO processes). Cloud Service 1012 can also be configured to persistently store second CSP-specific metadata for first CSP resources, such as the mapping of Azure identifiers to OCIDs for DB resources. Cloud Service 1012 can also be configured to have a first CSP identity to gain the scope to operate on a first CSP customer environment. Cloud Service 1012 can also be configured to act as a thin adapter layer, receiving requests formatted by a second CSP that has been authenticated by Service 1054, transforming them into first CSP requests, and delegating the requests to in-cloud services.

[0201] Therefore, cloud service 1012 performs several operations. These operations include transforming identifiers from one cloud to another and vice versa. These operations also include obtaining a first CSP identity for invoking cloud service 1014 for an incoming request from service 1054. These operations also include transforming a second CSP format request into a first CSP format request and invoking cloud service 1014. These operations also include limiting / quota / capacity verification pass-through or mediation, implicitly creating first CSP prerequisites for network connectivity resources (e.g., creating OCI DRGs, VCNs, and subnets to which VM clusters are attached), invoking links in the private cloud, and configuring DNS entries at the second CSP for resources with associated DNS records.

[0202] In the example, inter-cloud service 1012 can be hosted in one or more subsites. Inter-cloud service 1012 can host virtual resource 1020 in a subsite. In the Exadata service use case, virtual resource 1020 can include the DBaaS data plane via the DBaaS control plane. This control plane is hosted in a parent region as part of in-cloud service 1014. In this use case, compute instances (e.g., VMs) can be instantiated for the customer on the customer's private cloud (e.g., VNET in Azure) at the second CSP. The compute instances can perform database operations by making calls to the DBaaS data plane. Such operations include queries, storage, etc., or any operations supported by the Exadata service. The calls and responses to them can be within the private cloud at the second CSP. After use, the DBaaS data plane can report usage information (e.g., for metrics analytics, billing, etc.) to one or more of the in-cloud services 1014 (e.g., to the observability service). This usage information can then be provided to the monitoring service of the second CSP.

[0203] Figure 11 An exemplary user experience flow 1100 for provisioning resources according to some embodiments is described. In the example, user experience flow 1100 involves a client device 1120, a CSPI_B 1150 of a second CSP, and an inter-cloud service of a first CSP. The first CSP may provision cross-cloud services via the second CSP. Virtual resources may be provisioned to provide at least a portion of the cross-cloud services, wherein the provision follows user experience flow 1100.

[0204] User input is controlled by CSPI_B 1150 (e.g., by...). Figure 10 The CSP_B portal (similar to portal 1052) receives instructions from client device 1120 to create a subnet and mark it as delegated, enabling it to be used for cross-cloud services. The subnet and the client's second private cloud at the second CSP are created, and instructions regarding this creation are provided to client device 1100.

[0205] Next, user input is received by inter-cloud service 1110 from computing device 1100 (where this input can be at the portal), indicating a request to create cross-cloud service infrastructure (e.g., an Exadata service). User input can indicate various parameters for provisioning, such as region and availability zone. Inter-cloud service 1110 can indicate the start of provisioning to computing device 1100 (e.g., via the portal) and can execute a provisioning workflow that creates the cross-cloud service infrastructure in the relevant subsites. While the infrastructure is being created, inter-cloud service 1110 sets its status to "Provisioning". Once created, inter-cloud service 1110 updates the status to "Successful" and provides the infrastructure. Indications to these statuses can be provided to computing device 1100 (e.g., via the portal). Similarly, computing device 1100 can check the current status via the portal, where a status query request can be sent from CSPI_B 1150 to inter-cloud service 1110, and inter-cloud service 1110 will return a response with status information.

[0206] Subsequently, user input is received by cloud service 1110 from CSPI_B 1150 (where this input is provided at the portal) and corresponds to a request from computing device 1100 to create VM cluster resources. This request may indicate a subnet. Cloud service 1110 then performs a set of checks and begins provisioning the VM cluster. This provisioning will be further described in the following diagram. Cloud service 1110 sets the status to "Provisioning". Once created, cloud service 1110 updates the status to "Success". Here again, indications of these statuses can be provided to computing device 1100 (e.g., via the portal). Similarly, computing device 1100 can check the current status via the portal, where a status query request can be sent from CSPI_B 1150 to cloud service 1110, and cloud service 1110 will return a response with status information.

[0207] Figure 12 An exemplary control plane provisioning process 1260 according to some embodiments is depicted. In the example, the control plane provisioning process 1260 involves an inter-cloud service 1200, a control plane 1202 (e.g., an example of an in-cloud service), a customer's private cloud 1204 at a first CSP, a gateway 1206 (e.g., a DRG), a connectivity module 1208 (e.g., a connectivity module provided by a connectivity architecture and supporting connectivity protocols such as FastConnect), a cross-cloud service infrastructure 1210 at the first CSP, and a CSPI_B 1250 of a second CSP. The first CSP can provision cross-cloud services via the second CSP. Here, the control plane 1202 can execute part of the control plane provisioning process 1260 when triggered by the inter-cloud service 1200 to provision VM cluster resources. The inter-cloud service 1200 can make such a call to the control plane 1202 after receiving input from the CSPI_B 1250 (from ARM in Azure) in response to user input at the portal of the second CSP.

[0208] As described above, the inter-cloud service 1220 receives a request to create a VM cluster (e.g., an Exadata VM cluster) for cross-cloud services and passes this request, along with other information (e.g., a first identifier assigned by a first CSP and mapped to a second identifier assigned by a second CSP), to the control plane 1202. The control plane 1202 then retrieves details, such as about a subnet (e.g., including CIDR), from CSPI_B 1250 (e.g., from an ARM in Azure) and verifies that prerequisites (e.g., the subnet has been provisioned, the region of the second private cloud (e.g., a VNET in Azure) at the second CSP, etc.) are met. The control plane 1202 then creates a first private cloud (e.g., a VCN in OCI) at the first CSP in the customer lease (e.g., based on the first identifier) ​​and creates the subnet within that first private cloud. This subnet has the same CIDR as the subnet in the second private cloud.

[0209] Next, control plane 1202 creates and configures gateway 1206 (e.g., DRG) in the service lease and requests that gateway 1206 be attached to the first private cloud in the customer's lease. Control plane 1202 also configures routing information in gateway 1206 (e.g., by creating a DRG routing table for traffic between the two private clouds or a MeetMe router). Similarly, control plane 1202 also configures routing information in the first private cloud (e.g., by creating a VCN routing table for traffic to the DRG and VM cluster). Once the routing information has been created, control plane 1202 can notify inter-cloud service 1200 of success. In response, inter-cloud service 1200 can configure a network security group for the first private cloud and request the creation of a VM cluster. The VM cluster is then provisioned in the relevant subsite, thereby assigning it an IP address from the CIDR. DNS records corresponding to the IP addresses are also generated. Inter-cloud service 1200 can receive such DNS records and request that the first private network be attached to a second private network (e.g., attaching the VCN to the VNET).

[0210] Then, control plane 1202 calls the API of the second CSP, which allows IP addresses to be injected into the customer's subnet in the form of NICs. Each IP address can represent the IP of a VM cluster node. Control plane 1202 can register all the IP addresses that the VM cluster will have. The API call can include a device identifier (e.g., the GUID of the MeetMe router). This identifier can be based on a mapping of the GUID to a physical location (subsite). The call can also include a subnet resource identifier (e.g., the subnet of the private network in the customer's lease), an IP address (e.g., the IP address of the NIC being created, where the address is within the subnet range), and a resource name (the name of the NIC that will be visible to the user). The API can return a Virtual LAN identifier (VLAN ID), which can be used during virtual circuit creation. Then, control plane 1202 creates a virtual circuit that uses a connection to a router (e.g., to the MeetMe router) (e.g., a FastConnect connection) and provides DNS records that allow a private DNS zone to be added to the customer's second private network. At this point, the VM cluster is successfully created. Compute instances used for cross-cloud services (e.g., Exadata database instances) can then be hosted in that VM cluster.

[0211] resource providers

[0212] As discussed above, a first CSP can provide cloud-based services (e.g., database services, storage services, computing services, etc.) to its customers, and a second CSP can provide similar cloud-based services to its customers. The second CSP's customers can also be customers of the first CSP and may wish to access the cloud-based services provided by the first CSP through their leases within the cloud environment provided by the second CSP. Thus, the first CSP can provide cloud-based services as cross-cloud services to the second CSP's customers. Similarly, the second CSP can provide cloud-based services such as cross-cloud services to the first CSP's customers. At least one of the cross-cloud services provided by one CSP to another CSP's customers can be the same service as the cloud-based service provided by that CSP to its own customers. In this way, the platform-level experience of another CSP can be provided to the customers of that CSP from within that CSP's cloud environment. Furthermore, the customers of that CSP can be exposed to new features, releases, and resources of that other CSP without leaving that CSP's cloud environment.

[0213] For example, Oracle, as a CSP, provides in-cloud services to its own customers via OCI, and Microsoft, as a CSP, can provide similar in-cloud services to its own customers via Azure. Microsoft Azure customers can also be Oracle OCI customers and may wish to access in-cloud services provided by Oracle's OCI via their Microsoft Azure leases. Thus, Oracle's OCI can provide in-cloud services such as Oracle's Exadata database service to Microsoft Azure customers as cross-cloud services. Similarly, Microsoft Azure can provide in-cloud services such as Azure Synapse Analytics to Oracle OCI customers as cross-cloud services. At least one of the cross-cloud services provided by Oracle's OCI to Microsoft Azure customers can be the same service as the in-cloud service provided by Oracle's OCI to one of its own customers. For example, Oracle's OCI can provide Oracle's Exadata database service to both its own customers and Microsoft Azure customers through a Microsoft Azure environment. In this way, a platform-level experience of Oracle's OCI can be provided to Microsoft Azure customers from within Microsoft Azure. Furthermore, Microsoft Azure customers can be exposed to new features, releases, and resources of Oracle's OCI without leaving Microsoft Azure. While Oracle's OCI and Microsoft's Azure have been used as examples, the technologies described throughout this article are not limited to these CSPs and can be similarly applied to other CSPs, such as Google Cloud. TM and AWS ® .

[0214] To facilitate the provisioning of cross-cloud services, subsites can be provided within the corresponding CSPIs of different CSPs, and these subsites can be used to access cross-cloud services provided by other corresponding CSPs. For example, in the case of OCI and Azure described above, a subsite can be provided within the Azure CSPI, and this subsite can provide access to the Exadata database service provided by OCI from within the Azure cloud environment. Providing access to cross-cloud services using subsites can provide high-bandwidth access and reduced latency compared to accessing those cross-cloud services through a first CSP and / or other remote cloud environments. However, resources such as compute resources at each subsite may be limited. Therefore, it may be desirable to provide one or more management mechanisms to provision and manage the lifecycle of cross-cloud services from one or more CSPIs and / or cloud environments. The techniques described herein relate to resource management mechanisms for provisioning and managing the lifecycle of cross-cloud services provided by one or more CSPs and between one or more CSPs. The resource management mechanisms described herein are dynamic because the characteristics of the subsites, cloud environments, and / or the CSPs' CSPIs, as well as other factors, can be considered when provisioning and managing cross-cloud services.

[0215] Figure 13 An example architecture 1300 is described, including a resource management mechanism for provisioning and managing cross-cloud services across multiple cloud environments. For example... Figure 13 As shown, architecture 1300 may include a first cloud environment 1302 of a first CSP (e.g., Oracle's OCI) and a second cloud environment 1318 of a second CSP (e.g., Microsoft's Azure). This can be based on... Figures 6-9 The described distributed environment implements the first cloud environment 1302 and the second cloud environment 1318. The first cloud environment 1302 and the second cloud environment 1318 may include one or more private clouds (e.g., VCN in the case of Oracle's OCI and VNET in the case of Microsoft's Azure). Furthermore, it can be based on... Figures 10-12 The described experience and delivery process are used to deliver cross-cloud services between the first cloud environment 1302 and the second cloud environment 1318.

[0216] The first cloud environment 1302 can be configured to receive requests for cross-cloud services, assess the licensing status of such requests, generate instructions for provisioning such services in one or more other cloud environments (such as the second cloud environment 1318), deploy such services in the one or more other cloud environments, and manage the deployed services. In some implementations, cloud-based services 1310 of the first cloud environment 1302 can be configured to provide one or more of the cloud-based services 1310 (e.g., Exadata cloud-based services) to customers with leases in the second cloud environment 1318 as one or more cross-cloud services (e.g., Exadata cross-cloud services). The provisioning of cloud-based services supplied by the first cloud environment 1302 as cross-cloud services between the first cloud environment 1302 and the second cloud environment 1318 can be facilitated at least by the resource provider 1304 of the first cloud environment 1302. To provide cross-cloud services, resource provider 1304 can be configured to send a provisioning request for the requested cross-cloud service to the service control plane 1306 and network control plane 1308 of the first cloud environment 1302, and in response, the service control plane 1306 and network control plane 1308 can deploy the cloud-based service 1310 as a cross-cloud service to the second cloud environment 1318 (e.g., deploy the service data plane 1332 and network provider 1334 to the second cloud environment 1318).

[0217] In some implementations, the first cloud environment 1302 may include multiple parent regions, and the second cloud environment 1318 may include multiple sub-sites corresponding to the multiple parent regions. In some implementations, the service data plane 1332 of the second cloud environment 1318 may be used as and / or form one or more sub-sites of the corresponding parent region. In some implementations, each corresponding parent region of the first cloud environment 1302 may include a resource provider such as resource provider 1304, which, together with one or more sub-sites associated with the corresponding parent region, facilitates the provisioning and lifecycle management of one or more cross-cloud services. The one or more cross-cloud services may include one or more of the cloud-based services 1310 of the first cloud environment 1302. For example, resource provider 1304 may be a resource provider for a parent region in the first cloud environment 1302 and may provision and manage the lifecycle of the cloud-based services 1310 as cross-cloud services between the service control plane 1306 of the first cloud environment 1302 and the service data plane 1332 of the second cloud environment 1318. Sub-sites may be at least based on the above regarding Figure 7 It is implemented using the described physical system architecture.

[0218] In some implementations, the provisioning of cross-cloud services between the first cloud environment 1302 and the second cloud environment 1318 can be facilitated by the resource provider 1304 of the first cloud environment 1302 and the resource manager 1324 of the second cloud environment 1318. For example, the resource manager 1324 of the second cloud environment 1318 can send a cross-cloud service provisioning request to the resource provider 1304 of the first cloud environment 1302, and in response, the resource provider 1304 can work with the second cloud environment 1318 to facilitate the provisioning of cross-cloud services.

[0219] Similarly, managing the lifecycle of provisioned cross-cloud services between the first cloud environment 1302 and the second cloud environment 1318 can be facilitated by the resource provider 1304 of the first cloud environment 1302 and the resource manager 1324 of the second cloud environment 1318. For example, the resource manager 1324 of the second cloud environment 1318 can send a request to the resource provider 1304 for managing the lifecycle of the provisioned cross-cloud services (e.g., terminating a cross-cloud service request), and in response, the resource provider 1304 can work with the second cloud environment 1318 to facilitate lifecycle management functionality for the cross-cloud services. In some implementations, to facilitate provisioning and lifecycle management, the resource manager 1324 can be configured to communicate with the resource provider 1304 (e.g., using the API of the first cloud environment 1302 exposed by the resource provider 1304 to the resource manager 1324).

[0220] In some implementations, customers of the second cloud environment 1318 and / or the second CSP, who wish to provide cross-cloud services from within the second cloud environment 1318 and / or manage cross-cloud services provided by the second cloud environment 1318, may initiate a request 1336 to do so. Customers may initiate the request 1336 via portal 1320 of the second cloud environment 1318. In some implementations, portal 1320 may include one or more graphical user interfaces (GUIs) that can be accessed via client devices such as computers (e.g., via applications, operating systems, and / or software programs running on the client devices). The one or more GUIs, or portions thereof, may be generated, populated, and / or otherwise provisioned by resource manager 1324 of the second cloud environment 1318. Customers of the second cloud environment 1318 may access portal 1320 to manipulate the one or more GUIs and / or interact with the one or more GUIs to initiate the request 1336 and perform other functions, such as managing their rentals within the second cloud environment 1318.

[0221] In some implementations, the one or more graphical user interfaces (GUIs) or portions thereof may be generated, populated, and / or otherwise provisioned by the resource provider 1304 of the first cloud environment 1302. The one or more GUIs or portions thereof may be provided to and / or claimed to the portal 1320 using the blade 1322 of the portal 1320. The blade 1322 may be used as and / or act as an extension, plug-in, add-on, etc., of the portal 1320. Customers of both the first cloud environment 1302 and the second cloud environment 1318 may access the portal 1320 to manipulate one or more GUIs and / or interact with one or more GUIs to initiate requests 1336 and perform other functions, such as managing their rentals within the first cloud environment 1302 and the second cloud environment 1318.

[0222] In some implementations, a request for provisioning cross-cloud services received via portal 1320 can be routed to resource manager 1324 of a second cloud environment 1318, which in turn can route request 1336 to resource provider 1304 of a first cloud environment 1302 (e.g., via a first set of APIs of the first cloud environment 1302 exposed within resource manager 1324). Alternatively, a request received via portal 1320 to manage the lifecycle of a provisioned cross-cloud service (e.g., viewing analytics, consumption, costs, logs, etc.) can be routed to console 1314 of the first cloud environment 1302, which in turn can route request 1336 within the first cloud environment 1302 (e.g., via a second set of APIs exposed within the first cloud environment 1302). For example, console 1314 can be configured to route request 1336 to analytics service 1316 of the first cloud environment 1302 for viewing analytics, consumption, costs, logs, etc., related to the provisioned cross-cloud service. In some implementations, corresponding clients of the second cloud environment 1318 can be assigned corresponding identifiers, such that each request 1336 initiated by a corresponding client of the second cloud environment 1318 can be associated with the identifier used for that corresponding client. In this way, the resource manager 1324 can control and manage access to the portal and request initiation based on the roles and / or permissions associated with each client identifier.

[0223] To facilitate the provisioning of cross-cloud services and the lifecycle management of already provisioned cross-cloud services, resource provider 1304 can link to resource manager 1324 and resource provider-as-a-service (RPaaS) 1328 in the second cloud environment 1318. Linking resource provider 1304 to the second cloud environment 1318 enables resource provider 1304, resource manager 1324, and RPaaS 1328 to coordinate resources and operations. Resource provider 1304 can have an identity associated with the second cloud environment 1318. This identity can be configured to replicate the identity that resource provider 1304 has in the first cloud environment 1302. To facilitate the linking, resource provider 1304 can provide configuration 1326 to resource manager 1324 and configuration 1330 to RPaaS 1328. Configuration 1326 and configuration 1330 can include an identifier for resource provider 1304 and can define the location and / or API specifications and connection endpoints of in-cloud services associated with resource provider 1304.

[0224] Resource provider 1304 can be configured to supply cross-cloud services and / or manage the lifecycle of supplied cross-cloud services based on operations performed by multi-cloud platform 1312 of first cloud environment 1302. Multi-cloud platform 1312 can be configured to perform operations common to linking and integrating first cloud environment 1302 into second cloud environment 1318 and other CSPs. For example, multi-cloud platform 1312 can be configured to link a customer's account with the second CSP to a customer's account with the first CSP, publish observation information collected from first cloud environment 1302 and / or second cloud environment 1318, generate issuance tokens for accessing other cloud environments for the customer, etc. Furthermore, multi-cloud platform 1312 can be configured to create, define, supply, and / or otherwise implement contracts between resource provider 1304, resource manager 1324, and RPaaS 1328. The contract can identify resources supported by resource provider 1304, resource manager 1324, and RPaaS 1328, and / or operations to be performed by resource provider 1304, resource manager 1324, and RPaaS 1328. In some implementations, the contract can allow resource provider 1304, resource manager 1324, and RPaaS 1328 to operate on the same lease within the first cloud environment 1302. For example, the contract can define provisioning and / or lifecycle management events to be sent from resource manager 1324 and / or RPaaS 1328 when such events occur, wherein resource provider 1304 can be configured to asynchronously perform provisioning and / or lifecycle management operations based on the receipt of such events and / or changes in status.

[0225] Multi-cloud platform 1312 can also be configured to perform common cloud management operations, including but not limited to: (i) mapping subscriptions and leases of the second cloud environment 1318 to subscriptions and leases of the first cloud environment 1302; (ii) generating and managing policy claims that govern leases in the respective cloud environments (e.g., claims that facilitate the operation of multi-cloud platform 1312 and resource provider 1304 in the same lease); (iii) generating and managing access tokens that facilitate communication and / or cross-cloud access between the respective cloud environments; and / or (iv) mapping observability information of the first cloud environment 1302 to the second cloud environment 1318 (e.g., writing events to the second cloud environment 1318 when a backup is completed on the first cloud environment 1302, writing resource logs of the first cloud environment 1302 to the second cloud environment 1318, etc.). In this way, the first cloud environment 1302 and the second cloud environment 1318 can avoid overlapping operations and resources, which in turn can improve efficiency.

[0226] In some implementations, upon receiving a request 1336 to provision cross-cloud services, resource provider 1304 may be configured to map request 1336 to an identifier in first cloud environment 1302 and pass the request all the way to service control plane 1306. Service control plane 1306 may be configured to perform two main processes: the first process is to provision the relevant resources in first cloud environment 1302; and the second process is to connect these resources to the customer's lease in second cloud environment 1318 (e.g., a VNET in second cloud environment 1318). Under the first process, service control plane 1306 creates a VCN for the customer in first cloud environment 1302 and creates one or more subnets within that VCN. In some implementations, the VCN may act as a shadow lease for the customer's lease in second cloud environment 1318. One or more subnets within the VCN and one or more subnets in the VNET may use the same CIDR. Service control plane 1306 also creates a DRG in the first cloud environment 1302, attaches the DRG to the customer's VCN, and configures routing information for the DRG and the VCN (e.g., to interconnect the two resources). Service control plane 1306 also provides a VM cluster in service data plane 1332. The IP addresses(s) of this VM cluster come from the CIDR and are mapped to corresponding DNS records. In the second process, service control plane 1306 registers these IP addresses(s)(s) with the second cloud environment 1318, creates a virtual circuit between the DRG and network provider 1334, and sends DNS records to enable the establishment of a private DNS zone in the second cloud environment 1318.

[0227] Additionally or alternatively, upon receiving a request 1336 for providing cross-cloud services, resource provider 1304 is configured to: (i) map an identifier assigned to a customer by a second CSP to an identifier assigned to a customer by a first CSP; (ii) obtain the identity of resource provider 1304 associated with request 1336 (i.e., the second cloud environment 1318 from which request 1336 originates); and (iii) convert the format of request 1336 from the format of the second cloud environment 1318 to the format of the first cloud environment 1302, and route the formatter request along with the mapped identifier to the service control plane 1306 and the network. Control plane 1308; (iv) establishing network connectivity prerequisites for network connectivity between the first cloud environment 1302 and the second cloud environment 1318 (e.g., establishing DRGs, VCNs, and subnets for VMs and network providers 1334 connected to the service data plane 1332 of the second cloud environment 1318); (v) establishing network connectivity between the network control plane 1308 and the network provider 1334 based on the network connectivity prerequisites (e.g., linking delegated subnets of the second cloud environment 1318 to the VCN of the first cloud environment 1302 and configuring DNS entries in the second cloud environment 1318). Furthermore, once cross-cloud services are provisioned, resource provider 1304 can be configured to persist metadata (e.g., mapping between identifiers for the second cloud environment 1318 and the first cloud environment 1302) between the first cloud environment 1302 and the second cloud environment 1318, and act as a thin adapter layer that accepts requests formatted for the second cloud environment 1318 and already authenticated by resource manager 1324 (e.g., requests that manage the lifecycle of the provisioned cross-cloud services), transforms them into requests formatted for the first cloud environment 1302, and delegates the transformed requests to service control plane 1306.

[0228] To enhance monitoring of resources for cross-cloud services provisioned by Service Control Plane 1306 in Second Cloud Environment 1318, and to manage the health and performance of these resources, customers may want to access observability data (e.g., logs, metrics, events) as if it were natively accessible within Second Cloud Environment 1318. For example, in the case of OCI and Azure, Azure customers may want to access observability data generated by their use of OCI resources provisioned in Service Data Plane 1332 in a manner that matches and / or substantially matches their native experience and interaction with observability data generated by Azure native infrastructure resources. Azure customers can access observability data through portal 1320 and may want to view observability data generated by their native Azure resources alongside observability data generated by cross-cloud OCI resources in a graphical user interface provided by portal 1320.

[0229] In some implementations, observability data may be obtained or collected from within a first cloud environment 1302 and provided to a second cloud environment 1318. Obtaining or collecting observable data may include deploying an observability control plane 1338 and an observability data plane 1340 within the first cloud environment 1302 when initiating a cross-cloud service deployment. The observability control plane 1338 may provision observability resources within the observability data plane 1340 to allow data flow from relevant cross-cloud resources. In some examples, the first CSP and the second CSP may implement different models or patterns for observable data, which may make it difficult to view observable data associated with services provided by the first CSP in the portal 1320 used by the second CSP. To address these and other challenges, observable data collected in the first cloud environment may be transformed into a model, pattern, or format understood by the second CSP before being transferred to the observable data repository 1342 within the second cloud environment 1318.

[0230] In some implementations, the service control plane 1306 may be configured to initiate the provisioning of resources for collecting, acquiring, and / or receiving observability data. Observability may include monitoring, managing, and maintaining the data quality and performance of cloud services. As an example, observability data may include metrics associated with a database and events such as database creation and updates.

[0231] After fulfilling the request to provision a cross-cloud service to the second cloud environment 1318, the service control plane 1306 sends a request to the observability control plane 1338 to provide observability resources for the provisioned cross-cloud service in the observability data plane 1340. As an example, the provisioned cross-cloud service may be a VM cluster provided in a subsite of the second cloud environment 1332, and the service control plane 1306 may invoke the observability control plane 1338 to provide resources to enable observable data flow from the VM cluster to the observability data plane 1338. Observable data may include events and metrics related to services within the first private cloud associated with the customer (e.g., the Exadata service within a VCN). In some implementations, observable data is collected or obtained from cross-cloud resources provided in the service data plane 1332 of the second cloud environment 1318 and transmitted to the observability data plane 1340.

[0232] When provisioning cross-cloud services, Service Control Plane 1306 may retain customer and resource identifier information, including information about the first and second private clouds associated with the customer (e.g., the customer's VCN and VNET). Service Control Plane 1306 may provide the identifier information to the Observability Control Plane when sending a request to provision observable resources. Observability Control Plane 1338 stores the identifier information in one or more data repositories contained within the Observability Control Plane. The resource and customer identifier information can be retrieved when observable data is sent to the second cloud environment 1318 for customer access. In some implementations, Observability Control Plane 1338 exposes an internal API with endpoints to create, retrieve, and delete observable resources. When cross-cloud services have been provisioned, Service Control Plane 1306 may use the resource and customer identifier information to invoke the internal API. When Service Control Plane 1306 invokes Observability Control Plane 1338, Service Control Plane 1306 may provide a resource context that is scoped to a specific customer lease.

[0233] Certain resources that are not related to a specific customer or resource can be deployed in the observability data plane 1340 service lease before being initiated by the observability control plane 1338. As an example, observability metric exporter functionality, observability log exporter functionality, stream and / or service connectors can be deployed in the observability data plane 1340 and can be client-, customer-, and / or resource-agnostic.

[0234] Upon receiving a request from Service Control Plane 1306 to provision observability resources, Observability Control Plane 1338 can provision service- and customer-specific resources in the service lease of Data Plane 1340, including but not limited to event-managed rules for exposing events and metric service connectors for receiving metrics associated with cross-cloud services. Each new cross-cloud service can be associated with a new event-managed rule and / or metric service connector. When linking a customer's first and second private clouds (e.g., the customer's VCN and VNET), Service Control Plane 1306 can create policies in the customer's lease to allow reading events and metrics.

[0235] The observability data plane 1340 can receive observable data from one or more observable resources (e.g., service connectors, streams) supplied by the observability control plane 1338. The observability data plane 1340 can transform the observable data it receives into a schema or model implemented by the second CSP in the second cloud environment 1318. The observability data repository 1342, located in the second cloud environment 1318, can store observable data for the second CSP's clients. The observability data plane 1340 can provide the observable data to the observability data repository 1342 after transforming it into a schema associated with the second CSP. The observability data repository 1342 can provide the observable data received from the observability data plane 1340 to the resource manager 1324, allowing users to view the observable data in the portal 1320.

[0236] Observability

[0237] Figure 14 This is a simplified block diagram illustrating a data flow environment 1400 used to provide observable data from a first cloud environment to a second cloud environment. (See diagram for example.) Figure 14 As shown, the data flow environment 1400 includes a first cloud environment 1402 and a second cloud environment 1404. The first cloud environment 1402 may include a service control plane 1426 (e.g., Figure 13 Service control plane 1306), observability control plane 1408 (e.g., Figure 13 The observability control plane 1338 and the observability data plane 1406 service leases (e.g., Figure 13 The observability data plane 1340. The observability control plane 1408 may supply certain observability resources (e.g., event management rules 1414 and metric service connector 1424) for each cross-cloud service resource after receiving a request from the service control plane 1426. Other observability resources deployed in the observability data plane may be pre-created and may be client- and service-agnostic (e.g., streams 1416, event service connector 1418, log exporter function 1420, metric exporter function 1424).

[0238] The observability control plane 1408 may include separate planes for different types of observability data. As an example, the control plane may include an event control plane 1410 for events and a monitoring control plane 1412 for observability metrics.

[0239] Upon receiving a provisioning call from the service control plane 1426, the observability control plane can provision resources in the observability data plane 1406 to initiate a data flow from resources deployed in the second cloud environment (e.g., a VM cluster provisioned in a subsite in the second cloud environment 1404).

[0240] When provisioning cross-cloud resources, the event control plane 1410 can create an event management rule 1414 upon receiving a request from the service control plane. The event management rule 1414 allows events to flow from the cross-cloud resource. In some implementations, the event management rule 1414 includes conditions for exposing certain event types and client and / or resource identifier information. The event management rule 1414 may include conditions for exposing certain types of events. As an example, events for an autonomous database service may include, but are not limited to, access control updates, database creation, database updates, and database termination. As part of the connection, the conditions may include identifier information about the resource or compartment. The event management rule 1414 includes cross-cloud resource information containing resource identifiers to ensure a response based on events provisioned for the correct corresponding cross-cloud resource. The event management rule 1414 is associated with a flow 1416, which acts as the target to which events flow from the provisioned cross-cloud service. The event service connector 1418 polls the flow 1416 for newly received observable data related to events from the cross-cloud service. After recognizing that new data has been received, the event service connector 1418 invokes the log exporter function 1420 to transfer the observable data as an event log to the second cloud environment 1404.

[0241] The monitoring control plane 1412 can create a metric service connector 1422 upon receiving a request to provision observability resources from the service control plane 1426. The monitoring service connector 1422 transfers metric data points from a monitoring service (e.g., a VM cluster or other cross-cloud service provisioned in the second cloud environment 1404) to a target. A metric exporter function 1424 is defined as the target for the metric service connector 1422 to transfer metric data points to the second cloud environment 1404. In some examples, the metric namespace is provided to the metric service connector 1422 as an additional attribute and can vary based on the type of cross-cloud service.

[0242] Exporter functions (e.g., log exporter function 1420, metric exporter function 1424) can be serverless computing services that can be created and run without managing any infrastructure, and can be configured to transfer data to a second cloud environment 1404. Exporter functions deployed in the observability data plane 1406 receive data payloads from one or more service connectors (e.g., event service connector 1418, metric service connector 1422). The exporter functions group the data payloads by resource IDs (e.g., OCIDs) associated with the first cloud environment and use these resource IDs to invoke the observability control plane 1408 to retrieve details about cross-cloud resources, the second cloud provider, and client identifiers (e.g., Azure identifiers) associated with the data payloads. In some examples, the exporter functions can use API endpoints and retrieve cross-cloud resource details from the observability control plane 1408 by providing the resource ID as input.

[0243] The exporter function can then transform data points into a model that is understood or implemented by the second CSP. The second CSP can implement and store observability metrics using a schema that does not match the schema implemented by the first CSP. In some examples, the schema implemented by the second CSP can be retrieved from a manifest file provided by the second CSP. The manifest file can specify information about the schema required for the observability data intended to be sent to the second CSP. As an example, the manifest file can contain information such as multi-dimensional quantity accounts required to transfer observability data to the second CSP, metric specifications (e.g., a list of metrics being emitted by the resource), and log specifications. Dimensions can include, but are not limited to, resource ID, resource type, resource group name, subscription ID, or any combination thereof. In some examples, the first CSP can support one or more types of observable data that are not supported by the second CSP and are not included in the manifest file. In such an example, exporter functions deployed in the observability data plane 1406 (e.g., log exporter function 1420, metric exporter function 1424) can identify observability data types that are not supported by the second CSP and remove unsupported observability data types when transferring observability data to the second cloud environment 1404.

[0244] After transforming the data into a pattern or model implemented by the second CSP, the observability data plane 1406 sends the transformed data to another cloud provider.

[0245] In some instances, the control plane or other cloud providers may become unavailable. To ensure that incoming events from the service connector are not lost, events are sent to a retry stream and will be retried several times. After several retry attempts, the event may be dropped, and an alert indicating that the event is inaccessible may be triggered.

[0246] Figure 15 This is a simplified block diagram illustrating an exemplary observability data delivery environment 1500 for using an agent to provide observability data from a first cloud environment to a second cloud environment. In some examples, the backend observability storage 1506 located in the second cloud environment 1504 may only be able to interact with an agent that typically runs on the same machine as the application or service. In some examples, the configuration within the first cloud service provider may not allow the deployment of agents on the same machine. In such instances, one or more agents may be hosted on separate exporter pods 1512 within observability data planes 1502 (e.g., observability data planes 1340, 1406) in the first cloud environment to interface with the observability repository 1606 in the second cloud environment 1504.

[0247] like Figure 14 As described, the observability data plane 1502 may include fed data streams for measuring monitoring and events, which provide data payloads to log exporter function 1508 (e.g., log exporter function 1420) and metric exporter function 1510 (e.g., metric exporter function 1424). In some implementations, observability data supported by a first CSP and sent from the first CSP to a second CSP may include data types other than metrics and events, and the observability data plane 1502 may include additional data streams for related observability data.

[0248] In some examples, the second CSP can implement protocols for communication between observability resources, which the observability data plane 1502 may need to follow to transmit observability data to the second cloud environment 1504. As a specific example, the second CSP can conform to the OpenTelemetry protocol for encoding, transporting, and delivering telemetry data, and the observability data processed by the log exporter function 1508 and the metric exporter function 1510 can be transformed into a model conforming to the OpenTelemetry protocol. The exporter functions can use a software development kit (SDK) to transform the payload into a model conforming to this communication protocol.

[0249] Collectors can be deployed between exporter functions and agents to ensure secure communication. Log exporter function 1508 can transfer event-related observable data to log collector 1514, and metric exporter function 1510 can transfer metric-related observable data to metric collector 1518. Log collector 1514 can transfer transformed observable data to metric agent 1516, and metric collector 1518 can transfer transformed observable data to log agent 1520. Collectors can be deployed alongside agents within exporter pod 1512 for local communication via unencrypted loopback.

[0250] The agent sends the transformed observability data to the observability data repository 1506 located in the second cloud environment 1504. This communication can be performed via mTLS, and each agent can be provided with a certificate as an input parameter to establish a protected connection with the observability data repository 1506. The observability data repository 1506 may require accounts to store the observability data. As an example, the observability data repository 1506 may require multidimensional accounts as specified in the manifest file to store the observability data. Multidimensional accounts can be provided to the agents as input to enable the transfer of observability data. The observability data repository 1506 can determine the resource type associated with the incoming observability data based on the information corresponding to the multidimensional accounts.

[0251] Customer 1524, belonging to both the first and second CSPs, can log in to portal 1522, provided by the second CSP, to view observability data associated with a private cloud located in a second cloud environment (e.g., VNET in the case of Microsoft Azure). Portal 1522 can retrieve observability data associated with customer 1524 and its private cloud from observability data repository 1506. Portal 1522 can display observability data for services associated with one or more private clouds associated with customer 1524, including cross-cloud services linked to the first private cloud located in the first cloud environment. As a specific example, Azure customers can monitor and interact with observable data associated with and related to services natively provided by Azure and services provided by OCI and linked to VNET.

[0252] Explanatory methods

[0253] Figure 16 The illustration shows an example processing 1600 used to provide observable data for cross-cloud services across multiple cloud environments. Figure 16 The processes described herein can be implemented using software (e.g., code, instructions, programs), hardware, or a combination thereof, executed by one or more processing units (e.g., one or more processors, cores) throughout the corresponding system described herein. The software can be stored on a non-transitory storage medium (e.g., a memory device). Although Figure 16 The methods presented depict various processing steps that occur in a specific sequence or order, but this is not intended to be limiting. In some alternative implementations, these steps may be performed in parallel and / or in different orders. In some implementations, such as in Figures 6-13 In the embodiments depicted, Figure 16 The processing described herein can be performed by hardware and / or software components of a cloud environment such as a first cloud environment 1302 and / or a second cloud environment 1318.

[0254] At box 1602, a first identifier associated with the customer and a first private cloud in the first cloud environment, and a second identifier associated with the customer and a second private cloud in the second cloud environment, are identified. As an example, the first identifier may be an OCID, and the second identifier may be an Azure identifier. The customer may be a customer of both the first and second cloud environments. In some examples, when provisioning resources for cross-cloud services from the first cloud environment to the second cloud environment, the service control plane in the first cloud environment identifies the first and second identifiers.

[0255] At box 1604, the association between a first identifier, a second identifier, and a resource identifier associated with a cloud service is stored in the observability control plane within the first cloud environment. The observability control plane can receive the first identifier, the second identifier, and the resource identifier from the service control plane, as well as requests to supply observable resources in the observability data plane. When a new observable resource is supplied in the observability data plane, the observability control plane can store the first identifier, the second identifier, and the resource identifier associated with the cloud service in a data repository.

[0256] At box 1606, one or more targets are created in the observability data plane, configured to receive first observable data. These targets may include a metric service connector for receiving metrics related to cloud services and streams associated with event management rules for specified event types. The observability data plane may also include observability resources, including but not limited to event service connectors, log exporter functionality, and metric exporter functionality. In some implementations, the first observable data may be received from cloud services provisioned from the service data plane in a second cloud environment.

[0257] At box 1608, first observability data is obtained from the first cloud environment. The first observability data may include one or more metrics and / or one or more events associated with the execution of the cloud service. The first observability data may be obtained at the one or more targets provided in the observability data plane of the first cloud environment.

[0258] At box 1610, a resource identifier associated with the first observability data is identified. This resource identifier may be included in the data payload of the observability data received at the observability data plane. In some implementations, the resource identifier may be identified by an exporter function invoked by a service connector in the observability data plane.

[0259] At box 1612, customer, second cloud environment, and one or more resource details are identified based on resource identifiers and associations stored in the observability control plane. Components within the observability data plane (e.g., exporter functions) can request information about the customer, second cloud environment, and resource details from the observability control plane by providing resource identifiers. This information about the customer, second cloud environment, and resource details can be used by the exporter functions to determine the method for processing the first observable data.

[0260] At box 1614, first observable data is processed by a first cloud environment to generate second observable data. In some embodiments, the second observable data is compatible with the observable data format of the second cloud environment. In some embodiments, processing the first observable data to generate the second observable data may include identifying a pattern associated with the second cloud environment. Processing the first observable data into the second observable data may also include converting the format of the first observable data to the observable data format of the second cloud environment based on the pattern. In some examples, the pattern is derived from a manifest file retrieved from the second cloud environment. The first observable data may be processed into the second observable data by an exporter function associated with the observable data type in the observable data plane.

[0261] At box 1616, second observability data is provided from the first cloud environment to the second cloud environment. The second observability data may be provided by an exporter function in the observability data plane associated with the observability data type. As an example, a log exporter function may provide event-related observability data, and a metric exporter function may provide metric-related observability data. In some examples, providing the second observability data to the second cloud environment also includes providing the second observability data from the observability data plane within the first cloud environment to an agent configured to communicate with an observability data repository within the second cloud environment. The second cloud environment may implement standards for sending and disposing of observability data. The agent may be configured to comply with these standards and provide the second observability data to the observability data repository as if the observability data were natively provided within the second cloud environment.

[0262] Examples of cloud infrastructure

[0263] As noted above, 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.

[0264] In some cases, 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.

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

[0266] 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 processing of server preparation (e.g., installation 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 processing (OS), middleware, and / or application deployment (e.g., on self-service virtual machines, etc., which can be started on demand).

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

[0268] In some cases, IaaS provisioning presents two distinct challenges. First, there's the initial challenge of provisioning a set of initial infrastructure 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 cases, once the topology is defined, workflows for creating and / or managing the different components described in the configuration files can be generated.

[0269] In some examples, the infrastructure can have many interconnected elements. For example, there may be 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. In some examples, one or more inbound / outbound traffic group rules may also be provided to define how inbound / outbound traffic to the network is structured, along with one or more virtual machines (VMs). Other infrastructure elements, such as load balancers, databases, etc., may also be provided. The infrastructure can evolve incrementally as more and / or additional infrastructure elements are expected and / or added.

[0270] In some cases, continuous deployment techniques can be employed 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 intend 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 established. In some cases, 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.

[0271] Figure 17 This is a block diagram 1700 illustrating an example style of IaaS architecture according to at least one embodiment. Service operator 1702 may be communicatively coupled to a secure host lease 1704, which may include a VCN 1706 and a secure host subnet 1708. In some examples, service operator 1702 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 1706 and / or the internet.

[0272] VCN 1706 may include a local peering gateway (LPG) 1710, which may be communicatively coupled to SSH VCN 1712 via LPG 1710 contained in a Secure Shell (SSH) VCN 1712. SSH VCN 1712 may include an SSH subnet 1714, and SSH VCN 1712 may be communicatively coupled to control plane VCN 1716 via LPG 1710 contained in control plane VCN 1716. Furthermore, SSH VCN 1712 may be communicatively coupled to data plane VCN 1718 via LPG 1710. Control plane VCN 1716 and data plane VCN 1718 may be contained in a service lease 1719 that may be owned and / or operated by an IaaS provider.

[0273] The control plane VCN 1716 may include a control plane demilitarized zone (DMZ) layer 1720 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 assume limited liability and help control vulnerabilities. Furthermore, the DMZ layer 1720 may include one or more load balancer (LB) subnets 1722, a control plane application layer 1724 that may include one or more application subnets 1726, and a control plane data layer 1728 that may include one or more database (DB) subnets 1730 (e.g., one or more front-end DB subnets and / or one or more back-end DB subnets). One or more LB subnets 1722 contained in the control plane DMZ layer 1720 may be communicatively coupled to one or more application subnets 1726 contained in the control plane application layer 1724 and an Internet gateway 1734 that may be contained in the control plane VCN 1716. The application subnets 1726 may be communicatively coupled to one or more DB subnets 1730 contained in the control plane data layer 1728, as well as a service gateway 1736 and a Network Address Translation (NAT) gateway 1738. The control plane VCN 1716 may include the service gateway 1736 and the NAT gateway 1738.

[0274] The control plane VCN 1716 may include a data plane mirror application layer 1740, which may include one or more application subnets 1726. The one or more application subnets 1726 included in the data plane mirror application layer 1740 may include a virtual network interface controller (VNIC) 1742 capable of executing a compute instance 1744. The compute instance 1744 may communicatively couple the one or more application subnets 1726 of the data plane mirror application layer 1740 to the one or more application subnets 1726 that may be included in the data plane application layer 1746.

[0275] Data plane VCN 1718 may include data plane application layer 1746, data plane DMZ layer 1748, and data plane data layer 1750. Data plane DMZ layer 1748 may include one or more LB subnets 1722 communicatively coupled to one or more application subnets 1726 of data plane application layer 1746 and Internet gateway 1734 of data plane VCN 1718. One or more application subnets 1726 may be communicatively coupled to service gateway 1736 and NAT gateway 1738 of data plane VCN 1718. Data plane data layer 1750 may also include one or more DB subnets 1730 communicatively coupled to one or more application subnets 1726 of data plane application layer 1746.

[0276] The Internet gateway 1734 of the control plane VCN 1716 and data plane VCN 1718 can be communicatively coupled to the metadata management service 1752, which can be communicatively coupled to the public Internet 1754. The public Internet 1754 can be communicatively coupled to the NAT gateway 1738 of the control plane VCN 1716 and data plane VCN 1718. The service gateway 1736 of the control plane VCN 1716 and data plane VCN 1718 can be communicatively coupled to the cloud service 1756.

[0277] In some examples, the service gateway 1736 of the control plane VCN 1716 or data plane VCN 1718 can make application programming interface (API) calls to the cloud service 1756 without traversing the public internet 1754. API calls from the service gateway 1736 to the cloud service 1756 can be unidirectional: the service gateway 1736 can make API calls to the cloud service 1756, and the cloud service 1756 can send requested data to the service gateway 1736. However, the cloud service 1756 may not initiate API calls to the service gateway 1736.

[0278] In some examples, secure host lease 1704 can be directly connected to service lease 1719, which would otherwise be isolated. Secure host subnet 1708 can communicate with SSH subnet 1714 via LPG 1710, which enables bidirectional communication between otherwise isolated systems. Connecting secure host subnet 1708 to SSH subnet 1714 allows secure host subnet 1708 to access other entities within service lease 1719.

[0279] Control plane VCN 1716 allows users of service lease 1719 to set up or otherwise provision desired resources. Desired resources provisioned in control plane VCN 1716 can be deployed or otherwise used in data plane VCN 1718. In some examples, control plane VCN 1716 can be isolated from data plane VCN 1718, and the data plane mirror application layer 1740 of control plane VCN 1716 can communicate with the data plane application layer 1746 of data plane VCN 1718 via VNIC 1742, which can be included in both the data plane mirror application layer 1740 and the data plane application layer 1746.

[0280] 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 1754, which can transmit requests to the metadata management service 1752. The metadata management service 1752 can transmit requests to the control plane VCN 1716 via internet gateway 1734. Requests can be received by one or more LB subnets 1722 contained in the control plane DMZ layer 1720. The LB subnets 1722 can determine that the request is valid, and in response to this determination, they can transmit the request to one or more application subnets 1726 contained in the control plane application layer 1724. If the request is validated and requires a call to the public internet 1754, the call to the public internet 1754 can be transmitted to a NAT gateway 1738 that can make calls to the public internet 1754. The request may expect stored metadata to be stored in one or more DB subnets 1730.

[0281] In some examples, the data plane mirroring application layer 1740 can facilitate direct communication between the control plane VCN 1716 and the data plane VCN 1718. For example, it might be desirable to apply configuration changes, updates, or other appropriate modifications to resources contained in the data plane VCN 1718. Through VNIC 1742, the control plane VCN 1716 can communicate directly with the resources contained in the data plane VCN 1718, and thus can perform configuration changes, updates, or other appropriate modifications.

[0282] In some embodiments, the control plane VCN 1716 and data plane VCN 1718 may be included in service lease 1719. In this case, the system's users or customers may not own or operate the control plane VCN 1716 or data plane VCN 1718. Alternatively, the IaaS provider may own or operate both the control plane VCN 1716 and data plane VCN 1718, and both planes may be included in service lease 1719. This embodiment enables the isolation of networks that might prevent users or customers from interacting with resources from other users or customers. Furthermore, this embodiment allows users or customers of the system to privately store databases without relying on the public internet 1754, which may not have the desired level of threat prevention for storage.

[0283] In other embodiments, one or more LB subnets 1722 included in the control plane VCN 1716 may be configured to receive signals from the service gateway 1736. In this embodiment, the control plane VCN 1716 and the data plane VCN 1718 may be configured to be invoked by the IaaS provider's customers without invoking the public internet 1754. 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 a service lease 1719, which may be isolated from the public internet 1754.

[0284] Figure 18 This is a block diagram 1800 illustrating another example style of IaaS architecture according to at least one embodiment. Service operator 1802 (e.g., Figure 17 The service provider 1702) can communicatively couple to the secure host lease 1804 (e.g., Figure 17 The secure host lease 1704 may include a VCN 1806 (e.g., Figure 17 VCN1706) and Security Host Subnet 1808 (e.g., Figure 17 The secure host subnet 1708). VCN 1806 may include a local peering gateway (LPG) 1810 (e.g., Figure 17 The LPG 1710), which can be contained within the Secure Shell (SSH) VCN 1812 (e.g., Figure 17 The LPG 1810 in SSH VCN 1712 is communicatively coupled to SSH VCN 1812. SSH VCN 1812 may include SSH subnet 1814 (e.g., Figure 17 SSH subnet 1714), and SSH VCN 1812 can be communicatively coupled to control plane VCN 1816 via LPG 1810 contained in control plane VCN 1816 (e.g., Figure 17 Control plane VCN 1716). Control plane VCN 1816 may be included in service lease 1819 (e.g., Figure 17 In the service lease 1719), and the data plane VCN 1818 (e.g., Figure 17 The data plane VCN 1718 may be included in a customer lease 1821 that may be owned or operated by the system’s users or customers.

[0285] The control plane VCN 1816 may include one or more LB subnets 1822 (e.g., Figure 17 The control plane DMZ layer 1820 of (one or more) LB subnets 1722) (e.g., Figure 17 The control plane DMZ layer 1720 may contain one or more application subnets 1826 (e.g., Figure 17 The control plane application layer 1824 of (one or more) application subnets 1726 (e.g., Figure 17 The control plane application layer 1724) may contain one or more database (DB) subnets 1830 (e.g., similar to...). Figure 17 The control plane data layer 1828 of (one or more) DB subnets 1730 (e.g., Figure 17 The control plane data layer 1728). One or more LB subnets 1822 contained in the control plane DMZ layer 1820 can be communicatively coupled to one or more application subnets 1826 contained in the control plane application layer 1824 and an Internet gateway 1834 that can be contained in the control plane VCN 1816 (e.g., Figure 17 Internet gateway 1734), and application subnet(s) 1826 can communicatively couple to DB subnet(s) 1830 contained in control plane data layer 1828 and service gateway 1836 (e.g., Figure 17 Service gateway 1736) and Network Address Translation (NAT) gateway 1838 (e.g., Figure 17 (NAT gateway 1738). The control plane VCN 1816 may include the service gateway 1836 and the NAT gateway 1838.

[0286] The control plane VCN 1816 may include a data plane mirror of the application layer 1840, which may contain one or more application subnets 1826 (e.g., Figure 17 The data plane mirror application layer 1740). One or more application subnets 1826 contained in the data plane mirror application layer 1840 may include computational instances 1844 (e.g., similar to...). Figure 17 The virtual network interface controller (VNIC) 1842 (e.g., the VNIC of 1742) of the computing instance 1744. The computing instance 1844 may facilitate the mirroring of the application subnet(s) 1826 of the application layer 1840 in the data plane and may be included in the application layer 1846 in the data plane (e.g., Figure 17 Communication between one or more application subnets 1826 in the data plane application layer 1746 via VNIC 1842 contained in the data plane mirror application layer 1840 and VNIC 1842 contained in the data plane application layer 1846.

[0287] The Internet gateway 1834, included in the control plane VCN 1816, can be communicatively coupled to the metadata management service 1852 (e.g., Figure 17 Metadata management service 1752), which can communicatively couple to the public Internet 1854 (e.g., Figure 17 The public internet 1754. The public internet 1854 can communicatively couple to a NAT gateway 1838 contained in a control plane VCN 1816. The service gateway 1836 contained in a control plane VCN 1816 can communicatively couple to a cloud service 1656 (e.g., Figure 17 Cloud services (1756).

[0288] In some examples, data plane VCN 1818 may be included in customer lease 1821. In this case, the IaaS provider may provide control plane VCN 1816 for each customer, and the IaaS provider may establish a unique compute instance 1844 for each customer, included in service lease 1819. Each compute instance 1844 may allow communication between control plane VCN 1816 included in service lease 1819 and data plane VCN 1818 included in customer lease 1821. Compute instance 1844 may allow resources provisioned in control plane VCN 1816 included in service lease 1819 to be deployed or otherwise used in data plane VCN 1818 included in customer lease 1821.

[0289] In other examples, an IaaS provider's customer may have a database residing in customer lease 1821. In this example, control plane VCN 1816 may include data plane mirror application layer 1840, which may include one or more application subnets 1826. Data plane mirror application layer 1840 may reside in data plane VCN 1818, but may not reside in data plane VCN 1818. That is, data plane mirror application layer 1840 may have access to customer lease 1821, but may not exist in data plane VCN 1818 or be owned or operated by the IaaS provider's customer. Data plane mirror application layer 1840 may be configured to invoke data plane VCN 1818, but may not be configured to invoke any entity contained in control plane VCN 1816. Customers may expect to deploy or otherwise use resources provisioned in the control plane VCN 1816 in the data plane VCN 1818, and the data plane mirroring application layer 1840 can facilitate customers' desired deployments or other uses of resources.

[0290] In some embodiments, an IaaS provider's customer can apply filters to data plane VCN 1818. In this embodiment, the customer can determine what data plane VCN 1818 can access, and the customer can restrict access from data plane VCN 1818 to the public Internet 1854. The IaaS provider may not be able to apply filters or otherwise control data plane VCN 1818's access to any external networks or databases. Applying filters and controls to data plane VCN 1818, which is included in customer lease 1821, can help isolate data plane VCN 1818 from other customers and the public Internet 1854.

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

[0292] Figure 19 This is a block diagram 1900 illustrating another example style of IaaS architecture according to at least one embodiment. Service operator 1902 (e.g., Figure 17 Service providers (1702) can communicatively couple to secure host leases (1904, e.g., Figure 17 The secure host lease 1704 may include VCN 1906 (e.g., Figure 17 VCN1706) and Secure Host Subnet 1908 (e.g., Figure 17 The secure host subnet 1708). VCN 1906 can include LPG 1910 (e.g., Figure 17 The LPG 1710), which can be communicatively coupled to the SSHVCN 1912 via the LPG 1910 included in the SSH VCN 1912 (e.g., Figure 17 SSH VCN 1712). SSH VCN 1912 can include SSH subnet 1914 (e.g., Figure 17 SSH subnet 1714), and SSH VCN 1912 can be communicatively coupled to control plane VCN 1916 via LPG 1910 contained in control plane VCN 1916 (e.g., Figure 17 The control plane VCN 1716) and coupled to the data plane VCN 1918 via the LPG 1910 contained in the data plane VCN 1918 (e.g., Figure 17 Data plane 1718). Control plane VCN 1916 and data plane VCN 1918 can be included in service lease 1919 (e.g., Figure 17 In the service rental (1719).

[0293] The control plane VCN 1916 may include a subnet 1922 that may contain one or more load balancers (LBs). Figure 17 The control plane DMZ layer 1920 of (one or more) LB subnets 1722 (e.g., Figure 17 The control plane DMZ layer 1720 may include one or more application subnets 1926 (e.g., similar to...). Figure 17 The control plane application layer 1924 of (one or more) application subnets 1726 (e.g., Figure 17 The control plane application layer 1724), may include (one or more) DB subnets 1930, and the control plane data layer 1928 (e.g., Figure 17 The control plane data layer 1728). One or more LB subnets 1922 contained in the control plane DMZ layer 1920 can be communicatively coupled to one or more application subnets 1926 contained in the control plane application layer 1924 and an Internet gateway 1934 that can be contained in the control plane VCN 1916 (e.g., Figure 17 Internet gateway 1734), and application subnet(s) 1926 can communicatively couple to DB subnet(s) 1930 contained in control plane data layer 1928 and service gateway 1936 (e.g., Figure 17 The service gateway) and Network Address Translation (NAT) gateway 1938 (e.g., Figure 17 (NAT gateway 1738). The control plane VCN 1916 may include the service gateway 1936 and the NAT gateway 1938.

[0294] Data plane VCN 1918 may include data plane application layer 1946 (e.g., Figure 17 Data plane application layer 1746), data plane DMZ layer 1948 (e.g., Figure 17 Data plane DMZ layer 1748), and data plane data layer 1950 (e.g., Figure 17 The data plane data layer 1750. The data plane DMZ layer 1948 may include one or more trusted application subnets 1960 and one or more untrusted application subnets 1962 that can be communicatively coupled to the data plane application layer 1946, and one or more LB subnets 1922 of the Internet gateway 1934 contained in the data plane VCN 1918. One or more trusted application subnets 1960 may be communicatively coupled to the service gateway 1936 contained in the data plane VCN 1918, the NAT gateway 1938 contained in the data plane VCN 1918, and one or more DB subnets 1930 contained in the data plane data layer 1950. One or more untrusted application subnets 1962 may be communicatively coupled to the service gateway 1936 contained in the data plane VCN 1918 and the one or more DB subnets 1930 contained in the data plane data layer 1950. The data plane data layer 1950 may include one or more DB subnets 1930 that can be communicatively coupled to the service gateway 1936 contained in the data plane VCN 1918.

[0295] One or more untrusted application subnets 1962 may include one or more primary VNICs 1964(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1966(1)-(N). Each tenant VM 1966(1)-(N) may be communicatively coupled to a corresponding application subnet 1967(1)-(N) that may be contained in a corresponding container egress VCN 1968(1)-(N), which may be contained in a corresponding customer lease 1970(1)-(N). A corresponding secondary VNIC 1972(1)-(N) may facilitate communication between one or more untrusted application subnets 1962 contained in data plane VCN 1918 and application subnets contained in container egress VCN 1968(1)-(N). Each container exit VCN 1968(1)-(N) may include a NAT gateway 1938, which can communicatively couple to the public Internet 1954 (e.g., Figure 17 The public internet (1754).

[0296] The Internet gateway 1934, contained in the control plane VCN 1916 and the data plane VCN 1918, can communicatively couple to the metadata management service 1952 (e.g., Figure 17 A metadata management system 1752 is provided, which can communicatively couple to the public internet 1954. The public internet 1954 can communicatively couple to a NAT gateway 1938 contained in a control plane VCN 1916 and a data plane VCN 1918. A service gateway 1936 contained in a control plane VCN 1916 and a data plane VCN 1918 can communicatively couple to a cloud service 1956.

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

[0298] In some examples, an IaaS provider's customer may grant the IaaS provider temporary network access and request functionality attached to the data plane application layer 1946. The code running this functionality may execute in VMs 1966(1)-(N) and may not be configured to run anywhere else on the data plane VCN 1918. Each VM 1966(1)-(N) may be connected to a customer lease 1970. The corresponding container 1971(1)-(N) contained in VMs 1966(1)-(N) may be configured to run the code. In this case, dual isolation may exist (e.g., container 1971(1)-(N) runs the code, where container 1971(1)-(N) may be contained in at least one VM 1966(1)-(N) contained in untrusted application subnet 1962), which can help prevent incorrect or otherwise unintended code from corrupting the IaaS provider's network or the networks of different customers. Container 1971(1)-(N) may be communicatively coupled to Customer Lease 1970 and may be configured to transmit or receive data from Customer Lease 1970. Container 1971(1)-(N) may not be configured to transmit or receive data from any other entity in Data Plane VCN 1918. After the code execution is complete, the IaaS provider may terminate or otherwise dispose of Container 1971(1)-(N).

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

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

[0301] Figure 20 This is a block diagram 2000 illustrating another example style of IaaS architecture according to at least one embodiment. Service operator 2002 (e.g., Figure 17 Service providers (1702) can communicatively couple to secure host rental (2004) (e.g., Figure 17 Secure Host Rental 1704), which may include VCN 2006 (e.g., Figure 17 VCN1706) and Secure Host Subnet 2008 (e.g., Figure 17 The secure host subnet 1708). VCN 2006 can include LPG 2010 (e.g., Figure 17 LPG 1710), the LPG 2010 can be accessed via SSH VCN 2012 (e.g., LPG 1710), Figure 17 The LPG 2010 in SSH VCN 2012 is communicatively coupled to SSH VCN 2012. SSH VCN 2012 may include SSH subnet 2014 (e.g., Figure 17 SSH subnet 1714), and SSH VCN 2012 can be communicatively coupled to control plane VCN 2016 via LPG2010 included in control plane VCN 2016 (e.g., Figure 17 The control plane VCN 1716) and coupled to the data plane VCN 2018 via the LPG 2010 contained in the data plane VCN 2018 (e.g., Figure 17 Data plane 1718). Control plane VCN 2016 and data plane VCN 2018 can be included in service lease 2019 (e.g., Figure 17 In the service rental (1719).

[0302] The control plane VCN 2016 may include one or more LB subnets 2022 (e.g., Figure 17 The control plane DMZ layer of (one or more) LB subnets 1722) 2020 (e.g., Figure 17 The control plane DMZ layer 1720 may include (one or more) application subnets 2026 (e.g., Figure 17 The control plane application layer 2024 of (one or more) application subnets 1726 (e.g., Figure 17 The control plane application layer 1724) may include (one or more) DB subnets 2030 (e.g., Figure 19 The control plane data layer of (one or more) DB subnets 1930) 2028 (e.g., Figure 17 The control plane data layer 1728). One or more LB subnets 2022 contained in the control plane DMZ layer 2020 can be communicatively coupled to one or more application subnets 2026 contained in the control plane application layer 2024 and an Internet gateway 2034 that can be contained in the control plane VCN 2016 (e.g., Figure 17 Internet gateway 1734), and application subnet(s) 2026 can communicatively couple to DB subnet(s) 2030 contained in control plane data layer 2028 and service gateway 2036 (e.g., Figure 17 The service gateway) and Network Address Translation (NAT) gateway 2038 (e.g., Figure 17 (NAT gateway 1738). The control plane VCN 2016 may include service gateway 2036 and NAT gateway 2038.

[0303] Data plane VCN 2018 may include data plane application layer 2046 (e.g., Figure 17 Data plane application layer 1746), data plane DMZ layer 2048 (e.g., Figure 17 Data plane DMZ layer 1748), and data plane data layer 2050 (e.g., Figure 17 The data plane data layer 1750). The data plane DMZ layer 2048 may include one or more trusted application subnets 2060 that can be communicatively coupled to the data plane application layer 2046 (e.g., Figure 19 (one or more) trusted application subnets 1960) and (one or more) untrusted application subnets 2062 (e.g., Figure 19 The data plane VCN 2018 may include one or more untrusted application subnets 1962 and one or more LB subnets 2022 of Internet gateway 2034. One or more trusted application subnets 2060 may communicatively couple to service gateway 2036, NAT gateway 2038, and DB subnets 2030 in data plane VCN 2018. One or more untrusted application subnets 2062 may communicatively couple to service gateway 2036 and DB subnets 2030 in data plane VCN 2018. Data plane VCN 2050 may include one or more DB subnets 2030 that may communicatively couple to service gateway 2036 in data plane VCN 2018.

[0304] One or more untrusted application subnets 2062 may include a primary VNIC 2064(1)-(N) communicatively coupled to tenant virtual machines (VMs) 2066(1)-(N) residing within one or more untrusted application subnets 2062. Each tenant VM 2066(1)-(N) may run code in a corresponding container 2067(1)-(N) and is communicatively coupled to an application subnet 2026 that may be contained in a data plane application layer 2046 contained in a container egress VCN 2068. A corresponding secondary VNIC 2072(1)-(N) may facilitate communication between one or more untrusted application subnets 2062 contained in a data plane VCN 2018 and the application subnets contained in a container egress VCN 2068. The container egress VCN may include a public internet 2054 (e.g., Figure 17 NAT gateway 2038 for the public Internet (54).

[0305] Internet gateway 2034, included in control plane VCN 2016 and data plane VCN 2018, can communicatively couple to metadata management service 2052 (e.g., Figure 17 A metadata management system 1752 is provided, which can communicatively couple to the public internet 2054. The public internet 2054 can communicatively couple to a NAT gateway 2038 contained in a control plane VCN 2016 and a data plane VCN 2018. A service gateway 2036 contained in a control plane VCN 2016 and a data plane VCN 2018 can communicatively couple to a cloud service 2056.

[0306] In some examples, Figure 20 The block diagram 2000 architecture shown can be considered as... Figure 19 This is an exception to the architecture pattern shown in block diagram 1900, 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). Customers can access in real time the corresponding containers 2067(1)-(N) contained within each customer's VM 2066(1)-(N). Containers 2067(1)-(N) can be configured to invoke corresponding auxiliary VNICs 2072(1)-(N) contained in one or more application subnets 2026 of the data plane application layer 2046, which may be contained in a container egress VCN 2068. The auxiliary VNICs 2072(1)-(N) can transmit the calls to a NAT gateway 2038, which can then transmit the calls to the public internet 2054. In this example, containers 2067(1)-(N), which can be accessed by customers in real time, can be isolated from the control plane VCN 2016 and from other entities contained in the data plane VCN 2018. Containers 2067(1)-(N) can also be isolated from resources from other customers.

[0307] In other examples, a client may use container 2067(1)-(N) to invoke cloud service 2056. In this example, the client may run code within container 2067(1)-(N) requesting a service from cloud service 2056. Container 2067(1)-(N) may transmit the request to auxiliary VNIC 2072(1)-(N), which may transmit the request to a NAT gateway, which may then transmit the request to public internet 2054. Public internet 2054 may then transmit the request via internet gateway 2034 to one or more LB subnets 2022 contained in control plane VCN 2016. In response to determining that the request is valid, one or more LB subnets may transmit the request to one or more application subnets 2026, which may then transmit the request to cloud service 2056 via service gateway 2036.

[0308] It should be recognized that the IaaS architectures 1700, 1800, 1900, and 2000 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.

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

[0310] Figure 21 An example computer system 2100, in which various embodiments can be implemented, is illustrated. System 2100 can be used to implement any of the computer systems described above. As shown, computer system 2100 includes a processing unit 2104 that communicates with a plurality of peripheral subsystems via a bus subsystem 2102. These peripheral subsystems may include a processing acceleration unit 2106, an I / O subsystem 2108, a storage subsystem 2118, and a communication subsystem 2124. Storage subsystem 2118 includes a tangible computer-readable storage medium 2122 and system memory 2110.

[0311] Bus subsystem 2102 provides a mechanism for allowing various components and subsystems of computer system 2100 to communicate with each other as intended. While bus subsystem 2102 is schematically shown as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 2102 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, Micro Channel 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.

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

[0313] In various embodiments, processing unit 2104 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) 2104 and / or storage subsystem 2118. With appropriate programming, processor(s) 2104 can provide the various functions described above. Computer system 2100 may additionally include processing acceleration unit 2106, which may include digital signal processor (DSP), dedicated processor, etc.

[0314] I / O subsystem 2108 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, keyboards, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and / or gesture recognition devices, such as the Microsoft Kinect® motion sensor, which enables users to control and interact with input devices such as the Microsoft Xbox® 360 game controller 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 to 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.

[0315] 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 / video 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.

[0316] User interface output devices may include display subsystems, indicator lights, or non-visual displays such as audio output devices, etc. 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, etc. Generally, the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from computer system 2100 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.

[0317] Computer system 2100 may include storage subsystem 2118, 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 2104, provide the aforementioned functionality. Storage subsystem 2118 may also provide a repository for storing data used according to this disclosure.

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

[0319] System memory 2110 may also store operating system 2116. Examples of operating system 2116 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 where computer system 2100 executes one or more virtual machines, the virtual machine, along with the guest operating system (GOS), may be loaded into system memory 2110 and executed by one or more processors or cores of processing unit 2104.

[0320] System memory 2110 can be configured differently depending on the type of computer system 2100. For example, system memory 2110 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 2110 may include a basic input / output system (BIOS), which contains basic routines such as those that facilitate the transfer of information between components within computer system 2100 during startup.

[0321] Computer-readable storage medium 2122 may represent remote, local, fixed and / or removable storage devices and storage media for temporarily and / or more permanently containing and storing computer-readable information for use by computer system 2100, including instructions executable by processing unit 2104 of computer system 2100.

[0322] Computer-readable storage medium 2122 may include any suitable medium known or used in the art, including storage media and communication media, such as, but not limited to, volatile and non-volatile, removable and non-removable media implemented 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, magnetic tape cassette, magnetic tape, disk storage or other magnetic storage devices, or other tangible computer-readable media.

[0323] For example, computer-readable storage medium 2122 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 2122 may include, but is not limited to, Zip® drives, flash memory cards, Universal Serial Bus (USB) flash drives, Secure Digital (SD) cards, DVD discs, digital audio tapes, and so on. Computer-readable storage medium 2122 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 2100.

[0324] Machine-readable instructions executable by one or more processors or cores of processing unit 2104 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.

[0325] The communication subsystem 2124 provides an interface to other computer systems and networks. The communication subsystem 2124 serves as an interface for receiving data from other systems and sending data from computer system 2100 to other systems. For example, the communication subsystem 2124 enables computer system 2100 to connect to one or more devices via the Internet. In some embodiments, the communication subsystem 2124 may include radio frequency (RF) transceiver components (e.g., advanced data network technologies using cellular telephone technologies, 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 2124 may provide a wired network connection (e.g., Ethernet).

[0326] In some embodiments, the communication subsystem 2124 may also represent one or more users who may use the computer system 2100 to receive input communications in the form of structured and / or unstructured data feeds 2126, event streams 2128, event updates 2130, etc.

[0327] For example, the communication subsystem 2124 can be configured to receive data feeds 2126 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.

[0328] Furthermore, the communication subsystem 2124 can also be configured to receive data in the form of a continuous data stream, which may include event streams 2128 and / or event updates 2130 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 quotation machines, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, vehicle traffic monitoring, and so on.

[0329] The communication subsystem 2124 can also be configured to output structured and / or unstructured data feeds 2126, event streams 2128, event updates 2130, etc. to one or more databases, which can communicate with one or more streaming data source computers coupled to the computer system 2100.

[0330] The computer system 2100 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.

[0331] Due to the constantly evolving nature of computers and networks, the description of the computer system 2100 depicted in the figures is merely a concrete example. Many other configurations with more or fewer components than the system depicted in the figures are possible. For example, custom hardware may be used and / or specific elements may be implemented using hardware, firmware, software (including applets), 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.

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

[0333] 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 in any combination on the same processor or on different processors. Thus, 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 various 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.

[0334] Therefore, the specification and drawings are to be considered illustrative rather than restrictive. However, it will be apparent that additions, omissions, deletions, and other modifications and changes can be made therein 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.

[0335] 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 covering both singular and plural, unless otherwise indicated herein or obviously 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 obviously 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 stated. Nothing in the specification should be construed as indicating that any unclaimed element is essential to the practice of this disclosure.

[0336] Extractive 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 extractive 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.

[0337] 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. Thus, the present disclosure includes all modifications and equivalents to the subject matter recited in the appended claims, where permitted by applicable law. Moreover, unless otherwise indicated herein, the present disclosure includes any combination of the foregoing elements in all its possible variations.

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

[0339] 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 utilized in any number of settings and applications other than those described herein without departing from the broader spirit and scope of this specification. Therefore, this specification and the accompanying drawings should be considered illustrative rather than restrictive.< / realm>

Claims

1. A computer-implemented method, comprising: Obtain first observability data in the first cloud environment that is associated with cloud services provided by the first cloud environment in the second cloud environment; The first observable data is processed by the first cloud environment to generate the second observable data, wherein the second observable data is compatible with the observable data format of the second cloud environment; as well as Provide second observability data from the first cloud environment to the second cloud environment.

2. The computer-implemented method of claim 1, wherein the first observability data includes one or more metrics and / or one or more events associated with the execution of the cloud service.

3. The computer-implemented method according to claim 1, wherein: Processing the first observability data to generate the second observability data includes identifying patterns associated with the second cloud environment; and Based on the aforementioned pattern, the format of the first observable data is converted into the observable data format of the second cloud environment.

4. The computer-implemented method according to claim 3, wherein the pattern is derived from inventory information retrieved from a second cloud environment.

5. The computer-implemented method according to claim 1, further comprising: Before obtaining the first observable data: Create one or more targets in the observability data plane within the first cloud environment, configured to receive first observable data.

6. The computer-implemented method according to claim 1, further comprising: Identify a first identifier associated with a customer and a first private cloud in a first cloud environment, and a second identifier associated with a second private cloud in a second cloud environment; The association between the first identifier, the second identifier, and the resource identifier associated with the cloud service is stored in the observability control plane within the first cloud environment; as well as After obtaining the first observable data: Identify resource identifiers associated with the first observability data; and Based on the resource identifier and the association stored in the observability control plane, the customer, the second cloud environment, and one or more resource details are identified.

7. The computer-implemented method of claim 1, wherein providing the second observability data to the second cloud environment comprises: The second observable data is provided from the observable data plane in the first cloud environment to an agent configured to communicate with the observable data repository in the second cloud environment.

8. A system comprising: One or more processors; as well as One or more computer-readable media storing instructions that, when executed by the one or more processing systems, cause the systems to perform operations including: Obtain first observability data in the first cloud environment that is associated with cloud services provided by the first cloud environment in the second cloud environment; The first observable data is processed by the first cloud environment to generate second observable data, wherein the second observable data is compatible with the observable data format of the second cloud environment; and Provide second observability data from the first cloud environment to the second cloud environment.

9. The system of claim 8, wherein the first observability data includes one or more metrics and / or one or more events associated with the execution of the cloud service.

10. The system according to claim 8, wherein: Processing the first observability data to generate the second observability data includes identifying patterns associated with the second cloud environment; and Based on the aforementioned pattern, the format of the first observable data is converted into the observable data format of the second cloud environment.

11. The system of claim 10, wherein the pattern is derived from inventory information retrieved from a second cloud environment.

12. The system according to claim 8, wherein the operation further comprises: Before obtaining the first observable data: Create one or more targets in the observability data plane within the first cloud environment, configured to receive first observable data.

13. The system according to claim 9, wherein the operation further comprises: Identify a first identifier associated with a customer and a first private cloud in a first cloud environment, and a second identifier associated with a second private cloud in a second cloud environment; The association between the first identifier, the second identifier, and the resource identifier associated with the cloud service is stored in the observability control plane within the first cloud environment; as well as After obtaining the first observable data: Identify resource identifiers associated with the first observability data; and Based on the resource identifier and the association stored in the observability control plane, the customer, the second cloud environment, and one or more resource details are identified.

14. The system of claim 8, wherein providing the second observability data to the second cloud environment comprises: The second observable data is provided from the observable data plane in the first cloud environment to an agent configured to communicate with the observable data repository in the second cloud environment.

15. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause a system to perform operations, said operations including: Obtain first observability data in the first cloud environment that is associated with cloud services provided by the first cloud environment in the second cloud environment; The first observable data is processed by the first cloud environment to generate the second observable data, wherein the second observable data is compatible with the observable data format of the second cloud environment; as well as Provide second observability data from the first cloud environment to the second cloud environment.

16. One or more non-transitory computer-readable media according to claim 15, wherein the first observability data includes one or more metrics and / or one or more events associated with the execution of the cloud service.

17. One or more non-transitory computer-readable media according to claim 15, wherein: Processing the first observability data to generate the second observability data includes identifying patterns associated with the second cloud environment; and Based on the aforementioned pattern, the format of the first observable data is converted into the observable data format of the second cloud environment.

18. One or more non-transitory computer-readable media according to claim 17, wherein the mode is derived from inventory information retrieved from a second cloud environment.

19. The operation further comprises: one or more non-transitory computer-readable media according to claim 15. Before obtaining the first observable data: Create one or more targets in the observability data plane within the first cloud environment, configured to receive first observable data.

20. The operation further comprises: one or more non-transitory computer-readable media according to claim 15. Identify a first identifier associated with a customer and a first private cloud in a first cloud environment, and a second identifier associated with a second private cloud in a second cloud environment; The association between the first identifier, the second identifier, and the resource identifier associated with the cloud service is stored in the observability control plane within the first cloud environment; as well as After obtaining the first observable data: Identify resource identifiers associated with the first observability data; and Based on the resource identifier and the association stored in the observability control plane, the customer, the second cloud environment, and one or more resource details are identified.

Images