Virtual Bootstrap Environment for Building Regional Data Centers

Abstract

Techniques are disclosed for establishing a virtual bootstrap environment. The distributed computing environment may generate a virtual cloud network in a host region corresponding to one or more data centers. The distributed computing system may then implement the virtual bootstrap environment in the virtual cloud network. A first service may be deployed in the virtual bootstrap environment. A network connection may be established between the host region and a target region. Then, the first service in the virtual bootstrap environment may deploy resources to the target region via the network connection.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 18 / 105,779, entitled "VIRTUAL BOOTSTRAP ENVIRONMENT FOR BUILDING REGIONAL DATA CENTERS," filed February 3, 2023, U.S. Provisional Patent Application No. 63 / 314,945, entitled "VIRTUAL BOOTSTRAP ENVIRONMENT FOR AUTOMATED BUILDING OF REGIONAL DATA CENTERS," filed February 28, 2022, U.S. Provisional Patent Application No. 63 / 308,003, entitled "TECHNIQUES FOR BOOTSTRAPPING A REGION BUILD," filed February 8, 2022, and U.S. Provisional Patent Application No. 63 / 312,814, entitled "TECHNIQUES FOR IMPLEMENTING VIRTUAL DATA CENTERS," filed February 22, 2022, the entire contents of each of which are incorporated herein by reference.

[0002] Technical Field TECHNICAL FIELD The present disclosure relates to building regional data centers. More particularly, the present disclosure describes techniques for deploying resources into a data center infrastructure during the building of a regional data center using a virtual bootstrap environment. [Background technology]

[0003] background A cloud infrastructure provider may provide cloud computing infrastructure and related services in many geographic areas around the world. To provide this infrastructure, the cloud infrastructure provider may operate one or more data centers corresponding to a local geographic area. These data centers may be included as part of a "region," which is a logical abstraction of the geographic area and computing resources of the one or more data centers. Building a new region may include provisioning computing resources, configuring infrastructure, and deploying code to those resources. Conventional techniques for building a region involve significant manual operations. Bootstrapping existing services into a new region can be difficult because the services may depend on the functionality of other existing services and / or resources in the region. Relying on manual operations to bootstrap services and / or build a region may not scale well because it incurs significant time costs and introduces risks associated with manual configuration errors. Summary of the Invention

[0004] overview Embodiments of the present disclosure relate to creating a bootstrap environment to support the construction of a region. Region construction may include bootstrapping (e.g., provisioning and / or deployment) of resources (e.g., infrastructure components, artifacts, etc.) for any suitable number of services in a region (e.g., a geographic location associated with one or more data centers). The bootstrap environment may be a virtual environment (e.g., a virtual cloud network) in an existing region. Thus, a virtual bootstrap environment (ViBE) may be constructed and configured in an existing region prior to the region construction process. Deployment of services (e.g., core services) into the ViBE may support bootstrapping of operations to a target region (e.g., a region constructed in the region construction process). Services in the ViBE may be used to provision computing resources (e.g., bare metal computing hosts, virtual machines, storage, etc.) in the target region. Services in the ViBE may also be used to deploy services, including instances of services in the ViBE, to the target region. Using cloud infrastructure orchestration services in conjunction with ViBE, new regions may be intelligently and automatically constructed. [Means for solving the problem]

[0005] One embodiment is directed to a computer-implemented method, the method may include a distributed computing system of a cloud service provider generating a virtual cloud network in a host region. The method may further include implementing a virtual bootstrap environment in the virtual cloud network and deploying a first service in the virtual bootstrap environment. The method may include establishing a network connection between the virtual cloud network and a target region. In some embodiments, one or more additional services including a second service may be deployed in the virtual bootstrap environment. The second service may be used to provision infrastructure resources in the target region. In some embodiments, the host region may include a host data center, while the target region may include a target data center. The method may also include deploying resources of the virtual bootstrap environment to the target region. The first service may be used to deploy the resources, and the resources may be deployed over a network connection. In some embodiments, the resources may be deployed to the infrastructure resources provisioned by using the second service. In some embodiments, the network connection may include a virtual private network connection using one or more IPSec tunnels.

[0006] Another embodiment is directed to a computing device including one or more processors and instructions that, when executed by the one or more processors, cause the computing device to perform the methods disclosed herein.

[0007] Yet another embodiment is directed to a non-transitory computer-readable medium having computer-executable instructions stored thereon that, when executed by one or more processors of a computing cluster, cause the computing cluster to perform the methods disclosed herein.

[0008] To easily identify the discussion of any particular element or operation, the most significant digit or digits of a reference number refer to the figure number in which that element is first introduced. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram of an environment in which a cloud infrastructure orchestration service (CIOS) may operate to dynamically provide bootstrap services in a region, according to at least one embodiment. [Diagram 2] FIG. 1 is a block diagram illustrating an environment and method for building a Virtual Bootstrap Environment (ViBE) according to at least one embodiment. [Diagram 3] 1 is a block diagram illustrating an environment and method for bootstrapping a service to a target region using ViBE, according to at least one embodiment. [Figure 4] 1 is a simplified diagram illustrating a target region and multiple host regions for supporting ViBE, according to at least one embodiment. [Diagram 5] FIG. 2 is a block diagram illustrating an example flow for performing operations for provisioning and deployment of a service to a region in accordance with at least one embodiment. [Figure 6] 2 is a block diagram illustrating an example architecture of a network connection between a ViBE and a target region according to at least one embodiment. [Figure 7] FIG. 13 is another block diagram illustrating an example architecture of a network connection between a remote access tenancy and a ViBE according to at least one embodiment. [Figure 8] FIG. 2 illustrates an example method for bootstrapping a region using services in ViBE according to at least one embodiment. [Figure 9] FIG. 1 is a block diagram illustrating a pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 10] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 11] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 12] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 13] FIG. 1 is a block diagram illustrating an exemplary computer system according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Detailed Description Example data center construction (region construction) infrastructure In recent years, the adoption of cloud services has been growing rapidly. Currently, various types of cloud services are offered by various different cloud service providers (CSPs). The term cloud service is generally used to describe a service or functionality that is made available on demand (e.g., through a subscription model) to a user or customer by a CSP through the use of systems and infrastructure (cloud infrastructure) that the CSP provides. Typically, the servers and systems that make up the CSP's infrastructure and that are used to provide cloud services to customers are separate from the customer's own on-premise servers and systems. This allows customers to use cloud services offered by CSPs without having to purchase separate hardware and software resources for the services. Cloud services are designed to provide easy, scalable, and on-demand access to applications and computing resources to subscribing customers, without the customer having to invest in procuring the infrastructure used to provide the services or functionality. Cloud services can be offered in various different types or models, such as software as a service (SaaS), platform as a service (PaaS), infrastructure as a service (IaaS), etc. A customer can subscribe to one or more cloud services offered by a CSP. A customer can be any entity, such as an individual, an organization, or a business.

[0011] As mentioned above, a CSP is responsible for providing the infrastructure and resources used to provide cloud services to its subscribing customers. The resources provided by a CSP may include both hardware and software resources. These resources may include, for example, compute resources (e.g., virtual machines, containers, applications, processors), memory resources (e.g., databases, data stores), networking resources (e.g., routers, host machines, load balancers), identities, and other resources. In one embodiment, the resources provided by a CSP to provide a set of cloud services are organized as a datacenter. A datacenter may be configured to provide a particular set of cloud services. A CSP is responsible for populating its datacenter with the infrastructure and resources used to provide the particular set of cloud services. A CSP may build one or more datacenters.

[0012] Datacenters offered by a CSP may be hosted in different regions. A region is a local geographic area and may be identified by a region name. Regions are generally independent from each other and may be separated by large distances, for example across countries or continents. Regions are grouped into realms. Examples of CSP regions include US West, US East, Australia East, Australia Southeast, etc.

[0013] A region may include one or more data centers, which are located within a geographic area corresponding to the region. As an example, the data centers in a region may be located in cities within the region. For example, for a particular CSP, the data center for the US West region may be located in San Jose, California, the data center for the US East region may be located in Ashburn, Virginia, the data center for the Australia East region may be located in Sydney, Australia, the data center for the Australia Southeast region may be located in Melbourne, Australia, etc.

[0014] Data centers within a region may be organized as one or more availability domains that are used for high availability and disaster recovery. An availability domain may contain one or more data centers within a region. Availability domains within a region are isolated from each other, fault tolerant, and designed to make it highly unlikely that data centers in multiple availability domains will fail simultaneously. For example, availability domains within a region may be structured to make it less likely that a failure in one availability domain within a region will affect the availability of data centers in other availability domains in the same region.

[0015] When a customer or subscriber registers or signs up for one or more services offered by a CSP, the CSP creates a tenancy for the customer. A tenancy is like an account created for a customer. In one embodiment, the tenancy for a customer exists in a single realm and has access to all regions that belong to that realm. And the customer's users can access the services for which the customer has registered under this tenancy.

[0016] As mentioned above, a CSP provides cloud services to its customers by building or deploying data centers. As a CSP's customer base expands, the CSP typically builds new data centers in new regions or expands the capacity of existing data centers to accommodate and serve the growing demands of customers and to better serve the customers. Data centers are preferably built in close geographic proximity to the locations of the customers served by the data center. The geographical proximity between a data center and the customers served by the data center helps in more efficient use of resources and providing faster and more reliable services to the customers. Thus, a CSP typically builds a new data center in a new region in a geographic area that is geographically close to the customers served by the data center. For example, if the customer base is expanding in Germany, the CSP may build one or more data centers in a new region in Germany.

[0017] Building a datacenter(s) in a region is sometimes referred to as building a region. The term "region build" is used to refer to building one or more datacenters in a region. Building a datacenter in a region involves provisioning or creating a new set of resources that are required or used to provide the set of services that the datacenter is configured to provide. The end result of the region build process is the creation of a datacenter in the region that is capable of providing the set of services intended for the datacenter and includes a set of resources that are used to provide this set of services.

[0018] Building a new datacenter in a region is a very complex task that requires extensive coordination between various bootstrapping activities. At a high level, this involves performing and coordinating various tasks such as identifying the set of services to be provided by the datacenter, identifying the various resources required to provide the set of services, creating, provisioning, and deploying the identified resources, and properly describing the resources to enable their intended use. Each of these tasks has further subtasks that require coordination, which further increases the complexity. Due to this complexity, currently, building a datacenter in a region involves multiple manual initiation or control tasks that require careful manual coordination. As a result, the task of building a new region (building one or more datacenters in a region) requires a lot of time. Building a datacenter can take many months, for example. This process is also highly error-prone and may require multiple iterations before the desired configuration of the datacenter is achieved, further lengthening the time it takes to build the datacenter. These constraints and issues severely limit the ability of CSPs to scale computing resources in a timely manner to meet growing customer needs.

[0019] This disclosure describes techniques for reducing the construction time, thereby reducing the waste of computing resources and reducing the risks associated with the construction of one or more data centers in a region. Whereas previously it took weeks and months to build a data center in a region, by using the techniques described herein, a new data center can be built in a region in a relatively much shorter time with less risk of error than traditional approaches.

[0020] Disclosed herein is a cloud infrastructure orchestration service (CIOS) configured to bootstrap (e.g., provision and deploy) services to a new datacenter based on a predefined configuration file that identifies resources (e.g., infrastructure components and software to be deployed) for implementing a given change to the datacenter. The CIOS can identify dependencies between resources, execution targets, phases, and flocks by parsing and analyzing the configuration file (e.g., flock configuration). The CIOS may generate specific data structures from the analysis and may use these data structures to drive operations and manage the order in which services are bootstrapped to regions. The CIOS may utilize these data structures to identify when a service can be bootstrapped, when the bootstrap is blocked, and / or when a bootstrap operation associated with a previously blocked service can be resumed. Advantageously, the CIOS can identify circular dependencies in the data structures and perform operations to eliminate / resolve these circular dependencies prior to the execution of the task. Using these techniques, the CIOS significantly reduces the risk of executing a task before the resources on which the task depends are available.

[0021] Using the techniques disclosed herein, CIOS may perform datacenter modifications through parallel processing optimizations while preventing tasks from starting until functionality on which they depend is available in the region. In this manner, CIOS allows for more efficient execution of region construction, significantly reducing the time required to build datacenters and the wasted computing resource usage seen with traditional approaches.

[0022] Certain definitions A "region" is a logical abstraction that corresponds to a geographic location. A region may include any suitable number of one or more execution targets. In some embodiments, an execution target may correspond to a data center.

[0023] An "execution target" represents the smallest unit of change for executing a release. A "release" represents a statement of intent to orchestrate a particular change to a service (e.g., deploying version 8, "adding internal DNS records", etc.). For most services, an execution target represents an "instance" of the service. A single service can be bootstrapped onto one or more execution targets each. An execution target can be associated with a set of devices (e.g., a data center).

[0024] "Bootstrapping" is intended to refer to the collective tasks associated with the provisioning and deployment of any suitable number of resources (e.g., infrastructure components, artifacts, etc.) that correspond to a single service.

[0025] A "service" refers to a functionality provided by a set of resources. The set of resources for a service includes any suitable combination of cloud provider hosted infrastructure, platform, or software (e.g., applications) that can be configured to provide the functionality of the service. A service may be made available to users over the Internet.

[0026] "Artifact" refers to an infrastructure component or code that is deployed to a Kubernetes engine cluster, which may include software (e.g., applications), configuration information for the infrastructure component (e.g., configuration files), etc.

[0027] A "flock config" refers to a configuration file (or a set of configuration files) that describes a set of all resources (e.g., infrastructure components and artifacts) associated with a single service. A flock config may contain declarative statements that specify one or more aspects that correspond to a desired state of the service's resources.

[0028] A "service state" represents a point-in-time snapshot of all resources (e.g., infrastructure resources, artifacts, etc.) associated with a service. A service state indicates the status corresponding to provisioning and / or deployment tasks associated with the service resources.

[0029] IaaS provisioning (or "provisioning") refers to obtaining a computer or virtual host for use, and even installing the necessary libraries or services on it. The expression "provisioning a device" refers to the evolution of a device to a state where it can be used by an end user for a specific purpose. A device that has gone through the provisioning process may also be referred to as a "provisioned device". Preparing a provisioned device (installing libraries and daemons) may be part of provisioning, but this is different from deploying a new application or a new version of an application to a prepared device. In most cases, deployment does not include provisioning, which may need to be performed first. A prepared device may also be referred to as an "infrastructure component".

