Patent Application
20240098088
The present disclosure generally relates to techniques for providing cloud services. More specifically, novel techniques of resource allocation services for virtual private label cloud (vPLC) are disclosed. A vPLC may be created for a reseller of a Cloud Services Provider (CSP) using CSP-provided infrastructure in a region and used for providing one or more reseller-offered cloud services to customers of the reseller.
Cloud computing has gradually become a part of modern life and plays a significant role in everyday activities because of its ubiquitous presence and ease of access to essential data. However, there are only a few players in the cloud infrastructure business, just like in the early telecommunication era. Thus, there is a need to make cloud infrastructure services more widely available.
The present disclosure generally relates to techniques for providing cloud services. More specifically, novel techniques of resource allocation services for virtual private label cloud (vPLC) are disclosed. A vPLC is created for a reseller of a Cloud Services Provider (CSP) using CSP-provided infrastructure in a region such that the reseller can provide one or more reseller-offered cloud services to customers of the reseller.
The present disclosure generally relates to techniques for providing cloud services. More specifically, novel techniques are disclosed that enable cloud infrastructure in a region provided by a Cloud Services Provider (CSP), for providing CSP-offered cloud services to customers of the CSP, to be used to create one or more virtual private clouds (referred to herein as virtual private label clouds or “vPLCs”). Various embodiments are described herein, including methods, systems, non-transitory computer-readable storage media storing programs, code, or instructions executable by one or more processors, and the like.
The vPLCs created according to the various techniques described in this disclosure may be used for different purposes. For example, in one use case, a vPLC may be created for a reseller who is a customer of the CSP and can be used by the reseller to provide one or more reseller-offered cloud services to customers of the reseller. As another use case, a vPLC may be used as a virtual data center and may be associated with a different realm than the realm associated with the cloud infrastructure in the region provided by the CSP.
In certain implementations, a vPLC represents a virtual cloud comprising a set of resources that have been allocated to the vPLC from the CSP-provided infrastructure in a region. One or more vPLCs can be created using CSP-provided infrastructure in a region.
In certain embodiments, regional infrastructure provided by a CSP in a region can be used both to provide cloud services to customers of the CSP and also reseller-offered cloud services to customer of a reseller, who is a customer of the CSP. This is achieved by creating, from the CSP-provided regional infrastructure, one or more vPLCs for one or more resellers, where a vPLC created for a particular reseller can be used to provide reseller-offered and reseller-branded cloud services to customers of the particular reseller. This enables a reseller to become a provider of reseller-branded cloud services to its customers without having to invest in the infrastructure needed for providing those cloud services. Instead, the reseller uses infrastructure provided by the CSP to provide the reseller-branded cloud services to the reseller's customers. In this manner, a first portion of the infrastructure provided in a region by the CSP can be used to provide CSP-offered cloud services to customers of the CSP, a second portion of the infrastructure provided in the region by the CSP and allocated to a first vPLC created for a first reseller can be used to provide first reseller-offered cloud services to customers of the first reseller, a third portion of the infrastructure provided in the region by the CSP and allocated to a second vPLC created for a second reseller can be used to provide second reseller-offered cloud services to customers of the second reseller, and so on.
In certain embodiments, techniques are provided including a method that comprises using a first portion of cloud service provider (CSP)-provided infrastructure in a first region to provide one or more CSP-offered cloud services to one or more customers of the CSP; creating a first virtual private label cloud (vPLC) for a first reseller based upon the CSP-provided infrastructure, wherein creating the first vPLC comprises allocating a second portion of the CSP-provided infrastructure to the first vPLC; using the first vPLC to provide one or more first reseller-offered cloud services to one or more customers of the first reseller; allocating, from a plurality of resources provided by the CSP-provided infrastructure, a first set of resources for providing the one or more CSP-offered cloud services; and allocating, from the plurality of resources provided by the CSP-provided infrastructure, a second set of resources for use by a set of vPLCs including the first vPLC.
In yet another embodiment, allocating the second set of resources for use by a set of vPLCs comprises allocating a first subset of the second set of resources to the first vPLC.
In yet another embodiment, the method further comprises checking a first-level policy to determine whether the first subset of the second set of resources is allowed to be allocated to the first vPLC.
In yet another embodiment, the method further comprises checking a resource database to determine whether the first subset of the second set of resources is available to be allocated to the first vPLC, the resource database being configured to track resource allocation history associated with the first vPLC.
In yet another embodiment, the first-level policy is based at least in part on an agreement between the CSP and the first reseller.
In yet another embodiment, the first-level policy comprises a requirement for types of resources.
In yet another embodiment, the first-level policy comprises a requirement for amount of resources.
In yet another embodiment, the method further comprises allocating a first portion of the first subset of the second set of resources to a customer tenancy of a first customer of the first reseller.
In yet another embodiment, the method further comprises checking a second-level policy to determine whether the first portion of the first subset of the second set of resources is allowed to be allocated to the customer tenancy of the first customer of the first reseller.
In yet another embodiment, the second-level policy is based at least in part on an agreement between the first reseller and the first customer of the first reseller.
In yet another embodiment, allocating the second set of resources for use by a set of vPLCs further comprising allocating a subset of the second set of resources for the first vPLC based at least in part on a partitioning requirement for the first vPLC, and the partition requirement is an infrastructure level at which the subset of the second set of resources is allocated exclusively to the first vPLC and not shared by other vPLCs.
In various embodiments, a system is provided that includes one or more data processors and a non-transitory computer readable medium containing instructions which, when executed on the one or more data processors, cause the one or more data processors to perform part or all of one or more methods disclosed herein.
In various embodiments, a non-transitory computer-readable medium, storing computer-executable instructions which, when executed by one or more processors, cause the one or more processors of a computer system to perform one or more methods disclosed herein.
In various embodiments, a computer-program product, comprising computer program/instructions which, when executed by a processor, cause the processor to perform any of the methods disclosed herein.
The techniques described above and below may be implemented in a number of ways and in a number of contexts. Several example implementations and contexts are provided with reference to the following figures, as described below in more detail. However, the following implementations and contexts are but a few of many.
In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of certain embodiments. However, it will be apparent that various embodiments may be practiced without these specific details. The figures and description are not intended to be restrictive. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs.
The present disclosure generally relates to techniques for providing cloud services. More specifically, novel techniques are disclosed that enable cloud infrastructure in a region provided by a Cloud Services Provider (CSP), for providing CSP-offered cloud services to customers of the CSP, to be used to create one or more virtual private clouds (referred to herein as virtual private label clouds or “vPLCs”). Various embodiments are described herein, including methods, systems, non-transitory computer-readable storage media storing programs, code, or instructions executable by one or more processors, and the like.
The vPLCs created according to the various techniques described in this disclosure may be used for different purposes. For example, in one use case, a vPLC may be created for a reseller who is a customer of the CSP and can be used by the reseller to provide one or more reseller-offered cloud services to customers of the reseller. As another use case, a vPLC may be used as a virtual data center and may be associated with a different realm than the realm associated with the cloud infrastructure in the region provided by the CSP.
In certain implementations, a vPLC represents a virtual cloud comprising a set of resources that have been allocated to the vPLC from the CSP-provided infrastructure in a region. One or more vPLCs can be created using CSP-provided infrastructure in a region. In some embodiments, a virtual private label cloud (vPLC) refers to a model and architecture provided by the CSP within the CSP-provided infrastructure in a region that enables and facilitates the reseller-offered and reseller-branded cloud services.
Just as the CSP-provided infrastructure in a region provides cloud resources that can be accessed by the CSP's customers, a vPLC created for a reseller provides a set of resources that can be accessed by customers of the reseller. From the perspective of the reseller's customers, the vPLC is like reseller-provided infrastructure in a region providing resources that can be accessed by customers of the reseller. The vPLC resembles a data center in a region provided by the reseller offering reseller-offered cloud services to customers of the reseller.
In certain embodiments, regional infrastructure provided by a CSP in a region can be used both to provide cloud services to customers of the CSP and also reseller-offered cloud services to customer of a reseller, who is a customer of the CSP. This is achieved by creating, from the CSP-provided regional infrastructure, one or more vPLCs for one or more resellers, where a vPLC created for a particular reseller can be used to provide reseller-offered and reseller-branded cloud services to customers of the particular reseller. This enables a reseller to become a provider of reseller-branded cloud services to its customers without having to invest in the infrastructure needed for providing those cloud services. Instead, the reseller uses infrastructure provided by the CSP to provide the reseller-branded cloud services to the reseller's customers.
In the reseller use case, a vPLC is created for a reseller using cloud infrastructure in a region provided by a Cloud Services Provider (CSP). A vPLC created for a reseller can be used by the reseller to provide one or more reseller-offered cloud services to customers of the reseller. In certain implementations, the CSP-provided regional infrastructure providing the services that are used by the resellers to provide one or more reseller-offered services is partitioned into securely isolated portions, and the isolated portions (or partitions) allocated to different resellers such that a partition allocated to a reseller is isolated from other resellers. In this manner, a first portion of the infrastructure provided in a region by the CSP can be used to provide CSP-offered cloud services to customers of the CSP, a second portion of the infrastructure provided in the region by the CSP and allocated to a first vPLC created for a first reseller can be used to provide first reseller-offered cloud services to customers of the first reseller, a third portion of the infrastructure provided in the region by the CSP and allocated to a second vPLC created for a second reseller can be used to provide second reseller-offered cloud services to customers of the second reseller, and so on. Each portion of the infrastructure allocated to a reseller can also be further partitioned into a second level of securely isolated portions to provide multi-tenant cloud infrastructure services to the reseller's customers.
A reseller can be an entity such as an enterprise or business or an individual. Using the techniques described herein enables the reseller entity to quickly become a cloud services provider while avoiding all the barriers to entry discussed in the Background section of this disclosure. For example, the reseller does not have to procure the infrastructure that is used for providing the cloud services since the cloud services provided are using infrastructure provided by the CSP. To the customers of a reseller, it appears as if the reseller is providing the reseller-offered cloud services. From the perspective of the customers of the reseller, the reseller is thus the cloud services provider providing the services subscribed to by the customers. A reseller's customer may not even know or be aware of the CSP whose infrastructure is being used by the reseller to provide the reseller-offered and reseller-branded cloud services.
The ability to provide vPLCs may be offered as a service by the CSP and can be subscribed to by one or more customers. For example, an entity desiring to provide cloud services to its customers but not wanting to invest for procuring infrastructure needed for offering the services can subscribe to this CSP-offered vPLC service. Once subscribed to the vPLC service, the entity is a customer of the CSP, but is a “special” customer since the CSP-provided infrastructure allocated to the entity in the form of a vPLC is in turn used to provide entity-offered and branded services to customers of that entity. The customer is thus a customer of the CSP and also a reseller of cloud services using the vPLC created for the entity. The entity is thus referred to as a “reseller” to differentiate it from actual direct customers of the CSP. A direct customer of the CSP who is entity that is subscribes to and consumes one or more CSP-offered and branded services, and is not using the CSP infrastructure to sell cloud services to its customers. For purposes of this disclosure, a direct customer of the CSP is also referred to as a “non-reseller customer” to differentiate from a reseller. With respect to a reseller, as part of the vPLC service, the CSP provides infrastructure to the reseller in the form of a vPLC, and the vPLC is used by the reseller to offer reseller-branded cloud services to the reseller's customers.
A vPLC can be used for various other applications that do not involve a reseller. As an example, a vPLC can be created and associated with a realm that is different from a realm associated with the CSP-provided regional infrastructure that is used to create the vPLC. For example, the CSP-provided regional infrastructure may be associated with a first realm and the vPLC may be associated with a second realm that is different from the first realm. In such a scenario, the infrastructure corresponding to the vPLC is hosted by the first realm but is considered to belong to the second realm. This can be used for various different purposes. For example, since the vPLC is associated with the second realm it can communicate with other infrastructure (e.g., other data centers) in the second realm. Accordingly, a data center in the second realm can communicate with the vPLC since they are both in the same realm and share the second realm trust and identity profile.
The creation and management of the vPLCs is performed using infrastructure and services provided by the CSP and very technically complicated tasks. When a vPLC is created for a reseller, technical functionality is be provided to enable the reseller to use the vPLC to provide reseller-offered cloud services to the reseller's customers using the vPLC. This includes the ability to segregate traffic between resellers, segregate the traffic of different customers of a reseller, dynamically managing allocation of CSP-provided resources to the vPLC, managing the allocation of resources allocated to the vPLC among the different customers of the vPLC, measuring usage of vPLC-allocated for the reseller and performing related billing functions, measuring usage of vPLC-allocated among the different customers of the vPLC and performing related billing functions, enabling marketplaces for the different resellers, performing identity management functions of the resellers and their customers, and the like. The present disclosure describes various embodiments depicting various architectures and corresponding methods for performing and enabling the vPLC-related functions.
A reseller may use a vPLC created for the reseller to provide reseller-offered and reseller-branded cloud services offering specialized services in a domain in which the reseller specializes. The reseller-offered services may be tailored to different segments of customers. In certain implementations, a reseller-offered cloud service may be different from a cloud service offered by the CSP. In some other implementations, a reseller-offered cloud service may be based upon a cloud service offered by the CSP, for example, the reseller-offered service may be a customized version of a CSP-offered cloud service.
For example, a first vPLC may be created from CSP-provided infrastructure in a first region for a first reseller specialized in providing financial services. Customers of the first reseller may be banks and other financial institutions. Accordingly, the first reseller may use the first vPLC to provide customized and first reseller-branded financial cloud services to its customers. A second vPLC may be created from the same CSP-provided infrastructure in the first region for a second reseller specialized in providing telecom services. Customers of the second reseller may be users of telecom services. The second reseller may use the second vPLC to provide customized and second reseller-branded telecom cloud services to its customers. In addition to the first vPLC and the second vPLC, the CSP-provided infrastructure in the first region may be used by the CSP to provide CSP-offered and branded cloud services to one or more direct (non-reseller) customers of the CSP. In this manner, the same CSP-provided infrastructure in a region is used to provide CSP-offered and branded cloud services to one or more direct (non-reseller) customers of the CSP, to provide customized and first reseller-branded financial cloud services to customers of the first reseller, and to provide customized and second reseller-branded telecom cloud services to customers of the second reseller.
Cloud infrastructure is dynamic in nature. Balancing resource allocation to meet varying workloads can be challenging. Overprovisioning may lead to wasted resource, while under-provisioning may result in poor performance. As the demand for cloud services increases, CSPs look for ways to expand the presence of their cloud services, including having resellers offer more specialized services. However, the increase in cloud service demand may lead to increase in complexity of allocating resources in the cloud infrastructure. For example, cloud services may change from one-tier service (e.g., offering services to non-reseller customers of CSP only) to two-tier (e.g., offering services to resellers of the CSP and also customers of the resellers). Additionally, as a CSP-provided infrastructure hosts more tenants on the same physical hardware, the partition and segmentation of cloud resources become more complex. Thus, there is a need to address these challenges and others.
The present disclosure generally relates to techniques for providing cloud services. More specifically, novel techniques are disclosed for resource allocation and management under the virtual private label cloud (vPLC). A vPLC is created for a reseller of a Cloud Services Provider (CSP) using CSP-provided infrastructure in a region such that the reseller can provide one or more reseller-offered cloud services to customers of the reseller. Resource allocation services (referred to herein as resource management) include a resource manager playing a central role in allocating various resources for vPLCs. The various resources may include, but are not limited to, compute resources, storage resources, and networking resources.
The novel techniques described in the present disclosure address complexity of resource allocation in multi-tier cloud infrastructure by using a centralized resource manager (RM) to provide multi-level coordination among CSP, resellers, and customers of the reseller while interacting with various entities, resources, and information to streamline the resource allocation process. Additionally, a concept of called generic unbounded resource pool (GURP) can enable dynamic resource allocation and optimization among vPLCs to reduce wasted resources and improve scalability. Finally, the ability to segment infrastructure at different levels provides security and flexibility for multi-tenant cloud infrastructure.
A resource manager (RM) may receive requests directly or indirectly from resellers or customers of resellers, and interact with the control plane, resource database, and identity system to accomplish the resource allocation. During the resource allocation process, RM may also obtain topology-segmentation information and check policy information.
The resource manager's centralized role may help streamline the resource allocation process, and achieve better coordination among different stakeholders. For example, resource allocation for a vPLC may involve CSP, a reseller, and customers of the reseller. These parties may create two levels of policies, such as the CSP-reseller policy and the reseller-customer policy. Such multi-level interaction and checking may need good coordination to allocate resources.
In some embodiments, the CSP may own an overall availability resource pool containing many partitioned resource pools of different resource types (e.g., compute, storage, networking, etc.). Each of these partitioned resource pools for a resource type is referred to herein as a generic unbounded resource pool (GURP) for that particular resource type. A GURP may contain resources set aside by the CSP for resellers and may be shared and controlled by vPLC resellers for use. When a new vPLC is requested, a namespace for the new vPLC is created for each of the requested resource types. The resources in those namespaces may be associated with vPLC-related information (e.g., vPLC ID and customer tenancy ID) to help the RM identify and allocate resources upon receiving a resource request from a reseller or a customer of a reseller. When resources in a vPLC are not used, the unused resources may be returned to the GURPs for other vPLCs to use.
In some embodiments, reseller's policies may be aggregated and fulfilled on the shared resources to make the resource as widely available as possible to minimize cost on any given end-user or reseller. For example, two resellers have different policies; one may need to allocate more resources than another at a certain time, and vice versa. When the two vPLC resellers' policies are aggregated, the overall shared resource may be better utilized by reallocating under-utilized resources from one vPLC to another. In other instances, aggregated policies may help provide an overall picture and anticipate the demands from both vPLCs, adjust accordingly to fulfill both policies instead of looking blindly at only one policy at the expense of another.
The GURPs may increase resource utilization and optimization for CSP and resellers since such GURP architecture reduces duplicated or unused resources. Furthermore, the GURP architecture can improve scalability because resources can be added and made available to all resellers, or reallocated depending on the demand among resellers. Finally, the GURP architecture reduces cost ownership because of resource sharing and fewer wasted resources.
In certain embodiments, policies among the CSP, resellers, and customers of the resellers, may be in two tiers, CSP-reseller policy as tier-one and reseller-customer policy as tier-two.
In some embodiments, when allocating resources for a vPLC, RM may check the CSP-reseller policy and resource database tracking the history of resource allocation to ensure the requested resources are allowed and available in compliance with the CSP-reseller policy.
Similarly, when allocating resources for a customer of a reseller associated with a vPLC, RM may check the reseller-customer policy and resource database tracking history of resource allocation to ensure the requested resources are allowed and available in compliance with the reseller-customer policy.
In some embodiments, the CSP-reseller policy and the reseller-customer policy may sometimes conflict with each other, but can be resolved by certain guidelines agreed upon among these three parties, for example, following the more stringent policy between the two policies or one policy overriding another policy.
The two-tier policy may enable a reseller to have better control over the vPLC resources and provide vPLC-specific resources to the reseller's customers. For example, a customer's request for resources may be fulfilled by RM using the vPLC ID assigned to the vPLC to check the corresponding reseller-customer policy, rather than relying on the default CSP policy.
In some embodiments, vPLCs may be segmented at different infrastructure levels (e.g., rack, server, or hypervisor level). As a result, a vPLC may share resources with other vPLCs at one infrastructure level (e.g., sharing a rack) while that vPLC may have dedicated resources at another infrastructure level (e.g., a dedicated server not sharing with another vPLC). Such topology-segmentation feature provides security and flexibility, and can tailor to different needs of different resellers.
For example, a reseller R1 may put security as the highest priority and like to have a dedicated rack for its associated vPLC.R1. This dedicated rack is referred to as a segmentation level at the rack level. A reseller R2 may be more cost-conscious and like to have a shared server for its vPLC.R2 with vPLC.R3 associated with another reseller R3, while having securely isolated hypervisors within the server. The type of partition is referred to as a segmentation level at the hypervisor level. Yet, a reseller R4 may like to have the flexibility of security and performance by having a bare metal server for its vPLC.R4 in a rack shared with another reseller. This partition is referred to as a segmentation level at the server level.
The term cloud service is generally used to refer to a service that is made available by a cloud services provider (CSP) to users or customers on demand (e.g., via a subscription model) using systems and infrastructure (cloud infrastructure) provided by the CSP. Typically, the servers and systems that make up the CSP's infrastructure are separate from the customer's own on-premise servers and systems. Customers can thus avail themselves of cloud services provided by the CSP without having to purchase separate hardware and software resources for the services. Cloud services are designed to provide a subscribing customer easy, scalable access to applications and computing resources without the customer having to invest in procuring the infrastructure that is used for providing the services.
There are several cloud service providers that offer various types of cloud services. There are various different types or models of cloud services including Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), and others.
A customer can subscribe to one or more cloud services provided by a CSP. The customer can be any entity such as an individual, an organization, an enterprise, and the like. When a customer subscribes to or registers for a service provided by a CSP, a tenancy or an account is created for that customer. The customer can then, via this account, access the subscribed-to one or more cloud resources associated with the account.
As noted above, infrastructure as a service (IaaS) is one particular type of cloud computing service. In an IaaS model, the CSP provides infrastructure (referred to as cloud services provider infrastructure or CSPI) that can be used by customers to build their own customizable networks and deploy customer resources. The customer's resources and networks are thus hosted in a distributed environment by infrastructure provided by a CSP. This is different from traditional computing, where the customer's resources and networks are hosted by infrastructure provided by the customer.
The CSPI may comprise interconnected high-performance compute resources including various host machines, memory resources, and network resources that form a physical network, which is also referred to as a substrate network or an underlay network. The resources in CSPI may be spread across one or more data centers that may be geographically spread across one or more geographical regions. Virtualization software may be executed by these physical resources to provide a virtualized distributed environment. The virtualization creates an overlay network (also known as a software-based network, a software-defined network, or a virtual network) over the physical network. The CSPI physical network provides the underlying basis for creating one or more overlay or virtual networks on top of the physical network. The physical network (or substrate network or underlay network) comprises physical network devices such as physical switches, routers, computers and host machines, and the like. An overlay network is a logical (or virtual) network that runs on top of a physical substrate network. A given physical network can support one or multiple overlay networks. Overlay networks typically use encapsulation techniques to differentiate between traffic belonging to different overlay networks. A virtual or overlay network is also referred to as a virtual cloud network (VCN). The virtual networks are implemented using software virtualization technologies (e.g., hypervisors, virtualization functions implemented by network virtualization devices (NVDs) (e.g., smartNICs), top-of-rack (TOR) switches, smart TORs that implement one or more functions performed by an NVD, and other mechanisms) to create layers of network abstraction that can be run on top of the physical network. Virtual networks can take on many forms, including peer-to-peer networks, IP networks, and others. Virtual networks are typically either Layer-3 IP networks or Layer-2 VLANs. This method of virtual or overlay networking is often referred to as virtual or overlay Layer-3 networking. Examples of protocols developed for virtual networks include IP-in-IP (or Generic Routing Encapsulation (GRE)), Virtual Extensible LAN (VXLAN IETF RFC 7348), Virtual Private Networks (VPNs) (e.g., MPLS Layer-3 Virtual Private Networks (RFC 4364)), VMware's NSX, GENEVE (Generic Network Virtualization Encapsulation), and others.
For IaaS, the infrastructure (CSPI) provided by a CSP can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In an IaaS model, a cloud computing services provider can host the infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., a hypervisor layer), or the like). In some cases, an IaaS provider may also supply a variety of services to accompany those infrastructure components (e.g., billing, monitoring, logging, security, load balancing and clustering, etc.). Thus, as these services may be policy-driven, IaaS users may be able to implement policies to drive load balancing to maintain application availability and performance. CSPI provides infrastructure and a set of complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available hosted distributed environment. CSPI offers high-performance compute resources and capabilities and storage capacity in a flexible virtual network that is securely accessible from various networked locations such as from a customer's on-premises network. When a customer subscribes to or registers for an IaaS service provided by a CSP, the tenancy created for that customer is a secure and isolated partition within the CSPI where the customer can create, organize, and administer their cloud resources.
Customers can build their own virtual networks using compute, memory, and networking resources provided by CSPI. One or more customer resources or workloads, such as compute instances, can be deployed on these virtual networks. For example, a customer can use resources provided by CSPI to build one or multiple customizable and private virtual network(s) referred to as virtual cloud networks (VCNs). A customer can deploy one or more customer resources, such as compute instances, on a customer VCN. Compute instances can take the form of virtual machines, bare metal instances, and the like. The CSPI thus provides infrastructure and a set of complementary cloud services that enable customers to build and run a wide range of applications and services in a highly available virtual hosted environment. The customer does not manage or control the underlying physical resources provided by CSPI but has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., firewalls).
The CSP may provide a console that enables customers and network administrators to configure, access, and manage resources deployed in the cloud using CSPI resources. In certain embodiments, the console provides a web-based user interface that can be used to access and manage CSPI. In some implementations, the console is a web-based application provided by the CSP.
CSPI may support single-tenancy or multi-tenancy architectures. In a single tenancy architecture, a software (e.g., an application, a database) or a hardware component (e.g., a host machine or a server) serves a single customer or tenant. In a multi-tenancy architecture, a software or a hardware component serves multiple customers or tenants. Thus, in a multi-tenancy architecture, CSPI resources are shared between multiple customers or tenants. In a multi-tenancy situation, precautions are taken and safeguards put in place within CSPI to ensure that each tenant's data is isolated and remains invisible to other tenants.
In a physical network, a network endpoint (“endpoint”) refers to a computing device or system that is connected to a physical network and communicates back and forth with the network to which it is connected. A network endpoint in the physical network may be connected to a Local Area Network (LAN), a Wide Area Network (WAN), or other type of physical network. Examples of traditional endpoints in a physical network include modems, hubs, bridges, switches, routers, and other networking devices, physical computers (or host machines), and the like. Each physical device in the physical network has a fixed network address that can be used to communicate with the device. This fixed network address can be a Layer-2 address (e.g., a MAC address), a fixed Layer-3 address (e.g., an IP address), and the like. In a virtualized environment or in a virtual network, the endpoints can include various virtual endpoints such as virtual machines that are hosted by components of the physical network (e.g., hosted by physical host machines). These endpoints in the virtual network are addressed by overlay addresses such as overlay Layer-2 addresses (e.g., overlay MAC addresses) and overlay Layer-3 addresses (e.g., overlay IP addresses). Network overlays enable flexibility by allowing network managers to move around the overlay addresses associated with network endpoints using software management (e.g., via software implementing a control plane for the virtual network). Accordingly, unlike in a physical network, in a virtual network, an overlay address (e.g., an overlay IP address) can be moved from one endpoint to another using network management software. Since the virtual network is built on top of a physical network, communications between components in the virtual network involves both the virtual network and the underlying physical network. In order to facilitate such communications, the components of CSPI are configured to learn and store mappings that map overlay addresses in the virtual network to actual physical addresses in the substrate network, and vice versa. These mappings are then used to facilitate the communications. Customer traffic is encapsulated to facilitate routing in the virtual network.
Accordingly, physical addresses (e.g., physical IP addresses) are associated with components in physical networks and overlay addresses (e.g., overlay IP addresses) are associated with entities in virtual or overlay networks. A physical IP address is an IP address associated with a physical device (e.g., a network device) in the substrate 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 with a compute instance in a customer's virtual cloud network (VCN). Two different customers or tenants, each with their own private VCNs can potentially use the same overlay IP address in their VCNs without any knowledge of each other. Both the physical IP addresses and overlay IP addresses are types of real IP addresses. These are separate from virtual IP addresses. A virtual IP address is typically a single IP address that is represents or maps to multiple real IP addresses. A virtual IP address provides a 1-to-many mapping between the virtual IP address and multiple real IP addresses. For example, a load balancer may use a VIP to map to or represent multiple servers, each server having its own real IP address.
The cloud infrastructure or CSPI is physically hosted in one or more data centers in one or more regions around the world. The CSPI may include components in the physical or substrate network and virtualized components (e.g., virtual networks, compute instances, virtual machines, etc.) that are in a virtual network built on top of the physical network components. In certain embodiments, the CSPI is organized and hosted in realms, regions and availability domains. A region is typically a localized geographic area that contains one or more data centers. Regions are generally independent of each other and can be separated by vast distances, for example, across countries or even continents. For example, a first region may be in Australia, another one in Japan, yet another one in India, and the like. CSPI resources are divided among regions such that each region has its own independent subset of CSPI resources. Each region may provide a set of core infrastructure services and resources, such as, compute resources (e.g., bare metal servers, virtual machine, containers and related infrastructure, etc.); storage resources (e.g., block volume storage, file storage, object storage, archive storage); networking resources (e.g., virtual cloud networks (VCNs), load balancing resources, connections to on-premise networks), database resources; edge networking resources (e.g., DNS); and access management and monitoring resources, and others. Each region generally has multiple paths connecting it to other regions in the realm.
Generally, an application is deployed in a region (i.e., deployed on infrastructure associated with that region) where it is most heavily used, because using nearby resources is faster than using distant resources. Applications can also be deployed in different regions for various reasons, such as redundancy to mitigate the risk of region-wide events such as large weather systems or earthquakes, to meet varying requirements for legal jurisdictions, tax domains, and other business or social criteria, and the like.
The data centers within a region can be further organized and subdivided into availability domains (ADs). An availability domain may correspond to one or more data centers located within a region. A region can be composed of one or more availability domains. In such a distributed environment, CSPI resources are either region-specific, such as a virtual cloud network (VCN), or availability domain-specific, such as a compute instance.
ADs within a region are isolated from each other, fault tolerant, and are configured such that they are very unlikely to fail simultaneously. This is achieved by the ADs not sharing critical infrastructure resources such as networking, physical cables, cable paths, cable entry points, etc., such that a failure at one AD within a region is unlikely to impact the availability of the other ADs within the same region. The ADs within the same region may be connected to each other by a low latency, high bandwidth network, which makes it possible to provide high-availability connectivity to other networks (e.g., the Internet, customers' on-premise networks, etc.) and to build replicated systems in multiple ADs for both high-availability and disaster recovery. Cloud services use multiple ADs to ensure high availability and to protect against resource failure. As the infrastructure provided by the IaaS provider grows, more regions and ADs may be added with additional capacity. Traffic between availability domains is usually encrypted.
In certain embodiments, regions are grouped into realms. A realm is a logical collection of regions. Realms are isolated from each other and do not share any data. Regions in the same realm may communicate with each other, but regions in different realms cannot. A customer's tenancy or account with the CSP exists in a single realm and can be spread across one or more regions that belong to that realm. Typically, when a customer subscribes to an IaaS service, a tenancy or account is created for that customer in the customer-specified region (referred to as the “home” region) within a realm. A customer can extend the customer's tenancy across one or more other regions within the realm. A customer cannot access regions that are not in the realm where the customer's tenancy exists.
An IaaS provider can provide multiple realms, each realm catered to a particular set of customers or users. For example, a commercial realm may be provided for commercial customers. As another example, a realm may be provided for a specific country for customers within that country. As yet another example, a government realm may be provided for a government, and the like. For example, the government realm may be catered for a specific government and may have a heightened level of security than a commercial realm. For example, Oracle Cloud Infrastructure (OCI) currently offers a realm for commercial regions and two realms (e.g., FedRAMP authorized and IL5 authorized) for government cloud regions.
In certain embodiments, an AD can be subdivided into one or more fault domains. A fault domain is a grouping of infrastructure resources within an AD to provide anti-affinity. Fault domains allow for the distribution of compute instances such that the instances are not on the same physical hardware within a single AD. This is known as anti-affinity. A fault domain refers to a set of hardware components (computers, switches, and more) that share a single point of failure. A compute pool is logically divided up into fault domains. Due to this, a hardware failure or compute hardware maintenance event that affects one fault domain does not affect instances in other fault domains. Depending on the embodiment, the number of fault domains for each AD may vary. For instance, in certain embodiments each AD contains three fault domains. A fault domain acts as a logical data center within an AD.
When a customer subscribes to an IaaS service, resources from CSPI are provisioned for the customer and associated with the customer's tenancy. The customer can use these provisioned resources to build private networks and deploy resources on these networks. The customer networks that are hosted in the cloud by the CSPI are referred to as virtual cloud networks (VCNs). A customer can set up one or more virtual cloud networks (VCNs) using CSPI resources allocated for the customer. A VCN is a virtual or software defined private network. The customer resources that are deployed in the customer's VCN can include compute instances (e.g., virtual machines, bare-metal instances) and other resources. These compute instances may represent various customer workloads such as applications, load balancers, databases, and the like. A compute instance deployed on a VCN can communicate with publicly accessible endpoints (“public endpoints”) over a public network such as the Internet, with other instances in the same VCN or other VCNs (e.g., the customer's other VCNs, or VCNs not belonging to the customer), with the customer's on-premise data centers or networks, and with service endpoints, and other types of endpoints.
The CSP may provide various services using the CSPI. In some instances, customers of CSPI may themselves act like service providers and provide services using CSPI resources. A service provider may expose a service endpoint, which is characterized by identification information (e.g., an IP Address, a DNS name and port). A customer's resource (e.g., a compute instance) can consume a particular service by accessing a service endpoint exposed by the service for that particular service. These service endpoints are generally endpoints that are publicly accessible by users using public IP addresses associated with the endpoints via a public communication network such as the Internet. Network endpoints that are publicly accessible are also sometimes referred to as public endpoints.
In certain embodiments, a service provider may expose a service via an endpoint (sometimes referred to as a service endpoint) for the service. Customers of the service can then use this service endpoint to access the service. In certain implementations, a service endpoint provided for a service can be accessed by multiple customers that intend to consume that service. In other implementations, a dedicated service endpoint may be provided for a customer such that only that customer can access the service using that dedicated service endpoint.
In certain embodiments, when a VCN is created, it is associated with a private overlay Classless Inter-Domain Routing (CIDR) address space, which is a range of private overlay IP addresses that are assigned to the VCN (e.g., 10.0/16). A VCN includes associated subnets, route tables, and gateways. A VCN resides within a single region but can span one or more or all of the region's availability domains. A gateway is a virtual interface that is configured for a VCN and enables communication of traffic to and from the VCN to one or more endpoints outside the VCN. One or more different types of gateways may be configured for a VCN to enable communication to and from different types of endpoints.
A VCN can be subdivided into one or more sub-networks such as one or more subnets. A subnet is thus a unit of configuration or a subdivision that can be created within a VCN. A VCN can have one or multiple subnets. Each subnet within a VCN is associated with a contiguous range of overlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do not overlap with other subnets in that VCN and which represent an address space subset within the address space of the VCN.
Each compute instance is associated with a virtual network interface card (VNIC), that enables the compute instance to participate in a subnet of a VCN. A VNIC is a logical representation of physical Network Interface Card (NIC). In general. a VNIC is an interface between an entity (e.g., a compute instance, a service) and a virtual network. A VNIC exists in a subnet, has one or more associated IP addresses, and associated security rules or policies. A VNIC is equivalent to a Layer-2 port on a switch. A VNIC is attached to a compute instance and to a subnet within a VCN. A VNIC associated with a compute instance enables the compute instance to be a part of a subnet of a VCN and enables the compute instance to communicate (e.g., send and receive packets) with endpoints that are on the same subnet as the compute instance, with endpoints in different subnets in the VCN, or with endpoints outside the VCN. The VNIC associated with a compute instance thus determines how the compute instance connects with endpoints inside and outside the VCN. A VNIC for a compute instance is created and associated with that compute instance when the compute instance is created and added to a subnet within a VCN. For a subnet comprising a set of compute instances, the subnet contains the VNICs corresponding to the set of compute instances, each VNIC attached to a compute instance within the set of computer instances.
Each compute instance is assigned a private overlay IP address via the VNIC associated with the compute instance. This private overlay IP address is assigned to the VNIC that is associated with the compute instance when the compute instance is created and used for routing traffic to and from the compute instance. All VNICs in a given subnet use the same route table, security lists, and DHCP options. As described above, each subnet within a VCN is associated with a contiguous range of overlay IP addresses (e.g., 10.0.0.0/24 and 10.0.1.0/24) that do not overlap with other subnets in that VCN and which represent an address space subset within the address space of the VCN. For a VNIC on a particular subnet of a VCN, the private overlay IP address that is assigned to the VNIC is an address from the contiguous range of overlay IP addresses allocated for the subnet.
In certain embodiments, a compute instance may optionally be assigned additional overlay IP addresses in addition to the private overlay IP address, such as, for example, one or more public IP addresses if in a public subnet. These multiple addresses are assigned either on the same VNIC or over multiple VNICs that are associated with the compute instance. Each instance however has a primary VNIC that is created during instance launch and is associated with the overlay private IP address assigned to the instance—this primary VNIC cannot be removed. Additional VNICs, referred to as secondary VNICs, can be added to an existing instance in the same availability domain as the primary VNIC. All the VNICs are in the same availability domain as the instance. A secondary VNIC can be in a subnet in the same VCN as the primary VNIC, or in a different subnet that is either in the same VCN or a different one.
A compute instance may optionally be assigned a public IP address if it is in a public subnet. A subnet can be designated as either a public subnet or a private subnet at the time the subnet is created. A private subnet means that the resources (e.g., compute instances) and associated VNICs in the subnet cannot have public overlay IP addresses. A public subnet means that the resources and associated VNICs in the subnet can have public IP addresses. A customer can designate a subnet to exist either in a single availability domain or across multiple availability domains in a region or realm.
As described above, a VCN may be subdivided into one or more subnets. In certain embodiments, a Virtual Router (VR) configured for the VCN (referred to as the VCN VR or just VR) enables communications between the subnets of the VCN. For a subnet within a VCN, the VR represents a logical gateway for that subnet that enables the subnet (i.e., the compute instances on that subnet) to communicate with endpoints on other subnets within the VCN, and with other endpoints outside the VCN. The VCN VR is a logical entity that is configured to route traffic between VNICs in the VCN and virtual gateways (“gateways”) associated with the VCN. Gateways are further described below with respect to
In some other embodiments, each subnet within a VCN may have its own associated VR that is addressable by the subnet using a reserved or default IP address associated with the VR. The reserved or default IP address may, for example, be the first IP address from the range of IP addresses associated with that subnet. The VNICs in the subnet can communicate (e.g., send and receive packets) with the VR associated with the subnet using this default or reserved IP address. In such an embodiment, the VR is the ingress/egress point for that subnet. The VR associated with a subnet within the VCN can communicate with other VRs associated with other subnets within the VCN. The VRs can also communicate with gateways associated with the VCN. The VR function for a subnet is running on or executed by one or more NVDs executing VNICs functionality for VNICs in the subnet.
Route tables, security rules, and DHCP options may be configured for a VCN. Route tables are virtual route tables for the VCN and include rules to route traffic from subnets within the VCN to destinations outside the VCN by way of gateways or specially configured instances. A VCN's route tables can be customized to control how packets are forwarded/routed to and from the VCN. DHCP options refers to configuration information that is automatically provided to the instances when they boot up.
Security rules configured for a VCN represent overlay firewall rules for the VCN. The security rules can include ingress and egress rules, and specify the types of traffic (e.g., based upon protocol and port) that is allowed in and out of the instances within the VCN. The customer can choose whether a given rule is stateful or stateless. For instance, the customer can allow incoming SSH traffic from anywhere to a set of instances by setting up a stateful ingress rule with source CIDR 0.0.0.0/0, and destination TCP port 22. Security rules can be implemented using network security groups or security lists. A network security group consists of a set of security rules that apply only to the resources in that group. A security list, on the other hand, includes rules that apply to all the resources in any subnet that uses the security list. A VCN may be provided with a default security list with default security rules. DHCP options configured for a VCN provide configuration information that is automatically provided to the instances in the VCN when the instances boot up.
In certain embodiments, the configuration information for a VCN is determined and stored by a VCN Control Plane. The configuration information for a VCN may include, for example, information about: the address range associated with the VCN, subnets within the VCN and associated information, one or more VRs associated with the VCN, compute instances in the VCN and associated VNICs, NVDs executing the various virtualization network functions (e.g., VNICs, VRs, gateways) associated with the VCN, state information for the VCN, and other VCN-related information. In certain embodiments, a VCN Distribution Service publishes the configuration information stored by the VCN Control Plane, or portions thereof, to the NVDs. The distributed information may be used to update information (e.g., forwarding tables, routing tables, etc.) stored and used by the NVDs to forward packets to and from the compute instances in the VCN.
In certain embodiments, the creation of VCNs and subnets are handled by a VCN Control Plane (CP) and the launching of compute instances is handled by a Compute Control Plane. The Compute Control Plane is responsible for allocating the physical resources for the compute instance and then calls the VCN Control Plane to create and attach VNICs to the compute instance. The VCN CP also sends VCN data mappings to the VCN data plane that is configured to perform packet forwarding and routing functions. In certain embodiments, the VCN CP provides a distribution service that is responsible for providing updates to the VCN data plane. Examples of a VCN Control Plane are also depicted in
A customer may create one or more VCNs using resources hosted by CSPI. A compute instance deployed on a customer VCN may communicate with different endpoints. These endpoints can include endpoints that are hosted by CSPI and endpoints outside CSPI.
Various different architectures for implementing cloud-based service using CSPI are depicted in
As shown in the example depicted in
In the embodiment depicted in
Multiple compute instances may be deployed on each subnet, where the compute instances can be virtual machine instances, and/or bare metal instances. The compute instances in a subnet may be hosted by one or more host machines within CSPI 101. A compute instance participates in a subnet via a VNIC associated with the compute instance. For example, as shown in
Subnet-2 can have multiple compute instances deployed on it, including virtual machine instances and/or bare metal instances. For example, as shown in
VCN A 104 may also include one or more load balancers. For example, a load balancer may be provided for a subnet and may be configured to load balance traffic across multiple compute instances on the subnet. A load balancer may also be provided to load balance traffic across subnets in the VCN.
A particular compute instance deployed on VCN 104 can communicate with various different endpoints. These endpoints may include endpoints that are hosted by CSPI 200 and endpoints outside CSPI 200. Endpoints that are hosted by CSPI 101 may include: an endpoint on the same subnet as the particular compute instance (e.g., communications between two compute instances in Subnet-1); an endpoint on a different subnet but within the same VCN (e.g., communication between a compute instance in Subnet-1 and a compute instance in Subnet-2); an endpoint in a different VCN in the same region (e.g., communications between a compute instance in Subnet-1 and an endpoint in a VCN in the same region 106 or 110, communications between a compute instance in Subnet-1 and an endpoint in service network 110 in the same region); or an endpoint in a VCN in a different region (e.g., communications between a compute instance in Subnet-1 and an endpoint in a VCN in a different region 108). A compute instance in a subnet hosted by CSPI 101 may also communicate with endpoints that are not hosted by CSPI 101 (i.e., are outside CSPI 101). These outside endpoints include endpoints in the customer's on-premise network 116, endpoints within other remote cloud hosted networks 118, public endpoints 114 accessible via a public network such as the Internet, and other endpoints.
Communications between compute instances on the same subnet are facilitated using VNICs associated with the source compute instance and the destination compute instance. For example, compute instance C1 in Subnet-1 may want to send packets to compute instance C2 in Subnet-1. For a packet originating at a source compute instance and whose destination is another compute instance in the same subnet, the packet is first processed by the VNIC associated with the source compute instance. Processing performed by the VNIC associated with the source compute instance can include determining destination information for the packet from the packet headers, identifying any policies (e.g., security lists) configured for the VNIC associated with the source compute instance, determining a next hop for the packet, performing any packet encapsulation/decapsulation functions as needed, and then forwarding/routing the packet to the next hop with the goal of facilitating communication of the packet to its intended destination. When the destination compute instance is in the same subnet as the source compute instance, the VNIC associated with the source compute instance is configured to identify the VNIC associated with the destination compute instance and forward the packet to that VNIC for processing. The VNIC associated with the destination compute instance is then executed and forwards the packet to the destination compute instance.
For a packet to be communicated from a compute instance in a subnet to an endpoint in a different subnet in the same VCN, the communication is facilitated by the VNICs associated with the source and destination compute instances and the VCN VR. For example, if compute instance C1 in Subnet-1 in
For a packet to be communicated from a compute instance in VCN 104 to an endpoint that is outside VCN 104, the communication is facilitated by the VNIC associated with the source compute instance, VCN VR 105, and gateways associated with VCN 104. One or more types of gateways may be associated with VCN 104. A gateway is an interface between a VCN and another endpoint, where another endpoint is outside the VCN. A gateway is a Layer-3/IP layer concept and enables a VCN to communicate with endpoints outside the VCN. A gateway thus facilitates traffic flow between a VCN and other VCNs or networks. Various different types of gateways may be configured for a VCN to facilitate different types of communications with different types of endpoints. Depending upon the gateway, the communications may be over public networks (e.g., the Internet) or over private networks. Various communication protocols may be used for these communications.
For example, compute instance C1 may want to communicate with an endpoint outside VCN 104. The packet may be first processed by the VNIC associated with source compute instance C1. The VNIC processing determines that the destination for the packet is outside the Subnet-1 of C1. The VNIC associated with C1 may forward the packet to VCN VR 105 for VCN 104. VCN VR 105 then processes the packet and as part of the processing, based upon the destination for the packet, determines a particular gateway associated with VCN 104 as the next hop for the packet. VCN VR 105 may then forward the packet to the particular identified gateway. For example, if the destination is an endpoint within the customer's on-premise network, then the packet may be forwarded by VCN VR 105 to Dynamic Routing Gateway (DRG) gateway 122 configured for VCN 104. The packet may then be forwarded from the gateway to a next hop to facilitate communication of the packet to it final intended destination.
Various different types of gateways may be configured for a VCN. Examples of gateways that may be configured for a VCN are depicted in
In certain embodiments, a Remote Peering Connection (RPC) can be added to a DRG, which allows a customer to peer one VCN with another VCN in a different region. Using such an RPC, customer VCN 104 can use DRG 122 to connect with a VCN 108 in another region. DRG 122 may also be used to communicate with other remote cloud networks 118, not hosted by CSPI 101 such as a Microsoft Azure cloud, Amazon AWS cloud, and others.
As shown in
A Network Address Translation (NAT) gateway 128 can be configured for customer's VCN 104 and enables cloud resources in the customer's VCN, which do not have dedicated public overlay IP addresses, access to the Internet and it does so without exposing those resources to direct incoming Internet connections (e.g., L4-L7 connections). This enables a private subnet within a VCN, such as private Subnet-1 in VCN 104, with private access to public endpoints on the Internet. In NAT gateways, connections can be initiated only from the private subnet to the public Internet and not from the Internet to the private subnet.
In certain embodiments, a Service Gateway (SGW) 126 can be configured for customer VCN 104 and provides a path for private network traffic between VCN 104 and supported services endpoints in a service network 110. In certain embodiments, service network 110 may be provided by the CSP and may provide various services. An example of such a service network is Oracle's Services Network, which provides various services that can be used by customers. For example, a compute instance (e.g., a database system) in a private subnet of customer VCN 104 can back up data to a service endpoint (e.g., Object Storage) without needing public IP addresses or access to the Internet. In certain embodiments, a VCN can have only one SGW, and connections can only be initiated from a subnet within the VCN and not from service network 110. If a VCN is peered with another, resources in the other VCN typically cannot access the SGW. Resources in on-premises networks that are connected to a VCN with FastConnect or VPN Connect can also use the service gateway configured for that VCN.
In certain implementations, SGW 126 uses the concept of a service Classless Inter-Domain Routing (CIDR) label, which is a string that represents all the regional public IP address ranges for the service or group of services of interest. The customer uses the service CIDR label when they configure the SGW and related route rules to control traffic to the service. The customer can optionally utilize it when configuring security rules without needing to adjust them if the service's public IP addresses change in the future.
A Local Peering Gateway (LPG) 132 is a gateway that can be added to customer VCN 104 and enables VCN 104 to peer with another VCN in the same region. Peering means that the VCNs communicate using private IP addresses, without the traffic traversing a public network such as the Internet or without routing the traffic through the customer's on-premises network 116. In preferred embodiments, a VCN has a separate LPG for each peering it establishes. Local Peering or VCN Peering is a common practice used to establish network connectivity between different applications or infrastructure management functions.
Service providers, such as providers of services in service network 110, may provide access to services using different access models. According to a public access model, services may be exposed as public endpoints that are publicly accessible by compute instance in a customer VCN via a public network such as the Internet and or may be privately accessible via SGW 126. According to a specific private access model, services are made accessible as private IP endpoints in a private subnet in the customer's VCN. This is referred to as a Private Endpoint (PE) access and enables a service provider to expose their service as an instance in the customer's private network. A Private Endpoint resource represents a service within the customer's VCN. Each PE manifests as a VNIC (referred to as a PE-VNIC, with one or more private IPs) in a subnet chosen by the customer in the customer's VCN. A PE thus provides a way to present a service within a private customer VCN subnet using a VNIC. Since the endpoint is exposed as a VNIC, all the features associates with a VNIC such as routing rules, security lists, etc., are now available for the PE VNIC.
A service provider can register their service to enable access through a PE. The provider can associate policies with the service that restricts the service's visibility to the customer tenancies. A provider can register multiple services under a single virtual IP address (VIP), especially for multi-tenant services. There may be multiple such private endpoints (in multiple VCNs) that represent the same service.
Compute instances in the private subnet can then use the PE VNIC's private IP address or the service DNS name to access the service. Compute instances in the customer VCN can access the service by sending traffic to the private IP address of the PE in the customer VCN. A Private Access Gateway (PAGW) 130 is a gateway resource that can be attached to a service provider VCN (e.g., a VCN in service network 110) that acts as an ingress/egress point for all traffic from/to customer subnet private endpoints. PAGW 130 enables a provider to scale the number of PE connections without utilizing its internal IP address resources. A provider needs only configure one PAGW for any number of services registered in a single VCN. Providers can represent a service as a private endpoint in multiple VCNs of one or more customers. From the customer's perspective, the PE VNIC, which, instead of being attached to a customer's instance, appears attached to the service with which the customer wishes to interact. The traffic destined to the private endpoint is routed via PAGW 130 to the service. These are referred to as customer-to-service private connections (C2S connections).
The PE concept can also be used to extend the private access for the service to customer's on-premises networks and data centers, by allowing the traffic to flow through FastConnect/IPsec links and the private endpoint in the customer VCN. Private access for the service can also be extended to the customer's peered VCNs, by allowing the traffic to flow between LPG 132 and the PE in the customer's VCN.
A customer can control routing in a VCN at the subnet level, so the customer can specify which subnets in the customer's VCN, such as VCN 104, use each gateway. A VCN's route tables are used to decide if traffic is allowed out of a VCN through a particular gateway. For example, in a particular instance, a route table for a public subnet within customer VCN 104 may send non-local traffic through IGW 120. The route table for a private subnet within the same customer VCN 104 may send traffic destined for CSP services through SGW 126. All remaining traffic may be sent via the NAT gateway 128. Route tables only control traffic going out of a VCN.
Security lists associated with a VCN are used to control traffic that comes into a VCN via a gateway via inbound connections. All resources in a subnet use the same route table and security lists. Security lists may be used to control specific types of traffic allowed in and out of instances in a subnet of a VCN. Security list rules may comprise ingress (inbound) and egress (outbound) rules. For example, an ingress rule may specify an allowed source address range, while an egress rule may specify an allowed destination address range. Security rules may specify a particular protocol (e.g., TCP, ICMP), a particular port (e.g., 22 for SSH, 3389 for Windows RDP), etc. In certain implementations, an instance's operating system may enforce its own firewall rules that are aligned with the security list rules. Rules may be stateful (e.g., a connection is tracked and the response is automatically allowed without an explicit security list rule for the response traffic) or stateless.
Access from a customer VCN (i.e., by a resource or compute instance deployed on VCN 104) can be categorized as public access, private access, or dedicated access. Public access refers to an access model where a public IP address or a NAT is used to access a public endpoint. Private access enables customer workloads in VCN 104 with private IP addresses (e.g., resources in a private subnet) to access services without traversing a public network such as the Internet. In certain embodiments, CSPI 101 enables customer VCN workloads with private IP addresses to access the (public service endpoints of) services using a service gateway. A service gateway thus offers a private access model by establishing a virtual link between the customer's VCN and the service's public endpoint residing outside the customer's private network.
Additionally, CSPI may offer dedicated public access using technologies such as FastConnect public peering where customer on-premises instances can access one or more services in a customer VCN using a FastConnect connection and without traversing a public network such as the Internet. CSPI also may also offer dedicated private access using FastConnect private peering where customer on-premises instances with private IP addresses can access the customer's VCN workloads using a FastConnect connection. FastConnect is a network connectivity alternative to using the public Internet to connect a customer's on-premise network to CSPI and its services. FastConnect provides an easy, elastic, and economical way to create a dedicated and private connection with higher bandwidth options and a more reliable and consistent networking experience when compared to Internet-based connections.
In the example embodiment depicted in
The host machines or servers may execute a hypervisor (also referred to as a virtual machine monitor or VMM) that creates and enables a virtualized environment on the host machines. The virtualization or virtualized environment facilitates cloud-based computing. One or more compute instances may be created, executed, and managed on a host machine by a hypervisor on that host machine. The hypervisor on a host machine enables the physical computing resources of the host machine (e.g., compute, memory, and networking resources) to be shared between the various compute instances executed by the host machine.
For example, as depicted in
A compute instance can be a virtual machine instance or a bare metal instance. In
In certain instances, an entire host machine may be provisioned to a single customer, and all of the one or more compute instances (either virtual machines or bare metal instance) hosted by that host machine belong to that same customer. In other instances, a host machine may be shared between multiple customers (i.e., multiple tenants). In such a multi-tenancy scenario, a host machine may host virtual machine compute instances belonging to different customers. These compute instances may be members of different VCNs of different customers. In certain embodiments, a bare metal compute instance is hosted by a bare metal server without a hypervisor. When a bare metal compute instance is provisioned, a single customer or tenant maintains control of the physical CPU, memory, and network interfaces of the host machine hosting the bare metal instance and the host machine is not shared with other customers or tenants.
As previously described, each compute instance that is part of a VCN is associated with a VNIC that enables the compute instance to become a member of a subnet of the VCN. The VNIC associated with a compute instance facilitates the communication of packets or frames to and from the compute instance. A VNIC is associated with a compute instance when the compute instance is created. In certain embodiments, for a compute instance executed by a host machine, the VNIC associated with that compute instance is executed by an NVD connected to the host machine. For example, in
For compute instances hosted by a host machine, an NVD connected to that host machine also executes VCN VRs corresponding to VCNs of which the compute instances are members. For example, in the embodiment depicted in
A host machine may include one or more network interface cards (NIC) that enable the host machine to be connected to other devices. A NIC on a host machine may provide one or more ports (or interfaces) that enable the host machine to be communicatively connected to another device. For example, a host machine may be connected to an NVD using one or more ports (or interfaces) provided on the host machine and on the NVD. A host machine may also be connected to other devices such as another host machine.
For example, in
The NVDs are in turn connected via communication links to top-of-the-rack (TOR) switches, which are connected to physical network 218 (also referred to as the switch fabric). In certain embodiments, the links between a host machine and an NVD, and between an NVD and a TOR switch are Ethernet links. For example, in
Physical network 218 provides a communication fabric that enables TOR switches to communicate with each other. Physical network 218 can be a multi-tiered network. In certain implementations, physical network 218 is a multi-tiered Clos network of switches, with TOR switches 214 and 216 representing the leaf level nodes of the multi-tiered and multi-node physical switching network 218. Different Clos network configurations are possible including but not limited to a 2-tier network, a 3-tier network, a 4-tier network, a 5-tier network, and in general a “n”-tiered network. An example of a Clos network is depicted in
Various different connection configurations are possible between host machines and NVDs such as one-to-one configuration, many-to-one configuration, one-to-many configuration, and others. In a one-to-one configuration implementation, each host machine is connected to its own separate NVD. For example, in
In a one-to-many configuration, one host machine is connected to multiple NVDs.
The arrangement depicted in
In the configuration depicted in
Referring back to
An NVD may be implemented in various different forms. For example, in certain embodiments, an NVD is implemented as an interface card referred to as a smartNIC or an intelligent NIC with an embedded processor onboard. A smartNIC is a separate device from the NICs on the host machines. In
A smartNIC is however just one example of an NVD implementation. Various other implementations are possible. For example, in some other implementations, an NVD or one or more functions performed by the NVD may be incorporated into or performed by one or more host machines, one or more TOR switches, and other components of CSPI 200. For example, an NVD may be embodied in a host machine where the functions performed by an NVD are performed by the host machine. As another example, an NVD may be part of a TOR switch or a TOR switch may be configured to perform functions performed by an NVD that enables the TOR switch to perform various complex packet transformations that are used for a public cloud. A TOR that performs the functions of an NVD is sometimes referred to as a smart TOR. In yet other implementations, where virtual machines (VMs) instances, but not bare metal (BM) instances, are offered to customers, functions performed by an NVD may be implemented inside a hypervisor of the host machine. In some other implementations, some of the functions of the NVD may be offloaded to a centralized service running on a fleet of host machines.
In certain embodiments, such as when implemented as a smartNIC as shown in
An NVD receives packets and frames from a host machine (e.g., packets and frames generated by a compute instance hosted by the host machine) via a host-facing port and, after performing the necessary packet processing, may forward the packets and frames to a TOR switch via a network-facing port of the NVD. An NVD may receive packets and frames from a TOR switch via a network-facing port of the NVD and, after performing the necessary packet processing, may forward the packets and frames to a host machine via a host-facing port of the NVD.
In certain embodiments, there may be multiple ports and associated links between an NVD and a TOR switch. These ports and links may be aggregated to form a link aggregator group of multiple ports or links (referred to as a LAG). Link aggregation allows multiple physical links between two end-points (e.g., between an NVD and a TOR switch) to be treated as a single logical link. All the physical links in a given LAG may operate in full-duplex mode at the same speed. LAGs help increase the bandwidth and reliability of the connection between two endpoints. If one of the physical links in the LAG goes down, traffic is dynamically and transparently reassigned to one of the other physical links in the LAG. The aggregated physical links deliver higher bandwidth than each individual link. The multiple ports associated with a LAG are treated as a single logical port. Traffic can be load-balanced across the multiple physical links of a LAG. One or more LAGs may be configured between two endpoints. The two endpoints may be between an NVD and a TOR switch, between a host machine and an NVD, and the like.
An NVD implements or performs network virtualization functions. These functions are performed by software/firmware executed by the NVD. Examples of network virtualization functions include without limitation: packet encapsulation and de-capsulation functions; functions for creating a VCN network; functions for implementing network policies such as VCN security list (firewall) functionality; functions that facilitate the routing and forwarding of packets to and from compute instances in a VCN; and the like. In certain embodiments, upon receiving a packet, an NVD is configured to execute a packet processing pipeline for processing the packet and determining how the packet is to be forwarded or routed. As part of this packet processing pipeline, the NVD may execute one or more virtual functions associated with the overlay network such as executing VNICs associated with compute instances in the VCN, executing a Virtual Router (VR) associated with the VCN, the encapsulation and decapsulation of packets to facilitate forwarding or routing in the virtual network, execution of certain gateways (e.g., the Local Peering Gateway), the implementation of Security Lists, Network Security Groups, network address translation (NAT) functionality (e.g., the translation of Public IP to Private IP on a host by host basis), throttling functions, and other functions.
In certain embodiments, the packet processing data path in an NVD may comprise multiple packet pipelines, each composed of a series of packet transformation stages. In certain implementations, upon receiving a packet, the packet is parsed and classified to a single pipeline. The packet is then processed in a linear fashion, one stage after another, until the packet is either dropped or sent out over an interface of the NVD. These stages provide basic functional packet processing building blocks (e.g., validating headers, enforcing throttle, inserting new Layer-2 headers, enforcing L4 firewall, VCN encapsulation/decapsulation, etc.) so that new pipelines can be constructed by composing existing stages, and new functionality can be added by creating new stages and inserting them into existing pipelines.
An NVD may perform both control plane and data plane functions corresponding to a control plane and a data plane of a VCN. Examples of a VCN Control Plane are also depicted in
As indicated above, an NVD executes various virtualization functions including VNICs and VCN VRs. An NVD may execute VNICs associated with the compute instances hosted by one or more host machines connected to the VNIC. For example, as depicted in
An NVD also executes VCN Virtual Routers corresponding to the VCNs of the compute instances. For example, in the embodiment depicted in
In addition to VNICs and VCN VRs, an NVD may execute various software (e.g., daemons) and include one or more hardware components that facilitate the various network virtualization functions performed by the NVD. For purposes of simplicity, these various components are grouped together as “packet processing components” shown in
As described above, a compute instance in a customer VCN may communicate with various different endpoints, where the endpoints can be within the same subnet as the source compute instance, in a different subnet but within the same VCN as the source compute instance, or with an endpoint that is outside the VCN of the source compute instance. These communications are facilitated using VNICs associated with the compute instances, the VCN VRs, and the gateways associated with the VCNs.
For communications between two compute instances on the same subnet in a VCN, the communication is facilitated using VNICs associated with the source and destination compute instances. The source and destination compute instances may be hosted by the same host machine or by different host machines. A packet originating from a source compute instance may be forwarded from a host machine hosting the source compute instance to an NVD connected to that host machine. On the NVD, the packet is processed using a packet processing pipeline, which can include execution of the VNIC associated with the source compute instance. Since the destination endpoint for the packet is within the same subnet, execution of the VNIC associated with the source compute instance results in the packet being forwarded to an NVD executing the VNIC associated with the destination compute instance, which then processes and forwards the packet to the destination compute instance. The VNICs associated with the source and destination compute instances may be executed on the same NVD (e.g., when both the source and destination compute instances are hosted by the same host machine) or on different NVDs (e.g., when the source and destination compute instances are hosted by different host machines connected to different NVDs). The VNICs may use routing/forwarding tables stored by the NVD to determine the next hop for the packet.
For a packet to be communicated from a compute instance in a subnet to an endpoint in a different subnet in the same VCN, the packet originating from the source compute instance is communicated from the host machine hosting the source compute instance to the NVD connected to that host machine. On the NVD, the packet is processed using a packet processing pipeline, which can include execution of one or more VNICs, and the VR associated with the VCN. For example, as part of the packet processing pipeline, the NVD executes or invokes functionality corresponding to the VNIC (also referred to as executes the VNIC) associated with source compute instance. The functionality performed by the VNIC may include looking at the VLAN tag on the packet. Since the packet's destination is outside the subnet, the VCN VR functionality is next invoked and executed by the NVD. The VCN VR then routes the packet to the NVD executing the VNIC associated with the destination compute instance. The VNIC associated with the destination compute instance then processes the packet and forwards the packet to the destination compute instance. The VNICs associated with the source and destination compute instances may be executed on the same NVD (e.g., when both the source and destination compute instances are hosted by the same host machine) or on different NVDs (e.g., when the source and destination compute instances are hosted by different host machines connected to different NVDs).
If the destination for the packet is outside the VCN of the source compute instance, then the packet originating from the source compute instance is communicated from the host machine hosting the source compute instance to the NVD connected to that host machine. The NVD executes the VNIC associated with the source compute instance. Since the destination end point of the packet is outside the VCN, the packet is then processed by the VCN VR for that VCN. The NVD invokes the VCN VR functionality, which may result in the packet being forwarded to an NVD executing the appropriate gateway associated with the VCN. For example, if the destination is an endpoint within the customer's on-premise network, then the packet may be forwarded by the VCN VR to the NVD executing the DRG gateway configured for the VCN. The VCN VR may be executed on the same NVD as the NVD executing the VNIC associated with the source compute instance or by a different NVD. The gateway may be executed by an NVD, which may be a smartNIC, a host machine, or other NVD implementation. The packet is then processed by the gateway and forwarded to a next hop that facilitates communication of the packet to its intended destination endpoint. For example, in the embodiment depicted in
A compute instance deployed on a VCN can communicate with various different endpoints. These endpoints may include endpoints that are hosted by CSPI 200 and endpoints outside CSPI 200. Endpoints hosted by CSPI 200 may include instances in the same VCN or other VCNs, which may be the customer's VCNs, or VCNs not belonging to the customer. Communications between endpoints hosted by CSPI 200 may be performed over physical network 218. A compute instance may also communicate with endpoints that are not hosted by CSPI 200, or are outside CSPI 200. Examples of these endpoints include endpoints within a customer's on-premise network or data center, or public endpoints accessible over a public network such as the Internet. Communications with endpoints outside CSPI 200 may be performed over public networks (e.g., the Internet) (not shown in
The architecture of CSPI 200 depicted in
As shown in
In certain 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 separate VLAN ID is assigned to logical NIC B 418 for Tenant #2. When a packet is communicated from VM1 406, a tag assigned to Tenant #1 is attached to the packet by the hypervisor and the packet is then communicated from host machine 402 to NVD 412 over link 414. In a similar manner, when a packet is communicated from VM2 408, a tag assigned to Tenant #2 is attached to the packet by the hypervisor and the packet is then communicated from host machine 402 to NVD 412 over link 414. Accordingly, a packet 424 communicated from host machine 402 to NVD 412 has an associated tag 426 that identifies a specific tenant and associated VM. On the NVD, for a packet 424 received from host machine 402, the tag 426 associated with the packet is used to determine whether the packet is to be processed by VNIC-VM1 420 or by VNIC-VM2 422. The packet is then processed by the corresponding VNIC. The configuration depicted in
A feature of a Clos network is that the maximum hop count to reach from one Tier-0 switch to another Tier-0 switch (or from an NVD connected to a Tier-0-switch to another NVD connected to a Tier-0 switch) is fixed. For example, in a 3-Tiered Clos network at most seven hops are needed for a packet to reach from one NVD to another NVD, where the source and target NVDs are connected to the leaf tier of the Clos network. Likewise, in a 4-tiered Clos network, at most nine hops are needed for a packet to reach from one NVD to another NVD, where the source and target NVDs are connected to the leaf tier of the Clos network. Thus, a Clos network architecture maintains consistent latency throughout the network, which is important for communication within and between data centers. A Clos topology scales horizontally and is cost effective. The bandwidth/throughput capacity of the network can be easily increased by adding more switches at the various tiers (e.g., more leaf and spine switches) and by increasing the number of links between the switches at adjacent tiers.
In certain embodiments, each resource within CSPI is assigned a unique identifier called a Cloud Identifier (CID). This identifier is included as part of the resource's information and can be used to manage the resource, for example, via a Console or through APIs. An example syntax for a CID is:
Techniques are described herein that enable cloud infrastructure in a region provided by a Cloud Services Provider (CSP), for providing CSP-offered cloud services to customers of the CSP, to be used to create one or more virtual private clouds (referred to herein as virtual private label clouds or “vPLCs”). The vPLCs created according to the various techniques described in this disclosure may be used for different purposes. For example, in one use case, a vPLC may be created for a reseller who is a customer of the CSP and can be used by the reseller to provide one or more reseller-offered cloud services to customers of the reseller. As another use case, a vPLC may be used as a virtual data center and may be associated with a different realm than the realm associated with the cloud infrastructure in the region provided by the CSP.
A cloud service provider (CSP) provides infrastructure (referred to as cloud service provider infrastructure or CSPI or CSP-provided infrastructure) that is used to provide one or more cloud services to customers of the CSP. The CSP customers can include direct customers of the CSP and/or resellers. The CSPI may include physical infrastructure components and virtual infrastructure components. The physical CSPI may comprise interconnected high-performance compute resources including racks, servers and host machines, memory resources, network resources that are used to form a physical substrate or underlay network, network virtualization devices, and other resources. The virtual CSPI components may include components in the overly network such as virtual machines, virtual routers and gateways, and other virtual components.
A CSP may offer various types of cloud services. These may include various types of services including Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (IaaS), and others. In certain embodiments, as described in this disclosure, the CSP may offer a “vPLC cloud service.” A customer of the CSP can subscribe to one or more cloud services provided by the CSP. The customer can be any entity such as an individual, an organization, an enterprise, and the like.
Infrastructure-as-a-Service (IaaS) is a particular type of cloud computing service. In an IaaS model, the CSP provides infrastructure that can be used by customers to build their own customizable networks and deploy customer resources. The customer's resources and networks are thus hosted in a distributed environment by infrastructure provided by a CSP. This is different from traditional computing, where the customer's resources and networks are hosted by infrastructure provided by the customer. In certain embodiments, vPLC-as-a-service is a type of IaaS service where infrastructure is allocated for creating a virtual private label cloud for a customer. For example, if the customer of the CSP is a reseller, the vPLC created for the reseller can be used to provide reseller-offered cloud services.
When a customer subscribes to or registers for a cloud service provided by a CSP, a tenancy (or an account) is created for that customer. The customer can then, via this account/tenancy, access the subscribed-to one or more cloud resources associated with the account/tenancy. Each tenancy is identified by a tenancy identifier (T_ID) that is assigned to the tenancy and uniquely identifies the tenancy. The tenancy identifier is generated and associated with a tenancy when the tenancy is created. For example, when a direct customer of the CSP subscribes to a service provided by the CSP, a tenancy is created for the customer and a tenancy identifier that uniquely identifies that tenancy is created for the direct customer. When a reseller subscribes to the vPLC service, a tenancy is created for the reseller and a tenancy identifier that uniquely identifies that tenancy is created for that reseller. A tenancy may be a logical and secure compartment that contains all the resources and services utilized by the customer associated with the tenancy.
Resources within CSP-provided infrastructure are typically identified using unique resource identifiers (resource ID or RID). Since these resources are provided in a cloud and used for providing cloud services, the resource IDs are also referred to as cloud resource identifiers (or cloud IDs or CIDs). For example, in the cloud environment provided by Oracle Corporation, resources are identified using “ocids” or “Oracle cloud identifiers.” In certain implementations, a resource ID is a globally unique identifier string that identifies a cloud resource. In some implementations, a tenancy ID is a type of cloud resource ID (or called cloud identifier (CID)).
A resource or cloud ID (CID) may be represented, as an example, in the following format:
CIDs are generated for resources at the time of creation of those resources. Virtual machines, accounts, tenancies, authorization policies, virtual network subnets, access control lists (ACLs), and load balancers are examples of cloud resources and can therefore be referenced by their respective CIDs. A tenancy is a logical container used to group other cloud resources that belong to the same cloud customer account.
When an entity becomes a customer of the CSP and subscribes to the vPLC service, a vPLC is created for the customer and associated with the tenancy of the customer. For example, if the customer is a reseller, a vPLC is created for the reseller and associated with the tenancy of the reseller. The vPLC that is created for the reseller is treated as a resource and assigned a unique resource identifier, which is referred to as a vPLC identifier (vPLC ID) and the vPLC ID is associated with the reseller's tenancy. As described herein, for a vPLC created for a reseller, the vPLC ID for the vPLC is used to identify all resources and requests related to vPLC. Each vPLC ID uniquely identifies a vPLC.
For example, in certain implementations, all resources allocated to a vPLC are tagged with the vPLC identifier for that vPLC. In certain implementations, a vPLC ID field is inserted in the representation of the CID described above. When a resource is associated with a vPLC, the vPLC ID corresponding to that vPLC may be provided in this field of the CID, else the field may be left blank if the resource is not associated with a vPLC.
For the purpose of present disclosure, the following terminologies are used for clarity.
As describe herein, a vPLC is created for a reseller, who is a customer of the CSP. The vPLC is associated with the tenancy for the reseller. In certain implementations, the vPLC ID identifying the vPLC may be associated with the tenancy ID identifying the tenancy for the reseller. Accordingly, given a vPLC ID, the corresponding vPLC and the reseller for whom the vPLC is created, including the tenancy and tenancy identifier for the reseller, can be identified.
The CSPI or CSP-provided infrastructure may be organized into realms, regions, and data centers. A region refers to a localized geographic area comprising one or more connected data centers. Regions are independent of other regions and can be separated by vast distances, for example, across countries or even continents. A set of application programming interfaces (APIs) is provided for CSP-provided infrastructure in a region, where the APIs are used to perform operations using the infrastructure in the region. Operations that may be performed using infrastructure in a region may include creating a resource in infrastructure in the region, accessing a resource in infrastructure in a region, performing an operation involving a resource in infrastructure in the region, deleting a resource from infrastructure in the region, and performing other operations involving infrastructure in the region.
The set of APIs are region-specific. Accordingly, CSP-provided infrastructure in a region is characterized by a set of APIs that can be used with the infrastructure in the region. CSP-provided infrastructure in a different region has a different set of APIs that are provided for that different region. Accordingly, for purposes of this application, the phrase “CSP-provided infrastructure in a region” or “infrastructure provided by the CSP in a region” means that the infrastructure is characterized by a particular set of APIs provided for that region. Accordingly. a first set of APIs may be provided for a first region, a second set of APIs may be provided for a for a second region that is different from the first region, a third set of APIs may be provided for a third region that is different from the first and second regions, and so on. A particular set of APIs thus identifies CSP-provided infrastructure in a specific region. In other words, CSP-provided infrastructures in two separate regions will have two separate sets of APIs. A region is thus characterized by infrastructure in the region and a set of APIs associated with the region to perform operations involving the regional infrastructure. The CSP-provided infrastructure in a region is also referred to as “regional infrastructure” or “region-specific infrastructure.”
For example, a CSP may provide first infrastructure in Seattle and second infrastructure in Portland. A first set of APIs may be provided for the first infrastructure in Seattle and these APIs may be characterized by the following format:
The CSP-provided infrastructure in a region may be organized into one or more data centers. For example, in a particular region where the CSP may have two buildings, each building hosting infrastructure that is used to provide cloud services, the infrastructure in the first building may be organized and referred to as a first data center and the infrastructure in the second building may be organized and referred to as a second data center. As another example, in a particular region where the CSP may have a single building with multiple floors, each floor hosting infrastructure that is used to provide cloud services, the infrastructure on a first floor may be organized and referred to as a first data center and the infrastructure on the second floor may be organized and referred to as a second data center. As yet another example, in a particular region where the CSP may have infrastructure that is used to provide cloud services, a first portion of the infrastructure may be organized and referred to as a first data center and a second separate portion of the infrastructure may be organized and referred to as a second data center.
A region may have one or more data centers. In certain implementations, all the regional infrastructure may be contained in only one data center, while in other implementations, infrastructure in a region can have organized into multiple data centers. Each data center may include infrastructure resources, such as compute, storage, and networking resources, that the CSP provides. Within a region, the data centers in the region may be organized into one or more availability domains (ADs). Availability domains are isolated from each other, fault-tolerant, and very unlikely to fail simultaneously. ADs are configured such that a failure at one AD within a region is unlikely to impact the availability of the other ADs within the same region.
A realm refers to a logical collection of one or more regions. A realm can include one or more regions. Realms are typically isolated from each other and do not share data. Each realm has its own identity and trust profile (e.g., passwords, credentials, etc.). The identity and trust profile for a realm is configured such that cross-realm communications are not allowed. In this manner, each realm represents an isolated domain. For example, one realm may be created for a government entity that is a customer of the CSP, another realm may be created for commercial customers of the CSP, and yet a separate realm may be created for certain private party customers of the CSP, and the like. For regions within a realm, the regional-infrastructures can communicate with each other, but a regional-infrastructure associated a first realm is not allowed to communicate with a regional-infrastructure associated with a second different realm.
A cloud services reseller can be an entity such as a corporation (e.g., a telecom company), a system integrator, a government agency, an IT department of a big corporation, a school, etc.
CSP-provided regional infrastructure 601 may be used by the CSP to provide one or more CSP-offered cloud services to one or more direct customers of the CSP and can also be used to create one or more vPLCs. In the example depicted in
As shown, infrastructure 601 can be communicatively coupled with computing devices used by users associated with direct customers 640 and with computing devices used by users associated with customers of resellers (e.g., users associated with customers 642 of reseller R1 and users associated with customers 644 of reseller R2) via communication network 652. Communication network 652 can be of various types and can include one or more communication networks. Examples of communication network 652 include, without restriction, the Internet, a wide area network (WAN), a local area network (LAN), an Ethernet network, a public or private network, a wired network, a wireless network, and the like, and combinations thereof. Different communication protocols may be used to facilitate the communications including both wired and wireless protocols such as IEEE 802.XX suite of protocols, TCP/IP, IPX, SAN, AppleTalk®, Bluetooth®, and other protocols. In general, communication network 652 may include any infrastructure that facilitates communications with infrastructure 601.
As shown in
Partitioning of the resources includes partitioning storage resources 622 and compute resources 620. For example, as shown in
As also shown in
As described above, a set of APIs are provided for accessing and performing functions with respect to CSP-provided infrastructure in a region. These set of APIs can be accessed by users associated with direct customers 640 of the CSP using a set of end points 610-1 provided by the CSP. For example, one or more of endpoints 610-1 may be used by users to access and/or use compute resources 620a or memory resources 622a allocated to infrastructure that is used to provide CSP-offered cloud service to the CSP's customers. An endpoint in 610-1 may refer to an URL with an associated fully qualified domain name (FQDN) that is used to access cloud services provided by infrastructure 601. Example of these endpoints:
In certain embodiments, a set of vPLC-specific endpoints are created for each vPLC. For example, as depicted in
In certain implementations, a set of vPLC-specific endpoints for a vPLC is created based upon endpoints provided by the CSP for its direct customers. For example, in
Endpoints 614-1 for vPLC R2 may also be created based upon endpoints 610-1. For example, the endpoints 614-1 for vPLC.R2 may include:
Since endpoints associated with a vPLC include an identifier identifying a particular vPLC, when an API call is received by infrastructure 601, the endpoint invocation can be parsed to determine whether the invocation is for a direct customer of the CSP or for a reseller. Further, since the endpoints use unique identifiers for the different vPLCs, the particular vPLC and the associated reseller can also be identified from the endpoint invocation. In this manner, based upon the results of parsing of the endpoint invocation, the endpoint request can be appropriately forwarded to be processed.
The CSP also provides a console 610-2 for use by its direct customers 640. Users associated with direct customers 640 of the CSP can use console 610-2 to configure, access and manage the first portion 602 of the CSP-provided regional infrastructure. In certain implementations, console 610-2 can provide a set of web-based graphical user interfaces (GUI) that can be used to access and manage CSP-provided cloud infrastructure in the region. In some implementations, the console is a web-based application.
In certain embodiments, a console is also provided for each vPLC. For example, as depicted in
In some embodiments, a reseller may subscribe to two or more vPLCs, but each vPLC can still have a set of endpoints and a console. For example, if a reseller subscribes to two vPLCs, vPLC 1 and vPLC 2, then vPLC 1 may have a set of endpoints (e.g., 612-1) and a console (e.g., 612-2), and vPLC 2 (e.g., 614-1) may have another set of endpoints and a console (e.g., 614-2). Both vPLC 1 (e.g., 604) and vPLC 2 (606) may be associated with the same reseller.
Infrastructure 601 may include networking resources that enable communications to and from infrastructure 601. These network resources may include, for example, a network gateway 628 may be provided that enables communication of traffic to and from the CSP-provided regional infrastructure 601 to other destinations, where a destination may be communicatively coupled to infrastructure 601 via a public (e.g., the Internet) or private network, the destination may be in an on-premise network, in another cloud network, and the like. Gateway 628 may be implemented as a physical network device (e.g., a router), as a logical networking component (e.g., a virtual router), or some combination of a physical component and a logical component.
Infrastructure 601 may include a control plane (CP) 624 and a management plane (MP) 626 provided by CSP. In certain embodiments, CP 624 may be responsible for providing management, deployment, and orchestration functions within a cloud environment provided by a CSP. For example, CP may receive requests from the direct customers of CSP, customers of reseller R1, and customers of reseller R2, through endpoints and consoles, work with other components in the infrastructure, such as resource manager and management plane, to determine whether the requests can be fulfilled, and respond to the direct customers of CSP, customers of reseller R1, and customers of reseller R2, accordingly. In other words, CSP CP 624 may be responsible for performing vPLC related functions. In certain embodiments, the CSP may also provide vPLC-specific control planes that are configured specifically for performing vPLC operations. In some embodiments, there may be one vPLC control plane, that can perform processing for multiple vPLCs. In other embodiments, each vPLC may be provided its own CP.
In some embodiments, MP 626 may be a collection of software components that are responsible for provisioning all the processes and workflows that are needed for a requested operation. For example, for a service request to access a cloud service, the MP may provision a workflow that involves identity check for the requester and checking a DNS record to obtain an IP address for accessing a service backend. The MP ensures different tasks are performed properly and in the right order by the data plane.
In certain implementations, compute resources 620 can include one or more racks, each rack comprising one or more servers, and each server hosting one or more operating systems. Partitioning of compute resources 620 into resources 620a that are allocated to infrastructure for servicing the CSP's direct customers 640 and resources 620b and 620c that are allocated to the vPLCs can be done along different levels or boundaries. The partitioning of compute resources at a particular level may also be referred to herein as segmentation level. In certain implementations, the partitioning may be performed at the rack-level (i.e., segmented at the rack-level), where one or more individual racks are allocated to 620a, 620b, and 620c. In this implementation, a rack is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers 640.
In another implementation, the partitioning may be performed at the server level (i.e., segmented at the server-level), where one or more individual servers from the same or different racks are allocated to 620a, 620b, and 620c. In this implementation, a server is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers 640. Since a rack can have multiple servers, one server on the rack may be allocated to 620a, another server to 620b, and a third server to 620c. Thus, a rack may be shared between two vPLCs, or between infrastructure used by the CSP for providing CSP-offered services to its direct customers 640 and a vPLC.
In some implementations, the partitioning may be performed at the hypervisor level (i.e., segmented at the hypervisor-level), where one or more individual hypervisors from the same or different servers on the same or different racks are allocated to 620a, 620b, and 620c. In this implementation, a hypervisor is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers 640. Since a server can host multiple hypervisors, one hypervisor on the server may be allocated to 620a, another hypervisor on the same server may be allocated to 620b, and a third hypervisor on the same server may be allocated to 620c. Thus, a server may be shared between two vPLCs, or between infrastructure used by the CSP for providing CSP-offered services to its direct customers 640 and a vPLC.
A hypervisor on a server on a rack can manage and execute multiple virtual machines (VMs). In some implementations, the partitioning may be performed at the VM-level (i.e., segmented at the VM-level), where VMs executed by the same hypervisor can be allocated to 620a, 620b, and 620c. In this implementation, a VM is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers 640. Since a hypervisor can support multiple VMs, one VM may be allocated to 620a, another VM to 620b, and a third VM on the same hypervisor may be allocated to 620c. Thus, a hypervisor may be shared between two vPLCs, or between infrastructure used by the CSP for providing CSP-offered services to its direct customers 640 and a vPLC.
In yet other embodiments, a combination of the above partitioning techniques may be used. Irrespective of the partitioning technique used, the partitioning is done in a secure and safe manner, which ensure that traffic and storage intended for a particular vPLC for a particular reseller cannot be seen or accessed by other resellers or their customers, or by other direct customers of the CSP. Also, traffic and storage intended for a particular customer of a reseller cannot be seen or accessed by other customers of that reseller.
Customers 702 of CSP 710 may include direct or non-reseller customers and reseller customers. A reseller customer is an entity that subscribes to the vPLC service provided by the CSP and the vPLC created for the reseller as a result of subscribing to the vPLC service is used to provide reseller-offered and reseller-branded cloud services to customers of the reseller. The customer of a reseller may be different from the customers of the CSP. A direct or non-reseller customer of the CSP is an entity that subscribes to one or more CSP-offered cloud services but does not have use the CSP's infrastructure to provide any cloud services of its own to its customers.
In the example depicted in
In the depicted in
A reseller may in turn have its own customers that subscribe to one or more reseller-offered and reseller-branded cloud services, where the reseller-offered and branded cloud services are provided using a vPLC created by the CSP for the reseller. In
A customer of a reseller may have their own tenancy and associated set of users. For example, as depicted in
Reseller R2 722 can have multiple customers of its own subscribing to R2-offered and branded cloud services that are provided using the vPLC created for R2. As shown in
As shown in
Each securely isolated portion of resources associated with the first-level resource partition or tenancy for the resellers (i.e., R1 tenancy and R2 tenancy) may be assigned or tagged with a vPLC ID (i.e., a resource ID), such as vPLC_ID.vPLC.R1 820 and vPLC_ID.vPLC.R2 822. Each of these partitions for CSP's non-reseller direct customers may be tagged with a resource IDs. Each tenancy of CSP's non-reseller direct customers may be accessed by their respective users, where the users can use one or more of the CSP-offered cloud services subscribed to by their corresponding direct customers.
Inside each first-level resource partition (or portion) for a reseller may have additional second-level resource partitions that are allocated to the tenancies of customers of resellers. For example, a securely isolated resource partition (vPLC.R1.C1) 840 may be allocated to tenancy (T.R1.C1) associated with customer C1 of reseller R1, and a securely isolated resource partition (vPLC.R1.C2) 842 may be allocated to tenancy (T.R1.C2) associated with customer C2 of reseller R1. The isolated partition vPLC.R1.C1 may be tagged with a customer resource ID identifying resources allocated to T.R1.C1, and the isolated partition vPLC.R1.C2 may be tagged with a customer resource ID identifying resources allocated to T.R1.C1.
Similarly, a securely isolated resource partition (vPLC.R2.C1) 844 may be allocated to tenancy (T.R2.C1) associated with customer C1 of reseller R2 and a securely isolated resource partition (vPLC.R2.C2) 846 may be allocated to tenancy (T.R2.C2) associated with customer C2 of reseller R2. The isolated partition vPLC.R2.C1 may be tagged with a customer resource ID identifying resources allocated to T.R2.C1, and the isolated portion vPLC.R2.C2 may be tagged with a customer resource ID identifying resources allocated to T.R1.C1. Each tenancy (e.g., 840 for R1.C1, 842 for R1.C2, 844 for R2.C1, or 846 for R2.C2) associated with a customer of a reseller may be accessed by one or more users associated with the customer, where the user can use one or more of the reseller-offered cloud services subscribed to by the corresponding customer.
The same structure may also be used for table 920, storing three records for three customers, C1, C2, and C3, of reseller R2. The first record/row may include the tenancy ID (T_ID.T.R2.C1) for a tenancy associated with customer C1 of reseller R2 and customer C1's associated information, for example, identity, billing, etc. The second record/row may include the tenancy ID (T_ID.T.R2.C2) for a tenancy associated with customer C2 of reseller R2 and customer C2's associated information. The third record/row may include the tenancy ID (T_ID.T.R2.C3) for a tenancy associated with customer C3 of reseller R2 and customer C3's associated information.
The same structure may also be used to store the records for customers C1, C2 and C3 of reseller R2 in the same table 930, for example, the fourth row, the fifth row, and the sixth row. For example, the last three rows of table 930 under the vPLC ID column may be marked as vPLC_ID.vPLC.R2, which is the vPLC ID for vPLC.R2 created for reseller R2. The customer tenancy ID column of the fourth row can be marked as tenancy ID (T_ID.T.R2.C1) for a tenancy associated with customer C1 of reseller R2, while the tenancy ID column of the fifth row can be marked as tenancy ID (T_ID.T.R2.C2) for a tenancy associated with customer C2 of reseller R2, and the tenancy ID column of the sixth row can be marked as tenancy ID (T_ID.T.R2.C3) for a tenancy associated with customer C3 of reseller R2. The information stored in the last three rows belongs to customers C1, C2 and C3 of reseller R2.
In certain embodiments, for example, the processing depicted in
As previously described, when a reseller subscribes to a CSP-offered vPLC service, a vPLC may be created. At step 1002, a signal may be received to create a vPLC. In certain embodiments, the signal may be a request received when a reseller has subscribed to a CSP-offered vPLC service. The request may be an agreement between the CSP and the reseller, listing virtual models (e.g., nested, or segmented models), database, resource arrangements, customization details, etc. In other embodiments, the signal may be received from some components indicating that a vPLC is being created.
At step 1004, configuration information for the vPLC to be created may be received. In some embodiments, the configuration information may include tenancy information (e.g., tenancy identifier) for which the vPLC is created and information for identifying a realm to be associated with the vPLC. As discussed earlier, a tenancy is created for the reseller and a tenancy identifier that uniquely identifies that tenancy is also created for that reseller associated with the vPLC.
As discussed earlier, in a use case that the vPLC may be used as a virtual data center and may be associated with a different realm than the realm associated with the cloud infrastructure in the region provided by the CSP, the identity and trust profile information (e.g., passwords, credentials, etc.) of the different realm need to be associated with the vPLC. The association of the identity and trust profile information of a different realm may be accomplished by creating a mapping (or “shadow copy”) of identity and trust profile information in the vPLC. More details will be discussed in
Step 1006, which covers steps 1008 to 1018, may perform the process of creating a vPLC for the reseller R. At step 1008, a vPLC identifier for the vPLC may be created. The vPLC that is created for the reseller is treated as a resource and assigned a unique resource identifier, which is referred to as a vPLC identifier (vPLC ID), and the vPLC ID is associated with the reseller's tenancy.
At step 1010, a set of resources from the CSP-provided infrastructure in a region may be allocated to the vPLC. The set of resources allocated to the vPLC may be selected based on the contract between the reseller and the CSP. For example, reseller R may subscribe to one or more cloud services provided by the CSP, such as compute service and object storage service. Thus, the set of resources may include compute resources and object storage resources.
At step 1012, a namespace may be reserved for the vPLC. A resource allocation service (or resource manager (RM)) of the CSP may create and reserve a namespace to group different types of resources that can support the vPLC. A namespace may refer to a logical grouping or virtual boundary that helps organize and manage resources, prevents naming conflicts when multiple instances of similar resources are created. Thus, namespace provides a structured way to organize and group related resources. In some embodiments, namespace 0 is reserved for CSP. Namespace 1 and beyond are used for vPLCs. In certain implementations, a range of internet protocol (IP) addresses may be reserved and associated with the namespace for the vPLC for traffic segregation purpose.
At step 1014, a console may be created for the vPLC allowing reseller R, customers of the reseller and users associated with customers of resellers to configure, access, and manage resources deployed in the vPLC and visualize, access, and interact with reseller-offered cloud services. Additionally, reseller R may configure the console to provide different customized experience for different customers of the reseller.
At step 1016, a set of endpoints for the vPLC may be created. In some embodiments, some of the set of endpoints may be default endpoints (e.g., identity endpoint), which are available for use, and some endpoints are determined based on which cloud services the reseller subscribes to. For example, the reseller may subscribe to one or more CSP-offered cloud services, such as compute, storage, virtual cloud network (VCN), database, etc. As a result, in addition to the default identity endpoint for accessing identity service, endpoints for access the subscribed services may also be created.
At step 1018, vPLC-related information, such as vPLC ID, identity information of reseller and other information facilitating reseller-offered cloud services, may be stored in the namespace for the vPLC. At step 1020, the CSP may send a response and other information to the reseller R indicative of the created vPLC. The reseller may start managing the vPLC for customers of the reseller, such as creating customer accounts, configuring reseller-offered cloud services, etc.
However,
The compute resources, three real application clusters (RACs) 1140, 1142, and 1144, that share the same storage 1150 are partitioned and allocated for CSP's native cloud 1120, vPLC.R1 1122 and vPLC.R2 1124, respectively. For example, RAC 1140 is dedicated to CSP's direct customers, RAC 1142 is designated for vPLC.R1, and RAC 1144 is for vPLC.R2.
The network resources may also be partitioned or shared between the CSP's direct customers and the resellers, allowing their computing resources to connect to the internet or enterprise network. For example, each RACs 1140, 1142, and 1144 uses its network gateway 1160, 1162, and 1164 to access the internet 1108 or enterprise network 1109. In some embodiments, two RACs may share the same network interface. For example, RAC 1142 and RAC 1144 share the same gateway 1162 to access the internet 1108.
The storage in
In
Users can use the service endpoints 1170 and 1172 (two endpoints are shown but more are possible) that the CSP exposes, where the endpoints have DNS names. The native cloud 1120 may also include a console 1174 with a look and feel. The CSP's direct customers on the internet 1108 can access the CSP-provided regional infrastructure 1102 through public endpoints 1170 and 1172 to request instance launch or termination. The customers of reseller R1 on the internet 1108 can also access the CSP-provided regional infrastructure 1102 through public endpoints 1180 and 1182 to request instance launch or termination. The customers of reseller R2 on the enterprise network 1109 can access the CSP-provided regional infrastructure 1102 through dedicated endpoints 1190 and 1192 to request instance launch or termination. The control plane 1104 can then launch instances, terminates instances, configures the connectivity for those instances and orchestrates services in this data center. The network interface 1160 and 1162 (e.g., internet gateways (IGWs)) for CSP and vPLC.R1, respectively, may provide network interconnection to the internet 1108. The network interface 1164 (e.g., dynamic routing gateway (DRG)) for vPLC.R2 may provide network interconnection to the enterprise network 1109.
In
If the request comes in through the console 1194, it may go to the control plane 604. The control plane can determine that the request comes from vPLC.R2 1124, and can find an available resource (e.g., a computer) from the RAC designated for vPLC.R2 (i.e., 1144 in this case), provision, and then launch this resource. The control plane 604 may then reply to the reseller R2's customer through the console 1194 and provide an IP address for its network configuration (e.g., VCN). The control plane 1104 can orchestrate the gateway 1164 depending on how it is configured, either to the enterprise network 1109 or the internet 1108. The control plane can be aware of not only the request but also the requester, who is either CSP's direct customers, customers of reseller R1 or customers of reseller R2.
As discussed earlier, partitioning of a CSP-provided regional infrastructure can be performed for different vPLCs at various pre-defined infrastructure levels, for example, at the rack level, server level, hypervisor level or VM-level. To illustrate further, for partitioning at the rack level, a vPLC may have its own dedicated racks and the resources within it. For partitioning at the server level, multiple vPLCs may share a rack, but each vPLC has its dedicated servers. Yet, in another example, for partitioning at the hypervisor level, multiple vPLCs may share a server, but each vPLC has its dedicated hypervisors. For partitioning at the VM-level, multiple vPLCs may share a hypervisor, but each vPLC has its dedicated VMs. Thus, there can be two main vPLC infrastructure partitioning models (or the two ends of the spectrum) to achieve the multi-vPLC scheme: a segmented model and a nested model. A segmented model may refer to resource partitioning at the rack level. A nested model may refer to resource partitioning at the VM-level. However, other variations in between are possible considering operational efficiency (e.g., sharing control plane) and fragmentations (i.e., the partition of resources).
In
For logical partition, there is a common control plane 1250 and resource manager 1252 that are managed and operated by the CSP for all vPLCs. However, a data plane may be dedicated to each vPLC in the segmented model. For example, each vPLC.R1, vPLC.R2, and vPLC.Rn has its own data plane 1212, 1222 and 1232, respectively. In some embodiments, the resource manager 1252 may be part of a management plane. In other embodiments, the resource manager 1252 may be separate from the management plane.
In some embodiments, a user associated with a customer of reseller R1 1280 may send a request through one of vPLC.R1 endpoints 1270 to launch a VM instance or a bare metal server. Suppose the request is to launch a new VM instance. In that case, the control plane 1250 may work with identity service to check the user's proper credential for vPLC.R1, and then the resource manager 1252 may identify all the resources dedicated to vPLC.R1, such as IP address ranges. Then, a VM instance (e.g., 1218a) is launched on hypervisor 1216 in the vPLC.R1 segment 1210. After that, a response is sent back to the requesting user by the control plane 1250 through a vPLC.R1 endpoint 1270. If the request is for a bare metal server (e.g., 1214a), the resources for vPLC.R1 may be provisioned and assigned to vPLC.R1 with all necessary configurations by the resource manager 1252. A similar process may be performed for a request from a user associated with a customer of reseller R2 1282 to be fulfilled by vPLC.R2 segment 1220, and a request from a user associated with a customer of reseller Rn 1284 to be fulfilled by vPLC.Rn segment 1230. Each process for a vPLC may be performed independent of another vPLC, and concurrently with another vPLC.
The vPLC segmented model may have some advantages, such as physical separation, and a shared common control plane 1250 that the CSP operates. Additionally, the resource manager 1252 manages the resources across the vPLCs 1210-1230. However, resources, including networking and storage, are replicated to be designated for each vPLC and thus may have scaling challenges. Small footprints, such as a single rack or server, are also less feasible under this model. But, vPLC segmented model may still have shared power, cooling, etc. As mentioned above, the segmented model is just one end of the spectrum, and there are various ways to partition based on resources and efficiency.
In the embodiment of
In
Similarly, a packet destined for a VM 1332c belonging to a tenancy associated with customer C1 of reseller R2 associated with vPLC.R2 may be encapsulated with a vPLC_ID.vPLC.R2 and customer tenancy ID (T_ID.R2.C1) in the packet header. The packet can then be routed to resources partitioned for vPLC.R2 based on the vPLC ID (vPLC_ID.vPLC.R2). The customer tenancy ID (T_ID.R2.C1) associated with customer C1 of reseller R2 in the packet header can further help route the packet to tenant C1 running on VM 1332c in vPLC.R2. The packet is decapsulated before being delivered to VM 1332c.
An outgoing packet may be performed in a reverse process. For example, an outgoing packet originating from VM 1332a in vPLC.R1 and destined for internet 1360 may be encapsulated with vPLC_ID.vPLC.R1 and customer tenancy ID (T_ID.R1.C1) associated with customer C1 of reseller R1 in the packet header. When the packet reaches gateway 1340, the packet may be decapsulated before going to internet 1360. Similarly, an outgoing packet originating from VM 1332c in vPLC.R2 and destined for internet 1360 may be encapsulated with vPLC_ID.vPLC.R2 and customer tenancy ID (T_ID.R2.C1) associated with customer C1 of reseller R2 in the packet header. When the packet reaches gateway 1340, the packet may be decapsulated before going to internet 1360. As a result, both the incoming and outgoing traffic is segregated within the single segment 1310 shared by multiple vPLCs.
In some embodiments, in the nested model, one or more VMs may belong to CSP's direct customers and share the same hypervisor as other vPLCs.
Users of resellers accessing vPLC infrastructure are authenticated in both the segmented and nested models. A user associated with a customer of a particular reseller can access an endpoint and be authenticated as a user of a vPLC associated with the particular reseller by using the user's credential, for example, a username and a customer tenancy ID. For example, in some embodiments, in
At step S3, the CSP then creates a customer tenancy (or an account, T.R1.C1) for customer C1 1401 of reseller R1. A tenancy identifier (T_ID.T.R1.C1) is assigned to the newly created customer C1's tenancy (T.R1.C1). The vPLC ID (e.g., vPLC_ID.vPLC.R1) identifying vPLC.R1 for reseller R1 may be associated with the newly created customer tenancy ID (e.g., T_ID.T.R1.C1) for customer C1, shown in 1430, and stored in a database 1420 along with other credentials (e.g., account name and password). Other customers of reseller R1 and reseller R2 may also be stored in the database 1420. For example, customer tenancy ID of customer C2 of reseller R1 (i.e., R1.C2) is associated with vPLC ID for vPLC.R1-T_ID.T.R1.C2 and vPLC_ID.vPLC.R1, as shown in 1432. Customer tenancy ID of customer C2 of reseller R2 (i.e., R2.C1) is associated with vPLC ID for vPLC.R2-T_ID.T.R2.C1 and vPLC_ID.vPLC.R2, as shown in 1434.
The association between the vPLC ID and the tenancy ID of a customer of an individual reseller may provide isolation between the customer's tenancies within a vPLC. For example, the customer tenancy of R1.C1 may be securely isolated from customer tenancy of R1.C2 by using different customer tenancy IDs, T_ID.T.R1.C1 for customer C1 and T_ID.T.R1.C2 for customer C2, although both customer tenancies are within the same vPLC.R1. Tenancy associated with reseller R1 and tenancy associated with reseller R2 may be securely isolated using their respective vPLC IDs, vPLC_ID.vPLC.R1 for reseller R1 and vPLC_ID.vPLC.R2 for reseller R2.
At step S4, the CSP 1404 may return a handle, including the customer tenancy ID (e.g., T_ID.T.R1.C1), a temporary default password, and an account name back to the vPLC.R1 console 1402. At step S5, the vPLC.R1 console may receive the temporary credentials and forwards the customer tenancy ID and password to the customer C1 1401 of reseller R1. As shown in
As discussed above in relation to tenancy creation, a database of CSP (e.g., 1420 in
At step S1, a user 1501 associated with a customer of reseller R1 can log in with customer tenancy ID (or CT ID), username, and password at vPLC.R1 endpoint 1510. At S2, the user 1501 and its customer tenancy may be verified at the vPLC.R1 endpoint 1510 by going through a validation process, which may include, but is not limited to, user authentication (e.g., verifying valid credentials such as username and password), session management (e.g., session tokens or timeout), and access control enforcement (based on access privilege, permission, and policies).
At step S3, the vPLC.R1 endpoint 1510 may return a session handle. A session handle may refer to a token or unique identifier returned to a customer after successfully logging in to the customer's account. The session handle may be used for subsequent requests to access the cloud services and resources (e.g., launching an instance) without the need to reauthenticate for each individual request during the active login session (or API session).
Cloud resource IDs (CIDs), including customer tenancy ID, can be generated for resources at the time of the creation of those resources. Virtual machines, accounts, tenancies, authorization policies, virtual network subnets, ACLs, and load balancers may be examples of cloud resources and can therefore be referenced by their respective CIDs.
As discussed above, a vPLC-specific endpoint can be used by a user associated with a customer of a reseller to access resources associated with a vPLC and to perform one or more functions or operations involving resources allocated to the vPLC. In
The vPLC.R1 endpoint 1602, at step S2, may augment (or annotate) the request to indicate that the request comes from a customer of reseller R1 by tagging a corresponding vPLC ID (e.g., vPLC_ID.vPLC.R1) for vPLC.R1 endpoint, and forwards the request to the resource manager (RM) 1604. In other words, the annotated information (e.g., vPLC ID) allows the request to be processed with all the policies associated with vPLC.R1 once the request has been authenticated. In some embodiments, the policies associated with a vPLC may include, for example, the type of resources, the amount of the resources allowed for allocation (i.e., capacity limit), permission, etc.
At step S3, the RM 1604 queries its database (i.e., resources database) 1606 to determine if the requested resources are available for vPLC.R1 under the policy. Based on the query, at step S4, the RM may perform the resource allocation after confirming the requested resources are available under the policy. In other words, RM allocates a portion of the resources that are already allocated to vPLC.R1 for reseller R1 to the customer tenancy (T.R1.C1) associated with customer C1 of reseller R1 (based on customer tenancy ID when the user login).This resource allocation may be performed by assigning or designating a portion of available cloud resources (already allocated to vPLC.R1) to the user associated with customer C1 based on the policy agreed between the customer C1 and reseller R1, such as capacity limit or permission, etc. For example, reseller R1 and its customer C1 may have a contract policy to allow maximum 100 GB of memory available for use. Currently, 80 GB has been allocated (or used). If the user associated with customer C1 requests 10 GB, RM can identify the CID for the 10 GB to be provisioned by the CP. If the user associated with customer C1 requests 30 GB, which would exceed the total 100 GB limit, the request may be denied.
At step S5, the RM 1604 obtains a cloud resource ID assigned to the resources (vPLC.R1.C1) allocated to the tenancy (T.R1.C1) of customer C1 of reseller R1 from the resource database. At step S6, RM passes the resource ID to the vPLC.R1 endpoint 1602. At step S7, the vPLC.R1 endpoint 1602 makes a resource request to the control plane (CP) 1608, asking for resources with the specific resource ID assigned to the resources allocated to the tenancy (T.R1.C1) of customer C1 of reseller R1. In other words, the resource manager 1604 can augment (e.g., step S6) the user's request with information related to the vPLC (e.g., resource ID assigned to vPLC.R1.C1) that can be used by the control plane 1608 for provisioning resources (e.g., step S8).
At step S8, the control plane may provision the requested resources (e.g., launching a specific VM instance and storage). Resources may include compute, networking, storage, etc. At step S9, the control plane 1608 may respond with a status and a resource handle to the vPLC.R1 endpoint 1602. A resource handle may refer to a unique resource identifier assigned to a provisioned resource, such as cloud resource ID assigned to a provisioned compute instance (e.g., VM), a storage volume, virtual cloud network (VCN or subnet), database, etc. The resource handle may allow customers to access and manage the provisioned resources through APIs or command-line tools.
At step S10, the status and resource handle are forwarded to the user 1601 associated with customer C1 of reseller R1. At step S11, the control plane may notify the RM about the resource provisioning status, for example, success or failure. At step S12, the RM may update a record in the resource DB 1606 tracking the resource usage of customer C1 associated with the user. Continuing with the above example, the record may be updated to indicate that the total amount of memory used by customer C1 is 90 GB after successful provisioning of 10 GB on top of the previously provisioned 80 GB, or remains to be 80 GB after the user's request was denied. The record kept by the resource DB may help enforce the policies associated with a vPLC.
For example, in
At step S6, the RM obtains a resource ID assigned to the resources (vPLC.R1.C1) allocated to the tenancy (T.R1.C1) of customer C1 of reseller R1 from the resource database. At step S7, RM passes the resource ID to CP 1704. At step S8, the control plane may provision the requested resources. At step S9, the control plane 1704 may respond with a status and a resource handle to the vPLC.R1 endpoint 1702. At step S10, the status and resource handle may be forwarded to the user 1701. At step S11, the control plane may notify the RM about the resource provisioning status. At step S12, the RM may update a record in the resource DB tracking the resource usage of the customer associated with the user.
As shown in
A realm can have one or more regions. Each realm has its own identity and trust profile (e.g., passwords, credentials, etc.). These identity and trust profile information are shared between regions that are in the same realm, and thus the regions within a realm can communicate with each other. The identity and trust profile for a realm is configured such that cross-realm communications are not allowed.
In the example depicted in
In
As previously described, when a vPLC is created, as part of configuring the vPLC, the vPLC is associated with a particular realm. Typically, the vPLC is associated with the same realm that is associated with the region in which the CSP-provided regional infrastructure that hosts the vPLC is placed. In certain implementations, when a vPLC is configured, the vPLC may be associated with a realm that is different from the realm associated with the regional infrastructure that hosts the vPLC. For example, in the example depicted in
This causes vPLC 1818 and data center 1806 to be in the same realm, namely, realm A 1802. Since infrastructure in the same realm shares the same identity and trust profile, the vPLC 1818 is configured with the identity and trust profile of realm A 1802. The configuration of the identity and trust profile information of realm A 1802 may be accomplished by creating a mapping in the vPLC 1818. For example, the identity service APIs in the virtual realm (i.e., realm A 1802) may call the vPLC in the host realm (i.e., realm B 1812), which can accept the call and build trust (i.e., share the identity and trust profile information) between both realms. When an instance is created in a customer tenancy in the vPLC in the host realm, the resource ID and tenancy ID associated with the newly created instance in the host realm may be mapped to a new resource ID and tenancy ID in the virtual realm. Thus, a table of mappings (or “shadow tenancies”) may be maintained in the host realm (i.e., realm B 1812). The same process and mapping are also performed in the virtual realm (i.e., realm A 1802). Thus, both the vPLC 1818 and realm A 1802 (i.e., virtual realm) share the same identity and trust profile information. As a result, since vPLC 1818 and data center 1806 are in realm A 1802, they are able to communicate with each other, even though vPLC 1818 is physically hosted by infrastructure in a different realm B 1812. The vPLC 1818 may not be able to communicate with other infrastructure in Region B 1814 that is associated with realm B 1812.
Additionally, vPLC 1818 is also logically associated with Region A 1804 even though the vPLC is physically hosted by Region B 1814. Region B 1814 is referred to as the hosting region or host region for vPLC 1818. Region A 1804 in realm A 1802 is referred to as the logical region or virtual region for vPLC 1818. The virtual realm and the virtual region for the vPLC may be configured when the vPLC is created.
As described about the resource ID for a resource includes a portion that identifies a realm associated with the resource and a portion that identifies a region associated with the resource. A vPLC is considered a resource and thus is assigned a resource ID. In certain implementations, the vPLC ID that uniquely identifies a vPLC is a type of resource ID. The vPLC ID includes a portion that identifies the virtual realm associated with the vPLC identified by the vPLC ID, and a portion that identifies the virtual region associated with the vPLC. Accordingly, for identity management purposes in realm A 1802, the vPLC is considered to be part of the realm and region identified by the vPLC ID corresponding to the vPLC.
In certain embodiments, configuring a vPLC in the manner described above, where the vPLC is hosted by one region and one realm but is associated with a different virtual region and a different virtual realm may be performed utilizing virtual bootstrap environment (ViBE) technology. A ViBE may refer to a virtual cloud network (VCN) that is provisioned in the overlay of an existing region (e.g., a “host region”). Once provisioned, a ViBE is connected to a new region using a communication channel (e.g., an IPSec Tunnel VPN). Certain essential core services (or “seed” services) like a deployment orchestrator, a public key infrastructure (PKI) service, and the like can be provisioned in a ViBE. These services can provide the capabilities required to bring the hardware online, establish a chain of trust in the new region, and deploy the remaining services in the new region. Utilizing the virtual bootstrap environment can prevent circular dependencies between bootstrapping resources by utilizing resources of the host region. Services can be staged and tested in the ViBE prior to the physical region (e.g., the target region) being available.
For example, in some embodiments, realm B 1812 may create a ViBE within its realm, where the ViBE is shared with the identity and trust profile information of realm A 1802. The ViBE in realm B 1812 may then be used to bootstrap a new region in realm A 1802. Further details related to ViBE are described in the following applications, the entire contents of which are incorporated herein by reference for all purposes:
The architecture depicted in
Since the goal for DR sites is to minimize the occurrence of correlated failures by introducing a geographic separation between the primary and DR sites and by avoiding concurrent modification of both the primary and secondary locations, the DRCC 1806 can enjoy DR guarantees once the CSP can ensure that the DRCC and the paired vPLC 1818 (and by extension its hosting region in realm B 1812) will not be modified concurrently.
Processing commences at 1902 when information is received identifying a host region in a host realm in which the vPLC is to be created is to be physically hosted. For example, for the embodiment depicted in
At 1904, information may be received identifying a region in a particular realm, where the particular realm is different from the host realm identified in 1902, where the region identified in 1904 and the particular realm are to be associated as the virtual region and virtual realm for the vPLC to be created. For example, for the embodiment depicted in
At 1906, identity and trust profile information for the particular realm identified in 1904 is obtained. The information obtained in 1906 may include identity credentials including passwords, certificates, etc., associated with the realm that is to be the virtual realm for the vPLC.
At 1908, a vPLC ID is generated for the vPLC to be created, where the vPLC ID identifies the region and the particular realm identified in the information received in 1904.
At 1910, a vPLC is created in the host realm and resources are allocated to the vPLC, where the allocated resources are selected from resources in infrastructure provided by the CSP in the region identified in 1902 and in the realm identified in 1902. These resources may include one or more physical resources (e.g., racks, servers, routers, memory, or storage resources) and/or logical resources (e.g., hypervisors, virtual machines, virtual routers). For example, for the embodiment depicted in
At 1912, the vPLC is configured using the identity and trust profile information obtained in 1906. For example, for the embodiment depicted in
At 1914, the vPLC commences communication with CSP-provided infrastructure in the particular realm identified in 1904, which is the virtual realm for the vPLC. For example, for the embodiment depicted in
Virtual Private Label Clouds (vPLCs)—Resource Allocation
RM may interact with and receive requests from the control plane (CP) 2070 after resellers R1 2062 or reseller R2 2064 request a vPLC setup or additional resources through the CP. For example, after the CP has created tenancy for reseller R1 and assigned a vPLC ID for the tenancy of reseller R1, CP may send a notification to RM and request to allocate resources (e.g., compute, storage, and networking) for the vPLC associated with reseller R1.
RM may also interact with the resource database 2072 during the resource allocation for reseller R1 2062 and reseller R2 2064. Resource database may have information about the amount of resources in a CSP's resource pool and keep the resource allocation history to help track the availability of the requested resources from reseller R1 and reseller R2. For example, if reseller R1 requests ten CPUs from the CSP, the RM may check the resource DB to see whether the CSP resource pool for compute type has a sufficient amount of resources for the request (e.g., more than ten CPUs), and how much resources for reseller R1 have been allocated before. If the request is allowed and the amount of resources is available, RM may update the resource database after the resource allocation.
The policy information 2020 may include policies and configurations for vPLCs, such as threshold limitations for resources, configurations for dedicated servers or racks, and the like. The policies for resource allocation in vPLC infrastructure may be arranged in two-tier. One tier is between resellers and customers/end-user (referred to herein as reseller-customer policy), and another tier is between CSP and resellers (referred to herein as CSP-reseller policy). In some embodiments, the policies may be determined based on CSP-reseller agreements and reseller-customer agreements 2121. Typically, the CSP-reseller policy may be a superset or an aggregate of individual reseller-customer policies. In certain embodiments, the enforcement of the policies may be performed at the compute layer before reaching the resource manager. In certain embodiments, a CSP may have a default policy, but a reseller can request a CSP-reseller policy to override the CSP's default policy.
For example, a CSP may have a default policy limiting a new customer to having no more than ten virtual machines (VMs). Reseller R1 may contract with the CSP to override the CSP's default policy to allow its new customers to have a higher capacity of 50 VMs, but reseller R2 does not request the change of CSP's default policy. When a customer for reseller R1 and a customer for reseller R2 both request 20 VMs, the request of the reseller R1's customer may be fulfilled while the request of the reseller2's customer may be blocked and denied at the compute layer without reaching the resource manager at all. Thus, different intermediaries (i.e., resellers) may establish different user experiences.
In some embodiments, when the reseller-customer policy and CSP-reseller policy conflict, the more stringent one may be followed for the particular user-reseller-CSP chain. For example, a reseller-customer policy allows a maximum of 5 VMs, but a CSP-reseller policy allows 50 VMs. When a customer under the reseller-customer policy requests the 6th VMs, the RM may not fulfill the request because the request exceeds the more stringent policy of 5 VMs, reseller-customer policy. Although there are two different policies, the same set of available resources can still be used for different vPLCs.
In some embodiments, capacity may be oversubscribed. For example, the aggregate of limits associated with specific services for each vPLC may exceed the overall capacity for the resource available. Predictive models, such as machine learning and artificial intelligence (ML/AI) models, may be used to manage the resources and minimize unused capacity to fully utilize the benefits of shared resources for vPLC architecture. The system may learn over time which resources can be oversubscribed based on usage patterns and historical information. Combined with variable pricing and preemptive resources, demand can be shaped.
The topology-segmentation information 2030 may include partitioning requirements and represent the authoritative source of truth for topological information for segmentation purposes, for example, the placement of vPLC resources at different levels (such as rack, server, and hypervisor levels), and types of models (nested model, segmented model, or something in between) to use for achieving secured isolation among the resources of different vPLCs. The segmentation level, as part of the partitioning requirements, may define an infrastructure level that resources of a vPLC are dedicated to (i.e., allocated exclusively to) that vPLC to create an isolation unit, such as a rack, a server, or a hypervisor, in which no other vPLCs and its respective customers can have a presence.
The physical cloud resources may be segmented within a region at the data center level, rack level, server level, or hypervisor level. When vPLCs are segmented at a particular level, they can share resources above that particular level, but resources at or below that particular level are not shared (i.e., segmented) among vPLCs. For example, if the segmentation level is at the rack level, then a rack is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers.
In another example, if vPLCs are segmented at the server level, a server is exclusively allocated to a particular vPLC and is not used by other vPLCs or by the CSP for providing CSP-offered services to its direct customers. As a result, all the resources within the server (i.e., below the server level), such as hypervisors and VMs are also exclusively allocated to that particular vPLC. Since a rack can have multiple servers, one server on the rack may be allocated to a first vPLC, another server to a second vPLC, and a third server to a third vPLC. Thus, a rack may be shared between two vPLCs, or between infrastructure used by the CSP for providing CSP-offered services to its direct customers and a vPLC.
By contrast, if a vPLC that a user belongs to is not segmented even at the hypervisor level, then the requested VM can be placed on any hypervisor that hosts VMs for other vPLCs that do not require segmentation even at the server level. In other words, this is similar to nesting at the hypervisor level and all the way up the stack to the server level, the rack level, the network, and datacenter level.
The policy information and topology-segmentation information may be part of the agreements between resellers and CSP on how available non-virtual cloud infrastructure (e.g., control planes and data planes) can be configured and used (e.g., dedicated or shared), and the types of models for resource isolation and allocation (e.g., nested or segmented models) used.
The identity system 2040 may be a system that handles the management of tenancies, authorization policies, and authentication in a vPLC-aware manner. For example, identity ensures cloud resource identifiers (e.g., CIDs) are properly managed for each vPLC by using mechanisms, such as prefixes or lookup tables, to track the resource identifiers. Additionally, identity services of the identity system allow resellers to create and manage identity accounts of the reseller's customers based on reseller-customer agreements. RM may request the identity system to help check the identity of a requester and validate.
Storage block 2052, compute block 2054, and network block 2056 may represent the management of resources related to storage, compute (i.e., physical server hardware), and network, for example, the placement of storage and volume, hardware, and network. In certain embodiments, RM may check the policies established between CSP and resellers, and between resellers and their customers to determine whether the requested resources are allowed to allocate. RM may further check the resource database that keeps the allocation history to determine whether the requested resources are available to allocate. The resource manager may ensure that the resources are properly assigned to specific vPLCs (e.g., vPLC.R1 and vPLC.R2), replenished from a CSP overall availability pool (i.e., standard pool) when necessary, and returned back to the overall availability pool.
The resources in a GURP may be resources that have been set aside by the CSP for its resellers, but have not been allocated to individual resellers. In some embodiments, when receiving a request to create a vPLC, the RM (or the services) may create a namespace in all GURPs for different types of resources that may support the new vPLC. Typically, namespace 0 is reserved for CSP. Namespace 1 and beyond are used for vPLCs. For example, when a reseller requests to set up a vPLC with compute and storage resources, a namespace in compute GURP and a namespace in storage GURP are created accordingly for the reseller. Once a reseller requests the allocation of a type of resource and passes both validation check (including authentication and authorization checks) and policy check, the requested type of resources may be allocated into a namespace in the GURP of that resource type for the vPLC associated with that reseller. For example, resources in compute GURP 2110 may be allocated to namespace 1 for vPLC.R1 2120 upon reseller R1's request passing validation and policy checks Similarly, resources in compute GURP 2110 may be allocated to namespace 2 for vPLC.R2 2122 upon reseller R2's request passing validation and policy checks.
In some embodiments, a particular type of resources allocated to a vPLC for a reseller may be further allocated to the tenancy of a customer of that reseller after that customer subscribes to one or more of reseller-offered cloud services provided by that reseller and passes both validation (including authentication and authorization checks) and policy checks. For example, suppose customer C1 of reseller R1 subscribes to compute service provided by reseller R1, a portion (i.e., the requested resources by customer C1) of the compute resources already allocated to vPLC.R1 associated with namespace 1 2120 may be further allocated to the tenancy (i.e., R1.C1 tenancy) 2130 for customer C1 of reseller R1. Similarly, after customer C2 of reseller R1 subscribes to compute service provided by reseller R1, a portion (i.e., the requested resources by customer C2) of the compute resources already allocated to vPLC.R1 associated with namespace 1 2120 may be further allocated to the tenancy (i.e., R1.C2 tenancy) 2132 for customer C2 of reseller R1.
The generic unbounded pool may be a resource pool that looks “infinite and elastic” to customers of a reseller because a reseller may anticipate requested resources from all of the reseller's customers and additional future demand. Depending on the contract between the CSP and the reseller requesting a new vPLC, a GURP may have an extra capacity of resources in a vPLC namespace requested by a reseller in advance from a CSP to guarantee that the reseller's customers are unlikely to encounter any insufficient capacity error. The extra capacity of resources may be in the same region of the requested vPLC, part of CSP's resources, or part of other vPLCs. As an example, suppose a reseller may anticipate high demands from its customers. In that case, the reseller may contract with the CSP to allocate more resources than the CSP typically does for a new reseller. As a further example, a reseller may receive a request from its first customer for 5 VMs maximum under a first contract between the customer and the reseller, and a request from its second customer for 10 VMs maximum under a second contract. Then, the reseller may contract with the CSP to allocate 20 VMs (i.e., 5 extra VMs over customers' combined requests) to make its resource pool appear unbounded, and can control whether the unbounded pool is shared or separately dedicated to the reseller's customers. However, policies may still dictate the limits of resources, although the resource pool is perceived as unbounded by customers of the reseller.
The CSP overall availability pool 2102 may contain racks of servers. If the segmentation level associated with vPLC.R1 is at the rack level, the CSP may set aside a rack (e.g., rack 1) for vPLC.R1 in compute GURP 2110. Some servers on rack 1 may be allocated and put in namespace 1 2120 when reseller R1 requests the allocation, but other unallocated servers on rack 1 cannot be used for other vPLCs. On the other hand, if the segmentation level for both vPLC.R1 and vPLC.R2 is at the server level, some servers from a rack (e.g., rack 1) may be allocated and put in namespace 1 2120 for vPLC.R1, and some servers from the same rack (e.g., rack 1) may be allocated and put in namespace 2 2122 for vPLC.R2. The remaining unallocated servers on rack 1 are still part of the compute GURP 2110 for future allocation by either vPLC.R1 or vPLC.R2.
If a particular resource pool (e.g., compute GURP 2110) falls below a threshold, more allocable capacity may be automatically added to that particular resource pool from the overall available raw capacity (i.e., CSP overall availability pool 2102). For example, reseller R1 and reseller R2 may have an agreement with the CSP that the compute GURP should have a threshold of at least five unallocated servers at any time. If the total number of unallocated servers in compute GURP is five, and vPLC.R1 requests the allocation of one more server for a customer of reseller R1, then the CSP may replenish a server from the overall availability pool into the compute GURP.
If instances are terminated, for example, because customers of a reseller R1 associated with a vPLC.R1 (e.g., 2120) leaves, resulting in an empty isolation unit (e.g., a rack, a server, or a hypervisor) and an unused resource threshold (e.g., number of unused servers in a rack) is reached, the empty isolation unit may be moved back to a GURP (e.g., 2110) which become available for other vPLCs to use. For example, suppose reseller R1 has a segmentation level at the server level and thus has a dedicated server (i.e., an isolation unit). The reseller R1 additionally sets an unused resource threshold of 50% of an isolation unit for returning the isolation unit back to compute GURP. When one or more of reseller R1's customers reduce their demand and free up 5 servers in the rack with a total of 8 servers, one or more of these unused servers may be reclaimed and returned to the compute GURP 2110 if the reseller decides to also reduce its allocated resources.
Furthermore, when a vPLC is being retired, the resources associated with that vPLC may be reclaimed and moved back to the CSP overall availability pool 2102. Reclaiming resources may apply to other resources, such as storage and network. For example, storage resources for a vPLC that are freed up and becomes available may be reclaimed depending on policy control.
In some embodiments, resource allocation services of the resource manager can perform live migration. For example, if resources are available on the rack, the resource allocation services may assign capacity on the rack automatically. Resources on the racks allocated to a specific vPLC may be shuffled to optimize packing and reduce fragmentation. The CSP may deploy live migration to make this process transparent to the reseller and the reseller's customer.
At step 2212, RM may cause authentication and authorization checks for the reseller R regarding the request received in box 2210 after a tenancy for R has been set up. In some embodiments, RM may interact with the identity system (e.g., 2040 in
At step 2220, based on the CSP-reseller policy, RM checks whether the type of the requested resource is allowed to be allocated to the vPLC. At step 2222, if the type of the requested resource is not allowed, the process ends. If the check passes, the process proceeds to step 2224. For example, a CSP-reseller policy may allow only compute resources. If reseller R requests both compute and storage resources, the storage request is denied after the type check, but the compute resource is allowed.
At step 2224, based on the CSP-reseller policy and the resource database, RM checks whether the amount/number of the type of the requested resource is allowed to be allocated to the vPLC. This step checks the amount limit of the type of the requested resource, first based on the CSP-reseller policy, and then the allocation history in the resource database. At step 2226, if the amount/number of the type of the requested resource is not allowed, the process ends. Otherwise, the process proceeds to step 2228.
For example, if the CSP-reseller policy has a maximum of 5 CPU cores for compute resources but the reseller R requests 6 CPU cores, then the request may be denied (i.e., not allowed). However, if the reseller R requests 4 CPU cores (i.e., below 5 CPU cores limit), then RM may further check whether the number of CPU cores already allocated has reached the limit of 5 CPU cores under the CSP-reseller policy. For example, if the reseller R requests 4 CPU cores but the resource database that tracks the history of resource allocation indicates that the vPLC associated with reseller R has been allocated 5 CPU cores, then the request may be denied (i.e., not allowed). On the other hand, if only 3 CPU cores have been allocated in the past, then the request may be allowed.
At step 2228, based on the CSP-reseller policy and the resource database, RM checks whether the amount/number of the type of the requested resource is available for allocation. This step checks the remaining available amount of the type of the requested resource. At step 2230, if the amount/number of the type of the requested resource is not available, the process ends. Otherwise, the process proceeds to step 2252.
For example, continuing with the example above, if the resource database shows that 5 CPUs have been allocated in the past, which reaches the policy limit, then no resource is available for the request. In fact, this request should not have been allowed in step 2226. However, if the resource database shows that only 3 CPU cores have been allocated in the past, then 2 CPU cores are available for allocation.
At step 2250, which includes sub-steps 2252 to 2258, RM may allocate the requested resource to the vPLC from the pool of resources (i.e., GURP) set aside by CSP for vPLCs. At step 2252, RM may identify resource instances for allocation to the vPLC by taking into account topology-segmentation information for the vPLC. For example, as discussed earlier in relation to segmentation. For example, RM may check the segmentation level of the vPLC and determine the level to be at the server level. Thus, the identified resource instances may come from a rack shared with other vPLCs, but not come from a server that already contain resource instances for other vPLCs.
At step 2254, RM may associate an identification (vPLC ID) identifying vPLC with the requested resource to indicate that the requested resource is allocated to the vPLC for reseller R. For example, in
At step 2258, RM may update the resource database to reflect the allocation. For example, since the resource database (e.g., 2072 in
At step 2312, RM may cause an authentication and authorization checks for the customer of the reseller R regarding the request received in 2310 after a tenancy of the customer has been created. The tenancy creation of the customer of the reseller R is discussed earlier in relation to
The resource allocation process for the customer of a reseller may be similar to the process described in
At step 2330, based on the reseller-customer policy, RM checks whether the type of the requested resource is allowed to be allocated to the customer of the reseller R. At step 2332, if the type of the requested resource is not allowed, the process ends. If the check passes, the process proceeds to step 2334. For example, a reseller-customer policy may allow only compute resources. If the customer of the reseller requests both compute and storage resources, the storage request is denied after the type check, but the compute resource is allowed.
At step 2334, based on the reseller-customer policy and the resource database, RM checks whether the amount/number of the type of the requested resource is allowed to be allocated to the customer of the reseller. This step checks the amount limit of the type of the requested resource, first based on the reseller-customer policy, and then the allocation history in the resource database. At step 2336, if the amount/number of the type of the requested resource is not allowed, the process ends. Otherwise, the process proceeds to step 2338.
At step 2338, based on the reseller-customer policy and the resource database, RM checks whether the amount/number of the type of the requested resource is available for allocation. This step checks the remaining available amount of the type of the requested resource. At step 2340, if the amount/number of the type of the requested resource is not available, the process ends. Otherwise, the process proceeds to step 2350.
At step 2350, which includes sub-steps 2352 and 2358, RM may allocate a portion of the resources allocated for the vPLC to the customer of reseller. At step 2352, RM identifies resource instances for allocation to the tenancy of the customer of the reseller associated with the vPLC. For example, if reseller R1 has requested 10 servers for the vPLC (e.g., namespace 1 2120 in
At step 2354, the resource instances identified in 2352 are associated with the tenancy ID of the customer of the reseller. RM may store information indicating that the resource has been allocated to the customer of the reseller R, for example, assigning a resource ID to the resource allocated to the customer. In other words, RM may associate a vPLC ID with the resource allocated to the vPLC (i.e., vPLC.R1), associate customer tenancy ID (T_ID.T.R1.C1) with the customer, and associate a resource ID with the resource (i.e., vPLC.R1.C1) allocated to the customer of the reseller. At step 2356, RM then places the allocated resource instances in the tenancy of the customer of the reseller 156.
At step 2358, RM may update the resource database to reflect the allocation. For example, since the resource database (e.g., 2072 in
In some scenarios, the customer's requested resources may not be in the vPLC associated with the reseller. In those scenarios, RM may check if sufficient resource has already been allocated to the reseller R, from which allocation to the customer can be made. This check may be performed after step 2314 but before step 2330. For example, some resellers may request resources for known customers first, whether designating for these customers or a pool of resources shared by all known customers. It is possible that the requested resource by the customer is beyond the reseller's initial anticipation. For example, the reseller anticipated and requested resources for existing customers C1 and C2. A new customer C3 may sign up and request resources not previously allocated. In another example, customer C1 may like to increase its resource limit by negotiating a new reseller-customer policy with reseller R. If the requested resource is not available, the process may need to go through the processing in
At step 2412, based on the topology-segmentation information associated with a vPLC, RM may determine the segmentation configuration (i.e., segmentation level) associated with the vPLC. At step 2414, RM may allocate the resource instances per the segmentation level determined in step 2412 for the vPLC. For example, vPLC.R1 may have a segmentation level at the rack level, vPLC.R2 may have a segmentation level at the server level, and vPLC.R3 may have a segmentation level at the hypervisor level. In such case, a server allocated to the customer of reseller R1 may be a bare-metal server from a dedicated rack not sharing with other vPLCs. However, a server allocated to the customer of reseller R2 may be a bare-metal server but on a rack that also has a server allocated to the customer of reseller R3. In other words, R2 has a dedicated server but from a shared rack. Finally, for reseller R3, the resources (e.g., processors or memory) running the hypervisor are dedicated to the customer of reseller R3, but the server hosting the R3's hypervisor may also host hypervisors for other vPLCs that have a segmentation level at the hypervisor level.
At step 2420, RM may request CP to provision the allocated resources for the vPLC. For example, once the RM has allocated the requested resource to the requesting customer, information, such as vPLC ID, customer tenancy ID, and the resource ID associated with the allocated resource may be passed to CP for provisioning, as discussed in relation to
As noted above, infrastructure as a service (IaaS) is one particular type of cloud computing. IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In an IaaS model, a cloud computing provider can host the infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., a hypervisor layer), or the like). In some cases, an IaaS provider may also supply a variety of services to accompany those infrastructure components (example services include billing software, monitoring software, logging software, load balancing software, clustering software, etc.). Thus, as these services may be policy-driven, IaaS users may be able to implement policies to drive load balancing to maintain application availability and performance.
In some instances, IaaS customers may access resources and services through a wide area network (WAN), such as the Internet, and can use the cloud provider's services to install the remaining elements of an application stack. For example, the user can log in to the IaaS platform to create virtual machines (VMs), install operating systems (OSs) on each VM, deploy middleware such as databases, create storage buckets for workloads and backups, and even install enterprise software into that VM. Customers can then use the provider's services to perform various functions, including balancing network traffic, troubleshooting application issues, monitoring performance, managing disaster recovery, etc.
In most cases, a cloud computing model will require the participation of a cloud provider. The cloud provider may, but need not be, a third-party service that specializes in providing (e.g., offering, renting, selling) IaaS. An entity might also opt to deploy a private cloud, becoming its own provider of infrastructure services.
In some examples, IaaS deployment is the process of putting a new application, or a new version of an application, onto a prepared application server or the like. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed by the cloud provider, below the hypervisor layer (e.g., the servers, storage, network hardware, and virtualization). Thus, the customer may be responsible for handling (OS), middleware, and/or application deployment (e.g., on self-service virtual machines (e.g., that can be spun up on demand) or the like.
In some examples, IaaS provisioning may refer to acquiring computers or virtual hosts for use, and even installing needed libraries or services on them. In most cases, deployment does not include provisioning, and the provisioning may need to be performed first.
In some cases, there are two different challenges for IaaS provisioning. First, there is the initial challenge of provisioning the initial set of infrastructure before anything is running. Second, there is the challenge of evolving the existing infrastructure (e.g., adding new services, changing services, removing services, etc.) once everything has been provisioned. In some cases, these two challenges may be addressed by enabling the configuration of the infrastructure to be defined declaratively. In other words, the infrastructure (e.g., what components are needed and how they interact) can be defined by one or more configuration files. Thus, the overall topology of the infrastructure (e.g., what resources depend on which, and how they each work together) can be described declaratively. In some instances, once the topology is defined, a workflow can be generated that creates and/or manages the different components described in the configuration files.
In some examples, an infrastructure may have many interconnected elements. For example, there may be one or more virtual private clouds (VPCs) (e.g., a potentially on-demand pool of configurable and/or shared computing resources), also known as a core network. In some examples, there may also be one or more inbound/outbound traffic group rules provisioned to define how the inbound and/or outbound traffic of the network will be set up and one or more virtual machines (VMs). Other infrastructure elements may also be provisioned, such as a load balancer, a database, or the like. As more and more infrastructure elements are desired and/or added, the infrastructure may incrementally evolve.
In some instances, continuous deployment techniques may be employed to enable deployment of infrastructure code across various virtual computing environments. Additionally, the described techniques can enable infrastructure management within these environments. In some examples, service teams can write code that is desired to be deployed to one or more, but often many, different production environments (e.g., across various different geographic locations, sometimes spanning the entire world). However, in some examples, the infrastructure on which the code will be deployed is first set up. In some instances, the provisioning can be done manually, a provisioning tool may be utilized to provision the resources, and/or deployment tools may be utilized to deploy the code once the infrastructure is provisioned.
The VCN 2506 can include a local peering gateway (LPG) 2510 that can be communicatively coupled to a secure shell (SSH) VCN 2512 via an LPG 2510 contained in the SSH VCN 2512. The SSH VCN 2512 can include an SSH subnet 2514, and the SSH VCN 2512 can be communicatively coupled to a control plane VCN 2516 via the LPG 2510 contained in the control plane VCN 2516. Also, the SSH VCN 2512 can be communicatively coupled to a data plane VCN 2518 via an LPG 2510. The control plane VCN 2516 and the data plane VCN 2518 can be contained in a service tenancy 2519 that can be owned and/or operated by the IaaS provider.
The control plane VCN 2516 can include a control plane demilitarized zone (DMZ) tier 2520 that acts as a perimeter network (e.g., portions of a corporate network between the corporate intranet and external networks). The DMZ-based servers may have restricted responsibilities and help keep breaches contained. Additionally, the DMZ tier 2520 can include one or more load balancer (LB) subnet(s) 2522, a control plane app tier 2524 that can include app subnet(s) 2526, a control plane data tier 2528 that can include database (DB) subnet(s) 2530 (e.g., frontend DB subnet(s) and/or backend DB subnet(s)). The LB subnet(s) 2522 contained in the control plane DMZ tier 2520 can be communicatively coupled to the app subnet(s) 2526 contained in the control plane app tier 2524 and an Internet gateway 2534 that can be contained in the control plane VCN 2516, and the app subnet(s) 2526 can be communicatively coupled to the DB subnet(s) 2530 contained in the control plane data tier 2528 and a service gateway 2536 and a network address translation (NAT) gateway 2538. The control plane VCN 2516 can include the service gateway 2536 and the NAT gateway 2538.
The control plane VCN 2516 can include a data plane mirror app tier 2540 that can include app subnet(s) 2526. The app subnet(s) 2526 contained in the data plane mirror app tier 2540 can include a virtual network interface controller (VNIC) 2542 that can execute a compute instance 2544. The compute instance 2544 can communicatively coupled the app subnet(s) 2526 of the data plane mirror app tier 2540 to app subnet(s) 2526 that can be contained in a data plane app tier 2546.
The data plane VCN 2518 can include the data plane app tier 2546, a data plane DMZ tier 2548, and a data plane data tier 2550. The data plane DMZ tier 2548 can include LB subnet(s) 2522 that can be communicatively coupled to the app subnet(s) 2526 of the data plane app tier 2546 and the Internet gateway 2534 of the data plane VCN 2518. The app subnet(s) 2526 can be communicatively coupled to the service gateway 2536 of the data plane VCN 2518 and the NAT gateway 2538 of the data plane VCN 2518. The data plane data tier 2550 can also include the DB subnet(s) 2530 that can be communicatively coupled to the app subnet(s) 2526 of the data plane app tier 2546.
The Internet gateway 2534 of the control plane VCN 2516 and of the data plane VCN 2518 can be communicatively coupled to a metadata management service 2552 that can be communicatively coupled to public Internet 2554. Public Internet 2554 can be communicatively coupled to the NAT gateway 2538 of the control plane VCN 2516 and of the data plane VCN 2518. The service gateway 2536 of the control plane VCN 2516 and of the data plane VCN 2518 can be communicatively coupled to cloud services 2556.
In some examples, the service gateway 2536 of the control plane VCN 2516 or of the data plane VCN 2518 can make application programming interface (API) calls to cloud services 2556 without going through public Internet 2554. The API calls to cloud services 2556 from the service gateway 2536 can be one-way: the service gateway 2536 can make API calls to cloud services 2556, and cloud services 2556 can send requested data to the service gateway 2536. But, cloud services 2556 may not initiate API calls to the service gateway 2536.
In some examples, the secure host tenancy 2504 can be directly connected to the service tenancy 2519, which may be otherwise isolated. The secure host subnet 2508 can communicate with the SSH subnet 2514 through an LPG 2510 that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet 2508 to the SSH subnet 2514 may give the secure host subnet 2508 access to other entities within the service tenancy 2519.
The control plane VCN 2516 may allow users of the service tenancy 2519 to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN 2516 may be deployed or otherwise used in the data plane VCN 2518. In some examples, the control plane VCN 2516 can be isolated from the data plane VCN 2518, and the data plane mirror app tier 2540 of the control plane VCN 2516 can communicate with the data plane app tier 2546 of the data plane VCN 2518 via VNICs 2542 that can be contained in the data plane mirror app tier 2540 and the data plane app tier 2546.
In some examples, users of the system, or customers, can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet 2554 that can communicate the requests to the metadata management service 2552. The metadata management service 2552 can communicate the request to the control plane VCN 2516 through the Internet gateway 2534. The request can be received by the LB subnet(s) 2522 contained in the control plane DMZ tier 2520. The LB subnet(s) 2522 may determine that the request is valid, and in response to this determination, the LB subnet(s) 2522 can transmit the request to app subnet(s) 2526 contained in the control plane app tier 2524. If the request is validated and requires a call to public Internet 2554, the call to public Internet 2554 may be transmitted to the NAT gateway 2538 that can make the call to public Internet 2554. Metadata that may be desired to be stored by the request can be stored in the DB subnet(s) 2530.
In some examples, the data plane mirror app tier 2540 can facilitate direct communication between the control plane VCN 2516 and the data plane VCN 2518. For example, changes, updates, or other suitable modifications to configuration may be desired to be applied to the resources contained in the data plane VCN 2518. Via a VNIC 2542, the control plane VCN 2516 can directly communicate with, and can thereby execute the changes, updates, or other suitable modifications to configuration to, resources contained in the data plane VCN 2518.
In some embodiments, the control plane VCN 2516 and the data plane VCN 2518 can be contained in the service tenancy 2519. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN 2516 or the data plane VCN 2518. Instead, the IaaS provider may own or operate the control plane VCN 2516 and the data plane VCN 2518, both of which may be contained in the service tenancy 2519. This embodiment can enable isolation of networks that may prevent users or customers from interacting with other users', or other customers', resources. Also, this embodiment may allow users or customers of the system to store databases privately without needing to rely on public Internet 2554, which may not have a desired level of threat prevention, for storage.
In other embodiments, the LB subnet(s) 2522 contained in the control plane VCN 2516 can be configured to receive a signal from the service gateway 2536. In this embodiment, the control plane VCN 2516 and the data plane VCN 2518 may be configured to be called by a customer of the IaaS provider without calling public Internet 2554. Customers of the IaaS provider may desire this embodiment since database(s) that the customers use may be controlled by the IaaS provider and may be stored on the service tenancy 2519, which may be isolated from public Internet 2554.
The control plane VCN 2616 can include a control plane DMZ tier 2620 (e.g., the control plane DMZ tier 2520 of
The control plane VCN 2616 can include a data plane mirror app tier 2640 (e.g., the data plane mirror app tier 2540 of
The Internet gateway 2634 contained in the control plane VCN 2616 can be communicatively coupled to a metadata management service 2652 (e.g., the metadata management service 2552 of
In some examples, the data plane VCN 2618 can be contained in the customer tenancy 2621. In this case, the IaaS provider may provide the control plane VCN 2616 for each customer, and the IaaS provider may, for each customer, set up a unique compute instance 2644 that is contained in the service tenancy 2619. Each compute instance 2644 may allow communication between the control plane VCN 2616, contained in the service tenancy 2619, and the data plane VCN 2618 that is contained in the customer tenancy 2621. The compute instance 2644 may allow resources, that are provisioned in the control plane VCN 2616 that is contained in the service tenancy 2619, to be deployed or otherwise used in the data plane VCN 2618 that is contained in the customer tenancy 2621.
In other examples, the customer of the IaaS provider may have databases that live in the customer tenancy 2621. In this example, the control plane VCN 2616 can include the data plane mirror app tier 2640 that can include app subnet(s) 2626. The data plane mirror app tier 2640 can reside in the data plane VCN 2618, but the data plane mirror app tier 2640 may not live in the data plane VCN 2618. That is, the data plane mirror app tier 2640 may have access to the customer tenancy 2621, but the data plane mirror app tier 2640 may not exist in the data plane VCN 2618 or be owned or operated by the customer of the IaaS provider. The data plane mirror app tier 2640 may be configured to make calls to the data plane VCN 2618 but may not be configured to make calls to any entity contained in the control plane VCN 2616. The customer may desire to deploy or otherwise use resources in the data plane VCN 2618 that are provisioned in the control plane VCN 2616, and the data plane mirror app tier 2640 can facilitate the desired deployment, or other usage of resources, of the customer.
In some embodiments, the customer of the IaaS provider can apply filters to the data plane VCN 2618. In this embodiment, the customer can determine what the data plane VCN 2618 can access, and the customer may restrict access to public Internet 2654 from the data plane VCN 2618. The IaaS provider may not be able to apply filters or otherwise control access of the data plane VCN 2618 to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN 2618, contained in the customer tenancy 2621, can help isolate the data plane VCN 2618 from other customers and from public Internet 2654.
In some embodiments, cloud services 2656 can be called by the service gateway 2636 to access services that may not exist on public Internet 2654, on the control plane VCN 2616, or on the data plane VCN 2618. The connection between cloud services 2656 and the control plane VCN 2616 or the data plane VCN 2618 may not be live or continuous. Cloud services 2656 may exist on a different network owned or operated by the IaaS provider. Cloud services 2656 may be configured to receive calls from the service gateway 2636 and may be configured to not receive calls from public Internet 2654. Some cloud services 2656 may be isolated from other cloud services 2656, and the control plane VCN 2616 may be isolated from cloud services 2656 that may not be in the same region as the control plane VCN 2616. For example, the control plane VCN 2616 may be located in “Region 1,” and cloud service “Deployment 25,” may be located in Region 1 and in “Region 2.” If a call to Deployment 25 is made by the service gateway 2636 contained in the control plane VCN 2616 located in Region 1, the call may be transmitted to Deployment 25 in Region 1. In this example, the control plane VCN 2616, or Deployment 25 in Region 1, may not be communicatively coupled to, or otherwise in communication with, Deployment 25 in Region 2.
The control plane VCN 2716 can include a control plane DMZ tier 2720 (e.g., the control plane DMZ tier 2520 of
The data plane VCN 2718 can include a data plane app tier 2746 (e.g., the data plane app tier 2546 of
The untrusted app subnet(s) 2762 can include one or more primary VNICs 2764(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 2766(1)-(N). Each tenant VM 2766(1)-(N) can be communicatively coupled to a respective app subnet 2767(1)-(N) that can be contained in respective container egress VCNs 2768(1)-(N) that can be contained in respective customer tenancies 2770(1)-(N). Respective secondary VNICs 2772(1)-(N) can facilitate communication between the untrusted app subnet(s) 2762 contained in the data plane VCN 2718 and the app subnet contained in the container egress VCNs 2768(1)-(N). Each container egress VCNs 2768(1)-(N) can include a NAT gateway 2738 that can be communicatively coupled to public Internet 2754 (e.g., public Internet 2554 of
The Internet gateway 2734 contained in the control plane VCN 2716 and contained in the data plane VCN 2718 can be communicatively coupled to a metadata management service 2752 (e.g., the metadata management system 2552 of
In some embodiments, the data plane VCN 2718 can be integrated with customer tenancies 2770. This integration can be useful or desirable for customers of the IaaS provider in some cases such as a case that may desire support when executing code. The customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects. In response to this, the IaaS provider may determine whether to run code given to the IaaS provider by the customer.
In some examples, the customer of the IaaS provider may grant temporary network access to the IaaS provider and request a function to be attached to the data plane app tier 2746. Code to run the function may be executed in the VMs 2766(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN 2718. Each VM 2766(1)-(N) may be connected to one customer tenancy 2770. Respective containers 2771(1)-(N) contained in the VMs 2766(1)-(N) may be configured to run the code. In this case, there can be a dual isolation (e.g., the containers 2771(1)-(N) running code, where the containers 2771(1)-(N) may be contained in at least the VM 2766(1)-(N) that are contained in the untrusted app subnet(s) 2762), which may help prevent incorrect or otherwise undesirable code from damaging the network of the IaaS provider or from damaging a network of a different customer. The containers 2771(1)-(N) may be communicatively coupled to the customer tenancy 2770 and may be configured to transmit or receive data from the customer tenancy 2770. The containers 2771(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN 2718. Upon completion of running the code, the IaaS provider may kill or otherwise dispose of the containers 2771(1)-(N).
In some embodiments, the trusted app subnet(s) 2760 may run code that may be owned or operated by the IaaS provider. In this embodiment, the trusted app subnet(s) 2760 may be communicatively coupled to the DB subnet(s) 2730 and be configured to execute CRUD operations in the DB subnet(s) 2730. The untrusted app subnet(s) 2762 may be communicatively coupled to the DB subnet(s) 2730, but in this embodiment, the untrusted app subnet(s) may be configured to execute read operations in the DB subnet(s) 2730. The containers 2771(1)-(N) that can be contained in the VM 2766(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s) 2730.
In other embodiments, the control plane VCN 2716 and the data plane VCN 2718 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 2716 and the data plane VCN 2718. However, communication can occur indirectly through at least one method. An LPG 2710 may be established by the IaaS provider that can facilitate communication between the control plane VCN 2716 and the data plane VCN 2718. In another example, the control plane VCN 2716 or the data plane VCN 2718 can make a call to cloud services 2756 via the service gateway 2736. For example, a call to cloud services 2756 from the control plane VCN 2716 can include a request for a service that can communicate with the data plane VCN 2718.
The control plane VCN 2816 can include a control plane DMZ tier 2820 (e.g., the control plane DMZ tier 2520 of
The data plane VCN 2818 can include a data plane app tier 2846 (e.g., the data plane app tier 2546 of
The untrusted app subnet(s) 2862 can include primary VNICs 2864(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 2866(1)-(N) residing within the untrusted app subnet(s) 2862. Each tenant VM 2866(1)-(N) can run code in a respective container 2867(1)-(N), and be communicatively coupled to an app subnet 2826 that can be contained in a data plane app tier 2846 that can be contained in a container egress VCN 2868. Respective secondary VNICs 2872(1)-(N) can facilitate communication between the untrusted app subnet(s) 2862 contained in the data plane VCN 2818 and the app subnet contained in the container egress VCN 2868. The container egress VCN can include a NAT gateway 2838 that can be communicatively coupled to public Internet 2854 (e.g., public Internet 2554 of
The Internet gateway 2834 contained in the control plane VCN 2816 and contained in the data plane VCN 2818 can be communicatively coupled to a metadata management service 2852 (e.g., the metadata management system 2552 of
In some examples, the pattern illustrated by the architecture of block diagram 2800 of
In other examples, the customer can use the containers 2867(1)-(N) to call cloud services 2856. In this example, the customer may run code in the containers 2867(1)-(N) that requests a service from cloud services 2856. The containers 2867(1)-(N) can transmit this request to the secondary VNICs 2872(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet 2854. Public Internet 2854 can transmit the request to LB subnet(s) 2822 contained in the control plane VCN 2816 via the Internet gateway 2834. In response to determining the request is valid, the LB subnet(s) can transmit the request to app subnet(s) 2826 that can transmit the request to cloud services 2856 via the service gateway 2836.
It should be appreciated that IaaS architectures 2500, 2600, 2700, 2800 depicted in the figures may have other components than those depicted. Further, the embodiments shown in the figures are only some examples of a cloud infrastructure system that may incorporate an embodiment of the disclosure. In some other embodiments, the IaaS systems may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration or arrangement of components.
In certain embodiments, the IaaS systems described herein may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. An example of such an IaaS system is the Oracle Cloud Infrastructure (OCI) provided by the present assignee.
Bus subsystem 2902 provides a mechanism for letting the various components and subsystems of computer system 2900 communicate with each other as intended. Although bus subsystem 2902 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 2902 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.
Processing unit 2904, which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 2900. One or more processors may be included in processing unit 2904. These processors may include single core or multicore processors. In certain embodiments, processing unit 2904 may be implemented as one or more independent processing units 2932 and/or 2934 with single or multicore processors included in each processing unit. In other embodiments, processing unit 2904 may also be implemented as a quad-core processing unit formed by integrating two dual-core processors into a single chip.
In various embodiments, processing unit 2904 can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processor(s) 2904 and/or in storage subsystem 2918. Through suitable programming, processor(s) 2904 can provide various functionalities described above. Computer system 2900 may additionally include a processing acceleration unit 2906, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.
I/O subsystem 2908 may include user interface input devices and user interface output devices. User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands. User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.
User interface input devices may also include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio/visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices. Additionally, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasonography devices. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.
User interface output devices may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like. In general, use of the term “output device” is intended to include all possible types of devices and mechanisms for outputting information from computer system 2900 to a user or other computer. For example, user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio/video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.
Computer system 2900 may comprise a storage subsystem 2918 that provides a tangible non-transitory computer-readable storage medium for storing software and data constructs that provide the functionality of the embodiments described in this disclosure. The software can include programs, code modules, instructions, scripts, etc., that when executed by one or more cores or processors of processing unit 2904 provide the functionality described above. Storage subsystem 2918 may also provide a repository for storing data used in accordance with the present disclosure.
As depicted in the example in
System memory 2910 may also store an operating system 2916. Examples of operating system 2916 may include various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems, a variety of commercially-available UNIX® or UNIX-like operating systems (including without limitation the variety of GNU/Linux operating systems, the Google Chrome® OS, and the like) and/or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® OS, and Palm® OS operating systems. In certain implementations where computer system 2900 executes one or more virtual machines, the virtual machines along with their guest operating systems (GOSs) may be loaded into system memory 2910 and executed by one or more processors or cores of processing unit 2904.
System memory 2910 can come in different configurations depending upon the type of computer system 2900. For example, system memory 2910 may be volatile memory (such as random access memory (RAM)) and/or non-volatile memory (such as read-only memory (ROM), flash memory, etc.) Different types of RAM configurations may be provided including a static random access memory (SRAM), a dynamic random access memory (DRAM), and others. In some implementations, system memory 2910 may include a basic input/output system (BIOS) containing basic routines that help to transfer information between elements within computer system 2900, such as during start-up.
Computer-readable storage media 2922 may represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, computer-readable information for use by computer system 2900 including instructions executable by processing unit 2904 of computer system 2900.
Computer-readable storage media 2922 can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information. This can include tangible computer-readable storage media such as RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media.
By way of example, computer-readable storage media 2922 may include a hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive that reads from or writes to a removable, nonvolatile magnetic disk, and an optical disk drive that reads from or writes to a removable, nonvolatile optical disk such as a CD ROM, DVD, and Blu-Ray® disk, or other optical media. Computer-readable storage media 2922 may include, but is not limited to, Zip® drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tape, and the like. Computer-readable storage media 2922 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs. The disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, program modules, and other data for computer system 2900.
Machine-readable instructions executable by one or more processors or cores of processing unit 2904 may be stored on a non-transitory computer-readable storage medium. A non-transitory computer-readable storage medium can include physically tangible memory or storage devices that include volatile memory storage devices and/or non-volatile storage devices. Examples of non-transitory computer-readable storage medium include magnetic storage media (e.g., disk or tapes), optical storage media (e.g., DVDs, CDs), various types of RAM, ROM, or flash memory, hard drives, floppy drives, detachable memory drives (e.g., USB drives), or other type of storage device.
Communications subsystem 2924 provides an interface to other computer systems and networks. Communications subsystem 2924 serves as an interface for receiving data from and transmitting data to other systems from computer system 2900. For example, communications subsystem 2924 may enable computer system 2900 to connect to one or more devices via the Internet. In some embodiments communications subsystem 2924 can include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.11 family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components. In some embodiments communications subsystem 2924 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.
In some embodiments, communications subsystem 2924 may also receive input communication in the form of structured and/or unstructured data feeds 2926, event streams 2928, event updates 2930, and the like on behalf of one or more users who may use computer system 2900.
By way of example, communications subsystem 2924 may be configured to receive data feeds 2926 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.
Additionally, communications subsystem 2924 may also be configured to receive data in the form of continuous data streams, which may include event streams 2928 of real-time events and/or event updates 2930, that may be continuous or unbounded in nature with no explicit end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.
Communications subsystem 2924 may also be configured to output the structured and/or unstructured data feeds 2926, event streams 2928, event updates 2930, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system 2900.
Computer system 2900 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.
Due to the ever-changing nature of computers and networks, the description of computer system 2900 depicted in the figure is intended only as a specific example. Many other configurations having more or fewer components than the system depicted in the figure are possible. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, firmware, software (including applets), or a combination. Further, connection to other computing devices, such as network input/output devices, may be employed. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will appreciate other ways and/or methods to implement the various embodiments.
Although specific embodiments have been described, various modifications, alterations, alternative constructions, and equivalents are also encompassed within the scope of the disclosure. Embodiments are not restricted to operation within certain specific data processing environments, but are free to operate within a plurality of data processing environments. Additionally, although embodiments have been described using a particular series of transactions and steps, it should be apparent to those skilled in the art that the scope of the present disclosure is not limited to the described series of transactions and steps. Various features and aspects of the above-described embodiments may be used individually or jointly.
Further, while embodiments have been described using a particular combination of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of the present disclosure. Embodiments may be implemented only in hardware, or only in software, or using combinations thereof. The various processes described herein can be implemented on the same processor or different processors in any combination. Accordingly, where components or services are described as being configured to perform certain operations, such configuration can be accomplished, e.g., by designing electronic circuits to perform the operation, by programming programmable electronic circuits (such as microprocessors) to perform the operation, or any combination thereof. Processes can communicate using a variety of techniques including but not limited to conventional techniques for inter process communication, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times.
The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. It will, however, be evident that additions, subtractions, deletions, and other modifications and changes may be made thereunto without departing from the broader spirit and scope as set forth in the claims. Thus, although specific disclosure embodiments have been described, these are not intended to be limiting. Various modifications and equivalents are within the scope of the following claims.
The use of the terms “a” and “an” and “the” and similar referents in the context of describing the disclosed embodiments (especially in the context of the following claims) are to be construed to cover both the singular and the plural, unless otherwise indicated herein or clearly contradicted by context. The terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (i.e., meaning “including, but not limited to,”) unless otherwise noted. The term “connected” is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein and each separate value is incorporated into the specification as if it were individually recited herein. All methods described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. The use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments and does not pose a limitation on the scope of the disclosure unless otherwise claimed. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.
Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is intended to be understood within the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.
Preferred embodiments of this disclosure are described herein, including the best mode known for carrying out the disclosure. Variations of those preferred embodiments may become apparent to those of ordinary skill in the art upon reading the foregoing description. Those of ordinary skill should be able to employ such variations as appropriate and the disclosure may be practiced otherwise than as specifically described herein. Accordingly, this disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, any combination of the above-described elements in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein.
All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.
In the foregoing specification, aspects of the disclosure are described with reference to specific embodiments thereof, but those skilled in the art will recognize that the disclosure is not limited thereto. Various features and aspects of the above-described disclosure may be used individually or jointly. Further, embodiments can be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of the specification. The specification and drawings are, accordingly, to be regarded as illustrative rather than restrictive.
This application is a non-provisional of and claims the benefit and priority under 35 U.S.C. 119(e) U.S. Provisional Application No. 63/407,571, titled “VIRTUAL PRIVATE LABEL CLOUD,” and filed on Sep. 16, 2022, which is incorporated herein by reference in its entirety for all purposes. This application is also related to the following applications. The entire contents of each of the following applications are incorporated herein by reference for all purposes. (1) Non-provisional application Ser. No. ______, titled “VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311130 (344800US)) filed concurrently with the present application;(2) Non-provisional application Ser. No. ______, titled “CONSOLE CUSTOMIZATION FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311132 (344900US)) filed concurrently with the present application;(3) Non-provisional application Ser. No. ______, titled “ENDPOINTS FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311138 (345100US)) filed concurrently with the present application;(4) Non-provisional application Ser. No. ______, titled “IDENTITY MANAGEMENT FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311139 (345200US)) filed concurrently with the present application;(5) Non-provisional application Ser. No. ______, titled “METADATA CUSTOMIZATION FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311136 (345300US)) filed concurrently with the present application;(6) Non-provisional application Ser. No. ______, titled “REMOTE DATA PLANES FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311141 (345400US)) filed concurrently with the present application;(7) Non-provisional application Ser. No. ______, titled “CONNECTIVITY FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1311142 (345500US)) filed concurrently with the present application;(8) Non-provisional application Ser. No. ______, titled “RESOURCE USAGE MONITORING, BILLING AND ENFORCEMENT FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1315390 (346900US)) filed concurrently with the present application; and(9) Non-provisional application Ser. No. ______, titled “CLOUD INFRASTRUCTURE-BASED ONLINE PUBLISHING PLATFORMS FOR VIRTUAL PRIVATE LABEL CLOUDS” (Atty Docket No, 088325-1315384 (346800US)) filed concurrently with the present application.
| Number | Date | Country | |
|---|---|---|---|
| 63407571 | Sep 2022 | US |