[0030] IaaS deployment (or "deployment") refers to the process of provisioning and / or installing a new application or a new version of an application onto a provisioned infrastructure component. Once the infrastructure component has been provisioned (e.g., acquired, allocated, prepared, etc.), additional software may be deployed (e.g., provided and installed onto the infrastructure component). After provisioning and deployment are complete, the infrastructure component may be referred to as a "resource." Examples of resources include, but are not limited to, virtual machines, databases, object storage, block storage, load balancers, etc.

[0031] A "capability" identifies a unit of functionality associated with a service, which may be some or all of the functionality provided by the service. As an example, a capability may be published that indicates that a resource is available for authorization / authentication processing (e.g., a subset of the functionality provided by the resource). As another example, a capability may be published that indicates that all functionality of a service is available. Capabilities can be used to identify functionality on which a resource or service depends and / or the functionality of the resource or service that is available.

[0032] A "virtual bootstrap environment" (ViBE) represents a virtual cloud network that is provisioned in an overlay of an existing region (e.g., a "host region"). The provisioned ViBE is connected to the new region using a communication channel (e.g., IPSec Tunnel VPN). Certain essential core services (or "seed" services) can be provisioned in the ViBE, such as a deployment orchestrator, public key infrastructure (PKI) services, etc. These services can provide the capabilities required to bring hardware online, establish a chain of trust to the new region, and deploy other services in the new region. The use of a virtual bootstrap environment can prevent circular dependencies between bootstrap resources by utilizing resources in the host region. Services can be staged and tested in the ViBE before the physical region (e.g., the target region) is available.

[0033] "Cloud Infrastructure Orchestration Service" (CIOS) may refer to a system configured to manage the provisioning and deployment operations of any suitable number of services as part of a region construction.

[0034] A multi-flock orchestrator (MFO) may be a computing component (e.g., a service) that coordinates events between components of the CIOS to provision and deploy services to a target region (e.g., a new region). The MFO tracks events related to each service in the region build and takes action in response to the events.

[0035] A "host region" refers to a region that hosts a Virtual Bootstrap Environment (ViBE). A host region may be used to bootstrap a ViBE.

[0036] "Target region" refers to the region being constructed. "Publishing a capability" refers to "publishing" as used in "publisher-subscriber" computing design, or providing an indication that a particular capability is available (or unavailable). Capabilities provide an indication that a resource / service's functionality is available by "publishing" (e.g., collected by a capability service, provided to a capability service, pushed, pulled, etc.). In some embodiments, capabilities may be published / transmitted by an event, notification, data transmission, function call, API call, etc. An event (or other notification / data transmission, etc.) indicating availability of a particular capability can be broadcast / addressed (e.g., published) to a capability service.

[0037] A "capabilities service" may be a flock that is configured to model dependencies between different flocks. Capabilities services may be provided within a cloud infrastructure orchestration service and may define capabilities, services, and / or features that are made available in a region.

[0038] A "Real-time Regional Data Distributor" (RRDD) can be a service or system configured to manage regional data that can be injected into a flock configuration to dynamically create new regional execution targets.

[0039] In some examples, techniques are described herein for implementing a cloud infrastructure orchestration service (CIOS). Such techniques can be configured to manage the bootstrapping (e.g., software provisioning and deployment) of infrastructure components within a cloud environment (e.g., region), as briefly described above. In some cases, the CIOS can comprise computing components (e.g., CIOS central and CIOS regional (both of which are described in more detail below)) that can be configured to manage the bootstrapping tasks (provisioning and deployment) for a given service as well as a multi-flock orchestrator (also described in more detail below) that is configured to initiate / manage region construction (e.g., bootstrapping operations corresponding to multiple services).

[0040] CIOS enables region builds and global infrastructure provisioning and code deployment with minimal manual effort by service teams (e.g., beyond initial approval and / or physical shipping of hardware, as the case may be). High level responsibilities of CIOS include, but are not limited to, coordinating region builds, providing users with a current view of the resources it manages (e.g., within regions, across regions, globally, etc.), and managing the bootstrap operations to bootstrap resources within regions.

[0041] The CIOS may provide view reconciliation that can reconcile a view of a desired state (e.g., desired configuration) of a resource with the current / actual state (e.g., current configuration) of the resource. In some cases, view reconciliation may include obtaining state data that identifies the actual operating resources and their respective current configurations and / or states. Reconciliation may be performed at various levels of granularity, such as at the service level.

[0042] The CIOS can perform plan generation in which differences between desired and current states of resources are identified. Part of plan generation can include identifying actions that need to be performed to move resources from their current state to the desired state. In some examples, the CIOS can present the generated plan to a user for approval. In these examples, the CIOS can allow the user to accept or reject the plan based on user input from the user. This allows the user to spend less time reasoning about the plan, and since the plan is machine-generated, it is more accurate. Most of the plans are too detailed for human consumption, but the CIOS can provide this data through an advanced user interface (UI).

[0043] In some instances, the CIOS can handle change control execution by executing approved plans. Once an execution plan has been created and approved, engineers may not need to participate in change control unless the CIOS initiates a rollback. The CIOS can handle rollbacks to previous service versions (e.g., if it detects degradation of service health during execution) by generating a plan to revert the service to a previous (e.g., pre-release) state.

[0044] CIOS can measure service health by monitoring alerts and running integration tests. CIOS can help teams quickly prescribe and later execute rollback behavior in case of service degradation. CIOS can generate and display plans as well as track approvals. CIOS can combine provisioning and deployment capabilities in a single system that coordinates these tasks across region builds. CIOS also supports discovery of flocks (e.g., service resources such as flock configurations corresponding to any suitable number of services), artifacts, resources, and dependencies. CIOS can discover dependencies between execution tasks at any level (e.g., resource level, execution target level, phase level, service level, etc.) by static analysis (e.g., including parsing and processing the contents) of one or more configuration files. Using these dependencies, CIOS can generate various data structures from these dependencies that can be used to drive task execution (e.g., tasks related to provisioning infrastructure resources and deployment of artifacts across regions).

[0045] FIG. 1 is a block diagram of an environment 100 in which a cloud infrastructure orchestration service (CIOS) 102 may operate to dynamically provide bootstrap services in a region, according to at least one embodiment. CIOS 102 may include components such as, but not limited to, a real-time regional data distributor (RRDD) 104, a multi-flock orchestrator (MFO) 106, a CIOS central 108, a CIOS regional 110, and a capability service 112. The specific functions of CIOS central 108 and CIOS regional 110 are provided in more detail in U.S. patent application Ser. No. 17 / 016,754, entitled "Techniques for Deploying Infrastructure Resources with a Declarative Provisioning Tool," the entire contents of which are incorporated herein by reference. In some embodiments, any suitable combination of the components of CIOS 102 may be provided as a service. In some embodiments, any portion of CIOS 102 may be deployed to a region (e.g., a data center represented by host region 103). In some embodiments, CIOS 102 may include any suitable number of cloud services (not shown in FIG. 1), as discussed in more detail below with respect to U.S. patent application Ser. No. 17 / 016,754 and FIGS. 2 and 3.

[0046] The real-time regional data distributor (RRDD) 104 may be configured to maintain and provide regional data that identifies realms, regions, execution targets, and availability domains. In some cases, the regional data may be in any suitable form (e.g., JSON format, data object / container, XML, etc.). The regional data maintained by the RRDD 104 may include any suitable number of data subsets that may be individually referenceable by a corresponding identifier. As an example, an identifier "all_regions" may be associated with a data structure (e.g., a list, structure, object, etc.) that includes metadata for all defined regions. As another example, an identifier such as "realm" may be associated with a data structure that identifies metadata for a number of realms and a set of regions corresponding to each realm. In general, the regional data may maintain any suitable attributes of one or more realms, regions, availability domains (ADs), execution targets (ETs), etc. (identifiers, DNS suffixes, state (e.g., state of the region), etc.). The RRDD 104 may be configured to manage regional state as part of the regional data. The regional state may include any suitable information indicative of the state of bootstrap within the region. By way of example, some exemplary region states may include "initial," "constructing," "creating," "suspended," or "decommissioned." The "initial" state may indicate a region that has not yet been bootstrapped. The "constructing" state may indicate that bootstrapping of one or more blocks in the region has begun. The "creating" state may indicate that bootstrapping is complete and the region is ready for validation. The "suspended" state may indicate that CIOS Central 108 or CIOS Regional 110 has suspended internal interactions with the regional stack, possibly due to operational issues. The "decommissioned" state may indicate that the region has been decommissioned and may be unavailable and / or unable to be reconnected.

[0047] CIOS central 108 may be configured to provide any suitable number of user interfaces through which a user (e.g., user 109) may interact with CIOS 102. As an example, a user may modify region data through a user interface provided by CIOS central 108. CIOS central 108 may additionally provide a variety of interfaces that allow a user to review changes made to flocking and / or artifacts, generate and review plans, approve / reject plans, and review status regarding plan execution (e.g., corresponding to infrastructure provisioning, deployment, tasks involving region construction, and / or a desired state of any suitable number of resources managed by CIOS 102). CIOS central 108 may implement a control plane that is configured to manage any suitable number of CIOS regional 110 instances. CIOS central 108 may provide one or more user interfaces that allow user 109 to review and / or modify region data through presentation of the region data. CIOS central 108 may be configured to invoke RRDD 104 functions through any suitable number of interfaces. In general, the CIOS central 108 may be configured to manage region data directly or indirectly (e.g., via the RRDD 104). The CIOS central 108 may be configured to inject the region data into a flock configuration as a variable upon compilation of the flock configuration.

[0048] Each instance of CIOS regional 110 may correspond to a component or module configured to perform the bootstrapping tasks associated with a single service of the region. CIOS regional 110 may receive desired state data from CIOS central 108. In some embodiments, the desired state data may include a flock configuration that declares (e.g., by declarative statements) a desired state of the resources associated with the service. CIOS central 108 may maintain current state data that indicates any suitable aspect of the current state of the resources associated with the service. In some embodiments, CIOS regional 110 may identify one or more resources as requiring modification by comparing the desired state data and the current state data. For example, CIOS regional 110 may determine that provisioning of one or more infrastructure components, deployment of one or more artifacts, or any suitable modification of the resources of the service is required to bring the state of the resources into line with the desired state. When CIOS regional 110 performs the bootstrapping operation, it may publish data indicating various capabilities of the resources that have been made available. A "capability" identifies a unit of functionality associated with a service. This unit may be some or all of the functionality provided by the service. As an example, a capability may be published indicating that a resource is available for authorization / authentication processing (e.g., a subset of the functionality provided by the resource). As another example, a capability may be published indicating that all functionality of a service is available. Capabilities may be used to identify functionality on which a resource or service depends and / or the functionality of the resource or service that is available.

[0049] The capability service 112 is configured to maintain capability data that indicates: 1) capabilities of various services that are currently available; 2) whether any resources / services are waiting for a particular capability; 3) specific resources and / or services waiting for a given capability; or any suitable combination thereof. The capability service 112 may provide an interface through which the capability data may be requested. The capability service 112 may provide one or more interfaces (e.g., application programming interfaces) that enable the capability service 112 to send the capability data to the MFO 106 and / or CIOS regional 110 (e.g., each instance of the CIOS regional 110). In some embodiments, any suitable component or module of the MFO 106 and / or CIOS regional 110 may be configured to request the capability data from the capability service 112.

[0050] In some embodiments, a multi-flock orchestrator (MFO) 106 may be configured to drive region construction attempts. In some embodiments, the MFO 106 may manage information representing the flock / flock configuration version and / or artifact version utilized to bootstrap a given service in the region (or configure a change unit for the target region). In some embodiments, the MFO 106 may be configured to monitor (or be notified of) changes to the region data managed by the real-time regional data distributor 104. In some embodiments, region construction may be triggered by the MFO 106 upon receiving an indication that the region data has changed. In some embodiments, the MFO 106 may collect various flock configurations and artifacts used in region construction. Some or all of the flock configurations may be configured to be region agnostic; that is, the flock configuration may not explicitly identify the region to which the flock is bootstrapped. In some embodiments, the MFO 106 may initiate a data injection process in which the collected flock configurations are recompiled (e.g., by the CIOS central 108). During recompilation, execution of an action (e.g., by CIOS Central 108) injects the configuration file with region data maintained by the real-time regional data distributor 104. The flock configuration can reference the region data through variables / parameters without requiring hard-coded identification of the region data. This data injection allows the flock configuration to be dynamically modified at run time without hard-coding the region data, making it more difficult to change.

[0051] The multi-flock orchestrator 106 can perform static flock analysis, which analyzes the flock configuration to identify dependencies between resources, execution targets, phases, and flocks, and in particular, to identify circular dependencies that need to be eliminated. In some embodiments, the MFO 106 can generate any suitable number of data structures based on the identified dependencies. These data structures (e.g., directed acyclic graphs, linked lists, etc.) can be utilized by the cloud infrastructure orchestration service 102 to drive operations to perform region construction. As an example, these data structures can collectively specify the order in which services are bootstrapped within a region. An example of such a data structure is discussed separately below with respect to the construction dependency graph 338 of FIG. 3. If circular dependencies (e.g., service A requires service B and vice versa) exist and are identified by the static flock analysis and / or graph, the MFO can be configured to notify any suitable service team that a corresponding change in the flock configuration is required to correct these circular dependencies. The MFO 106 can be configured to manage the order in which services are bootstrapped into a region by traversing one or more data structures. The MFO 106 can identify capabilities available within a given region at any given time (e.g., using data obtained from the capability service 112). The MFO 106 can use this data to identify when the CIOS regional 110 can bootstrap a service, when bootstrap is blocked, and / or when a bootstrap operation associated with a previously blocked service can be resumed. Based on this passage, the MFO 106 can perform various releases in which the MFO 106 sends instructions to the CIOS central 108 to perform bootstrap operations corresponding to any suitable number of flock configurations. In some examples, the MFO 106 can be configured to identify that one or more flock configurations may require multiple releases due to the presence of circular dependencies in the graph.As a result, the MFO 106 may resolve circular dependencies identified in the graph by sending multiple sets of instructions to the CIOS central 108 for a given block configuration.

[0052] In some embodiments, a user may request the construction of a new region (e.g., target region 114). This may include bootstrapping resources corresponding to various services. In some embodiments, target region 114 may not be reachable (and / or secure) at the time the region construction request is initiated. Rather than deferring bootstrapping until the target region 114 is available and configured to perform the bootstrapping operation, CIOS 102 may initiate region construction using a virtual bootstrap environment 116. The virtual bootstrap environment (ViBE) 116 may be an overlay network hosted by host region 103 (an existing region that has previously been configured with a core set of services, is reachable, and is secure). MFO 106 may utilize the resources of host region 103 to bootstrap resources into ViBE 116 (commonly referred to as "constructing a ViBE"). As an example, MFO 106, through CIOS Central 108, can provide instructions to an instance of CIOS Regional 110 in a host region (e.g., host region 103) to bootstrap another instance of CIOS Regional in ViBE 116. Once the CIOS Regional in ViBE is available for processing, bootstrapping of services to target region 114 can continue in ViBE 116. Previously bootstrapped services in ViBE 116 can be moved to target region 114 when target region 114 is available to perform the bootstrap operation. By utilizing these techniques, CIOS 102 can greatly increase the speed of region construction by significantly reducing the need for any manual input and / or provision of configuration.

[0053] 2 is a block diagram illustrating an environment 200 and method for constructing a virtual bootstrap environment (ViBE) 202 (an example of ViBE 116 of FIG. 1) according to at least one embodiment. ViBE 202 represents a virtual cloud network that is provisioned in an overlay of an existing region (e.g., hosted region 204, which is an example of hosted region 103 of FIG. 1 and, in one embodiment, a hosted region service enclave). ViBE 202 represents an environment in which services may be staged to a target region (e.g., a region under construction, such as target region 114 of FIG. 1) before the target region is available.

[0054] To bootstrap a new region (e.g., target region 114 in FIG. 1), a core set of services can be bootstrapped. These core set of services exist in the host region 204, but do not exist in ViBE (nor in the target region). These essential core services provide the functionality required for provisioning devices, establishing a chain of trust to the new region, and deploying other services (e.g., flocks) to the region. ViBE 202 can be a tenancy deployed in the host region 204. This can be thought of as a virtual region.

[0055] When a target region is available for bootstrapping operations, ViBE202 can connect to the target region so that services in the ViBE can interact with services and / or infrastructure components of the target region. This allows for deployment of generation-level services instead of self-contained seed services as in traditional systems and requires connectivity to the target region over the Internet. Traditionally, seed services are deployed as part of a collection of containers and used to bootstrap dependencies required to build the region. Using the existing regional infrastructure / tools, resources can be bootstrapped (e.g., provisioned and deployed) to ViBE202 and connected to the service enclaves of the region (e.g., host region 204) for hardware provisioning and service deployment until the target region is self-sufficient and can communicate directly. Utilization of ViBE202 allows for establishment of dependencies and services required to enable infrastructure provisioning / preparation and software deployment while utilizing the host region's resources breaks circular dependencies for core services.

[0056] A multi-flock orchestrator (MFO) 206 may be configured to perform operations to build (e.g., configure) ViBE 202. MFO 206 may obtain applicable flock configurations corresponding to various resources to be bootstrapped into a new region (in this case, the ViBE region of ViBE 202). As an example, MFO 206 may obtain a flock configuration (e.g., a "ViBE flock configuration") that identifies aspects of bootstrap capability service 208 and worker 210. As another example, MFO 206 may obtain another flock configuration corresponding to bootstrap of domain name service (DNS) 212 into ViBE 202.

[0057] In step 1, MFO 206 may issue instructions to CIOS central 214 (e.g., an example of CIOS central 108 and CIOS central 214 of FIGS. 1 and 2, respectively). For example, MFO 206 may send a request (e.g., including a ViBE flock configuration) to bootstrap capability services 208 and workers 210 that do not yet exist in ViBE 202 at this point. In some embodiments, CIOS central 214 may have access to all flock configurations. Thus, in some examples, MFO 206 may send an identifier for the ViBE flock configuration rather than the file itself, and CIOS central 214 may independently retrieve the identifier from storage (e.g., DB 308 or flock DB 312 of FIG. 3).

[0058] In step 2, CIOS central 214 may provide, via a corresponding request, the ViBE flock configuration to CIOS regional 216. In step 3, CIOS regional 216 may analyze the ViBE flock configuration to identify and perform specific infrastructure provisioning and deployment operations.

[0059] In some embodiments, CIOS regional 216 may utilize additional corresponding services for provisioning and deployment. For example, in step 4, CIOS regional 216 may instruct deployment orchestrator 218 (e.g., an example of the host region's 204 core services or other writing, building, and deployment application software) to execute instructions that bootstrap capability service 208 and worker 210 in ViBE 202.

[0060] In step 5, a capability may be sent to capability service 208 (e.g., from CIOS regional 216, deployment orchestrator 218, via worker 210) indicating that resources corresponding to the ViBE block are available. Capability service 208 may persist this data. In some embodiments, capability service 208 adds this information to a list that maintains capabilities available in ViBE. As an example, the capability provided to capability service 208 in step 5 may indicate that capability service 208 and worker 210 are available for processing.

[0061] In step 6, the MFO 206 may, based on receiving or obtaining data (an identifier corresponding to a capability) from the capability service 208, identify that the capability indicates that the capability service 208 and worker 210 are available.

[0062] In step 7, as a result of receiving / obtaining the data in step 6, MFO 206 may instruct CIOS Central 214 to bootstrap a DNS service (e.g., DNS 212) into ViBE 202. These instructions may identify or include a particular block configuration that corresponds to the DNS service.

[0063] In step 8, CIOS central 214 may instruct CIOS regional 216 to deploy DNS 212 to ViBE 202. In some embodiments, CIOS central 214 provides a DNS flocking configuration for DNS 212.

[0064] In step 9, a worker 210 deployed on ViBE 202 may be assigned the task of deploying DNS 212 by CIOS regional 216. Worker 210 may execute a declarative infrastructure provisioner as described above in connection with FIGURE 3 to identify a set of operations that need to be performed for the deployment of DNS 212 (e.g., by comparing the flock configuration (desired state) against the current state of the (non-existent) resources associated with the flock).

[0065] At step 10, deployment orchestrator 218 may instruct worker 210 to deploy DNS 212 according to the actions identified at step 9. As shown, worker 210 proceeds to perform the actions of deploying DNS 212 to ViBE 202 at step 11. At step 12, worker 210 notifies capability service 208 that DNS 212 is available on ViBE 202. MFO 206 may then identify the ViBE flock configuration and resources associated with the DNS flock configuration as available and proceed to bootstrap any suitable number of additional resources into ViBE.

[0066] After steps 1-12 are completed, the process for building ViBE 202 is complete and ViBE 202 may be considered built.

[0067] FIG. 3 is a block diagram illustrating an environment 300 and method for bootstrapping a service to a target region using ViBE, according to at least one embodiment.

[0068] In step 1, user 302 may modify region data using any suitable user interface provided by CIOS central 304 (an example of CIOS central 108 and CIOS central 214 in FIGS. 1 and 2, respectively). As an example, user 302 may create a new region into which a number of services are bootstrapped.

[0069] In step 2, CIOS central 304 may perform an operation to send the changes to RRDD 306 (an example of RRDD 104 in FIG. 1). In step 3, RRDD 306 may store the received region data in database 308, which is a data store configured to store region data including any suitable identifiers, attributes, states, etc., such as region, AD, realm, ET, etc. In some embodiments, updater 307 may be utilized to store the region data in database 308 or any suitable data store that may make such updates accessible (e.g., by a service team). In some embodiments, updater 307 may be configured to notify updates to database 308 (e.g., by any suitable electronic notification).

[0070] In step 4, the MFO 310 (an example of the MFOs 106 and 206 in FIGS. 1 and 2, respectively) may detect changes in the region data. In some embodiments, the MFO 310 may be configured to poll the RRDD 306 for changes in the region data. In some embodiments, the RRDD 306 may be configured to publish or notify the MFO 310 of the region changes.

[0071] In step 5, detecting a change in region data may trigger MFO 310 to retrieve a version set (e.g., a version set associated with a particular identifier, such as a "golden version set" identifier) ​​that identifies the specific version of each flock (e.g., service) and each artifact corresponding to that flock that is to be bootstrapped into the new region. The version set may be retrieved from DB 312. As a flock evolves and changes, the versions of each corresponding setting and artifact used to build the region may also change. These changes may be persisted in flock DB 312 so that MFO 310 may identify the version of the flock setting and artifact to use to build the region (e.g., ViBE region, target region / non-ViBE region, etc.). Flock settings (e.g., all versions of a flock setting) and / or artifacts (e.g., all versions of an artifact) may be stored in DB 308, DB 312, or any suitable data store that CIOS Central 304 and / or MFO 310 may have access to.

[0072] In step 6, the MFO 310 may request that the CIOS Central 304 recompile each of the flock settings associated with the version set with the current region data. In some embodiments, this request may indicate the version of each flock setting and / or the artifacts that correspond to those flock settings.

[0073] In step 7, the CIOS Central 304 may obtain the current regional data from the DB 308 (eg, directly or via the real-time regional data distributor 306) and retrieve any suitable flock settings and artifacts according to the version requested by the MFO 310.

[0074] In step 8, CIOS Central 304 may inject the current region data into the flock configuration by recompiling the flock configuration with the region data obtained in step 7. CIOS Central 304 may return the compiled flock configuration to MFO 310. In some embodiments, CIOS Central 304 may only indicate that compilation has occurred, and MFO 310 may access the recompiled flock configuration via RRDD 306.

[0075] In step 9, the MFO 310 may perform a static analysis of the recompiled flock configuration. As part of the static analysis, the MFO 310 may identify dependencies between flocks by analyzing the flock configuration (e.g., using a library associated with a declarative infrastructure provisioner (e.g., Terraform, etc.)). From this analysis and the identified dependencies, the MFO 310 may generate a construction dependency graph 338. The construction dependency graph 338 may be a directed acyclic graph that identifies the order in which flocks are bootstrapped into new regions (and / or changes indicated in the flock configuration are applied). Each node in the graph may correspond to the bootstrapping of any suitable portion of a particular flock. A specific bootstrap order may be identified based at least in part on the dependencies. In some embodiments, the dependencies may be expressed as attributes of the nodes and / or specified by the edges of the graph connecting the nodes. The MFO 310 may drive the region construction operations by traversing the graph (e.g., starting from a start node).

[0076] In some embodiments, MFO 310 may utilize a cycle detection algorithm to detect the presence or absence of a cycle (e.g., service A depends on service B, and vice versa). MFO 310 may identify orphan capability dependencies. For example, MFO 310 may identify orphan nodes in construction dependency graph 338 that are not connected to other nodes. MFO 310 may identify capabilities that have been issued improperly (e.g., when a capability is issued prematurely and the corresponding functionality is not yet actually available). MFO 310 may detect from the graph that there are one or more instances that issue the same capability. In some embodiments, any suitable number of these errors may be detected, and MFO 310 (or another suitable component, such as CIOS Central 304) may be configured to notify or present this information to a user (e.g., via electronic notification, a user interface, etc.). In some embodiments, MFO 310 may be configured to resolve circular dependencies by force-deleting / recreating resources and may again instruct CIOS Central 304 to perform bootstrap operations for those resources and / or corresponding block configurations.

[0077] The initiating node may correspond to bootstrapping the ViBE flock, and the second node may correspond to bootstrapping the DNS. Steps 10-15 correspond to deployment of the ViBE flock (by deployment orchestrator 317, which is an example of deployment orchestrator 218 of FIG. 2) to ViBE 316 (e.g., an example of ViBE 116 and 202 of FIGS. 1 and 2, respectively). That is, steps 10-15 of FIG. 3 generally correspond to steps 1-6 of FIG. 2. Upon being notified that capabilities exist corresponding to deployment of the ViBE flock (e.g., indicating that capability service 318 and worker 320, which correspond to capability service 208 and worker 210 of FIG. 2, are available), MFO 310 resumes traversing build dependency graph 338 and identifies the next operation to perform.

[0078] As an example, MFO 310 may continue traversing construction dependency graph 338 and identify a DNS block to be deployed. By performing steps 16-21, MFO 310 may deploy DNS 322 (an example of DNS 212 in FIG. 2). These operations may generally correspond to steps 7-12 in FIG. 2.

[0079] At step 21, a capability may be stored indicating that DNS 322 is available. Upon detection of this capability, MFO 310 may resume traversing build dependency graph 338. During this traversal, MFO 310 may identify any suitable portion of an instance of CIOS regional (e.g., an instance of CIOS regional 314) to be deployed to ViBE 316. In some embodiments, steps 16-21 may be substantially repeated with respect to the deployment of CIOS regional (ViBE) 326 (CIOS regional 314, an instance of CIOS regional 110 in FIG. 1) and worker 328 to ViBE 316. Additionally, a capability that CIOS regional (ViBE) 326 is available may be sent to capability service 318.

[0080] Upon detecting that CIOS Regional (ViBE) 326 is available, MFO 310 may resume traversing build dependency graph 338. During this traversal, MFO 310 may identify a deployment orchestrator (e.g., deployment orchestrator 330, which is an example of deployment orchestrator 317) to be deployed to ViBE 316. In some embodiments, steps 16-21 may be substantially repeated for the deployment of deployment orchestrator 330. Additionally, information may be sent to capability service 318 identifying capabilities indicating that deployment orchestrator 330 is available.

[0081] After deployment orchestrator 330 is deployed, ViBE 316 may be considered available for processing subsequent requests. Upon detecting that deployment orchestrator 330 is available, MFO 310 may direct the routing of subsequent bootstrap requests to ViBE components rather than utilizing the host region components (host region 332 components). Thus, MFO 310 may continue traversing build dependency graph 338 at each node directing flock deployment to ViBE 316 via CIOS Central 304. CIOS Central 304 may request CIOS Regional (ViBE) 326 to deploy resources according to the flock configuration.

[0082] At some point in this process, the target region 334 may become available. An indication that the target region is available may be discernible from region data for the target region 334 provided by the user 302 (e.g., as an update to the region data). The availability of the target region 334 may depend on the establishment of a network connection between the target region 334 and an external network (e.g., the Internet). The network connection may be supported over a public network (e.g., the Internet), but may provide one or more encrypted tunnels (e.g., IPSec tunnels, such as tunnel 336) from ViBE 316 to the target region 334 through the use of software security tools (e.g., IPSec). As used herein, “IPSec” refers to a suite of protocols for authenticating and encrypting network traffic on networks that use the Internet Protocol (IP), and may include one or more available implementations of the suite of protocols (e.g., Openswan, Libreswan, strongSwan, etc.). The network may connect ViBE 316 to a service enclave in the target region 334.

[0083] Prior to the establishment of the IPSec tunnel, the initial network connection to the target region 334 may be sufficient connectivity (e.g., an out-of-band VPN tunnel) to allow bootstrapping of networking services until IPSec gateways are deployed to assets (e.g., bare metal assets) in the target region 334. To bootstrap the network resources of the target region 334, the deployment orchestrator 330 may deploy IPSec gateways at the assets in the target region 334. The deployment orchestrator 330 may then deploy VPN hosts in the target region 334 that are configured to terminate IPSec tunnels from ViBE 316. Once the services in ViBE 316 (e.g., deployment orchestrator 330, Service A, etc.) can establish IPSec connections with VPN hosts in the target region 334, the bootstrap operation from ViBE 316 to the target region 334 may begin.

[0084] In some embodiments, the bootstrap operation may begin with services in ViBE 316 that support hosting instances of core services deployed from ViBE 316 by provisioning resources in the target region 334. For example, the host provisioning service may allocate computing resources for VMs by provisioning a hypervisor on infrastructure (e.g., bare metal hosts) in the target region 334. When the host provisioning service completes the allocation of physical resources in the target region 334, it may publish information indicating a capability indicating that the physical resources in the target region 334 have been allocated. This capability may be published (e.g., by worker 328) to capability service 318 via CIOS regional (ViBE) 326.

[0085] Once the hardware allocation for the target region 334 has been established and posted to the capability service 318, CIOS regional (ViBE) 326 can orchestrate the deployment of instances of core services from ViBE 316 to the target region 334. This deployment may be similar to the process described above with respect to building ViBE 316, but using ViBE components (e.g., CIOS regional (ViBE) 326, worker 328, deployment orchestrator 330) instead of the service enclave components of the host region 332. The deployment operations may generally correspond to steps 16-21 described above.

[0086] When a service is deployed from ViBE 316 to target region 334, the DNS record associated with the service may correspond to an instance of the service in ViBE 316. The DNS record associated with the service may be updated later to complete the deployment of the service to target region 334. In other words, the instance of the service in ViBE 316 may continue to receive traffic (e.g., requests) to the service until the DNS record is updated. The service may be partially deployed to target region 334 and may publish information (e.g., to capability service 318) indicating a capability that the service is partially deployed. For example, a service running in ViBE 316 may be deployed to target region 334 along with corresponding compute instances, load balancers, and associated applications and other software, but may need to wait for database data to move to target region 334 before completing the deployment. The DNS record (e.g., managed by DNS 322) may still be associated with the service in ViBE 316. Once the data movement of the service is complete, the DNS record may be updated to point to the operational service deployed to target region 334. Thereafter, while a deployed service in target region 334 receives traffic (eg, requests) for that service, an instance of the service in ViBE 316 may not receive traffic for that service.

[0087] Building Regions Using ViBE As described above, a CSP can offer cloud services to its customers in new regions by building or deploying data centers. A region may correspond to a general geographic area and may be preferably close to new customers or customers with expanding service needs (e.g., customers with increasing requirements for scaling up cloud services, expanding cloud services to new geographic areas, etc.). To support the building of new regions, a ViBE (e.g., ViBE 316 of FIG. 3) may be created in the designated host region through use of a CIOS (e.g., CIOS 102 of FIG. 1).

[0088] A ViBE may be created prior to or in parallel with the build of a new regional datacenter. For example, a ViBE may be created prior to (e.g., days, weeks, etc.) the completion of a new datacenter because the build and provisioning of physical components (e.g., bare metal hosts, racks, networking switches, etc.) may take months. An operator may support the deployment of services to a new datacenter by deploying core services into a ViBE once the new datacenter's physical infrastructure is ready to host cloud services. By creating a ViBE prior to (or in parallel with) the build of a regional datacenter, the core services to be deployed may be assessed for deployment readiness (e.g., test generation, resolve dependencies, etc.).

[0089] 4 is a simplified diagram illustrating a CSP's region 400 including multiple host regions (e.g., host region 404, host regions 406-410) suitable for hosting a ViBE (e.g., ViBE 402, which may be an example of any of the ViBEs described herein, including ViBE 316 of FIG. 3). A host region may be any datacenter configured to provide any cloud infrastructure service (e.g., CIOS central 304, etc.). Target region 412 may be a new region being built and may include one or more datacenters hosting the physical computing, storage, and networking infrastructure for providing cloud services.

[0090] A ViBE may be created in any suitable host region. As described above, a ViBE may be a tenancy (e.g., similar to a customer account) of a CSP. A tenancy may span multiple regions. For example, a tenancy may have access to resources (e.g., compute, storage, services, etc.) in one or more regions. Similarly, since a ViBE tenancy may have access to resources in one or more regions, a ViBE may be created in one or more host regions to support region construction in one or more target regions. As an example, a ViBE tenancy may be used to create a ViBE in each of host regions 404-410. Each ViBE in a different region may support region construction in a corresponding target region (e.g., target region 412). In some embodiments, one ViBE in a host region (e.g., host region 404) may be used to create a region in one target region (e.g., target region 412).

[0091] A suitable host region for a ViBE to be used to build a target region may be selected based on network proximity (e.g., low latency network connectivity) between the host region and the target region. In some embodiments, a suitable host region may be located within the same jurisdiction (e.g., same country, same geopolitical region, etc.) as the target region. Because different jurisdictions may have different rules for handling customer data, a suitable host region for building a target region using a ViBE may be a host region located within the same jurisdiction as the target region. For example, host region 404 and target region 412 may both be in one jurisdiction indicated by boundary 414 (e.g., national border, regional boundary, etc.), while host region 410 is in a different jurisdiction. Although host region 410 may have better network connectivity with target region 412, host region 404 may be selected as the host region for ViBE 402 to build target region 412 because it is in the same jurisdiction as target region 412.

[0092] FIG. 5 is a block diagram illustrating an environment 500 and an exemplary method for bootstrapping a service to a target region using ViBE. The operations described herein with respect to FIG. 5 may be considered an extension of the method described above with respect to FIG. 3. For example, MFO 510 (an example of MFO 310 of FIG. 3) may deploy a service (e.g., service 502) to a target region 534 by instructing CIOS Central 504 to bootstrap the service to the target region in the same manner as the service (e.g., deployment orchestrator 530, an example of deployment orchestrator 330 of FIG. 3) was deployed to ViBE. The operations described with respect to FIG. 5 (as well as any other method or process described herein) may be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, these operations represent computer-executable instructions that are stored on one or more computer-readable storage media and that, when executed by one or more processors, perform the described operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, etc. that perform particular functions or implement particular data types. The order of the described operations is not intended to be construed as limiting in any way, and any number of the described operations may be omitted or combined in any order and / or in parallel to achieve the process.

[0093] In step 1, a network connection may be established between ViBE 516 in host region 532 and target region 534. The network connection may be established by network service 509 (e.g., one of the core services deployed in ViBE 516). The network connection may include one or more tunnels 536 (one example of tunnel 336 in FIG. 3). Tunnel 536 may be an encrypted tunnel (e.g., an IPSec tunnel). The network connection may form one or more virtual private network (VPN) connections between the network hosting ViBE 516 (e.g., a virtual cloud network (VCN) in host region 532) and a service enclave in target region 534 (e.g., a VCN in target region 534). The network configuration between ViBE and the target region is described in more detail below with respect to FIG. 6. Once the network connection is established, in step 2, network service 509 may publish a capability to capability service 518 indicating that ViBE 516 is connected to target region 534.

[0094] Execution of steps 3-11 may deploy the service 502 to the target region 534. The operations of steps 3, 4, 5, and 11 may generally correspond to steps 7, 8, 9, and 12 of FIG. 2. Steps 6 and 7 include operations associated with provisioning infrastructure resources in the target region 534, while steps 8-10 may be similar to repeating steps 10 and 11 of FIG. 2 to deploy the service to the target region 534.

[0095] The steps described below include provisioning of infrastructure (e.g., steps 6 and 7) as part of a method of provisioning infrastructure resources using CIOS as a preliminary part of deploying a service (e.g., a service according to a flock configuration using a declarative provisioning tool). In some embodiments, provisioning of infrastructure resources (e.g., infrastructure resources 503) may be performed as a separate operation under the direction of CIOS Central 504 and MFO 510. For example, a host provisioning service (e.g., host provisioning service 506) may be deployed in ViBE 516 and be able to support deployment of a service to a target region 534 by provisioning infrastructure resources in the target region 534 before a deployment orchestration service (e.g., deployment orchestrator 530) is fully deployed in ViBE 516. In this case, based on capabilities provided to capability service 518, MFO 510 may initiate provisioning of infrastructure resources in target region 534 using host provisioning service 506 without deployment of the service.

[0096] In step 3, MFO 510 may instruct CIOS Central 504 to deploy service 502 to target region 534. Service 502 may require provisioning of infrastructure resources 503 in target region 534. For example, service 502 may be executed by one or more compute instances executing on one or more VMs in the target region. The instructions to deploy service 502 may identify or include resources (e.g., infrastructure resources 503) for provisioning in target region 534. The provisioning of resources may include configuration of one or more hosts (e.g., one or more virtual machines (VMs)) in the computing environment of target region 534. The instructions to deploy service 502 may also identify or include a flock configuration corresponding to service 502.

[0097] In step 4, CIOS Central 504 may instruct CIOS Regional (ViBE) 526 to provision infrastructure resources 503 and deploy services 502 to target regions 534. In some embodiments, CIOS Central 504 provides a flocking configuration for services 502.

[0098] In step 5, a worker 528 may be assigned by CIOS regional (ViBE) 526 to the task of provisioning infrastructure resources 503 and deploying service 502. Worker 528 may run a declarative provisioner to identify a set of operations that need to be performed for deployment of service 502 (e.g., by comparing the flock configuration against the current state of the resources associated with the flock).

[0099] In step 6, worker 528 may instruct host provisioning service 506 to provision infrastructure resources 503 in target region 534 (which may be done by host provisioning service 506 in step 7) according to the actions identified in step 5. In steps 8 and 9, worker 528 may instruct compute control plane 508 and deployment orchestrator 530 to launch instances and deploy services 502 to the launched instances, respectively. Compute control plane 508 and deployment orchestrator 530 may perform the instructed launch and deployment tasks in step 10.

[0100] In step 11, the worker 528 may post one or more capabilities to the capability service 518 that the service 502 is available, and the MFO 510 may identify the resources associated with the flocking configuration of the service 502 as available and may proceed with further bootstrapping operations.

[0101] In some embodiments, completion of infrastructure provisioning (step 7), launching of instances (step 8), and deployment of a service (step 9) may each result in a corresponding capability being posted to capability service 518. Typically, provisioning of infrastructure for a service involves updating a corresponding DNS record using DNS 522 (an example of DNS 322 in FIG. 3) to point to the newly provisioned resources (e.g., associated network addresses) for the service. However, as noted above, deployment of a corresponding service may occur separately from the provisioning of its underlying infrastructure (e.g., steps 6-8 may occur before completion of steps 9 and 10). Thus, premature updates to DNS records may result in services in ViBE 516 and / or host region 532 attempting to access services in target region 534 before capability service 518 is available to serve traffic. After deploying a service, the capability posted to capability service 518 in step 11 may indicate that the deployment is partially complete (e.g., "partially scaled out of service 502"). The MFO 510 can then identify the partially completed state of the deployed service and have the Worker 528 update the DNS 522 by performing another pass through the CIOS Central 504 and the CIOS Regional (ViBE) 526 .

[0102] 6 is a block diagram illustrating an example architecture of an environment 600 having a network connection between a ViBE (e.g., ViBE VCN 604) in a host region (e.g., host region 632) and a target region (e.g., target region 634). As the illustrated architecture relates to network connections, the ViBE in FIG. 6 is shown as a VCN in a ViBE tenancy 602 in host region 632. ViBE VCN 604 may be an example of ViBE 516 in FIG. 5. Detailed examples of the relationship between tenancies and VCNs are provided below with respect to FIGS. 9-12.

[0103] ViBE VCN 604 may include services similar to ViBE 516 of Figure 5, and like-numbered components may be similar to one another. For example, deployment orchestrator 630 may be an example of deployment orchestrator 530, host provisioning services 606 may be an example of host provisioning services 506, and so on.

[0104] The ViBE VCN 604 may comprise one or more networking gateways, including a network address translation (NAT) gateway 612, a service gateway 614, and an Internet gateway 616. A gateway may be a logical connection (e.g., a virtual router or other suitable software implementation) between one or more network resources in the ViBE VCN 604 and an external network. For example, a gateway may route inbound and outbound traffic (e.g., according to a VCN's routing table) to network addresses of hosts (e.g., hosts of ViBE services) in the ViBE VCN 604.

[0105] The NAT gateway 612 may be configured to route traffic for resources in the ViBE VCN 604 that do not have a public network address (e.g., a public IP address). The service gateway 614 may be configured to route traffic for one or more cloud services 620 offered by a CSP without exposing them to the public Internet (e.g., the public Internet 624). The Internet gateway 616 may be configured to route traffic for resources that have an exposed public network address. For example, CIOS Regional (ViBE) 626 may have a public address in the ViBE VCN 604 for communication with CIOS Central 638. CIOS Central 638 may be included in a VCN associated with CIOS tenancy 636 or another tenancy of the CSP. Although not shown in FIG. 6, CIOS tenancy 636 may be included in the host region 632 or another region of the CSP.

[0106] In some embodiments, incoming public traffic to the ViBE VCN 604 may be limited to connections between CIOS Central 638 and CIOS Regional (ViBE) 626 for improved security. Connections to the Internet Gateway 616 may pass through a load balancer 618 that can be configured to apply load balancing policies to manage (e.g., throttle, limit, etc.) traffic to any public network addresses of the ViBE VCN 604 resources (e.g., CIOS Regional (ViBE) 626). The load balancer 618 may also be configured to restrict available ports and provide authentication of inbound connections via security protocols (e.g., mutual Transport Layer Security (mTLS)).

[0107] Cloud services 620 may include services available from a CSP. As a non-limiting example, cloud services 620 may include an identity service (e.g., identity cloud service) that performs authentication and authorization procedures, a key-value storage service, and a deployment orchestration service (e.g., deployment orchestrator 317 of FIG. 3). During operation of ViBE VCN 604 (e.g., during provisioning and deployment operations to target region 634), services in ViBE VCN 604 may communicate with cloud services 620 to perform operations related to ViBE VCN 604. For example, deployment orchestrator 630 may store data created by the deployment orchestrator 630 by communicating with a storage service of cloud services 620.

[0108] The NAT gateway 612 may be stateful. A stateful NAT gateway may accept outbound traffic (e.g., requests from services in the ViBE VCN 604) while rejecting inbound traffic that is not a response to the outbound traffic (e.g., rejecting the inbound connection). For example, one or more of the services in the ViBE VCN 604 (e.g., deployment orchestrator 630) may establish an encrypted network connection (e.g., an IPSec tunnel) with a target region 634. To negotiate the encrypted connection, the services in the ViBE VCN 604 may send outbound traffic through the NAT gateway 612 to the target region 634 (e.g., security gateway 642) and receive an inbound response (e.g., IPSec key exchange). Once established, the state of the encrypted network connection may be preserved by the NAT gateway 612 to allow ongoing two-way traffic over the connection while continuing to block inbound traffic from the public Internet 624 that is not responding to the outbound traffic.

[0109] The host region 632 may connect to the target region 634 via the public Internet 624, which may be any suitable public network (e.g., the Internet). The target region 634 may include a network gateway 640, which may be any suitable gateway for establishing a connection between the target region 634 and the public Internet 624. The target region 634 may also include a security gateway 642, a region network fabric 644, and one or more services (e.g., Service A 646, Service N 648), which may be services that were bootstrapped from the ViBE VCN 604 to the target region 634 according to the process described above. For example, Service A 646 may be an instance of a deployment orchestrator 630 following deployment from the ViBE VCN 604 to the target region 634.

[0110] Security gateway 642 may be configured to implement a security protocol (e.g., IPSec). The security protocol may be any suitable protocol for establishing a secure (e.g., encrypted, authenticated, etc.) connection between security gateway 642 and a service in ViBE VCN 604. For example, security gateway 642 may terminate one or more IPSec tunnels established over a network connection between ViBE VCN 604 and target region 634. The IPSec tunnel termination may be an endpoint where encrypted traffic (e.g., IPSec encrypted IP packets) is decrypted according to the encryption protocol. The decrypted traffic may then be routed to a destination (e.g., Service A 646, Service N 648, another host, etc.) in target region 634.

[0111] The region network fabric 644 may include the physical and virtual network infrastructure in the target region 634. For example, the region network fabric 644 may include physical switches, routers, etc. as well as virtual networking components (e.g., virtual routers, virtual gateways). The region network fabric 644 may be a network for the service enclaves of the target region 634.

[0112] 7 is a diagram illustrating an example architecture of an environment 700 having a network connection between a remote access tenancy 704 and a ViBE tenancy 706. As shown in FIG. 7, the components may be similar to components described elsewhere herein. For example, ViBE VCN 708 may be an example of a ViBE VCN 604, NAT gateway 712 may be an example of a NAT gateway 612, ViBE tenancy 706 may be an example of a ViBE tenancy 602, and so on. ViBE services 702 may include the services described above deployed to a ViBE as part of creating a ViBE and / or bootstrapping a service into a target region (e.g., target region 734).

[0113] During the creation of the ViBE VCN 708, an operator (e.g., user 722) may perform manual operations with one or more of the ViBE services 702. For example, to test the deployment of services to the ViBE before connecting the ViBE VCN 708 to the target region 734, the operator may access the services in the ViBE to interact with the services by running tests, modifying or updating service configurations, retrieving service information, or performing any other suitable task. As another example, new core services may be identified for future ViBE bootstrap into the target region. To verify the functionality of the new core services in the ViBE, the operator may test the new core services after their deployment into the ViBE and before connecting the ViBE to the target region. The creation of the ViBE VCN 708 in the host region allows those services to be deployed as if in a production environment (e.g., the target region) prior to using ViBE to deploy the ViBE services 702 to the target region.

[0114] Because the ViBE VCN 708 is typically protected from inbound connections (e.g., by a NAT gateway 712), access to the ViBE service 702 may use a remote access tenancy 704 that connects to a jump VCN 718 in the ViBE tenancy 706. The remote access tenancy 704 may be in the host region that hosts the ViBE VCN 708 or in another region. The remote access tenancy 704 may comprise an access VCN 710 that includes hosts to support secure connections to the jump VCN 718. Similarly, the jump VCN 718 may comprise a jump subnet 720 that may include intermediate hosts. The intermediate hosts in the jump VCN may be deployed for each ViBE instance (e.g., each ViBE VCN in the host region).

[0115] Also, the jump VCN 718 may comprise a virtual network interface card (VNIC) that interacts with a VNIC in the ViBE VCN 708. A network connection 724 may be configured between the jump VCN 718 and the ViBE VCN 708. The connection between the access VCN 710 and the jump VCN may be through a gateway 714 and a gateway 716, which may be local peering gateways (LPGs). General details of operator access to VCNs, including the ViBE VCN 708, may be found below with respect to Figures 9-13, where the remote access tenancy 704 may be similar to the secure host tenancy 904, the access VCN 710 may be similar to the VCN 906, the gateway 714 and the gateway 716 may be similar to the LPG 910, and the jump VCN 718 may be similar to the SSH VCN 912.

[0116] 8 illustrates an example method 800 for creating a ViBE and deploying one or more resources (e.g., one or more services) from a ViBE to a target region according to some embodiments. Method 800 may be performed by one or more components of a distributed computing system (e.g., a cloud computing system), including one or more components of cloud infrastructure orchestration service 102 of FIG. 1. A computer-readable storage medium including computer-readable instructions that, when executed by one or more processors of the distributed computing system, cause a computing device to perform method 800. The operations of method 800 may be performed in any suitable order and may include more or less operations than those illustrated in FIG.

[0117] Some or all of method 800 (or any other process and / or method described herein, or variations and / or combinations thereof) may be adapted to be executed under the control of one or more computer systems configured with executable instructions, and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) collectively executed on one or more processors by hardware or a combination thereof. The code may be stored on a computer-readable storage medium, e.g., in the form of a computer program including a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

[0118] The method 800 may begin at block 802 when a virtual cloud network (VCN) may be created in a hosting region. The VCN may be a Virtual Bootstrap Environment (ViBE) VCN (e.g., ViBE VCN 604). In some embodiments, the hosting region may include one or more data centers of a cloud service provider.

[0119] At block 804, a Virtual Bootstrap Environment (ViBE) may be implemented in the VCN. As described above, the ViBE may be configured to stage one or more services for deployment to a target region.

[0120] At block 806, the first service may be deployed to the ViBE. The deployment of the first service may be accomplished by a multi-flock orchestrator (MFO) (e.g., MFO 106 of FIG. 1) of the CIOS (e.g., CIOS 102 of FIG. 1). The MFO may deploy the first service to the ViBE using one or more services in a service enclave of the host region (e.g., deployment orchestrator 218 of FIG. 2).

[0121] At block 808, a network connection may be established between the VCN and the target region. In some embodiments, the network connection may be a virtual private network connection implementing a security protocol (e.g., IPSec). Like the host region, the target region may include one or more data centers that include a physical computing infrastructure suitable for hosting cloud services in accordance with the techniques of this disclosure.

[0122] At block 810, resources of the ViBE may be deployed to the target region over the network connection. These resources may include resources of one or more services in the ViBE (including an instance of the first service or another service). These resources may also include infrastructure components, artifacts, etc. The deployment of the resources may use the first service. For example, the first service may be an instance of a deployment orchestration service in the ViBE (e.g., deployment orchestrator 530 of FIG. 5). These resources may be deployed by using the first service in conjunction with MFO and / or other CIOS components (e.g., CIOS Central 504 of FIG. 5).

[0123] Exemplary Architecture for Providing Infrastructure as a Service (IaaS) As mentioned above, infrastructure as a service (IaaS) is a particular type of cloud computing. IaaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet). In the IaaS model, a cloud computing provider can host infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., hypervisor layer), etc.). In some cases, an IaaS provider can also provide various services (e.g., billing, monitoring, logging, load balancing, clustering, etc.) that are associated with these infrastructure components. Thus, since these services can be policy-driven, an IaaS user can maintain application availability and performance by implementing policies that drive load balancing.

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

[0125] In most cases, the cloud computing model may require the participation of a cloud provider, which may be, but need not be, a third-party service dedicated to providing IaaS (e.g., providing, renting, selling). An entity may also choose to deploy a private cloud and become its own provider of infrastructure services.

[0126] 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, etc. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed below the hypervisor layer (e.g., server, storage, network hardware, and virtualization) by the cloud provider. Thus, the customer may be responsible for handling (e.g., on self-service virtual machines (which can be spun up on demand)), middleware, and / or application deployment, etc.

[0127] In some instances, IaaS provisioning may refer to obtaining a computer or virtual host to use and even installing the necessary libraries or services on them. In most cases, deployment does not include provisioning, which may need to be performed first.

[0128] Sometimes there are two different challenges in IaaS provisioning. First, there is the initial challenge of provisioning an initial set of infrastructure before anything works. Second, there is the challenge of evolving the existing infrastructure after all the provisioning (e.g. adding new services, modifying services, removing services, etc.). Sometimes these two challenges can be addressed by allowing the configuration of the infrastructure to be defined declaratively. In other words, the infrastructure (e.g. the components required and how they interact) can be specified by one or more configuration files. Thus, the overall topology of the infrastructure (e.g. which resources depend on which resources and how they work together) can be described declaratively. Sometimes, once the topology is specified, workflows can be generated to create and / or manage the various components described in the configuration files.

[0129] In some examples, the infrastructure may have many interconnected elements. For example, there may be one or more virtual private clouds (VPCs) (e.g., potential on-demand pools of configurable and / or shared computing resources), also known as a core network. Also, in some examples, there may be one or more inbound / outbound traffic group rules provisioned to define how the network inbound and / or outbound traffic is configured and one or more virtual machines (VMs). Other infrastructure elements such as load balancers, databases, etc. may also be provisioned. If there is a desire and / or addition of more infrastructure elements, the infrastructure may evolve in increments.

[0130] In some cases, the employment of continuous deployment techniques may enable deployment of infrastructure code across various virtual computing environments. The described techniques may also enable infrastructure management within these environments. In some instances, a service team may write code that is desired to be deployed to one or more (but often many) different production environments (e.g., across various geographic locations, possibly even across the globe). In some instances, however, the infrastructure into which the code will be deployed may first need to be configured. In some cases, provisioning may be performed manually, provisioning tools may be used to provision resources, and / or deployment tools may be used to deploy the code after the infrastructure has been provisioned.

[0131] 9 is a block diagram 900 illustrating an example pattern of an IaaS architecture according to at least one embodiment. A service operator 902 may be communicatively coupled to a secure host tenancy 904, which may include a virtual cloud network (VCN) 906 and a secure host subnet 908. In some examples, the service operator 902 may employ one or more client computing devices, which may be portable handheld devices (e.g., iPhones, mobile phones, iPads, computing tablets, personal digital assistants (PDAs)) or wearable devices (e.g., Google Glass head-mounted displays, etc.) running software such as Microsoft Windows Mobile and / or a variety of mobile operating systems such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, etc., and capable of using the Internet, email, short message service (SMS), BlackBerry, or other communications protocols. Alternatively, the client computing devices may be general purpose personal computers, examples of which include personal and / or laptop computers running various versions of the Microsoft Windows, Apple Macintosh, and / or Linux operating systems. The client computing devices may be workstation computers running any of a variety of commercially available UNIX or UNIX-like operating systems, including, but not limited to, various GNU / Linux operating systems such as Google Chrome OS.Alternatively or additionally, the client computing device may be any other electronic device, such as a thin-client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and / or a personal messaging device, capable of communicating over a network that can access the VCN 906 and / or the Internet.

[0132] VCN 906 may comprise a local peering gateway (LPG) 910 that may be communicatively coupled to a secure shell (SSH) VCN 912 via an LPG 910 that is included in the SSH VCN 912. The SSH VCN 912 may comprise an SSH subnet 914, and the SSH VCN 912 may be communicatively coupled to a control plane VCN 916 via an LPG 910 that is included in the control plane VCN 916. The SSH VCN 912 may also be communicatively coupled to a data plane VCN 918 via the LPG 910. The control plane VCN 916 and the data plane VCN 918 may be included in a service tenancy 919, which may be owned and / or operated by the IaaS provider.

[0133] The control plane VCN 916 may comprise a control plane demilitarized zone (DMZ) tier 920 that operates as a perimeter network (e.g., a portion of an enterprise network between an enterprise intranet and an external network). DMZ-based servers may help limit liability and limit intrusions. The DMZ tier 920 may also comprise one or more load balancer (LB) subnets 922, a control plane app tier 924 that may include an app subnet 926, and a control plane data tier 928 that may include a database (DB) subnet 930 (e.g., a front-end DB subnet and / or a back-end DB subnet). The LB subnet 922 included in the control plane DMZ tier 920 may be communicatively coupled to the app subnet 926 included in the control plane app tier 924 and an Internet gateway 934 that may be included in the control plane VCN 916, and the app subnet 926 may be communicatively coupled to the DB subnet 930, a service gateway 936, and a network address translation (NAT) gateway 938 included in the control plane data tier 928. The control plane VCN 916 may include a service gateway 936 and a NAT gateway 938.

[0134] The control plane VCN 916 may include a data plane mirrored app tier 940 that may include an app subnet 926. The app subnet 926 included in the data plane mirrored app tier 940 may include a virtual network interface controller (VNIC) 942 that may run a compute instance 944. The compute instance 944 may communicatively couple the app subnet 926 of the data plane mirrored app tier 940 to the app subnet 926 that may be included in the data plane app tier 946.

[0135] The data plane VCN 918 may comprise a data plane app layer 946, a data plane DMZ layer 948, and a data plane data layer 950. The data plane DMZ layer 948 may comprise a LB subnet 922, which may be communicatively coupled to an app subnet 926 of the data plane app layer 946 and an Internet gateway 934 of the data plane VCN 918. The app subnet 926 may be communicatively coupled to a service gateway 936 of the data plane VCN 918 and a NAT gateway 938 of the data plane VCN 918. Additionally, the data plane data layer 950 may comprise a DB subnet 930, which may be communicatively coupled to the app subnet 926 of the data plane app layer 946.

[0136] The internet gateways 934 of the control plane VCNs 916 and data plane VCNs 918 may be communicatively coupled to a metadata management service 952, which may be communicatively coupled to the public internet 954. The public internet 954 may be communicatively coupled to a NAT gateway 938 of the control plane VCNs 916 and data plane VCNs 918. The service gateways 936 of the control plane VCNs 916 and data plane VCNs 918 may be communicatively coupled to cloud services 956.

[0137] In some examples, the service gateways 936 of the control plane VCNs 916 and the data plane VCNs 918 can make application programming interface (API) calls to the cloud services 956 without going through the public Internet 954. The API calls from the service gateways 936 to the cloud services 956 can be unidirectional. The service gateways 936 can make API calls to the cloud services 956, and the cloud services 956 can send the requested data to the service gateways 936. However, the cloud services 956 do not have to initiate the API calls to the service gateways 936.

[0138] In some examples, the secure host tenancy 904 may be directly connected to an otherwise isolated service tenancy 919. The secure host subnet 908 may communicate with the SSH subnet 914 through an LPG 910, which may allow bidirectional communication through an otherwise isolated system. By connecting the secure host subnet 908 to the SSH subnet 914, the secure host subnet 908 may be accessible to other entities in the service tenancy 919.

[0139] The control plane VCN 916 may enable configuration or provisioning of desired resources by users of the service tenancy 919. The desired resources provisioned in the control plane VCN 916 may be deployed or used in the data plane VCN 918. In some examples, the control plane VCN 916 may be isolated from the data plane VCN 918, and a data plane mirror app layer 940 of the control plane VCN 916 may communicate with a data plane app layer 946 of the data plane VCN 918 via a VNIC 942 that may be included in the data plane mirror app layer 940 and the data plane app layer 946.

[0140] In some examples, a user or customer of the system may make a request, e.g., a create, read, update, or delete (CRUD) operation, through the public internet 954, which may send the request to the metadata management service 952. The metadata management service 952 may send the request to the control plane VCN 916 through the internet gateway 934. The request may be received by the LB subnet 922 included in the control plane DMZ layer 920. The LB subnet 922 may determine that the request is valid, and in response to this determination, the LB subnet 922 may send the request to the app subnet 926 included in the control plane app layer 924. If the request is validated and a call to the public internet 954 is required, the call to the public internet 954 may be sent to the NAT gateway 938, which may make the call to the public internet 954. Memory that may be desired to be stored by the request may be stored in the DB subnet 930.

[0141] In some examples, the data plane mirror app layer 940 may facilitate direct communication between the control plane VCN 916 and the data plane VCN 918. For example, it may be desirable to apply configuration changes, updates, or other suitable modifications to resources included in the data plane VCN 918. The control plane VCN 916 may perform the configuration changes, updates, or other suitable modifications of the resources by communicating directly with the resources included in the data plane VCN 918 via the VNIC 942.

[0142] In some embodiments, the control plane VCN 916 and the data plane VCN 918 may be included in the service tenancy 919. In this case, the user or customer of the system may not own or operate either the control plane VCN 916 or the data plane VCN 918. Alternatively, the IaaS provider may own and operate both the control plane VCN 916 and the data plane VCN 918, and both may be included in the service tenancy 919. This embodiment may allow for network isolation that may prevent users or customers from interacting with the resources of other users or customers. This embodiment may also allow for private storage of databases by users or customers of the system without having to rely on the public internet 954, which may not have the desired level of threat prevention for storage.

[0143] In another embodiment, the LB subnet 922 included in the control plane VCN 916 can be configured to receive signals from the service gateway 936. In this embodiment, the control plane VCN 916 and the data plane VCN 918 can be configured to be called by the IaaS provider's customers without calling the public internet 954. The IaaS provider's customers may desire this embodiment because databases they use can be stored in a service tenancy 919 that is controlled by the IaaS provider and can be isolated from the public internet 954.

[0144] 10 is a block diagram 1000 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 1002 (e.g., service operator 902 of FIG. 9 ) may be communicatively coupled to a virtual cloud network (VCN) 1006 (e.g., VCN 906 of FIG. 9 ) and a secure host tenancy 1004 (e.g., secure host tenancy 904 of FIG. 9 ), which may include a secure shell (SSH) VCN 1012 (e.g., SSH VCN 912 of FIG. 9 ). The VCN 1006 may comprise a local peering gateway (LPG) 1010, which may be communicatively coupled to an SSH VCN 1012 via an LPG 910 (e.g., LPG 910 of FIG. 9 ) included in the SSH VCN 1012 (e.g., SSH VCN 912 of FIG. 9 ). The SSH VCN 1012 may comprise an SSH subnet 1014 (e.g., SSH subnet 914 in FIG. 9 ), and the SSH VCN 1012 may be communicatively coupled to a control plane VCN 1016 via an LPG 1010 that is included in the control plane VCN 1016 (e.g., control plane VCN 916 in FIG. 9 ). The control plane VCN 1016 may be included in a service tenancy 1019 (e.g., service tenancy 919 in FIG. 9 ), and the data plane VCN 1018 (e.g., data plane VCN 918 in FIG. 9 ) may be included in a customer tenancy 1021, which may be owned or operated by a user or customer of the system.

[0145] The control plane VCN 1016 may comprise a control plane DMZ tier 1020 (e.g., control plane DMZ tier 920 of FIG. 9 ) that may include a LB subnet 1022 (e.g., LB subnet 922 of FIG. 9 ), a control plane app tier 1024 (e.g., control plane app tier 924 of FIG. 9 ) that may include an app subnet 1026 (e.g., app subnet 926 of FIG. 9 ), and a control plane data tier 1028 (e.g., control plane data tier 928 of FIG. 9 ) that may include a DB subnet 1030 (e.g., similar to database (DB) subnet 930 of FIG. 9 ). The LB subnet 1022 included in the control plane DMZ tier 1020 may be communicatively coupled to an app subnet 1026 included in the control plane app tier 1024 and an Internet gateway 1034 (e.g., Internet gateway 934 in FIG. 9 ) that may be included in the control plane VCN 1016, and the app subnet 1026 may be communicatively coupled to a DB subnet 1030, a service gateway 1036 (e.g., service gateway in FIG. 9 ), and a network address translation (NAT) gateway 1038 (e.g., NAT gateway 938 in FIG. 9 ) included in the control plane data tier 1028. The control plane VCN 1016 may comprise the service gateway 1036 and the NAT gateway 1038.

[0146] The control plane VCN 1016 may include a data plane mirrored app layer 1040 (e.g., data plane mirrored app layer 940 of FIG. 9 ), which may include an app subnet 1026. The app subnet 1026 included in the data plane mirrored app layer 1040 may include a virtual network interface controller (VNIC) 1042 (e.g., the VNIC of 942) on which a compute instance 1044 (e.g., similar to the compute instance 944 of FIG. 9 ) may run. The compute instance 1044 may facilitate communication between the app subnet 1026 of the data plane mirrored app layer 1040 and the app subnet 1026 that may be included in the data plane app layer 1046 via the VNIC 1042 included in the data plane mirrored app layer 1040 and the VNIC 1042 included in the data plane app layer 1046 (e.g., data plane app layer 946 of FIG. 9 ).

[0147] The Internet gateway 1034 included in the control plane VCN 1016 may be communicatively coupled to a metadata management service 1052 (e.g., metadata management service 952 of FIG. 9 ), which may be communicatively coupled to a public Internet 1054 (e.g., public Internet 954 of FIG. 9 ). The public Internet 1054 may be communicatively coupled to a NAT gateway 1038 included in the control plane VCN 1016. The service gateway 1036 included in the control plane VCN 1016 may be communicatively coupled to cloud services 1056 (e.g., cloud services 956 of FIG. 9 ).

[0148] In some examples, the data plane VCN 1018 may be included in the customer tenancy 1021. In this case, the IaaS provider may provide a control plane VCN 1016 for each customer, and the IaaS provider may configure a unique compute instance 1044 for each customer, which is included in the service tenancy 1019. Each compute instance 1044 may enable communication between the control plane VCN 1016 in the service tenancy 1019 and the data plane VCN 1018 in the customer tenancy 1021. The compute instance 1044 may enable deployment or use of resources provisioned in the control plane VCN 1016 in the service tenancy 1019 in the data plane VCN 1018 in the customer tenancy 1021.

[0149] In another example, an IaaS provider customer may have a database that resides in customer tenancy 1021. In this example, control plane VCN 1016 may include a data plane mirror app tier 1040 that may include app subnet 1026. The data plane mirror app tier 1040 may reside in the data plane VCN 1018, but may not reside in the data plane VCN 1018. That is, the data plane mirror app tier 1040 may be accessible to customer tenancy 1021, but may not reside in the data plane VCN 1018, and may not be owned or operated by the IaaS provider customer. The data plane mirror app tier 1040 may be configured to make calls to the data plane VCN 1018, but may not be configured to make calls to any entities included in the control plane VCN 1016. A customer may desire deployment or use of resources in the data plane VCN 1018 that have been provisioned in the control plane VCN 1016, and the data plane mirror app layer 1040 may facilitate the deployment or other use of the resources that the customer desires.

[0150] In some embodiments, the IaaS provider's customer can apply filters to the data plane VCN 1018. In this embodiment, the customer can determine what the data plane VCN 1018 can access, and the customer can limit access from the data plane VCN 1018 to the public Internet 1054. The IaaS provider may not be able to apply filters or control the data plane VCN 1018's access to any external networks or databases. The customer's application of filters and controls to the data plane VCN 1018 contained in the customer tenancy 1021 can help isolate the data plane VCN 1018 from other customers and the public Internet 1054.

[0151] In some embodiments, the cloud services 1056 can access services that may not be in the public internet 1054, the control plane VCN 1016, or the data plane VCN 1018 by making calls through the service gateway 1036. The connection between the cloud services 1056 and the control plane VCN 1016 or the data plane VCN 1018 may not be live or continuous. The cloud services 1056 may be on different networks owned or operated by the IaaS provider. The cloud services 1056 may be configured to receive calls from the service gateway 1036 or may be configured not to receive calls from the public internet 1054. Some cloud services 1056 may be isolated from other cloud services 1056, and the control plane VCN 1016 may be isolated from cloud services 1056 that may not be in the same region as the control plane VCN 1016. For example, control plane VCN 1016 may be located in "region 1," and cloud service "deployment 9" may be located in region 1 and "region 2." If a call to deployment 9 is made by a service gateway 1036 included in control plane VCN 1016 located in region 1, the call may be sent to deployment 9 in region 1. In this example, control plane VCN 1016 or deployment 9 in region 1 may not be communicatively coupled to or communicable with deployment 9 in region 2.

[0152] 11 is a block diagram 1100 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 1102 (e.g., service operator 902 of FIG. 9 ) may be communicatively coupled to a secure host tenancy 1104 (e.g., secure host tenancy 904 of FIG. 9 ), which may include a virtual cloud network (VCN) 1106 (e.g., VCN 906 of FIG. 9 ) and a secure host subnet 1108 (e.g., secure host subnet 908 of FIG. 9 ). The VCN 1106 may comprise an LPG 1110, which may be communicatively coupled to an SSH VCN 1112 via an LPG 1110 (e.g., LPG 910 of FIG. 9 ) included in the SSH VCN 1112 (e.g., SSH VCN 912 of FIG. 9 ). SSH VCN 1112 may comprise an SSH subnet 1114 (e.g., SSH subnet 914 in FIG. 9 ), and SSH VCN 1112 may be communicatively coupled to a control plane VCN 1116 via an LPG 1110 included in the control plane VCN 1116 (e.g., control plane VCN 916 in FIG. 9 ) and to a data plane VCN 1118 via an LPG 1110 included in the data plane VCN 1118 (e.g., data plane VCN 918 in FIG. 9 ). The control plane VCN 1116 and the data plane VCN 1118 may be included in a service tenancy 1119 (e.g., service tenancy 919 in FIG. 9 ).

[0153] The control plane VCN 1116 may comprise a control plane DMZ tier 1120 (e.g., control plane DMZ tier 920 of FIG. 9 ) that may include a load balancer (LB) subnet 1122 (e.g., LB subnet 922 of FIG. 9 ), a control plane app tier 1124 (e.g., control plane app tier 924 of FIG. 9 ) that may include an app subnet 1126 (e.g., similar to app subnet 926 of FIG. 9 ), and a control plane data tier 1128 (e.g., control plane data tier 928 of FIG. 9 ) that may include a DB subnet 1130. The LB subnet 1122 included in the control plane DMZ layer 1120 may be communicatively coupled to an app subnet 1126 included in the control plane app layer 1124 and an Internet gateway 1134 (e.g., Internet gateway 934 in FIG. 9 ) that may be included in the control plane VCN 1116, and the app subnet 1126 may be communicatively coupled to a DB subnet 1130, a service gateway 1136 (e.g., service gateway in FIG. 9 ), and a network address translation (NAT) gateway 1138 (e.g., NAT gateway 938 in FIG. 9 ) included in the control plane data layer 1128. The control plane VCN 1116 may comprise the service gateway 1136 and the NAT gateway 1138.

[0154] The data plane VCN 1118 may comprise a data plane app layer 1146 (e.g., data plane app layer 946 of FIG. 9 ), a data plane DMZ layer 1148 (e.g., data plane DMZ layer 948 of FIG. 9 ), and a data plane data layer 1150 (e.g., data plane data layer 950 of FIG. 9 ). The data plane DMZ layer 1148 may comprise a LB subnetwork 1122 that may be communicatively coupled to a trusted app subnetwork 1160 and a non-trusted app subnetwork 1162 of the data plane app layer 1146 and an Internet gateway 1134 included in the data plane VCN 1118. The trusted app subnetwork 1160 may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118, a NAT gateway 1138 included in the data plane VCN 1118, and a DB subnetwork 1130 included in the data plane data layer 1150. The untrusted app subnet 1162 may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118 and a DB subnet 1130 included in the data plane data layer 1150. The data plane data layer 1150 may comprise a DB subnet 1130 that may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118.

[0155] The untrusted app subnet 1162 may comprise one or more primary VNICs 1164(1)-1164(N), which may be communicatively coupled to tenant virtual machines (VMs) 1166(1)-1166(N). Each tenant VM 1166(1)-1166(N) may be communicatively coupled to a respective app subnet 1167(1)-1167(N), which may be included in a respective container egress VCN 1168(1)-1168(N), which may be included in a respective customer tenancy 1170(1)-1170(N). Each secondary VNIC 1172(1)-1172(N) may facilitate communication between the untrusted app subnet 1162 included in the data plane VCN 1118 and the app subnet included in the container egress VCN 1168(1)-1168(N). Each container egress VCN 1168(1)-1168(N) may include a NAT gateway 1138 that may be communicatively coupled to the public Internet 1154 (e.g., the public Internet 954 in FIG. 9).

[0156] An Internet gateway 1134 included in the control plane VCN 1116 and the data plane VCN 1118 may be communicatively coupled to a metadata management service 1152 (e.g., metadata management system 952 of FIG. 9 ), which may be communicatively coupled to the public Internet 1154. The public Internet 1154 may be communicatively coupled to a NAT gateway 1138 included in the control plane VCN 1116 and the data plane VCN 1118. A service gateway 1136 included in the control plane VCN 1116 and the data plane VCN 1118 may be communicatively coupled to cloud services 1156.

[0157] In some embodiments, the data plane VCN 1118 may be integrated with a customer tenancy 1170. This integration may be useful or desirable for an IaaS provider's customer, such as when they may want support for running code. A customer may provide code to run, which may be disruptive, may communicate with other customer resources, or may have undesirable effects. In response, the IaaS provider may determine whether to run the code provided to it by the customer.

[0158] In some examples, a customer of an IaaS provider may request a capability to be granted to the data plane app layer 1146, granting temporary network access to the IaaS provider. The code to execute this capability may be configured to execute in VMs 1166(1)-1166(N) and may not be configured to execute anywhere else on the data plane VCN 1118. Each VM 1166(1)-1166(N) may be connected to one customer tenancy 1170. Each container 1171(1)-1171(N) contained in VMs 1166(1)-1166(N) may be configured to execute code. In this case, there may be double isolation (the containers 1171(1)-1171(N) executing the code may be contained in VMs 1166(1)-1166(N) contained in at least the untrusted app subnet 1162), which may help prevent erroneous or unwanted code from damaging the IaaS provider's network or a different customer's network. The containers 1171(1)-1171(N) may be communicatively coupled to the customer tenancy 1170 and may be configured to send or receive data to the customer tenancy 1170. The containers 1171(1)-1171(N) may not be configured to send or receive data to any other entity in the data plane VCN 1118. Upon completion of the code execution, the IaaS provider may disable and discard the containers 1171(1)-1171(N).

[0159] In some embodiments, the Trusted App Subnet 1160 may execute code that may be owned or operated by the IaaS provider. In this embodiment, the Trusted App Subnet 1160 may be communicatively coupled to the DB Subnet 1130 and may be configured to perform CRUD operations on the DB Subnet 1130. The Non-Trusted App Subnet 1162 may be communicatively coupled to the DB Subnet 1130, but in this embodiment, may be configured to perform read operations on the DB Subnet 1130. The containers 1171(1)-1171(N) that may be included in each customer's VMs 1166(1)-1166(N) and that may execute code from the customer may not be communicatively coupled to the DB Subnet 1130.

[0160] In other embodiments, the control plane VCN 1116 and the data plane VCN 1118 may not be directly communicatively coupled. In this embodiment, there may not be direct communication between the control plane VCN 1116 and the data plane VCN 1118. However, communication may occur indirectly in at least one manner. An LPG 1110 may be established by an IaaS provider that may facilitate communication between the control plane VCN 1116 and the data plane VCN 1118. In another example, the control plane VCN 1116 or the data plane VCN 1118 may make a call to a cloud service 1156 via a service gateway 1136. For example, a call from the control plane VCN 1116 to the cloud service 1156 may include a request for a service that may communicate with the data plane VCN 1118.

[0161] 12 is a block diagram 1200 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 1202 (e.g., service operator 902 of FIG. 9 ) may be communicatively coupled to a secure host tenancy 1204 (e.g., secure host tenancy 904 of FIG. 9 ), which may include a virtual cloud network (VCN) 1206 (e.g., VCN 906 of FIG. 9 ) and a secure host subnet 1208 (e.g., secure host subnet 908 of FIG. 9 ). VCN 1206 may comprise an LPG 1210, which may be communicatively coupled to an SSH VCN 1212 via an LPG 1210 (e.g., LPG 910 of FIG. 9 ) included in SSH VCN 1212 (e.g., SSH VCN 912 of FIG. 9 ). SSH VCN 1212 may comprise an SSH subnet 1214 (e.g., SSH subnet 914 in FIG. 9 ), and SSH VCN 1212 may be communicatively coupled to a control plane VCN 1216 via an LPG 1210 included in the control plane VCN 1216 (e.g., control plane VCN 916 in FIG. 9 ) and to a data plane VCN 1218 via an LPG 1210 included in the data plane VCN 1218 (e.g., data plane VCN 918 in FIG. 9 ). The control plane VCN 1216 and the data plane VCN 1218 may be included in a service tenancy 1219 (e.g., service tenancy 919 in FIG. 9 ).

[0162] The control plane VCN 1216 may comprise a control plane DMZ layer 1220 (e.g., control plane DMZ layer 920 of FIG. 9 ) that may include a LB subnet 1222 (e.g., LB subnet 922 of FIG. 9 ), a control plane app layer 1224 (e.g., control plane app layer 924 of FIG. 9 ) that may include an app subnet 1226 (e.g., app subnet 926 of FIG. 9 ), and a control plane data layer 1228 (e.g., control plane data layer 928 of FIG. 9 ) that may include a DB subnet 1230 (e.g., DB subnet 1130 of FIG. 11 ). The LB subnet 1222 included in the control plane DMZ layer 1220 may be communicatively coupled to an app subnet 1226 included in the control plane app layer 1224 and an Internet gateway 1234 (e.g., Internet gateway 934 in FIG. 9 ) that may be included in the control plane VCN 1216, and the app subnet 1226 may be communicatively coupled to a DB subnet 1230, a service gateway 1236 (e.g., service gateway in FIG. 9 ), and a network address translation (NAT) gateway 1238 (e.g., NAT gateway 938 in FIG. 9 ) included in the control plane data layer 1228. The control plane VCN 1216 may comprise the service gateway 1236 and the NAT gateway 1238.

[0163] The data plane VCN 1218 may comprise a data plane app layer 1246 (e.g., data plane app layer 946 of FIG. 9 ), a data plane DMZ layer 1248 (e.g., data plane DMZ layer 948 of FIG. 9 ), and a data plane data layer 1250 (e.g., data plane data layer 950 of FIG. 9 ). The data plane DMZ layer 1248 may comprise a trusted app subnet 1260 (e.g., trusted app subnet 1160 of FIG. 11 ) and a non-trusted app subnet 1262 (e.g., non-trusted app subnet 1162 of FIG. 11 ) of the data plane app layer 1246 and a LB subnet 1222 that may be communicatively coupled to an Internet gateway 1234 included in the data plane VCN 1218. The trusted app subnet 1260 may be communicatively coupled to a service gateway 1236 included in the data plane VCN 1218, a NAT gateway 1238 included in the data plane VCN 1218, and a DB subnet 1230 included in the data plane data layer 1250. The untrusted app subnet 1262 may be communicatively coupled to a service gateway 1236 included in the data plane VCN 1218 and a DB subnet 1230 included in the data plane data layer 1250. The data plane data layer 1250 may comprise a DB subnet 1230 that may be communicatively coupled to a service gateway 1236 included in the data plane VCN 1218.

[0164] The untrusted app subnet 1262 may comprise primary VNICs 1264(1)-1264(N) that may be communicatively coupled to tenant virtual machines (VMs) 1266(1)-1266(N) that reside within the untrusted app subnet 1262. Each tenant VM 1266(1)-1266(N) may execute code in a respective container 1267(1)-1267(N) and may be communicatively coupled to an app subnet 1226 that may be included in a data plane app layer 1246 that may be included in a container egress VCN 1268. Each secondary VNIC 1272(1)-1272(N) may facilitate communication between the untrusted app subnet 1262 included in the data plane VCN 1218 and the app subnet included in the container egress VCN 1268. The container egress VCN may comprise a NAT gateway 1238 that may be communicatively coupled to the public Internet 1254 (e.g., public Internet 954 of FIG. 9 ).

[0165] An Internet gateway 1234 included in the control plane VCN 1216 and the data plane VCN 1218 may be communicatively coupled to a metadata management service 1252 (e.g., metadata management system 952 of FIG. 9 ), which may be communicatively coupled to the public Internet 1254. The public Internet 1254 may be communicatively coupled to a NAT gateway 1238 included in the control plane VCN 1216 and the data plane VCN 1218. A service gateway 1236 included in the control plane VCN 1216 and the data plane VCN 1218 may be communicatively coupled to cloud services 1256.

[0166] In some examples, the pattern illustrated by the architecture of block diagram 1200 of FIG. 12 may be considered an exception to the pattern illustrated by the architecture of block diagram 1100 of FIG. 11 and may be desirable for customers of an IaaS provider when the IaaS provider cannot communicate directly with the customer (e.g., in a non-connected region). Each of containers 1267(1)-1267(N) contained in VMs 1266(1)-1266(N) for each customer may be accessible in real time by the customer. Containers 1267(1)-1267(N) may be configured to make calls to secondary VNICs 1272(1)-1272(N) respectively contained in app subnet 1226 of data plane app tier 1246 which may be contained in container egress VCN 1268. Secondary VNICs 1272(1)-1272(N) may send the calls to NAT gateway 1238, which may send the calls to public Internet 1254. In this example, containers 1267(1)-1267(N) that are accessible in real time by customers may be isolated from control plane VCN 1216 and may be isolated from other entities included in data plane VCN 1218. Containers 1267(1)-1267(N) may also be isolated from resources of other customers.

[0167] In another example, a customer can use containers 1267(1)-1267(N) to call cloud service 1256. In this example, the customer can execute code in containers 1267(1)-1267(N) that requests a service from cloud service 1256. Containers 1267(1)-1267(N) can send the request to secondary VNICs 1272(1)-1272(N), which can send the request to a NAT gateway, which can send the request to public internet 1254. Public internet 1254 can send the request to LB subnet 1222 included in control plane VCN 1216 via internet gateway 1234. In response to determining that the request is valid, the LB subnet can send the request to the app subnet 1226, which can send the request to the cloud service 1256 via the service gateway 1236.

[0168] It should be understood that the IaaS architectures 900, 1000, 1100, 1200 depicted in the figures may have components other than those depicted. Additionally, the embodiments depicted in the figures are merely some examples of cloud infrastructure systems that may incorporate an embodiment of the present disclosure. In some other embodiments, an IaaS system may have more or fewer components than depicted, may combine two or more components, or may have a different configuration or arrangement of components.

[0169] In one embodiment, the IaaS system described herein may include a self-service, subscription-based, elastically scalable, reliable, highly available and secure suite of application, middleware and database services delivered to customers. Oracle Cloud Infrastructure (OCI), offered by the Assignee, is one example of such an IaaS system.

[0170] 13 illustrates an exemplary computer system 1300 upon which various embodiments may be implemented. The system 1300 may be used to implement any of the computer systems described above. As shown in the figure, the computer system 1300 includes a processing unit 1304 that communicates with a number of peripheral subsystems via a bus subsystem 1302. The peripheral subsystems may include a processing acceleration unit 1306, an I / O subsystem 1308, a storage subsystem 1318, and a communication subsystem 1324. The storage subsystem 1318 includes a tangible computer readable storage medium 1322 and a system memory 1310.

[0171] Bus subsystem 1302 provides a mechanism for allowing the various components and subsystems of computer system 1300 to communicate with each other as desired. Although bus subsystem 1302 is shown diagrammatically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1302 may be any of a number of 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, which may be implemented as a mezzanine bus manufactured in accordance with the IEEE P1386.1 standard, a MicroChannel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

[0172] Processing unit 1304, which may be implemented as one or more integrated circuits (e.g., conventional microprocessors or microcontrollers), controls the operation of computer system 1300. Processing unit 1304 may include one or more processors. These processors may include single-core or multi-core processors. In some embodiments, processing unit 1304 may be implemented as one or more independent processing units 1332 and / or 1334, each including a single-core or multi-core processor. In other embodiments, processing unit 1304 may be implemented as a quad-core processing unit formed by incorporating two dual-core processors on a single chip.

[0173] In various embodiments, the processing unit 1304 is capable of executing various programs in response to program code as well as maintaining multiple simultaneously executing programs or processes. At any time, some or all of the program code being executed may reside on the processor 1304 and / or on the storage subsystem 1318. With suitable programming, the processor 1304 may provide the various functions discussed above. The computer system 1300 may also include a processing acceleration unit 1306, which may include a digital signal processor (DSP), a special purpose processor, and / or the like.

[0174] The I / O subsystem 1308 may include user interface input devices and user interface output devices. User interface input devices may include pointing devices such as keyboards, mice or trackballs, touch pads or touch screens integrated into displays, scroll wheels, click wheels, dials, buttons, switches, keypads, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include motion sensing and / or gesture recognition devices such as Microsoft Kinect® motion sensors that enable user control and interaction with input devices such as Microsoft Xbox® 360 game controllers through a natural user interface using gestures and voice commands. User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects a user's eye activity (e.g., "blinking" during filming and / or menu selection) and translates eye gestures as input to an input device (e.g., Google Glass®). The user interface input devices may also include a voice recognition sensing device that allows a user to interact with a voice recognition system (eg, the Siri® navigator) via voice commands.

[0175] User interface input devices may also include, but are not limited to, three-dimensional (3D) mice, joysticks or pointing sticks, game pads and graphic tablets, as well as audio / visual devices such as speakers, digital cameras, digital video cameras, portable media players, webcams, image scanners, fingerprint scanners, barcode readers 3D scanners, 3D printers, laser range finders, and eye-tracking devices. User interface input devices may also include medical imaging input devices such as, for example, computed tomography, magnetic resonance imaging, position emission tomography, and medical ultrasound devices. User interface input devices may also include audio input devices such as, for example, MIDI keyboards, digital musical instruments, and the like.

[0176] User interface output devices may include non-visual displays such as a display subsystem, indicator lights, or audio output devices. The display subsystem may be a flat panel device such as one using a cathode ray tube (CRT), a liquid crystal display (LCD) or a plasma display, a projection device, a touch screen, etc. 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 1300 to a user or to another computer. For example, user interface output devices may include, but are not limited to, a variety of display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, automobile navigation systems, plotters, audio output devices, and modems.

[0177] Computer system 1300 may include a storage subsystem 1318 that provides a tangible, non-transitory computer-readable storage medium for storing software and data constructs that provide the functionality of embodiments described in this disclosure. The software may include programs, code, instructions, scripts, etc. that, when executed by one or more cores or processors of processing unit 1304, provide the functionality described above. Storage subsystem 1318 may also provide a repository for storing data used in accordance with the present disclosure.

[0178] As shown in the example of Figure 13, storage subsystem 1318 may comprise various components including a system memory 1310, a computer readable storage medium 1322, and a computer readable storage medium reader 1320. The system memory 1310 may store program instructions that may be loaded and executed by the processing unit 1304. The system memory 1310 may also store data used during execution of the instructions and / or data generated during execution of the program instructions. A variety of different types of programs may be loaded into the system memory 1310, including, but not limited to, client applications, web browsers, mid-tier applications, relational database management systems (RDBMS), virtual machines, containers, etc.

[0179] System memory 1310 may also store operating system 1316. Examples of operating systems 1316 include various versions of Microsoft Windows, Apple Macintosh, and / or Linux operating systems, various commercially available UNIX or UNIX-like operating systems (including, but not limited to, various GNU / Linux operating systems, Google Chrome OS, etc.), and / or mobile operating systems such as iOS, Windows Phone, Android OS, BlackBerry OS, and Palm OS operating systems. In certain embodiments in which computer system 1300 runs one or more virtual machines, the virtual machines, along with their guest operating systems (GOS), may be loaded into system memory 1310 and executed by one or more processors or cores of processing unit 1304.

[0180] The system memory 1310 may have a variety of configurations depending on the type of computer system 1300. For example, the system memory 1310 may be volatile memory (such as random access memory (RAM)) and / or non-volatile memory (such as read-only memory (ROM), flash memory, etc.). Also, different types of RAM configurations may be provided, including static random access memory (SRAM), dynamic random access memory (DRAM), and others. In some implementations, the system memory 1310 may include a basic input / output system (BIOS) containing the basic routines that help to transfer information between elements within the computer system 1300, such as during start-up.

[0181] Computer-readable storage medium 1322 may represent remote, local, fixed, and / or removable storage devices, as well as storage media for temporarily and / or permanently containing and storing computer-readable information used by computer system 1300 (including instructions executable by processing unit 1304 of computer system 1300).

[0182] The computer readable storage medium 1322 may include any suitable medium known or used in the art (including storage media and communication media), including, but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing and / or transmitting information. This may 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 tapes, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media.

[0183] As an example, the computer readable storage medium 1322 may include hard disk drives that read from and write to non-removable, non-volatile magnetic media, magnetic disk drives that read from and write to removable, non-volatile magnetic disks, and optical disk drives that read from and write to removable, non-volatile optical disks, such as CD ROMs, DVDs, Blu-Ray disks, or other optical media. The computer readable storage medium 1322 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 tapes, and the like. The computer readable storage medium 1322 may also include flash memory-based SSDs, enterprise flash drives, solid-state drives (SSDs) based on non-volatile memory, such as solid-state ROMs, 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, programs, and other data for the computer system 1300.

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

[0185] The communications subsystem 1324 provides an interface to other computer systems and networks. The communications subsystem 1324 serves as an interface for the transmission and reception of data between the computer system 1300 and other systems. For example, the communications subsystem 1324 may enable the computer system 1300 to connect to one or more devices via the Internet. In some embodiments, the communications subsystem 1324 may comprise a wireless voice and / or data network (e.g., using cellular technology, 3G, 4G, or Enhanced Data Rates for Global Evolution (EDGE), WiFi (advanced data network technology such as the IEEE 802.11 family of standards, or other mobile communications technology, or any combination thereof), a global positioning system (GPS) receiver component, and / or a radio frequency (RF) transceiver component for accessing other components. In some embodiments, the communications subsystem 1324 may provide a wired network connection (e.g., Ethernet) in addition to or as an alternative to a wireless interface.

[0186] Also, in some embodiments, the communications subsystem 1324 can receive incoming communications in the form of structured and / or unstructured data feeds 1326, event streams 1328, event updates 1330, etc., on behalf of one or more users who may be using the computer system 1300.

[0187] As an example, the communications subsystem 1324 may be configured to receive data feeds 1326 in real time from users of other communications services, such as social networks and / or web feeds such as Twitter® feeds, Facebook® updates, RSS (Rich Site Summary) feeds, and / or real-time updates from one or more third party information sources.

[0188] The communications subsystem 1324 may also be configured to receive data in the form of a continuous data stream, which may include an event stream 1328 of real-time events and / or event updates 1330, which may be continuous and may be effectively infinite with no apparent end. Examples of applications that generate continuous data include, for example, sensor data applications, financial tickers, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.

[0189] The communications subsystem 1324 may also be configured to output structured and / or unstructured data feeds 1326, event streams 1328, event updates 1330, etc. to one or more databases that may be in communication with one or more streaming data source computers coupled to the computer system 1300.

[0190] The computer system 1300 can be one of a variety of types, including a portable handheld device (such as an iPhone® mobile phone, an iPad® computing tablet, a PDA, etc.), a wearable device (such as a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.

[0191] Due to the ever-changing nature of computers and networks, the description of the illustrated computer system 1300 is intended as a specific example only. Many other configurations are possible, whether with more or fewer components than the illustrated system. For example, customized hardware may also be used, and / or particular elements may be implemented in hardware, firmware, software (including applets), or a combination. Furthermore, connections to other computing devices, such as network input / output devices, may be employed. Based on the disclosure and teachings provided herein, one of ordinary skill in the art will recognize other ways and / or methods of implementing various embodiments.

[0192] Although specific embodiments have been described above, various modifications, variations, alternative configurations, and equivalents are within the scope of the present disclosure. The embodiments are not limited to operating in a particular data processing environment, but may freely operate in multiple data processing environments. Furthermore, while the embodiments have been described using a specific sequence of transactions and steps, it will be apparent to those skilled in the art that the scope of the present disclosure is not limited to the sequence of transactions and steps described. Various features and aspects of the above-described embodiments may be used individually or together.

[0193] Furthermore, while embodiments have been described using a particular combination of hardware and software, it will be appreciated that other combinations of hardware and software are within the scope of the present disclosure. The embodiments may be implemented solely in hardware, solely in software, or by using a combination thereof. The various processes described herein may be implemented on the same processor or on different processors in any combination. Thus, when a component or module is described as being configured to perform a certain operation, such configuration may be achieved, for example, by designing an electronic circuit to perform the operation, by programming a programmable electronic circuit (such as a microprocessor) to perform the operation, or any combination thereof. The processes may communicate using a variety of techniques, including, but not limited to, conventional techniques for inter-process communication. Also, different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times. The embodiments may be implemented using a computer program product that includes computer programs / instructions that, when executed by a processor, cause the processor to perform any of the methods described in the present disclosure.

[0194] Accordingly, the specification and drawings are to be regarded as illustrative rather than restrictive. However, it will be apparent that additions, differences, deletions, and other modifications and alterations may be made without departing from the broad spirit and scope of the appended claims. Thus, although specific embodiments of the present disclosure have been described, they are not intended to be limiting. Various modifications and equivalents are intended to be within the scope of the following claims.

[0195] Use of the terms "a," "an," and "the," and similar referents in the context of describing the disclosed embodiments (particularly in the context of the claims below) shall 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" shall be construed as open-ended terms (i.e., meaning "including, but not limited to"), unless otherwise noted. The term "connected" shall be construed as partly or wholly contained in, attached to, or integrally connected to, even if there is something intervening. The recitation of ranges of values ​​herein is merely intended to serve as a shorthand method of individually referring to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated herein as if it were a separate recitation herein. All methods described herein may be performed in any suitable order, unless otherwise indicated herein or clearly contradicted by context. The use of any and all examples or exemplary language (e.g., "such as") herein is intended to facilitate understanding of the embodiments only and does not limit the scope of the disclosure unless otherwise asserted. No language in the specification should be construed as indicating any non-claimed element as essential to the practice of the disclosure.

[0196] Unless otherwise noted, disjunctive language, such as the phrase "at least one of X, Y, or Z," is intended to be understood in the context in which it is commonly used to indicate that an item, term, etc. can be either X, Y, Z, or any combination thereof (e.g., X, Y, and / or Z). Thus, such disjunctive language is generally not intended to, and should not, imply that an embodiment requires the presence of at least one of X, at least one of Y, or at least one of Z, respectively.

[0197] Preferred embodiments of the present disclosure are described herein, including the best mode known for carrying out the present disclosure. Modifications of these preferred embodiments may become apparent to those skilled in the art upon reading the above description. Such modifications may be adopted by those skilled in the art as necessary, and the present disclosure may be practiced differently from the specific descriptions 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, unless otherwise indicated herein, this disclosure includes any combination of the above-described elements in all possible variations thereof.

[0198] All references cited in this specification, including publications, patent applications, and patents, are herein incorporated by reference to the same extent as if each reference was individually and specifically indicated to be incorporated by reference in its entirety.

[0199] Although aspects of the disclosure are described in the above specification with reference to specific embodiments, those skilled in the art will recognize that the disclosure is not limited thereto. The various features and aspects of the disclosure described above may be used individually or together. Moreover, the embodiments may be utilized in any number of environments and applications beyond those described herein without departing from the broad spirit and scope of the specification. Accordingly, the specification and drawings are to be regarded as illustrative rather than limiting.

Claims

1. A distributed computing system of a cloud service provider generates a virtual cloud network in a host region; the distributed computing system implementing a virtual bootstrap environment in the virtual cloud network; the distributed computing system deploying a first service of the virtual bootstrap environment; The distributed computing system establishes a network connection between the virtual cloud network and a target region; the distributed computing system deploying resources of the virtual bootstrap environment to the target region by using the first service; The resource is deployed over the network connection.

2. the distributed computing system deploying a second service in the virtual bootstrap environment; the distributed computing system further comprising: provisioning a computing infrastructure in the target region by using the second service; The method of claim 1 , wherein deploying the resources of the virtual bootstrap environment comprises deploying the resources to the provisioned computing infrastructure.

3. The method of claim 1 or claim 2, wherein deploying the resources of the virtual bootstrap environment includes deploying an instance of the first service in the target region.

4. The method of claim 1 or claim 2, wherein the host region comprises a host data center.

5. The method of claim 1 or claim 2, wherein the target region comprises a target data center.

6. The method of claim 1 or claim 2, wherein the network connection comprises a virtual private network connection.

7. The method of claim 6 , further comprising establishing an IPSec tunnel over the virtual private network connection.

8. 1. A computing system comprising: one or more processors; one or more memories storing computer-executable instructions that, when executed by the one or more processors, cause the computing system to perform at least: generating a virtual cloud network in the host region; Implementing a virtual bootstrap environment in the virtual cloud network; Deploying a first service in the virtual bootstrap environment; Establishing a network connection between the virtual cloud network and a target region; A computing system that uses the first service to deploy resources of the virtual bootstrap environment to the target region, the resources being deployed over the network connection.

9. The one or more memories further store instructions that, when executed by the one or more processors, cause the computing system to further: Deploying a second service in the virtual bootstrap environment; Provisioning computing infrastructure in the target region using the second service; The computing system of claim 8 , wherein deploying the resources of the virtual bootstrap environment comprises deploying the resources to the provisioned computing infrastructure.

10. The computing system of claim 8 or claim 9, wherein deploying the resources of the virtual bootstrap environment includes deploying an instance of the first service in the target region.

11. The computing system of claim 8 or claim 9, wherein the host region comprises a host data center.

12. The computing system of claim 8 or claim 9, wherein the target region comprises a target data center.

13. 10. The computing system of claim 8 or claim 9, wherein the network connection comprises a virtual private network connection.

14. 14. The computing system of claim 13, wherein the one or more memories further store instructions that, when executed by the one or more processors, further cause the computing system to establish an IPSec tunnel over the virtual private network connection.

15. A computer program comprising computer-executable instructions that, when executed by one or more processors, cause a computing system to perform at least: generating a virtual cloud network in the host region; Implementing a virtual bootstrap environment in the virtual cloud network; Deploying a first service in the virtual bootstrap environment; Establishing a network connection between the virtual cloud network and a target region; A computer program that deploys resources of the virtual bootstrap environment to the target region by using the first service, the resources being deployed over the network connection.

16. and further storing instructions that, when executed by the one or more processors, cause the computing system to further: Deploying a second service in the virtual bootstrap environment; Provisioning computing infrastructure in the target region using the second service; The computer program product of claim 15 , wherein deploying the resources of the virtual bootstrap environment comprises deploying the resources to the provisioned computing infrastructure.

17. 17. The computer program product of claim 15 or 16, wherein deploying the resources of the virtual bootstrap environment includes deploying an instance of the first service in the target region.

18. 17. The computer program product of claim 15 or claim 16, wherein the host region comprises a host data center.

19. The computer program product of claim 15 or 16, wherein the target region comprises a target data center.

20. 17. The computer program product of claim 15 or 16, wherein the network connection comprises an IPSec tunnel.

Images