Technologies used for migrating services from virtual boot environments

Abstract

Techniques for migrating services from a virtual bootstrap environment are disclosed. A distributed computing system can generate a virtual cloud network within a data center in a host region. The virtual bootstrap environment can be implemented within this virtual cloud network. The virtual bootstrap environment can include multiple services. The distributed computing system can also deploy instances of one of these services to a target region data center. When an instance has been deployed, a successful deployment indication can be received by the distributed computing system. In response, the distributed computing system can identify any additional resources associated with the deployed instance of the service and update another service in the virtual bootstrap environment with those resources.

Description

[0001] Cross-reference to related applications

[0002] This application claims U.S. Patent Application No. 18 / 105,766, filed February 3, 2023, entitled “TECHNIQUES FOR MIGRATING SERVICES FROM A VIRTUAL BOOTSTRAP ENVIRONMENT”; U.S. Provisional Patent Application No. 63 / 315,017, filed February 28, 2022, entitled “TECHNIQUES FOR MIGRATING SERVICES FROM A VIRTUAL BOOTSTRAP ENVIRONMENT”; U.S. Provisional Patent Application No. 63 / 308,003, filed February 8, 2022, entitled “TECHNIQUES FOR BOOTSTRAPPING A REGION BUILD”; and U.S. Provisional Patent Application No. 63 / 308,003, filed February 22, 2022, entitled “TECHNIQUES FOR IMPLEMENTING VIRTUAL ENVIRONMENT”. Priority to U.S. Provisional Patent Application No. 63 / 312,814, “DATACENTERS”, the contents of each of which are incorporated herein by reference in their entirety for all purposes. Technical Field

[0003] This disclosure relates to the construction of regional data centers. More specifically, this disclosure describes techniques for migrating services from a virtual boot environment to data center infrastructure during the construction of a regional data center. Background Technology

[0004] Cloud infrastructure providers can provision cloud computing infrastructure and related services across many geographic regions globally. To provide this infrastructure, a cloud infrastructure provider may operate one or more data centers corresponding to a local geographic region. These data centers may be included as part of a “region,” which is a logical abstraction of the computing resources of a geographic region and one or more data centers. Building a new region may involve provisioning computing resources, configuring infrastructure, and deploying code to those resources. The typical techniques used to build regions involve a significant amount of manual work. Porting existing services to a new region can be challenging because services may depend on the functionality of other existing services and / or resources within the region. Relying on manual operations to port services and / or build regions incurs substantial time costs and risks associated with manual configuration errors, and may not scale well. Summary of the Invention

[0005] Embodiments of this disclosure relate to creating a bootstrap environment to support the construction of a region. The region construction process may include bootstrapping (e.g., provisioning and / or deploying) resources (e.g., infrastructure components, artifacts, etc.) for any appropriate number of services within 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) within an existing region. Therefore, a virtual bootstrap environment (ViBE) can be built and configured in an existing region prior to the region construction process. Services (e.g., core services) may be deployed to the ViBE to support bootstrap operations to a target region (e.g., the region to be built during the region construction process). Services in the ViBE can be used to provision computing resources (e.g., bare-metal compute hosts, virtual machines, storage, etc.) in the target region. Services in the ViBE can also be used to deploy services to the target region, including instances of services in the ViBE. By using cloud infrastructure orchestration services with the ViBE, new regions can be built intelligently and automatically.

[0006] One embodiment relates to a computer-implemented method performed by a distributed computing system (e.g., a cloud computing system) of a cloud service provider. The method may include generating a virtual cloud network (ViBE) in a data center within a host region and implementing a ViBE within the ViBE. The ViBE may include multiple services. The method may also include deploying an instance of one of the multiple services in the ViBE to a target region data center. The instance may be configured to perform the same service functions as the service in the ViBE. The method may also include receiving an indication from the deployed instance that the instance has been successfully deployed. Since the deployed service may not have all the resources associated with its corresponding service in the ViBE (e.g., data resources created by the service in the ViBE), in some embodiments, the indication may be a capability indicating successful partial deployment of the service. The capability may be advertised to a capability service in the ViBE. The method may also include identifying resources (e.g., DNS records) associated with the instance deployed to the target region data center. The resources may then be used by the distributed computing system to update a second service in the ViBE (e.g., update DNS in the ViBE). In some embodiments, the resources may also be used to update the service instance deployed to the target region data center.

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

[0008] Another embodiment relates to a non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors of a computing cluster, cause the computing cluster to perform one or more of the methods disclosed herein. Attached Figure Description

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

[0010] Figure 1 It is a block diagram of an environment in which a cloud infrastructure orchestration service (CIOS) according to at least one embodiment is operable to dynamically provide bootstrapping services in a region.

[0011] Figure 2 It is a block diagram illustrating an environment and method for constructing a Virtual Boot Environment (ViBE) according to at least one embodiment.

[0012] Figure 3 This is a block diagram illustrating an environment and method for directing services to a target area using ViBE, according to at least one embodiment.

[0013] Figure 4 This is a block diagram of an environment in which a cloud infrastructure orchestration service (CIOS) according to at least one embodiment can utilize a resource discoverer to discover resources during region building.

[0014] Figure 5 This is a block diagram depicting an example flow of operations according to at least one embodiment for performing services provisioning and deployment to a data center in a new region and importing resources before updating the DNS records of the deployed services.

[0015] Figure 6 This is an example method for migrating a service from ViBE to a target region according to at least one embodiment.

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

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

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

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

[0020] Figure 11 An example computer system in which various embodiments can be implemented is illustrated. Detailed Implementation

[0021] Example data center construction (regional construction) infrastructure

[0022] The adoption of cloud services has recently seen rapid growth. Currently, various cloud service providers (CSPs) offer a wide range of cloud services. The term cloud service generally refers to services or functions made available to users or customers on demand (e.g., via a subscription model) by a CSP using its own systems and infrastructure (cloud infrastructure). Typically, the servers and systems that constitute the CSP infrastructure and are used to provide cloud services to customers are separate from the customer's own on-premises servers and systems. Therefore, customers can utilize cloud services provided by CSPs without having to purchase separate hardware and software resources for the service. Cloud services are designed to provide subscribers with easy, scalable, and on-demand access to applications and computing resources without requiring customers to invest in the infrastructure used to provide the services or functions. Various types or models of cloud services can be provided, such as Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS), etc. Customers can subscribe to one or more cloud services provided by a CSP. Customers can be any entity, such as individuals, organizations, enterprises, etc.

[0023] As described above, the CSP is responsible for providing the infrastructure and resources used to deliver cloud services to subscribers. The resources provided by the CSP can include both hardware and software resources. These resources can include, for example, computing resources (e.g., virtual machines, containers, applications, processors), storage resources (e.g., databases, data stores), networking resources (e.g., routers, servers, load balancers), identity, and other resources. In some implementations, the resources provided by the CSP for delivering a set of cloud services are organized into a data center. A data center can be configured to provide a specific set of cloud services. The CSP is responsible for equipping the data center with the infrastructure and resources used to deliver that specific set of cloud services. The CSP can build one or more data centers.

[0024] CSP-provided data centers may be hosted in different regions. A region is a local geographic area and can be identified by its name. Regions are typically independent of each other and may be geographically separated, such as spanning countries or even continents. Regions are grouped into domains. Examples of CSP regions could include the western United States, the eastern United States, eastern Australia, southeastern Australia, etc.

[0025] A region can include one or more data centers located within a specific geographic area corresponding to that region. For example, a data center within a region could be located in a city within that region. For instance, for a specific CSP, a data center in the Western United States region might be located in San Jose, California; a data center in the Eastern United States region might be located in Ashburn, Virginia; a data center in the Eastern Australia region might be located in Sydney, Australia; a data center in the Southeastern Australia region might be located in Melbourne, Australia; and so on.

[0026] Data centers within a region can be organized into one or more availability domains for high availability and disaster recovery purposes. An availability domain can include one or more data centers within the region. Availability domains within a region are isolated from each other, fault-tolerant, and architected in a way that makes it unlikely that data centers in multiple availability domains will fail simultaneously. For example, availability domains within a region can be structured such that a failure in one availability domain within the region is unlikely to affect the availability of data centers in other availability domains within the same region.

[0027] When a customer or subscriber subscribes to or registers for one or more services offered by a CSP, the CSP creates a lease for the customer. A lease is like an account created for the customer. In some implementations, a customer's lease exists in a single domain and has access to all areas belonging to that domain. The customer's user can then access the services the customer has subscribed to under this lease.

[0028] As described above, CSPs build or deploy data centers to provide cloud services to their customers. As a CSP's customer base grows, it typically builds new data centers in new regions or increases the capacity of existing data centers to serve the growing needs of its customers and improve customer service. Preferably, data centers are built in geographical proximity to the locations of the customers they serve. This geographical proximity leads to more efficient use of resources and faster, more reliable service delivery to customers. Therefore, CSPs often build new data centers in new regions geographically close to the customers they serve. For example, for a growing customer base in Germany, a CSP might build one or more data centers in new regions within Germany.

[0029] Building a data center (or multiple data centers) within a region is sometimes referred to as building a region. The term "region building" is used to refer to building one or more data centers within a region. Building a data center within a region involves provisioning or creating a new set of resources required or used by the data center to provide a set of services. The end result of the region building process is the creation of a data center within the region, which is capable of providing a set of services intended for that data center and includes a set of resources for providing those services.

[0030] Building a new data center within a region is a highly complex activity requiring extensive coordination among various bootstrapping activities. At a high level, this involves the execution and coordination of a variety of tasks, such as: identifying the set of services the data center will provide; identifying the various resources required to provide these services; creating, provisioning, and deploying the identified resources; properly connecting the resources so they can be used as intended; and so on. Each of these tasks further comprises sub-tasks that need to be coordinated, further increasing the complexity. Due to this complexity, currently, building a data center within a region involves several manually initiated or manually controlled tasks requiring careful manual coordination. Therefore, the task of building a new region (i.e., building one or more data centers within a region) is very time-consuming. Building a data center can take, for example, many months. Furthermore, the process is highly error-prone, sometimes requiring several iterations before the desired configuration of the data center is achieved, further increasing the time spent building the data center. These limitations and issues severely restrict the ability of CSPs to grow computing resources in a timely manner to respond to increasing customer demand.

[0031] This disclosure describes techniques for reducing build time, minimizing wasted computing resources, and reducing the risks associated with building one or more data centers in a region. Instead of the weeks and months previously required to build data centers in a region, the techniques described herein can be used to build new data centers in a region in a relatively short time, while reducing the risk of errors compared to conventional methods.

[0032] This paper discloses a Cloud Infrastructure Orchestration Service (CIOS) configured to bootstrap (e.g., provisioning and deployment) services to new data centers based on predefined profiles that identify resources (e.g., infrastructure components and software to be deployed) used to implement a given change to the data center. CIOS can parse and analyze profiles (e.g., group configurations) to identify dependencies between resources, execution goals, stages, and groups. CIOS can generate specific data structures from the analysis and use these structures to drive operations and manage the order in which services are bootstrapped to regions. CIOS can leverage these data structures to identify when services can be bootstrapped, when bootstrap is blocked, and / or when bootstrap operations associated with previously blocked services can be resumed. Advantageously, CIOS can identify circular dependencies within data structures and perform operations to eliminate / resolve these circular dependencies before task execution. Using these techniques, CIOS significantly reduces the risk of executing tasks before the resources on which those tasks depend become available.

[0033] Using the techniques disclosed in this paper, CIOS can optimize parallel processing to execute changes to the data center while ensuring that tasks are not started until the functionality they depend on becomes available in the region. In this way, CIOS enables region building to be performed more efficiently, significantly reducing the time required to build the data center and the wasted computing resources found in conventional methods.

[0034] Some definitions

[0035] A "region" is a logical abstraction corresponding to a geographical location. A region can include any appropriate number or more execution targets. In some embodiments, an execution target can correspond to a data center.

[0036] An "execution target" is the smallest unit of change used to perform a release. A "release" is an indication of an intent to orchestrate specific changes 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 directed to each of one or more execution targets. Execution targets can be associated with a set of devices (e.g., a data center).

[0037] "Guidance" is intended to refer to a collective task associated with the provisioning and deployment of any appropriate number of resources (e.g., infrastructure components, artifacts, etc.) corresponding to a single service.

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

[0039] "Artifacts" refer to code deployed to infrastructure components or Kubernetes engine clusters, which may include software (e.g., applications), configuration information for infrastructure components (e.g., configuration files), or the like.

[0040] A "group configuration" refers to a configuration file (or a set of configuration files) that describes a group of all resources (e.g., infrastructure components and artifacts) associated with a single service. A group configuration may include declarative statements that specify one or more aspects corresponding to the desired state of the service resources.

[0041] "Service status" refers to a point-in-time snapshot of each resource (e.g., infrastructure resources, artifacts, etc.) associated with a service. Service status indicates the status of the provisioning and / or deployment tasks associated with the service resource.

[0042] IaaS provisioning (or "provisioning") refers to acquiring a computer or virtual host for use, and even installing necessary libraries or services on it. The phrase "provisioning equipment" refers to evolving equipment to a state where it can be used by end users for their specific purposes. Equipment that has undergone the provisioning process can be referred to as "provisioned equipment." Preparing provisioned equipment (installing libraries and daemons) may be part of provisioning; this preparation is different from deploying a new application or a new version of an application to a prepared equipment. In most cases, deployment does not include provisioning, and provisioning may need to be performed first. Once ready, the equipment can be referred to as an "infrastructure component."

[0043] IaaS deployment (or "deployment") refers to the process of providing and / or installing new applications or new versions of applications on provisioned infrastructure components. Once the infrastructure components are provisioned (e.g., acquired, allocated, prepared, etc.), additional software can be deployed (e.g., providing additional software to the infrastructure components and installing it on them). After provisioning and deployment are complete, the infrastructure components may be referred to as "resources". Examples of resources may include, but are not limited to, virtual machines, databases, object storage, block storage, load balancers, etc.

[0044] A “capability” identifies a functional unit associated with a service. This unit can be a subset or all of the functionality to be provided by the service. For example, capabilities indicating that a resource is available for authorization / authentication processing (e.g., a subset of functionality to be provided by the resource) can be published. As another example, capabilities indicating that all functionality of a service is available can be published. Capabilities can be used to identify the functionality on which a resource or service depends and / or the functionality of a resource or service that can be used.

[0045] A Virtual Boot Environment (ViBE) is a virtual cloud network provisioned within the coverage of an existing region (e.g., a "host region"). Once provisioned, the ViBE connects to the new region using a communication channel (e.g., an IPSec tunnel VPN). Certain essential core services (or "seed" services), such as deployment orchestrators and public key infrastructure (PKI) services, can be provisioned in the ViBE. These services provide the capabilities needed to bring hardware online, establish a chain of trust to the new region, and deploy the remaining services in the new region. Utilizing a Virtual Boot Environment prevents circular dependencies between boot resources by leveraging the resources of the host region. Services can be staged and tested in the ViBE before they become available in the physical region (e.g., the target region).

[0046] "Cloud Infrastructure Orchestration Service" (CIOS) can refer to a system configured to manage the provisioning and deployment operations of any appropriate number of services as part of a region's architecture.

[0047] A Multi-Group Orchestrator (MFO) can be a computing component (e.g., a service) that coordinates events between CIOS components to provision and deploy services to a target region (e.g., a new region). The MFO tracks relevant events for each service built into the region and takes action in response to those events.

[0048] "Host Zone" refers to the zone that hosts the Virtual Boot Environment (ViBE). The Host Zone can be used to boot the ViBE.

[0049] "Target area" refers to the area that has been constructed.

[0050] "Publish capability" refers to "publication" as used in a "publisher-subscriber" computing design, or otherwise providing an indication that a particular capability is available (or unavailable). A capability is "published" (e.g., collected by a capability service, provided to a capability service, pushed, pulled, etc.) to provide an indication that a resource / service is available. In some embodiments, capabilities may be published / transmitted via events, notifications, data transfers, function calls, API calls, or the like. Events (or other notifications / data transfers / etc.) indicating the availability of a particular capability may be broadcast / addressed (e.g., published) to the capability service.

[0051] A "capability service" can be a group configured to model dependencies between different groups. Capability services can be provided within cloud infrastructure orchestration services and can define what capabilities, services, and / or features have been enabled and are available in a region.

[0052] A Real-Time Region Data Distributor (RRDD) can be a service or system configured to manage region data. This region data can be injected into a group configuration to dynamically create execution targets for new regions.

[0053] In some examples, this paper describes technologies for implementing Cloud Infrastructure Orchestration Services (CIOS). As briefly described above, such technologies can be configured to manage infrastructure components (e.g., provisioning and deploying software) within a bootstrapping cloud environment (e.g., a region). In some cases, CIOS may include compute components (e.g., CIOS hubs and CIOS regions, both described in further detail below) that can be configured to manage bootstrapping tasks (provisioning and deployment) for a given service, as well as a multi-group orchestrator (also described in further detail below) configured to launch / manage region builds (e.g., bootstrapping operations corresponding to multiple services).

[0054] CIOS enables region building and global infrastructure provisioning, as well as code deployment (e.g., in some cases, beyond initial approval and / or physical transportation of hardware) with minimal manual runtime effort from the service team. CIOS's advanced responsibilities include, but are not limited to, coordinating region building, providing users with a current state view of resources managed by CIOS (e.g., regional, cross-regional, global, etc.), and managing bootstrap operations for bootstrap resources within a region.

[0055] CIOS provides view reconciliation, where a view of the desired state (e.g., desired configuration) of a resource can be reconciled with the resource's current / actual state (e.g., current configuration). In some cases, view reconciliation may include obtaining state data to identify which resources are actually running and their current configuration and / or state. Reconciliation can be performed at a wide range of granularities, such as at the service level.

[0056] CIOS can perform plan generation, where the difference between the desired state and the current state of a resource is identified. Part of plan generation may include identifying the operations that need to be performed to bring the resource from its current state to its desired state. In some examples, CIOS can present the generated plan to the user for approval. In these examples, CIOS can mark the plan as approved or rejected based on user input. Therefore, users can spend less time reasoning about the plan, and because the plan is machine-generated, it is more accurate. The plan is almost too detailed for human use; however, CIOS can provide this data via a sophisticated user interface (UI).

[0057] In some examples, CIOS can handle change management by executing an approved plan. Once the execution plan has been created and approved, engineers may no longer need to be involved in change management unless CIOS initiates a rollback. CIOS can handle rollbacks to previous service versions (e.g., when CIOS detects a service health degradation during execution) by generating a plan that returns the service to a previous (e.g., pre-release) state.

[0058] CIOS can measure service health by monitoring alerts and performing integration tests. In the event of a service degradation, CIOS can help teams quickly define rollback actions that can be performed later. CIOS can generate and display plans and track approvals. CIOS can combine provisioning and deployment capabilities into a single system that coordinates these tasks built across regions. CIOS also supports the discovery of groups (e.g., service resources, such as group configurations corresponding to any appropriate number of services), artifacts, resources, and dependencies. CIOS can discover dependencies between execution tasks at each level (e.g., resource level, execution target level, phase level, service level, etc.) through static analysis of one or more profiles (e.g., including parsing and processing content). Using these dependencies, CIOS can generate various data structures that can be used to drive task execution (e.g., tasks related to the provisioning of infrastructure resources and the deployment of artifacts across regions).

[0059] Figure 1 This is a block diagram of an environment 100 operable with a Cloud Infrastructure Orchestration Service (CIOS) 102 according to at least one embodiment to dynamically provide bootstrapping services in a region. CIOS 102 may include, but is not limited to, the following components: a Real-time Regional Data Distributor (RRDD) 104, a Multi-Group Orchestrator (MFO) 106, a CIOS Center 108, a CIOS Region 110, and a Capability Service 112. Specific functionalities of CIOS Center 108 and CIOS Region 110 are provided in more detail in U.S. Application 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 for all purposes. In some embodiments, any suitable combination of the components of CIOS 102 may be provided as a service. In some embodiments, portions 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 those described in U.S. Application No. 17 / 016,754 and the following description... Figure 2 and Figure 3 Any appropriate number of cloud services to be discussed in further detail Figure 1 (Not depicted in the text).

[0060] The Real-Time Region Data Distributor (RRDD) 104 can be configured to maintain and provide region data that identifies realms, regions, execution targets, and availability domains. In some cases, region data can be in any suitable form (e.g., JSON format, data object / container, XML, etc.). The region data maintained by RRDD 104 can include any suitable number of data subsets, which can be individually referenced by corresponding identifiers. For example, the identifier “all_regions” can be associated with a data structure (e.g., a list, structure, object, etc.) that includes metadata for all defined regions. As another example, identifiers (such as “realms”) can be associated with a data structure that identifies multiple realms and a set of regions corresponding to each realm. Typically, region data can maintain any suitable attributes such as identifiers, DNS suffixes, status (e.g., region status) for one or more realms, regions(one or more), availability domains (AD), execution targets(one or more) etc. RRDD 104 can be configured to manage region status as part of the region data. Region status can include any suitable information indicating the boot status within a region. For example, some sample region states may include "Initial," "Build," "Production," "Paused," or "Eprecated." The "Initial" state indicates a region that has not yet been booted. The "Build" state indicates that booting for one or more groups within the region has begun. The "Production" state indicates that booting has been completed and the region is ready for verification. The "Paused" state indicates that CIOS Center 108 or CIOS Region 110 has paused internal interaction with the region stack, possibly due to operational issues. The "Eprecated" state indicates that the region has been deprecated and may be unavailable and / or will no longer be contactable.

[0061] CIOS Center 108 is configured to provide any appropriate number of user interfaces through which users (e.g., user 109) can interact with CIOS 102. For example, a user can make changes to region data via the user interfaces provided by CIOS Center 108. CIOS Center 108 can also provide a variety of interfaces enabling users to: view changes made to group configurations and / or artifacts, generate and view plans, approve / reject plans, and view the status of plan execution (e.g., tasks corresponding to the desired status of any appropriate number of resources involved in infrastructure provisioning, deployment, region building, and / or management by CIOS 102). CIOS Center 108 can implement a control plane configured to manage any appropriate number of CIOS Region 110 instances. CIOS Center 108 can provide one or more user interfaces to present region data, enabling user 109 to view and / or modify the region data. CIOS Center 108 can be configured to invoke the functions of RRDD 104 via any appropriate number of interfaces. Typically, CIOS Center 108 can be configured to manage region data directly or indirectly (e.g., via RRDD 104). CIOS Center 108 can be configured to compile group configurations to inject region data as variables into the group configuration.

[0062] Each instance of CIOS Zone 110 may correspond to a component or module configured to perform bootstrapping tasks associated with a single service in the zone. CIOS Zone 110 may receive expected state data from CIOS Center 108. In some embodiments, expected state data may include a group configuration of the expected state of resources associated with the service, declaring (e.g., via declarative statements). CIOS Center 108 may maintain current state data indicating any appropriate aspects of the current state of resources associated with the service. In some embodiments, CIOS Zone 110 may identify necessary changes to one or more resources by comparing expected state data and current state data. For example, CIOS Zone 110 may determine that one or more infrastructure components need to be provisioned, one or more artifacts need to be deployed, or any appropriate changes to resources of the service are needed to bring the state of those resources into alignment with the expected state. When CIOS Zone 110 performs bootstrapping operations, it may publish data indicating various capabilities of the resource as the various capabilities of the resource become available. A “capability” identifies a functional unit associated with the service. This unit may be a subset or all of the functionality to be provided by the service. For example, capabilities indicating that a resource can be used for authorization / authentication processing (e.g., a subset of functionality to be provided by the resource) may be published. As another example, capabilities that indicate the full functionality of a service can be published. These capabilities can be used to identify the functionality a resource or service depends on and / or the functionality of the resource or service that can be used.

[0063] Capability service 112 is configured to maintain capability data indicating 1) which capabilities of various services are currently available, 2) whether any resource / service is waiting for a specific function, 3) what specific resources and / or services are waiting for a given capability, or any suitable combination of the above. Capability service 112 may provide an interface through which capability data can be requested. Capability service 112 may provide one or more interfaces (e.g., application programming interfaces) enabling capability service 112 to transmit capability data to MFO 106 and / or CIOS region 110 (e.g., each instance of CIOS region 110). In some embodiments, any suitable component or module of MFO 106 and / or CIOS region 110 may be configured to request capability data from capability service 112.

[0064] In some embodiments, the Multi-Group Orchestrator (MFO) 106 may be configured to drive region building operations. In some embodiments, the MFO 106 may manage information describing which groups / group configuration versions and / or artifact versions will be used to bootstrap a given service within a region (or make changes to a unit of a target region). In some embodiments, the MFO 106 may be configured to monitor (or otherwise be notified) of changes to region data managed by the Real-Time Region Data Distributor 104. In some embodiments, receiving an indication that region data has been changed may cause a region building to be triggered by the MFO 106. In some embodiments, the MFO 106 may collect various group configurations and artifacts to be used for region building. Some or all of the group configurations may be configured to be region-agnostic. That is, the group configurations may not explicitly identify which region the group is to be bootstrap. In some embodiments, the MFO 106 may trigger a data injection process through which the collected group configurations are recompiled (e.g., by CIOS center 108). During recompilation, operations may be performed (e.g., by CIOS center 108) to inject region data maintained by the Real-Time Region Data Distributor 104 into the configuration file. Group configurations can reference region data via variables / parameters without requiring hard-coded identification of the region data. Using this data injection, group configurations can be dynamically modified at runtime, rather than having the region data hard-coded and therefore much harder to change.

[0065] The multi-group orchestrator 106 can perform static group analysis, where group configurations are parsed to identify dependencies between resources, execution goals, stages, and groups, particularly identifying circular dependencies that need to be removed. In some embodiments, the MFO 106 can generate any appropriate number of data structures based on the identified dependencies. These data structures (e.g., one or more directed acyclic graphs, linked lists, etc.) can be used by the cloud infrastructure orchestration service 102 to drive the operation of executing region building. For example, these data structures can collectively define the order in which services are bootstrapped within a region. The following is about... Figure 3 The build dependency graph 338 further discusses examples of such data structures. If circular dependencies exist (e.g., service A requires service B, and vice versa), and are identified through static group analysis and / or the graph, the MFO can be configured to notify any appropriate service team that changes to the corresponding group configurations are needed to correct these circular dependencies. MFO 106 can be configured to traverse one or more data structures to manage the order in which services are bootstrapped to regions. MFO 106 can identify capabilities available in a given region at any given time (e.g., using data obtained from capability service 112). MFO 106 can use this data to identify when CIOS region 110 can boots services, when booting is blocked, and / or when booting operations associated with previously blocked services can be resumed. Based on this traversal, MFO 106 can execute a wide variety of releases, where instructions are transmitted by MFO 106 to CIOS center 108 to execute booting operations corresponding to any appropriate number of group configurations. In some examples, MFO 106 can be configured to identify one or more group configurations that may require multiple releases due to circular dependencies found within the graph. Therefore, MFO 106 can send multiple instruction sets to CIOS center 108 for a given group configuration to break circular dependencies identified in the graph.

[0066] In some embodiments, a user may request the construction of a new region (e.g., target region 114). This may involve bootstrapping resources corresponding to a variety of services. In some embodiments, target region 114 may not be communicatively available (and / or secure) when the region construction request is initiated. CIOS 102 can use a Virtual Boot Environment 116 to initiate the region construction instead of delaying boot until target region 114 becomes available and is configured to perform boot operations. The Virtual Boot Environment (ViBE) 116 may be an overlay network hosted by host region 103 (a pre-existing region that has a set of core services previously configured and is communicatively available and secure). MFO 106 may utilize the resources of host region 103 to bootstrap resources into ViBE 116 (often referred to as "building the ViBE"). For example, MFO 106 may provide instructions via CIOS hub 108 to bootstrap an instance of CIOS region 110 within host region (e.g., host region 103) into an instance of another CIOS region within ViBE 116. Once the CIOS region within ViBE becomes available for processing, the services of bootstrapping target region 114 can continue within ViBE 116. When target region 114 becomes available to perform boot operations, previously booted services within ViBE 116 can be migrated to target region 114. Utilizing these techniques, CIOS 102 can significantly increase the speed of region construction by drastically reducing the need for any manual input and / or configuration.

[0067] Figure 2 The diagram illustrates a method for constructing a Virtual Boot Environment (ViBE) 202 according to at least one embodiment. Figure 1 A block diagram of environment 200 and methods (example of ViBE116). ViBE 202 represents an existing area (e.g., host area 204). Figure 1 Example of host region 103, and in one embodiment, a virtual cloud network provisioned within the coverage of a host region service enclave. ViBE 202 represents a virtual cloud network provisioned within a target region (e.g., a region built under, such as...). Figure 1 The environment for deploying services to the target area (114) can be phased out before the target area becomes available.

[0068] In order to guide the new area (e.g., Figure 1 In target zone 114, a set of core services can be bootstrapping. While those core service sets exist in host zone 204, they do not yet exist in the ViBE (nor in the target zone). These basic core services provide the functionality needed to provision equipment, establish trust chains to the new zone, and deploy remaining services (e.g., groups) to the zone. ViBE 202 can be a lease deployed in host zone 204. It can be considered a virtual zone.

[0069] When a target region becomes available to provide bootstrapping operations, ViBE 202 can connect to the target region, allowing services in ViBE to interact with services and / or infrastructure components in the target region. This enables the deployment of production-grade services, replacing self-contained seed services as in previous systems, and requires internet connectivity to the target region. Typically, seed services are deployed as part of a collection of containers and used to bootstrap the dependencies necessary to build the region. Using existing region infrastructure / tools, resources can be bootstrap (e.g., provisioned and deployed) into ViBE 202 and connected to service enclaves of regions (e.g., host region 204) to provision hardware and deploy services until the target region is self-sufficient and can communicate directly with it. Utilizing ViBE 202 allows the establishment of dependencies and services necessary to provision / prepare infrastructure and deploy software, while leveraging host region resources to break circular dependencies in core services.

[0070] Multi-Group Orchestrator (MFO) 206 can be configured to perform operations to build (e.g., configure) ViBE 202. MFO 206 can obtain applicable group configurations corresponding to the various resources to be bootstrapped to the new zone (in this case, the ViBE zone, ViBE 202). For example, MFO 206 can obtain group configurations (e.g., "ViBE Group Configuration") that identify aspects of Bootstrap Capability Service 208 and Worker 210. As another example, MFO 206 can obtain another group configuration corresponding to bootstrapping Domain Name Service (DNS) 212 to ViBE 202.

[0071] In step 1, MFO 206 may instruct CIOS center 214 (e.g., respectively) Figure 1 and 2 Examples of CIOS Center 108 and CIOS Center 214 (e.g., in the example). For instance, MFO 206 may transmit a request (e.g., including ViBE group configurations) to request booting capability services 208 and worker 210 that are not yet present in ViBE 202. In some embodiments, CIOS Center 214 may have access to all group configurations. Thus, in some examples, MFO 206 may transmit the identifier of the ViBE group configuration instead of the file itself, and CIOS Center 214 may independently access storage (e.g., from...). Figure 3 Obtain the identifier from DB 308 or group DB 312.

[0072] In step 2, CIOS center 214 can provide ViBE group configuration via a corresponding request to CIOS zone 216. In step 3, CIOS zone 216 can resolve the ViBE group configuration to identify and perform specific infrastructure provisioning and deployment operations.

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

[0074] In step 5, capabilities may be transmitted to capability service 208 (from CIOS region 216, deployment orchestrator 218 via worker 210, or otherwise) indicating the availability of resources corresponding to the ViBE group. Capability service 208 may maintain this data. In some embodiments, capability service 208 adds this information to its maintained list of available capabilities for the ViBE. For example, the capabilities provided to capability service 208 in step 5 may indicate that capability service 208 and worker 210 are available for processing.

[0075] In step 6, MFO 206 may identify the capabilities that indicate the availability of capability service 208 and worker 210 based on data received or obtained from capability service 208 (identifiers corresponding to capabilities).

[0076] In step 7, as a result of receiving / obtaining data in step 6, MFO 206 may instruct CIOS center 214 to route DNS services (e.g., DNS 212) to ViBE 202. The instructions may identify or include specific group configurations corresponding to the DNS services.

[0077] In step 8, CIOS center 214 may instruct CIOS zone 216 to deploy DNS 212 to ViBE 202. In some embodiments, the DNS group configuration of DNS 212 is provided by CIOS center 214.

[0078] In step 9, worker 210, now deployed in ViBE 202, can be assigned by CIOS zone 216 to the task deploying DNS 212. Worker 210 can be combined as described above. Figure 3 The described approach enables the declarative infrastructure provider to identify (e.g., from comparing the group configuration (desired state) with the current state of resources associated with the group (currently non-existent)) a set of operations that need to be performed to deploy DNS212.

[0079] In step 10, deployment orchestrator 218 instructs worker 210 to deploy DNS 212 according to the operation identified in step 9. As shown, in step 11, worker 210 continues to perform the operation to deploy DNS 212 to ViBE 202. In step 12, worker 210 notifies capability service 208 that DNS 212 is available in ViBE 202. MFO 206 can then identify the resources available associated with the ViBE group configuration and DNS group configuration, and can continue to bootstrap any appropriate number of additional resources to ViBE.

[0080] After steps 1-12 are completed, the process of building ViBE 202 can be considered complete, and ViBE 202 can be considered built.

[0081] Figure 3 This is a block diagram illustrating an environment 300 and method for directing services to a target area using ViBE according to at least one embodiment.

[0082] In step 1, user 302 can utilize CIOS center 304 (respectively...) Figure 1 and 2Examples of CIOS Centers 108 and 214 (provided in the CIOS Centers) can use any suitable user interface to modify zone data. For example, user 302 can create a new zone to which multiple services will be routed.

[0083] In step 2, CIOS center 304 can perform operations to send changes to RRDD 306 (e.g., Figure 1 (Example of RRDD104). In step 3, RRDD 306 may store the received region data in DB 308, which is configured to store region data including any suitable identifier, attribute, status, etc., such as region, AD, domain, ET, or the like. In some embodiments, updater 307 may be used to store region data in DB 308 or in any suitable data storage where such updates are accessible (e.g., to the service team). In some embodiments, updater 307 may be configured to notify (e.g., via any suitable electronic notification) of updates made to DB 308.

[0084] In step 4, the multi-group orchestrator (MFO) 310 (which are respectively) Figure 1 and 2 Examples of MFOs 106 and 206 in the examples can detect changes in area data. In some embodiments, MFO 310 can be configured to poll RRDD 306 for changes in area data. In some embodiments, RRDD 306 can be configured to publish or otherwise notify MFO 310 of area changes.

[0085] In step 5, detecting changes to the region data can trigger MFO 310 to obtain a version set (e.g., a version set associated with a specific identifier, such as a "gold version set" identifier). A specific version for each group (e.g., a service) to be routed to the new region, and a specific version for each artifact corresponding to that group, are identified. The version set can be obtained from group DB 312. As groups evolve and change, the versions of their corresponding configurations and artifacts used for region building may change. These changes can be maintained in group DB 312, allowing MFO 310 to identify which versions of group configurations and artifacts to use for region building (e.g., ViBE region, target region / non-ViBE region, etc.). Group configurations (e.g., group configurations for all versions) and / or artifacts (e.g., artifacts for all versions) can be stored in DB 308, group DB 312, or CIOS center 304 and / or any suitable data storage accessible to MFO 310.

[0086] In step 6, MFO 310 may request CIOS center 304 to recompile each of the group configurations associated with the version set having the current region data. In some embodiments, the request may specify the version of each group configuration and / or the artifact corresponding to those group configurations.

[0087] In step 7, CIOS center 304 can obtain current area data from DB 308 (e.g., directly or via real-time area data distributor 306) and retrieve any appropriate group configurations and artifacts according to the version requested by MFO 310.

[0088] In step 8, CIOS center 304 can recompile the group configuration using the area data obtained in step 7 to inject the current area data into the group configuration. CIOS center 304 can return the compiled group configuration to MFO 310. In some embodiments, CIOS center 304 can simply indicate that compilation is complete, and MFO 310 can access the recompiled group configuration via RRDD 306.

[0089] In step 9, MFO 310 may perform static analysis on the recompiled group configuration. As part of the static analysis, MFO 310 may resolve the group configuration (e.g., using libraries associated with a declarative infrastructure provider (e.g., Terraform or similar)) to identify dependencies between groups. MFO 310 may generate a build dependency graph 338 from the analysis and the identified dependencies. The build dependency graph 338 may be an acyclic directed graph that identifies the order in which groups are bootstrapping (and / or where changes indicated in the group configuration are applied) to new regions. Each node in the graph may correspond to any appropriate portion of bootstrapping a particular group. A particular bootstrapping order may be identified at least in part based on dependencies. In some embodiments, dependencies may be expressed as attributes of nodes and / or indicated via edges of the graph connecting the nodes. MFO 310 may traverse the graph (e.g., starting at the starting node) to drive the region building operations.

[0090] In some embodiments, MFO 310 may utilize a cycle detection algorithm to detect the existence of cycles (e.g., service A depends on service B, or vice versa). MFO 310 may identify orphaned capability dependencies. For example, MFO 310 may identify orphaned nodes in the build dependency graph 338 that are not connected to any other nodes. MFO 310 may identify erroneously published capabilities (e.g., when a capability is published prematurely and the corresponding functionality is not actually available). MFO 310 may detect from the graph the existence of one or more instances of the same capability being published. In some embodiments, any appropriate number of these errors may be detected and MFO 310 (or another appropriate component, such as CIOS center 304) may be configured to notify or otherwise present this information to the user (e.g., via electronic notification, user interface, or the like). In some embodiments, MFO 310 may be configured to force the deletion / recreation of resources to break circular dependencies and may again provide instructions to CIOS center 304 to perform bootstrapping operations on those resources and / or their corresponding group configurations.

[0091] The starting node may correspond to the bootstrapping ViBE group, and the second node may correspond to the bootstrapping DNS. Steps 10-15 correspond to deploying the ViBE group (via deployment orchestrator 317). Figure 2 Examples of deployment orchestrator 218) to ViBE 316 (e.g., respectively) Figure 1 and 2 (Examples of ViBE 116 and 202). That is to say, Figure 3 Steps 10-15 typically correspond to Figure 2 Steps 1-6. Once notified that the capability corresponding to the ViBE group being deployed exists (e.g., indicating that...), Figure 2 (If capability service 208 and worker 210 are available, corresponding to capability service 318 and worker 320), then MFO 310 restarts the traversal of the build dependency graph 338 to identify the next operation to be performed.

[0092] For example, MFO 310 can continue traversing the build dependency graph 338 to identify the DNS groups to be deployed. Steps 16-21 can be performed to deploy DNS 322 ( Figure 2 (Example of DNS212). These operations can typically correspond to... Figure 2 Steps 7-12.

[0093] In step 21, the capability indicating the availability of DNS 322 can be stored. Upon detecting this capability, MFO 310 can restart the traversal of the build dependency graph 338. During this traversal, MFO 310 can identify any appropriate portion of the CIOS zone instance (e.g., an example of CIOS zone 314) to be deployed to ViBE 316. In some embodiments, steps 16-21 can relate to deploying CIOS zone (ViBE) 326 ( Figure 1 The instances of CIOS region 314 and CIOS region 110, and worker 328 are deployed to ViBE 316, which is essentially the same. The capabilities available in CIOS region (ViBE) 326 can be sent to capability service 318.

[0094] Upon detecting that CIOS region (ViBE) 326 is available, MFO 310 may restart the traversal of build dependency graph 338. During this traversal, MFO 310 may identify deployment orchestrators (e.g., deployment orchestrator 330, examples of deployment orchestrator 317) to be deployed to ViBE 316. In some embodiments, steps 16-21 may be substantially repeated with respect to deploying deployment orchestrator 330. Information identifying capabilities may be transmitted to capability service 318, indicating that deployment orchestrator 330 is available.

[0095] After deployment orchestrator 330 is deployed, ViBE 316 can be considered available to handle subsequent requests. Upon detecting the availability of deployment orchestrator 330, MFO 310 can instruct subsequent bootstrap requests to be routed to ViBE components instead of utilizing host zone components (components of host zone 332). Therefore, MFO 310 can continue traversing the build dependency graph 338, directing group deployments to ViBE 316 at each node via CIOS center 304. CIOS center 304 can then request CIOS zone (ViBE) 326 to deploy resources according to the group configuration.

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

[0097] Before establishing an IPSec tunnel, the initial network connection to target area 334 can reside on a connection sufficient to allow bootstrapping of networking services (e.g., an out-of-band VPN tunnel) until the IPSec gateway can be deployed on an asset (e.g., a bare metal asset) within target area 334. To bootstrap network resources in target area 334, deployment orchestrator 330 can deploy the IPSec gateway on the asset within target area 334. Deployment orchestrator 330 can then deploy a VPN host in target area 334, configured to terminate the IPSec tunnel from ViBE 316. Once services in ViBE 316 (e.g., deployment orchestrator 330, service A, etc.) can establish an IPSec connection with the VPN host in target area 334, bootstrapping operations from ViBE 316 to target area 334 can begin.

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

[0099] After the hardware allocation in target region 334 is established and published to capability service 318, CIOS region (ViBE) 326 can orchestrate the deployment of core service instances from ViBE 316 to target region 334. This deployment may be similar to the process described above for building ViBE 316, but uses ViBE components (e.g., CIOS region (ViBE) 326, worker 328, deployment orchestrator 330) instead of the components of the service enclave in host region 332. The deployment operation can typically correspond to steps 16-21 above.

[0100] When a service is deployed from ViBE 316 to target zone 334, the DNS records associated with that service may correspond to the service instance in ViBE 316. The DNS records associated with the service may be updated at a later time to complete the deployment of the service to target zone 334. In other words, the service instance in ViBE 316 may continue to receive traffic (e.g., requests) for the service until the DNS records are updated. The service may be partially deployed to target zone 334 and may advertise information indicating the partial deployment of the service (e.g., to capability service 318). For example, a service running in ViBE 316 may be deployed to target zone 334 through its corresponding compute instance, load balancer, and associated applications and other software, but may need to wait for database data migration to target zone 334 before being fully deployed. DNS records (e.g., those managed by DNS 322) may still be associated with the service in ViBE 316. Once the service's data migration is complete, the DNS records may be updated to point to the operational service deployed in target zone 334. Then, the deployed services in target area 334 may receive service traffic (e.g., requests), while service instances in ViBE 316 may no longer receive service traffic.

[0101] Migrate services from ViBE to the target region

[0102] As discussed above, CSPs can build or deploy data centers to deliver cloud services to their customers in new regions. These regions may correspond to general geographic areas, which are preferably located near new customers or customers with expanding service needs (e.g., customer growth requiring vertical scaling of cloud services, expansion of cloud services to new geographic areas, etc.). To support the construction of new regions, CIOS (e.g., Figure 1 CIOS102 in the above can be used to generate ViBE (e.g., in an assigned host region (e.g., one or more data centers within the host region)). Figure 3 ViBE 316 (in the text).

[0103] A ViBE can be created before or concurrently with the construction of a data center in a new region. For example, since the construction and provisioning of physical components (e.g., bare metal servers, racks, networking switches, etc.) can take several months, a ViBE can be built before the new data center is completed (e.g., days, weeks, etc.). Once the physical infrastructure of the new data center is ready to host cloud services, operators can deploy core services to the ViBE to support service deployment to the new data center. By creating a ViBE before (or concurrently with) the construction of a regional data center, the core services deployed therein can be evaluated for deployment readiness (e.g., production testing, dependency resolution, etc.).

[0104] Provisioning infrastructure and deploying services from ViBE to a target region can include a “horizontal scaling” process, through which instances of ViBE core services (e.g., CIOS region (ViBE) 326, deployment orchestrator 330, etc.) are deployed to the target region. During horizontal scaling, core services are deployed to the target region in a manner similar to how services are deployed to ViBE.

[0105] When services operate in ViBE, they may create new resources (e.g., new data, new artifacts). Because these resources are created independently of service deployment using CIOS, CIOS may not be aware of these new resources when deploying services to the target region (e.g., the group configuration used for deployment to the target region may not have information about resources created by the service in ViBE). To complete the scale-out process, it may be necessary to discover ViBE resources and migrate them to the target region. Services deployed in the target region before the resources are located there may not be able to respond to requests for service. To prevent traffic from being sent to services in the target region before the service's data and other resources are fully migrated, the target service's DNS records may not be updated during the initial scale-out to the target region. CIOS may later recognize the target region service's DNS records as resources and update them in the DNS (e.g., ViBE DNS, target region DNS). Once the DNS records are updated to point to the service in the target region, the service migration and scale-out process is complete.

[0106] Figure 4 This is a block diagram of an environment in which a Cloud Infrastructure Orchestration Service (CIOS) according to at least one embodiment can utilize a resource discoverer to discover resources during region building. Environment 400 may be... Figure 1 Example of environment 100. Cloud Infrastructure Orchestration Service (CIOS) 402 can be... Figure 1 An example of CIOS102. The Real-Time Area Data Distributor (RRDD) 404 can be respectively... Figure 1and 3 Examples of real-time area data distributors 104 and / or 306. The multi-group orchestrator (MFO) 406 can be respectively... Figure 1-3 Examples of multi-group orchestrators 106, 206, and / or 310. CIOS center 408 can be respectively... Figure 1-3 Examples of CIOS centers 108, 214, and / or 304. CIOS region 410 can be respectively Figure 1-3 Examples of CIOS regions 110, 216, and / or 314. Capability service 412 can be respectively Figure 1-3 Examples of capability services 112, 208, and / or 318. Target region 414 can be respectively... Figure 1 and 3 Examples of target regions 114 and / or 334. Virtual boot environment 416 can be respectively... Figure 1-3 Examples of virtual boot environments 116, 202, and / or 316. The components of CIOS 402 (including RRDD 404, MFO 406, CIOS Center 408, CIOS Zone 410, and Capability Service 412) are each executable as described above. Figure 1-3 Chinese combination Figure 1-3 The corresponding functions discussed for the corresponding components.

[0107] Environment 400 may include a Resource Finder Service (RHS) 420. RHS 420 can be configured to attempt resource discovery at any appropriate time. For example, any appropriate number of resources may exist in any appropriate zone before the zone is built in this or another zone. For example, resources(one or more) 422 may include resources existing in host zone 403 (which are respectively...) Figure 1-3 The resources (e.g., infrastructure resources, artifacts, configuration files, etc.) in host zones 103, 204, and / or 332 (examples) may be any appropriate number of resources. One or more resources 424 may exist in ViBE 416 and / or one or more resources 426 may exist in the target zone. Any appropriate combination of one or more resources 422-426 may be created at any appropriate time before, during, or after the zone building process is performed to bootstrap any appropriate number of services within ViBE 416 and / or target zone 414.

[0108] RHS 420 can be configured to receive group configuration information from MFO 406 (and / or any appropriate component of CIOS 402 and / or any services booted within host zone 403, ViBE 416, and / or target zone 414). In some embodiments, MFO 406 may provide a group identifier, and RHS 420 may be configured to access a corresponding group profile associated with that group. Alternatively, MFO 406 may provide group configuration to RHS 420. The following is in conjunction with... Figure 5 The example group configuration will be discussed in more detail.

[0109] RHS 420 can identify resource discovery data within a group configuration. "Resource discovery data" refers to any appropriate data (e.g., a set of parameters) used to identify previously existing resources (e.g., one or more resources 422-426). RHS 420 can perform operations to identify any appropriate number of resources 422-426 using the parameter set of the resource discovery data. For example, RHS 420 can search (e.g., within a region specified by the resource discovery data) for specific resources associated with attributes matching the parameter set provided in the resource discovery data. If one or more matching resources are found, RHS 420 can directly provide MFO 406 with identifiers of the matching resources, and / or RHS 420 can store the identifiers in a record accessible to MFO 406.

[0110] MFO 406 may include a state manager 428. State manager 428 may be configured to implement a state machine that transitions between states to drive delivery. For example, a single group may require multiple publications (e.g., multiple instruction transfers to CIOS hub 408, multiple publications corresponding to one or more group configurations associated with a single service, etc.). State manager 428 may be configured to coordinate operations performed for a single publication. This may include monitoring messages from CIOS hub 408 and / or resource finder service 420. In some embodiments, state manager 428 may be configured to monitor one or more capabilities delivered by capability service 412.

[0111] Figure 5 This is a block diagram depicting an example flow of operations according to at least one embodiment for performing services provisioning and deployment to a data center in a new region and importing resources before updating the DNS records of the deployed services.

[0112] The article about Figure 5 The described operation can be considered as the above regarding Figure 3 An extension of the described method. For example, similar to a service (e.g., deploying orchestrator 530, Figure 3 How is the deployment orchestrator 330 (example) deployed to ViBE, MFO510 ( Figure 3 The example of MFO 310 can deploy a service (e.g., service A 502) to target region 534 by instructing CIOS center 504 to direct the service to the target region. Furthermore, this document regarding... Figure 5 One or more of the operations described may be similar to those described above. Figure 4 The described operation. For example, environment 500 may include operations that are similar to... Figure 4 The Resource Finder Service (RHS) 420 511.

[0113] about Figure 5 The described operations (and any other methods or processes described herein) can be implemented in hardware, computer instructions, or a combination thereof. In the context of computer instructions, an operation refers to a computer-executable instruction stored on one or more computer-readable storage media that, when executed by one or more processors, performs the listed operation. Typically, computer-executable instructions include routines, programs, objects, components, data structures, etc., that perform a particular function or implement a particular data type. The order in which the operations are described should not be intended to be construed as limiting, and any number of the described operations may be omitted or combined in any order and / or in parallel to implement the process.

[0114] Service migration within a Virtual Bootstrap Environment (ViBE) may be referred to herein as a “scale-out” process and may include operations typically referred to as “migration” within the context of a distributed computing environment (e.g., migrating a database, migrating application data, etc.). Environment 500 may include host zone 532 in which ViBE 516 has been implemented. Environment 500 may also include target zone 534 in which services hosted in ViBE 516 can be scaled out. Host zone 532 and target zone 534 may be respectively Figure 3 Examples of host region 332 and target region 334 in the example.

[0115] Before the horizontal scaling process begins from ViBE 516, a network connection can be established between ViBE 516 in host region 532 and target region 534. The network connection may include one or more tunnels 536. Figure 3 (Example of tunnel 336 in the example). Tunnel 536 can be an encrypted tunnel (e.g., an IPSec tunnel). Network connectivity can form one or more Virtual Private Network (VPN) connections between the network hosting ViBE 516 (e.g., the Virtual Cloud Network (VCN) of host zone 532) and the service enclave of target zone 534 (e.g., the VCN of target zone 534).

[0116] Steps 1-8 can be performed to deploy service A 502 to target region 534. The operations in steps 1, 2, 3, and 8 typically correspond to... Figure 2 Steps 7, 8, 9, and 12. Steps 4-5 involve operations related to supplying infrastructure resources at target area 534, while steps 6-8 can be similar. Figure 2 The iterations of steps 10 and 11 are used to deploy the service to target region 534.

[0117] The steps described below include infrastructure provisioning (e.g., steps 4-5) as part of a method for provisioning infrastructure resources using CIOS, and as an initial part of deploying services (e.g., services configured according to groups using declarative provisioning tools). In some embodiments, provisioning infrastructure resources (e.g., infrastructure resource 503) may be performed as a separate operation under the guidance of CIOS center 504 and MFO 510. For example, before deployment orchestration services (e.g., deployment orchestrator 530) are fully deployed in ViBE 516 to support the deployment of services to target area 534, host provisioning services (e.g., host provisioning service 506) may be deployed to ViBE 516 and be able to provision infrastructure resources in target area 534. In this case, based on the capabilities provided to capability service 518, MFO 510 may use host provisioning service 506 to begin provisioning infrastructure resources in target area 534 without the deployment of accompanying services.

[0118] In step 1, MFO 510 may instruct CIOS center 504 to deploy service A 502 to target region 534. Service A 502 may require infrastructure resources 503 to be provisioned in target region 534. For example, service A 502 may be executed via one or more compute instances running on one or more VMs in the target region. The instructions to deploy service A 502 may identify or include resources (e.g., infrastructure resources 503) to be provisioned in target region 534. Provisioning resources may include configuring one or more hosts (e.g., one or more virtual machines (VMs)) in the compute environment of target region 534. The instructions to deploy service A 502 may also identify or include group configurations corresponding to service A 502.

[0119] Service A 502 may be an instance of Service A 509 deployed in ViBE 516. Since ViBE 516 and Target Zone 534 can be connected via tunnel 536 to form a distributed virtual private network (VPN) between service enclaves in ViBE 516 and Target Zone 534, the deployment of Service A 502 may result in duplicate service stacks available within the distributed VPN. To avoid conflicts and ensure that traffic is handled by only one instance of the service, the service's DNS records (e.g., DNS managed by DNS 522) may initially point to Service A 509 in ViBE. These DNS records may be created as part of the deployment of Service A 509 to ViBE (e.g., using MFO 510 and CIOS center 504). When Service A 502 is deployed to Target Zone 534, the DNS records associated with Service A may not be updated.

[0120] In step 2, CIOS center 504 may instruct CIOS region (ViBE) 526 to provision infrastructure resources 503 and deploy service A 502 to target region 534. In some embodiments, the group configuration of service A 502 is provided by CIOS center 504.

[0121] In step 3, worker 528 may be assigned by CIOS region (ViBE) 526 to provision infrastructure resources 503 and deploy service A 502. Worker 528 may perform declarative provisioning to identify (e.g., by comparing group configuration with the current state of resources associated with the group) a set of operations that need to be performed to deploy service A 502.

[0122] In step 4, worker 528 may instruct host provisioning service 506 to provision infrastructure resources 503 in target area 534 according to the operations identified in step 3. Host provisioning service 506 may perform these operations in step 5. In steps 6 and 7, worker 528 may instruct compute control plane 508 and deployment orchestrator 530 to launch instances and deploy service A 502 to the launched instances, respectively. Compute control plane 508 and deployment orchestrator 530 may perform the instructed launch and deployment tasks in step 8.

[0123] In step 9, worker 528 may publish one or more capabilities available to service A 502 to capability service 518. This capability may indicate that the service has been "partially" deployed. For example, the capability could be a value like "servicea_partial_scaleout". As described above, service A 502 may be successfully deployed to infrastructure resource 503 in target region 534, but may lack the resources necessary to handle service traffic (e.g., service data, data resources, etc.). For example, service A 509 in ViBE 516 may create, update, store, or otherwise produce and / or manipulate data in ViBE 516. This data may include resource 540. In some embodiments, service A 509 may use services in the service enclave of host region 532 (e.g., data storage service 544) to maintain data associated with the operation of service A 509. This data may include service data 546. The data for resource 540 and service data 546 may be generated by service A 509 after deployment to ViBE 516. Because the data is generated after deployment, MFO 510 and other CIOS components (e.g., CIOS Center 504, CIOS Region (ViBE) 526, etc.) may not be aware that the resource is part of a configuration (e.g., group configuration) used to deploy an instance of service A502 to the target region.

[0124] MFO 510 can acquire some of the published horizontal scaling capabilities. In step 10, MFO 510 can provide RHS 511 with an identifier for service A 502 indicating partial horizontal scaling (e.g., an identifier for the group corresponding to service A 502). RHS 511 can identify resource discovery data within the group configuration corresponding to service A 502 and use the resource discovery data to identify resources (e.g., resource 540). RHS 511 can provide MFO 510 with resources (or resource identifiers).

[0125] In step 11, MFO 510 may use resources (or resource identifiers) provided by RHS 511 to configure another delivery for deploying the group corresponding to service A 502 (e.g., another delivery for deploying and / or updating service A 502). The second delivery may include operations similar to steps 1-3 to instruct a worker (e.g., worker 528) to perform operations with one or more services in ViBE 516 to deploy an update to service A 502. The update may include updating services in ViBE (e.g., DNS 522) or services in target zone 534 (e.g., horizontally scaling DNS in target zone 534).

[0126] For the example where the resource is a DNS record, in step 12, CIOS center 504 may instruct CIOS zone (ViBE) 526 to deploy service A 502 based on the group configuration updated using the discovered DNS record.

[0127] In step 13, worker 528 may be assigned the task of updating DNS records by CIOS zone (ViBE) 526. Worker 528 may perform a declarative provider to identify (e.g., by comparing the group configuration with the current state of the resources associated with the group) a set of operations that need to be performed to deploy service A 502. Since the updated DNS record may be the only difference between the current state of the deployed group corresponding to service A 502, the declarative provider may generate instructions to update only the DNS record (rather than redeploying all resources of service A 502). Worker 528 may use the new DNS record to update DNS 522. The DNS record update may cause DNS 522 to identify service A 502 as the destination of service A traffic within the VPN between ViBE 516 and target zone 534.

[0128] In some embodiments, the resource identified by RHS 511 may include data created by service A 509 (e.g., resource 540). MFO 510, CIOS center 504, and CIOS region (ViBE) 526 may perform operations similar to steps 1-3 and 11-13 to deploy resource 540 from ViBE 516 to target region 534. In this way, resource 542, which may include data from resource 540, may be provided to service A 502.

[0129] Resources can be migrated to target zone 534 before the CIOS pass for updating DNS records is performed. Resources located in host zone 532 but outside of ViBE 516 that are associated with services in ViBE 516 (e.g., resources in a service enclave in host zone 532) can be migrated to target zone 534 as part of a database migration process or other data transfer process that operates independently of the CIOS operation. Figure 5 (This is indicated as step 15). In some examples, the resources migrated to target area 534 may include secrets (e.g., credentials, passwords, keys, tokens, etc.) used for authentication and / or authorization. To improve security, the secrets migrated to target area 534 can be re-encrypted using a new master key associated with target area 534. The migrated secrets can then be rotated (e.g., changed) within target area 534 to prevent any secrets held in host area 532 from becoming available in target area 534.

[0130] It should be understood that the above description of the operation of horizontally extending service A 502 to target zone 534 also applies to any service hosted in ViBE 516. Services hosted in ViBE 516 are deployed to target zone 534 using CIOS, and resources associated with those initially deployed services not deployed by CIOS are discovered by RHS (e.g., RHS 511), and service traffic is switched from being routed to the service in ViBE to being routed to the service in the target zone by updating the corresponding DNS records. This may occur after all necessary resources for the service have been migrated from ViBE, the service enclave in host zone 532, and / or other locations.

[0131] Figure 6 An example method 600 for migrating services from a ViBE to a target region, according to at least one embodiment, is illustrated. Method 600 may be comprised of one or more components of a distributed computing system (e.g., a cloud computing system), including... Figure 1 The cloud infrastructure orchestration service 102 is executed by one or more components. The computer-readable storage medium may include computer-readable instructions that, when executed by one or more processors of the distributed computing system, cause the distributed computing system to perform method 600. The operations of method 600 may be performed in any suitable order, and method 600 may include... Figure 6 The more or fewer operations described in the text.

[0132] Some or all of method 600 (or any other process and / or method described herein, or variations and / or combinations thereof) may 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) that executes jointly on one or more processors, by hardware, or by a combination thereof. The code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors. The computer-readable storage medium may be non-transitory.

[0133] Method 600 can begin at box 602, where a Virtual Cloud Network (VCN) can be generated in the data center of the host zone. The VCN can be a Virtual Boot Environment (ViBE) VCN.

[0134] At box 604, a virtual boot environment (ViBE) can be implemented in the VCN (e.g., Figure 5 ViBE 516 (as described above). ViBE can be configured to deploy one or more services in stages to a target region. ViBE can host multiple services (e.g., ...). Figure 5 Service A 509).

[0135] At box 606, an instance of one of several services in ViBE can be deployed to a target region data center (e.g., Figure 5 The target area is data center 534. The deployment of the first service can be via CIOS (e.g., Figure 1 CIOS102's multi-group orchestrator (MFO) (e.g., Figure 1 The MFO (MFO 106) can utilize one or more services in the ViBE (e.g., CIOS Region (ViBE) 526, Deployment Orchestrator 530, etc.) to deploy instances of services to the target region data center.

[0136] At box 608, an indication that the service has been successfully deployed can be received from the deployed instance. This indication can be published to the capability service (e.g., Figure 5 The capabilities of service 518). In some embodiments, the capabilities may indicate that an instance of the service has been successfully partially deployed.

[0137] At box 610, resources associated with the service can be identified. Resource search services (e.g., Figure 5 The RHS 511 can identify resources. In some embodiments, the resource may be a DNS record of an instance in the target region data center.

[0138] At box 612, resources can be used to update a second service among multiple services. In some embodiments, the second service is ViBE's DNS. In some embodiments, resources can be used to update services deployed to a target region.

[0139] Example architecture for providing Infrastructure as a Service (IaaS)

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

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

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

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

[0144] In some examples, IaaS provisioning can refer to acquiring a computer or virtual host for use, and even installing the necessary libraries or services on it. In most cases, deployment does not include provisioning, and provisioning may need to be performed first.

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

[0146] In some examples, the infrastructure may have many interconnecting elements. For example, there may be one or more Virtual Private Clouds (VPCs) (e.g., potential on-demand pools of configurable and / or shared computing resources), also known as the core network. In some examples, there may also be one or more inbound / outbound traffic group rules, provisioned to define how inbound / outbound traffic to the network will be established, and one or more virtual machines (VMs). Other infrastructure elements, such as load balancers, databases, or the like, may also be provisioned. As more infrastructure elements are expected and / or added, the infrastructure may evolve gradually.

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

[0148] Figure 7 This is a block diagram 700 illustrating an example pattern of an IaaS architecture according to at least one embodiment. Service provider 702 may be communicatively coupled to a secure host lease 704, which may include a virtual cloud network (VCN) 706 and a secure host subnet 708. In some examples, service provider 702 may use one or more client computing devices, which may be portable handheld devices (e.g., Cellular phone Computing tablets, personal digital assistants (PDAs), or wearable devices (e.g., Google) Head-mounted display), running software (such as Microsoft Windows) ) and / or a variety of mobile operating systems (such as iOS, Windows Phone, Android, BlackBerry 8, Palm OS, etc.), and enabling internet, email, and SMS services. Or other communication protocols. Alternatively, the client computing device can be a general-purpose personal computer, including, for example, computers running various versions of Microsoft... Apple Personal computers and / or laptops running Linux operating systems. Client computing devices can be any of a wide variety of commercial operating systems. Or a workstation computer operating a UNIX-like operating system, including but not limited to various GNU / Linux operating systems, such as Google Chrome OS. Alternatively or additionally, the client computing device can be any other electronic device capable of communicating via a network that can access the VCN 706 and / or the Internet, such as a thin client computer, an Internet-enabled gaming system (e.g., with or without a VCN 706 and / or the Internet). The Microsoft Xbox game console with gesture input devices, and / or personal messaging devices.

[0149] VCN 706 may include a local peering gateway (LPG) 710, which may be communicatively coupled to a Secure Shell (SSH) VCN 712 via an LPG 710 included in an SSH VCN 712. SSH VCN 712 may include an SSH subnet 714, and SSH VCN 712 may be communicatively coupled to a control plane VCN 716 via an LPG 710 included in a control plane VCN 716. Furthermore, SSH VCN 712 may be communicatively coupled to a data plane VCN 718 via an LPG 710. Control plane VCN 716 and data plane VCN 718 may be included in a service lease 719 that may be owned and / or operated by an IaaS provider.

[0150] The control plane VCN 716 may include a control plane isolation zone (DMZ) layer 720, which acts as a portion of the perimeter network (e.g., a corporate network between an intranet and an external network). DMZ-based servers may have limited liability and help keep violations contained. Additionally, the control plane DMZ layer 720 may include one or more load balancer (LB) subnets 722, a control plane application layer 724 that may include one or more application subnets 726, and a control plane data layer 728 that may include one or more database (DB) subnets 730 (e.g., one or more front-end DB subnets and / or one or more back-end DB subnets). One or more LB subnets 722 contained in the control plane DMZ layer 720 can be communicatively coupled to one or more application subnets 726 contained in the control plane application layer 724 and an Internet gateway 734 that can be contained in the control plane VCN 716. The application subnets 726 can be communicatively coupled to one or more DB subnets 730 and a service gateway 736 and a Network Address Translation (NAT) gateway 738 contained in the control plane data layer 728. The control plane VCN 716 may include a service gateway 736 and a NAT gateway 738.

[0151] The control plane VCN 716 may include a data plane mirror application layer 740, which may include one or more application subnets 726. The one or more application subnets 726 included in the data plane mirror application layer 740 may include a Virtual Network Interface Controller (VNIC) 742, which can execute a compute instance 744. The compute instance 744 may communicatively couple the one or more application subnets 726 of the data plane mirror application layer 740 to the one or more application subnets 726 that may be included in the data plane application layer 746.

[0152] Data plane VCN 718 may include data plane application layer 746, data plane DMZ layer 748, and data plane data layer 750. Data plane DMZ layer 748 may include one or more application subnets 726 communicatively coupled to data plane application layer 746 and one or more LB subnets 722 of Internet gateway 734 of data plane VCN 718. One or more application subnets 726 may be communicatively coupled to service gateway 736 and NAT gateway 738 of data plane VCN 718. Data plane data layer 750 may also include one or more DB subnets 730 communicatively coupled to one or more application subnets 726 of data plane application layer 746.

[0153] The Internet gateway 734 of the control plane VCN 716 and data plane VCN 718 can be communicatively coupled to the metadata management service 752, which in turn can be communicatively coupled to the public Internet 754. The public Internet 754 can be communicatively coupled to the NAT gateway 738 of the control plane VCN 716 and data plane VCN 718. The service gateway 736 of the control plane VCN 716 and data plane VCN 718 can be communicatively coupled to the cloud service 756.

[0154] In some examples, the service gateway 736 of the control plane VCN 716 or the data plane VCN 718 can make application programming interface (API) calls to the cloud service 756 without traversing the public internet 754. API calls from the service gateway 736 to the cloud service 756 can be unidirectional: the service gateway 736 can make API calls to the cloud service 756, and the cloud service 756 can send requested data to the service gateway 736. However, the cloud service 756 may not initiate API calls to the service gateway 736.

[0155] In some examples, secure host lease 704 can connect directly to service lease 719; in other cases, service lease 719 is isolated. Secure host subnet 708 can communicate with SSH subnet 714 via LPG 710, which can enable bidirectional communication through systems that are otherwise isolated. Connecting secure host subnet 708 to SSH subnet 714 grants secure host subnet 708 access to other entities within service lease 719.

[0156] Control plane VCN 716 allows users of service lease 719 to establish or otherwise provision desired resources. Desired resources provisioned in control plane VCN 716 can be deployed or otherwise used in data plane VCN 718. In some examples, control plane VCN 716 can be isolated from data plane VCN 718, and the data plane mirror application layer 740 of control plane VCN 716 can communicate with the data plane application layer 746 of data plane VCN 718 via a VNIC 742 that can be included in both the data plane mirror application layer 740 and the data plane application layer 746.

[0157] In some examples, users or clients of the system can make requests, such as create, read, update, or delete (CRUD) operations, via the public internet 754, which can then relay the request to the metadata management service 752. The metadata management service 752 can relay the request to the control plane VCN 716 via an internet gateway 734. The request can be received by one or more LB subnets 722 contained in the control plane DMZ layer 720. The LB subnets 722 can determine that the request is valid, and in response to this determination, they can forward the request to one or more application subnets 726 contained in the control plane application layer 724. If the request is validated and requires a call to the public internet 754, the call to the public internet 754 can be relayed to a NAT gateway 738 that can make the call to the public internet 754. Storage that may be expected to be stored via the request can be stored in one or more DB subnets 730.

[0158] In some examples, the data plane mirroring application layer 740 can facilitate direct communication between the control plane VCN 716 and the data plane VCN 718. For example, it might be desirable to apply configuration changes, updates, or other appropriate modifications to resources contained in the data plane VCN 718. Through VNIC 742, the control plane VCN 716 can communicate directly with the resources contained in the data plane VCN 718, thereby enabling the execution of configuration changes, updates, or other appropriate modifications to the resources contained in the data plane VCN 718.

[0159] In some embodiments, the control plane VCN 716 and data plane VCN 718 may be included in a service lease 719. In this case, the system's users or customers may not own or operate the control plane 716 or data plane VCN 718. Instead, the IaaS provider may own or operate both the control plane VCN 716 and data plane VCN 718, both of which may be included in the service lease 719. This embodiment enables network isolation that prevents users or customers from interacting with the resources of other users or customers. Furthermore, this embodiment allows the system's users or customers to privately store databases without relying on the public internet 754, which may not have the desired level of threat prevention.

[0160] In other embodiments, one or more LB subnets 722 included in the control plane VCN 716 may be configured to receive signals from the service gateway 736. In this embodiment, the control plane VCN 716 and the data plane VCN 718 may be configured to be invoked by the IaaS provider's customers without invoking the public internet 754. The IaaS provider's customers may expect this embodiment because the database(s) used by the customer can be controlled by the IaaS provider and can be stored on a service lease 719 that can be isolated from the public internet 754.

[0161] Figure 8 This is a block diagram 800 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 802 (e.g., Figure 7 The service provider (702) can communicatively couple to the secure host lease (804) (e.g., Figure 7 Secure hosting rental (704), which may include Virtual Cloud Network (VCN) (e.g., Figure 7 VCN 706) and Secure Host Subnet 808 (e.g., Figure 7 The secure host subnet 708). VCN 806 may include a local peering gateway (LPG) 810 (e.g., Figure 7The LPG 710), which can be communicatively coupled to the Secure Shell (SSH) VCN 812 (e.g., via the LPG 810 included in the SSH VCN 812) Figure 7 SSH VCN 712). SSH VCN 812 can include SSH subnet 814 (e.g., Figure 7 SSH subnet 714), and SSH VCN 812 can be communicatively coupled to control plane VCN 816 via LPG 810 included in control plane VCN 816 (e.g., Figure 7 Control plane VCN 716). Control plane VCN 816 may be included in service lease 819 (e.g., Figure 7 In the service lease 719), and the data plane VCN 818 (e.g., Figure 7 The data plane VCN 718 can be included in a customer lease 821 that can be owned or operated by the system's users or customers.

[0162] The control plane VCN 816 may include one or more LB subnets 822 (e.g., Figure 7 The control plane DMZ layer 820 of (one or more) LB subnets 722) (e.g., Figure 7 The control plane DMZ layer 720), may include one or more application subnets 826 (e.g., Figure 7 The control plane application layer 824 of (one or more) application subnets 726 (e.g., Figure 7 The control plane application layer 724) may include one or more database (DB) subnets 830 (e.g., similar to...). Figure 7 The control plane data layer 828 of (one or more) DB subnets 730 (e.g., Figure 7 The control plane data layer 728). One or more LB subnets 822 contained in the control plane DMZ layer 820 can be communicatively coupled to one or more application subnets 826 contained in the control plane application layer 824 and an Internet gateway 834 that can be contained in the control plane VCN 816 (e.g., Figure 7 Internet gateway 734), and application subnet(s) 826 can communicatively couple to DB subnet(s) 830 and service gateway 836 contained in control plane data layer 828 (e.g., Figure 7 The service gateway) and the Network Address Translation (NAT) gateway 838 (e.g., Figure 7 (NAT gateway 738). The control plane VCN 816 may include the service gateway 836 and the NAT gateway 838.

[0163] The control plane VCN 816 may include a data plane mirror of the application layer 840 (e.g., Figure 7 The data plane mirror application layer 740 may include one or more application subnets 826. The one or more application subnets 826 included in the data plane mirror application layer 840 may include computational instances 844 (e.g., similar to...). Figure 7 The virtual network interface controller (VNIC) 842 (e.g., the VNIC of 742) of the computing instance 744. The computing instance 844 may facilitate the mirroring of the application subnet(s) 826 of the application layer 840 in the data plane and may be included in the application layer 846 in the data plane (e.g., Figure 7 Communication between one or more application subnets 826 in the data plane application layer 746 via VNIC 842 contained in the data plane mirror application layer 840 and VNIC 842 contained in the data plane application layer 846.

[0164] The Internet gateway 834 included in the control plane VCN 816 can be communicatively coupled to the metadata management service 852 (e.g., Figure 7 Metadata management service 752), which can communicatively couple to the public Internet 854 (e.g., Figure 7 The public internet 854 can communicatively couple to a NAT gateway 838 contained in the control plane VCN 816. The service gateway 836 contained in the control plane VCN 816 can communicatively couple to a cloud service 856 (e.g., ...). Figure 7 Cloud services 756).

[0165] In some examples, data plane VCN 818 may be included in customer lease 821. In this case, the IaaS provider may provide control plane VCN 816 for each customer, and the IaaS provider may establish a unique compute instance 844 for each customer, included in service lease 819. Each compute instance 844 may allow communication between control plane VCN 816 included in service lease 819 and data plane VCN 818 included in customer lease 821. Compute instance 844 may allow resources provisioned in control plane VCN 816 included in service lease 819 to be deployed or otherwise used in data plane VCN 818 included in customer lease 821.

[0166] In other examples, an IaaS provider's customer may own a database residing in customer lease 821. In this example, control plane VCN 816 may include a data plane mirror application layer 840, which may include one or more application subnets 826. Data plane mirror application layer 840 may reside in data plane VCN 818, but it may not reside in data plane VCN 818. That is, data plane mirror application layer 840 may have access to customer lease 821, but it may not reside in data plane VCN 818 or be owned or operated by an IaaS provider's customer. Data plane mirror application layer 840 may be configured to make calls to data plane VCN 818, but may not be configured to make calls to any entities contained in control plane VCN 816. Customers may expect to deploy or otherwise use resources provided in the control plane VCN 816 in the data plane VCN 818, and the data plane mirroring application layer 840 can facilitate customers' expected deployments or other uses of resources.

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

[0168] In some embodiments, cloud service 856 may be invoked by service gateway 836 to access services that may not exist on public internet 854, control plane VCN 816, or data plane VCN 818. The connection between cloud service 856 and control plane VCN 816 or data plane VCN 818 may not be active or continuous. Cloud service 856 may reside on different networks owned or operated by the IaaS provider. Cloud service 856 may be configured to receive calls from service gateway 836 and may be configured not to receive calls from public internet 854. Some cloud services 856 may be isolated from other cloud services 856, and control plane VCN 816 may be isolated from cloud services 856 that may not be in the same region as control plane VCN 816. For example, control plane VCN 816 may be located in "Region 1," while cloud service "Deployment 7" may be located in both Region 1 and "Region 2." If a call to deployment 7 is made by a service gateway 836 contained in a control plane VCN 816 located in region 1, the call can be forwarded to deployment 7 in region 1. In this example, the control plane VCN 816 or deployment 7 in region 1 may be non-communicatively coupled to deployment 7 in region 2, or may otherwise communicate with deployment 7 in region 2.

[0169] Figure 9 This is a block diagram 900 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 902 (e.g., Figure 7 The service provider (702) can communicatively couple to the secure host lease (904) (e.g., Figure 7 Secure hosting lease 704), the secure hosting lease 904 may include a Virtual Cloud Network (VCN) 906 (e.g., Figure 7 VCN 706) and Secure Host Subnet 908 (e.g., Figure 7 The secure host subnet 708). VCN 906 can include LPG 910 (e.g., Figure 7 The LPG 710), and the LPG 910 can be communicatively coupled to the SSH VCN 912 (e.g., via the LPG 910 included in the SSH VCN 912) Figure 7 SSH VCN 712). SSH VCN 912 can include SSH subnet 914 (e.g., Figure 7 The SSH subnet 714), and the SSH VCN 912 can be communicatively coupled to the control plane VCN 916 via the LPG 910 included in the control plane VCN 916 (e.g., Figure 7 The control plane VCN 716) and the LPG 910 communicatively coupled to the data plane VCN 918 (e.g., via a control plane VCN 716) and the data plane VCN 918 via an LPG 910 contained in the data plane VCN 918. Figure 7 Data plane VCN 718). Control plane VCN 916 and data plane VCN 918 may be included in service lease 919 (e.g., Figure 7 (Service rental 719).

[0170] The control plane VCN 916 may include one or more load balancer (LB) subnets 922 (e.g., Figure 7 The control plane DMZ layer 920 of (one or more) LB subnets 722) (e.g., Figure 7 The control plane DMZ layer 720 may include one or more application subnets 926 (e.g., similar to...). Figure 7 The control plane application layer 924 of (one or more) application subnets 726 (e.g., Figure 7 The control plane application layer 724 may include (one or more) control plane data layers 928 of the DB subnet 930 (e.g., Figure 7 The control plane data layer 728). One or more LB subnets 922 contained in the control plane DMZ layer 920 can be communicatively coupled to one or more application subnets 926 contained in the control plane application layer 924 and an Internet gateway 934 that can be contained in the control plane VCN 916 (e.g., Figure 7 The Internet gateway 734), and one or more application subnets 926 can be communicatively coupled to one or more DB subnets 930 and service gateways 936 contained in the control plane data layer 928 (e.g., Figure 7 The service gateway) and Network Address Translation (NAT) gateway 938 (e.g., Figure 7 (NAT gateway 738). The control plane VCN 916 may include the service gateway 936 and the NAT gateway 938.

[0171] The data plane VCN 918 may include the data plane application layer 946 (e.g., Figure 7 Data plane application layer 746), data plane DMZ layer 948 (e.g., Figure 7 Data plane DMZ layer 748), and data plane data layer 950 (e.g., Figure 7The data plane data layer 750. The data plane DMZ layer 948 may include one or more LB subnets 922, which may be communicatively coupled to one or more trusted application subnets 960 and one or more untrusted application subnets 962 of the data plane application layer 946, and an Internet gateway 934 contained in the data plane VCN 918. One or more trusted application subnets 960 may be communicatively coupled to a service gateway 936 contained in the data plane VCN 918, a NAT gateway 938 contained in the data plane VCN 918, and one or more DB subnets 930 contained in the data plane data layer 950. One or more untrusted application subnets 962 may be communicatively coupled to a service gateway 936 contained in the data plane VCN 918 and one or more DB subnets 930 contained in the data plane data layer 950. The data plane data layer 950 may include one or more DB subnets 930, which may be communicatively coupled to a service gateway 936 contained in the data plane VCN 918.

[0172] One or more untrusted application subnets 962 may include one or more primary VNICs 964(1)-(N) that may be communicatively coupled to tenant virtual machines (VMs) 966(1)-(N). Each tenant VM 966(1)-(N) may be communicatively coupled to a corresponding application subnet 967(1)-(N) that may be contained in a corresponding container egress VCN 968(1)-(N) that may be contained in a corresponding customer lease 970(1)-(N). A corresponding secondary VNIC 972(1)-(N) may facilitate communication between one or more untrusted application subnets 962 contained in a data plane VCN 918 and application subnets contained in a container egress VCN 968(1)-(N). Each container exit VCN 968(1)-(N) may include a NAT gateway 938, which can communicatively couple to the public Internet 954 (e.g., Figure 7 (Public Internet 754).

[0173] The Internet gateway 934, contained in the control plane VCN 916 and the data plane VCN 918, can be communicatively coupled to the metadata management service 952 (e.g., Figure 7Metadata management service 952 can be communicatively coupled to the public Internet 954. The public Internet 954 can be communicatively coupled to a NAT gateway 938 contained in a control plane VCN 916 and a data plane VCN 918. Service gateway 936 contained in a control plane VCN 916 and a data plane VCN 918 can be communicatively coupled to a cloud service 956.

[0174] In some embodiments, the data plane VCN 918 may be integrated with customer leases 970(1)-(N). This integration may be useful or desired by the IaaS provider's customers in certain situations, such as when support may be expected during code execution. Customers may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause adverse effects. In response to this, the IaaS provider may determine whether to run the code provided by the customer to the IaaS provider.

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

[0176] In some embodiments, one or more trusted application subnets 960 may run code owned or operated by an IaaS provider. In this embodiment, one or more trusted application subnets 960 may be communicatively coupled to one or more DB subnets 930 and configured to perform CRUD operations in one or more DB subnets 930. One or more untrusted application subnets 962 may be communicatively coupled to one or more DB subnets 930, but in this embodiment, one or more untrusted application subnets may be configured to perform read operations in one or more DB subnets 930. Containers 971(1)-(N) that may be contained in each customer's VM 966(1)-(N) and may run code from the customer may not be communicatively coupled to one or more DB subnets 930.

[0177] In other embodiments, the control plane VCN 916 and the data plane VCN 918 may be coupled without direct communication. In this embodiment, there may be no direct communication between the control plane VCN 916 and the data plane VCN 918. However, communication can occur indirectly through at least one method. The LPG 910 may be established by an IaaS provider, which can facilitate communication between the control plane VCN 916 and the data plane VCN 918. In another example, either the control plane VCN 916 or the data plane VCN 918 may make a call to the cloud service 956 via the service gateway 936. For example, a call from the control plane VCN 916 to the cloud service 956 may include a request for a service that can communicate with the data plane VCN 918.

[0178] Figure 10 This is a block diagram 1000 illustrating another example pattern of an IaaS architecture according to at least one embodiment. Service operator 1002 (e.g., Figure 7 The service provider 702) can communicatively couple to the secure host lease 1004 (e.g., Figure 7 Secure hosting lease 704), the secure hosting lease 1004 may include a virtual cloud network (VCN) 1006 (e.g., Figure 7 VCN706) and Secure Host Subnet 1008 (e.g., Figure 7 The secure host subnet 708). VCN 1006 may include LPG 1010 (e.g., Figure 7 The LPG 1010 can be communicatively coupled to the SSH VCN 1012 via the LPG 1010 included in the SSH VCN 1012 (e.g., LPG 710), Figure 7 SSH VCN 712). SSH VCN 1012 can include SSH subnet 1014 (e.g., Figure 7 SSH subnet 714), and SSH VCN 1012 can be communicatively coupled to control plane VCN 1016 via LPG 1010 included in control plane VCN 1016 (e.g., Figure 7 The control plane VCN 716) and the LPG 1010 communicatively coupled to the data plane VCN 1018 (e.g., via the control plane VCN 716) and the data plane VCN 1018 via the LPG 1010 contained in the data plane VCN 1018. Figure 7 Data plane VCN 718). Control plane VCN 1016 and data plane VCN 1018 may be included in service lease 1019 (e.g., Figure 7 (Service rental 719).

[0179] The control plane VCN 1016 may include one or more LB subnets 1022 (e.g., Figure 7 The control plane DMZ layer 1020 of (one or more) LB subnets 722) (e.g., Figure 7 The control plane DMZ layer 720 may include one or more application subnets 1026 (e.g., Figure 7 The control plane application layer 1024 of (one or more) application subnets 726 (e.g., Figure 7 The control plane application layer 724) may include one or more DB subnets 1030 (e.g., Figure 9 The control plane data layer 1028 of (one or more) DB subnets 930 (e.g., Figure 7 The control plane data layer 728). One or more LB subnets 1022 contained in the control plane DMZ layer 1020 can be communicatively coupled to one or more application subnets 1026 contained in the control plane application layer 1024 and an Internet gateway 1034 that can be contained in the control plane VCN 1016 (e.g., Figure 7 Internet gateway 734), and application subnet(s) 1026 can communicatively couple to DB subnet(s) 1030 and service gateway 1036 contained in control plane data layer 1028 (e.g., Internet gateway 734), and application subnet(s) 1026 can be communicatively coupled to DB subnet(s) 1030 and service gateway(s) 1036 contained in control plane data layer 1028 (e.g., Internet Figure 7 The service gateway) and Network Address Translation (NAT) gateway 1038 (e.g., Figure 7 (NAT gateway 738). The control plane VCN1016 may include service gateway 1036 and NAT gateway 1038.

[0180] The data plane VCN 1018 may include the data plane application layer 1046 (e.g., Figure 7 Data plane application layer 746), data plane DMZ layer 1048 (e.g., Figure 7Data plane DMZ layer 748), and data plane data layer 1050 (e.g., Figure 7 The data plane data layer 750). The data plane DMZ layer 1048 may include one or more LB subnets 1022, which may be communicatively coupled to one or more trusted application subnets 1060 of the data plane application layer 1046 (e.g., Figure 9 (one or more) trusted application subnets 960 and (one or more) untrusted application subnets 1062 (e.g., Figure 9 The data plane VCN 1050 may include one or more untrusted application subnets 962 and an Internet gateway 1034 contained in the data plane VCN 1018. One or more trusted application subnets 1060 may be communicatively coupled to a service gateway 1036 contained in the data plane VCN 1018, a NAT gateway 1038 contained in the data plane VCN 1018, and one or more DB subnets 1030 contained in the data plane data layer 1050. One or more untrusted application subnets 1062 may be communicatively coupled to a service gateway 1036 contained in the data plane VCN 1018 and one or more DB subnets 1030 contained in the data plane data layer 1050. The data plane data layer 1050 may include one or more DB subnets 1030 that may be communicatively coupled to a service gateway 1036 contained in the data plane VCN 1018.

[0181] One or more untrusted application subnets 1062 may include a primary VNIC 1064(1)-(N) that may be communicatively coupled to tenant virtual machines (VMs) 1066(1)-(N) residing within one or more untrusted application subnets 1062. Each tenant VM 1066(1)-(N) may run code in a corresponding container 1067(1)-(N) and be communicatively coupled to an application subnet 1026 that may be contained in a data plane application layer 1046, which may be contained in a container egress VCN 1068. A corresponding secondary VNIC 1072(1)-(N) may facilitate communication between one or more untrusted application subnets 1062 contained in a data plane VCN 1018 and the application subnets contained in the container egress VCN 1068. The container's egress VCN may include a NAT gateway 1038, which may communicatively couple to the public internet 1054 (e.g., Figure 7 (Public Internet 754).

[0182] Internet gateway 1034, contained in control plane VCN 1016 and data plane VCN 1018, can be communicatively coupled to metadata management service 1052 (e.g., Figure 7 Metadata management service 752), which can be communicatively coupled to public internet 1054. Public internet 1054 can be communicatively coupled to NAT gateway 1038, which is contained in control plane VCN 1016 and data plane VCN 1018. Service gateway 1036, which is contained in control plane VCN 1016 and data plane VCN 1018, can be communicatively coupled to cloud service 1056.

[0183] In some examples, by Figure 10 The architecture diagram of block diagram 1000 can be considered as a pattern. Figure 9 The architecture shown in block diagram 900 is an exception to the pattern, and may be what the IaaS provider's customers expect if the IaaS provider cannot communicate directly with the customer (e.g., in a disconnected region). The corresponding container 1067(1)-(N) contained in each customer's VM 1066(1)-(N) is accessible to the customer in real time. Container 1067(1)-(N) can be configured to make calls to the corresponding secondary VNIC 1072(1)-(N) contained in one or more application subnets 1026 of the data plane application layer 1046, which may be contained in the container egress VCN 1068. The secondary VNIC 1072(1)-(N) can forward the calls to a NAT gateway 1038, which can then forward the calls to the public internet 1054. In this example, containers 1067(1)-(N), which can be accessed by clients in real time, can be isolated from the control plane VCN 1016 and from other entities contained in the data plane VCN 1018. Containers 1067(1)-(N) can also be isolated from resources from other clients.

[0184] In other examples, a client may use containers 1067(1)-(N) to invoke cloud service 1056. In this example, the client may run code within containers 1067(1)-(N) requesting services from cloud service 1056. Container 1067(1)-(N) may forward this request to a secondary VNIC 1072(1)-(N), which may forward the request to a NAT gateway, which may forward the request to the public internet 1054. The public internet 1054 may forward the request via internet gateway 1034 to one or more LB subnets 1022 contained in control plane VCN 1016. In response to determining that the request is valid, one or more LB subnets may forward the request to one or more application subnets 1026, which may forward the request to cloud service 1056 via service gateway 1036.

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

[0186] In some embodiments, the IaaS system described herein may include a suite of application, middleware, and database services delivered to customers in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner. An example of such an IaaS system is the Oracle Cloud Infrastructure (OCI) provided by this assignee.

[0187] Figure 11 An example computer system 1100, in which various embodiments can be implemented, is illustrated. Computer system 1100 can be used to implement any computer system described above. As shown, computer system 1100 includes a processing unit 1104 that communicates with a plurality of peripheral subsystems via a bus subsystem 1102. These peripheral subsystems may include a processing acceleration unit 1106, an I / O subsystem 1108, a storage subsystem 1118, and a communication subsystem 1124. Storage subsystem 1118 includes a tangible computer-readable storage medium 1122 and system memory 1110.

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

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

[0190] In various embodiments, processing unit 1104 can execute a wide variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed may reside in processing unit 1104 and / or storage subsystem 1118. With appropriate programming, processing unit 1104 can provide the various functions described above. Computer system 1100 may additionally include processing acceleration unit 1106, which may include a digital signal processor (DSP), a dedicated processor, and / or the like.

[0191] I / O subsystem 1108 may include user interface input devices and user interface output devices. User interface input devices may include keyboards, pointing devices such as mice or trackballs, touchpads or touchscreens integrated into the display, scroll wheels, click wheels, dial pads, buttons, switches, keypads, audio input devices with voice command recognition systems, microphones, and other types of input devices. User interface input devices may include, for example, motion sensing and / or gesture recognition devices, such as natural user interfaces that enable users to control input devices using gestures and verbal commands (such as Microsoft...). Microsoft 360 Game Controller and its interaction Motion sensors. User interface input devices can also include eye gesture recognition devices, such as Google's... A blink detector detects eye movements from the user (e.g., blinking when taking a photo and / or making menu selections) and translates the eye gestures into the input device (e.g., Google). Input can be made via voice commands or by a voice recognition system. Additionally, the user interface input device may include features that enable the user to interact with a voice recognition system (e.g., [system name]) through voice commands. A voice recognition sensing device for interaction with navigators.

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

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

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

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

[0196] System memory 1110 may also store operating system 1116. Examples of operating system 1116 may include various versions of Microsoft operating system 1116. Apple and / or Linux operating system, various commercial Or a UNIX-like operating system (including but not limited to various GNU / Linux operating systems, Google...) OS (and / or mobile operating systems, such as iOS) and / or mobile operating systems Phone OS OS and Operating system (OS). In some implementations of computer system 1100 that execute one or more virtual machines, the virtual machines, along with the guest operating system (GOS), may be loaded into system memory 1110 and executed by one or more processors or cores of processing unit 1104.

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

[0198] Computer-readable storage medium 1122 may represent remote, local, fixed and / or removable storage devices and storage media for temporarily and / or more permanently containing and storing computer-readable information used by computer system 1100, including instructions executable by processing unit 1104 of computer system 1100.

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

[0200] For example, computer-readable storage medium 1122 may include a hard disk drive that reads from or writes to a non-removable non-volatile magnetic medium, a disk drive that reads from or writes to a removable non-volatile magnetic disk, and a drive that reads from or writes to a removable non-volatile optical disk (such as CD ROM, DVD, and Blu-ray disc). An optical disc drive that reads from or writes to an optical disc (or other optical medium). Computer-readable storage medium 1122 may include, but is not limited to, [other types of media]. Disk drives, flash memory cards, Universal Serial Bus (USB) flash drives, Secure Digital (SD) cards, DVD discs, digital video tapes, etc. Computer-readable storage media 1122 may also include solid-state drives (SSDs) based on non-volatile memory (such as flash-based SSDs, enterprise flash drives, solid-state ROMs, etc.), volatile memory-based SSDs (such as SSDs based on solid-state RAM, dynamic RAM, static RAM, DRAM), magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs using a combination of DRAM and flash-based SSDs. Disk drives and their associated computer-readable media can provide non-volatile storage of computer-readable instructions, data structures, programs, and other data for computer system 1100.

[0201] Machine-readable instructions executable by one or more processors or cores of processing unit 1104 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 that include volatile memory storage devices and / or non-volatile memory storage devices. Examples of non-transitory computer-readable storage media include magnetic storage media (e.g., magnetic disks or magnetic tapes), optical storage media (such as DVDs, CDs), various types of RAM, ROM, or flash memory, hard disk drives, floppy disk drives, removable storage drives (e.g., USB drives), or other types of storage devices.

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

[0203] In some embodiments, the communication subsystem 1124 may also represent one or more users who may use the computer system 1100 to receive input communications in the form of structured and / or unstructured data feeds 1126, event streams 1128, event updates 1130, etc.

[0204] For example, the communication subsystem 1124 can be configured to receive data feeds 1126 in real time from users of social networks and / or other communication services, such as... feed, Updates, web feeds such as rich site summary (RSS) feeds, and / or real-time updates from one or more third-party information sources.

[0205] Additionally, the communication subsystem 1124 can also be configured to receive data in the form of a continuous data stream, which may include event streams 1128 and / or event updates 1130 of real-time events, and may be continuous or unbounded in nature without a definite end. Examples of applications that generate continuous data may include, for example, sensor data applications, financial market data, network performance measurement tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, vehicle traffic monitoring, etc.

[0206] The communication subsystem 1124 can also be configured to output structured and / or unstructured data feeds 1126, event streams 1128, event updates 1130, etc., to one or more databases that can communicate with one or more streaming data source computers coupled to the computer system 1100.

[0207] Computer system 1100 can be of a variety of types, including handheld portable devices (e.g., Cellular phone Computing tablets, PDAs), and wearable devices (e.g., Google). Head-mounted displays, PCs, workstations, mainframes, kiosks, server racks, or any other data processing systems.

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

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

[0210] Furthermore, while embodiments have been described using specific combinations of hardware and software, it should be recognized that other combinations of hardware and software are also within the scope of this disclosure. Embodiments may be implemented using only hardware, or only software, or a combination thereof. The various processes described herein may be implemented on the same or different processors in any combination. Thus, where components are described as being configured to perform certain operations, such configuration may be implemented, for example, by designing electronic circuits to perform operations, by programming programmable electronic circuits (such as microprocessors), or any combination thereof. Processes may communicate using a wide variety of techniques, including but not limited to conventional techniques for inter-process communication, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times. Embodiments may be implemented using a computer program product comprising a computer program / instructions that, when executed by a processor, cause the processor to perform any of the methods described in this disclosure.

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

[0212] In the context of describing the disclosed embodiments (particularly in the context of the appended claims), the terms “a,” “an,” and “the,” and similar pronouns, should be interpreted as encompassing both the singular and plural, unless otherwise stated herein or clearly contradicted by the context. Unless otherwise stated, the terms “comprising,” “having,” “including,” and “containing” should be interpreted as open-ended terms (i.e., meaning “including, but not limited to”). The term “connected to” should be interpreted as partially or wholly included, attached to, or combined with, even if something else is involved. Unless otherwise stated herein, the enumeration of numerical ranges herein is intended only as a shorthand method for individually referring to each separate value falling within that range, and each separate value is incorporated into the specification as if it were individually enumerated herein. Unless otherwise stated herein or clearly contradicted by the context, all methods described herein can be performed in any suitable order. Unless otherwise claimed, the use of any and all examples or exemplary language (e.g., “such as”) provided herein is intended only to better illustrate the embodiments and does not limit the scope of this disclosure. Nothing in the specification should be construed as indicating that any unclaimed element is essential to the practice of this disclosure.

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

[0214] This document describes preferred embodiments of the present disclosure, including known best modes for carrying out the present disclosure. Variations of those preferred embodiments will become apparent to those skilled in the art upon reading the foregoing description. Those skilled in the art should be able to suitably employ such variations, and the present disclosure can be practiced in addition to those specifically described herein. Therefore, the present disclosure includes all modifications and equivalents of the subject matter set forth in the appended claims as permitted by applicable law. Furthermore, unless otherwise stated herein, any combination of the foregoing elements in all possible variations is included in this disclosure.

[0215] All references cited herein, including publications, patent applications and patents, are incorporated herein by reference to the extent that each reference is individually and specifically indicated as being incorporated herein by reference in its entirety.

[0216] In the foregoing description, aspects of this disclosure have been described with reference to specific embodiments thereof; however, those skilled in the art will recognize that this disclosure is not limited thereto. The various features and aspects of the foregoing disclosure may be used individually or in combination. Furthermore, embodiments may be utilized in any number of environments and applications beyond those described herein without departing from the broader spirit and scope of this specification. Therefore, the description and drawings are to be considered illustrative rather than restrictive.

Claims

1. A method comprising: generating, by a distributed computing system of a cloud service provider, a virtual cloud network in a data center of a home region; implementing, by the distributed computing system, a virtual onboarding environment in the virtual cloud network, the virtual onboarding environment comprising a plurality of services; deploying, by the distributed computing system, an instance of a first service of the plurality of services of the virtual onboarding environment to a target region data center; receiving, from the instance of the first service in the target region data center, an indication that the instance was successfully deployed; migrating, from the virtual onboarding environment to the target region data center, a data resource, the data resource being associated with the instance of the first service deployed to the target region data center and the data resource being identified using a resource search service executing in the distributed computing system; in response to the indication and after migrating the data resource, identifying the data resource associated with the instance of the first service; and updating, by the distributed computing system, a second service of the plurality of services with the data resource.

2. The method of claim 1, further comprising updating, by the distributed computing system, the instance of the first service deployed to the target region data center.

3. The method of claim 1, wherein deploying the instance uses a virtual private network connection between the data center of the home region and the target region data center.

4. The method of claim 1, wherein the data resource is a domain name service record.

5. The method of claim 1, wherein the indication comprises a capability published to a capability service of the plurality of services, the capability indicating a partially successful deployment.

6. The method of claim 5, further comprising receiving a second capability from the instance deployed to the target region data center in response to the updating of the second service, the second capability indicating a fully successful deployment.

7. The method of claim 1, wherein the data resource is (i) generated by the first service in the virtual onboarding environment and (ii) durably saved in the data center of the home region.

8. A computing system comprising: one or more processors; and one or more memories storing computer-executable instructions that, when executed with the one or more processors, cause the computing system to at least: generate a virtual cloud network in a data center of a home region; implement a virtual onboarding environment in the virtual cloud network, the virtual onboarding environment comprising a plurality of services; deploy an instance of a first service of the plurality of services of the virtual onboarding environment to a target region data center; receive, from the instance of the first service in the target region data center, an indication that the instance was successfully deployed; migrate, from the virtual onboarding environment to the target region data center, a data resource, the data resource being associated with the instance of the first service deployed to the target region data center and the data resource being identified using a resource search service executing in the computing system; ​ ​ in response to the indication and after migrating the data resource, identifying the data resource associated with the instance of the first service; and updating a second service of the plurality of services with the data resource.

9. The computing system of claim 8, wherein the one or more memories store additional instructions that, when executed with the one or more processors, cause the computing system to further update the instance of the first service deployed to the target regional data center.

10. The computing system of claim 8, wherein deploying the instance uses a virtual private network connection between the data center of the home region and the target regional data center.

11. The computing system of claim 8, wherein the data resource is a domain name service record.

12. The computing system of claim 8, wherein the indication comprises a capability published to a capability service of the plurality of services, the capability indicating a successful partial deployment.

13. The computing system of claim 12, wherein the one or more memories store additional instructions that, when executed with the one or more processors, cause the computing system to further receive a second capability from the instance deployed to the target regional data center in response to the update of a second service, the second capability indicating a successful full deployment.

14. The computing system of claim 8, wherein the data resource is (i) generated by the first service in the virtual bootstrapping environment and (ii) persisted in the data center of the home region.

15. A non-transitory computer-readable medium storing computer-executable instructions that, when executed with one or more processors, cause a computing system to at least: generate a virtual cloud network in a data center of a home region; implement a virtual bootstrapping environment in the virtual cloud network, the virtual bootstrapping environment comprising a plurality of services; deploy an instance of a first service of the plurality of services of the virtual bootstrapping environment to a target regional data center; receive an indication from the instance of the first service in the target regional data center that the instance was successfully deployed; migrate a data resource from the virtual bootstrapping environment to the target regional data center, the data resource being associated with the instance of the first service deployed to the target regional data center and the data resource being identified using a resource search service executed in the computing system; in response to the indication and after migrating the data resource, identify the data resource associated with the instance of the first service; and update a second service of the plurality of services with the data resource.

16. The non-transitory computer-readable medium of claim 15, storing further instructions that, when executed with the one or more processors, cause the computing system to further update the instance of the first service deployed to the target regional data center.

17. The non-transitory computer-readable medium of claim 16, wherein deploying the instance uses a virtual private network connection between the data center of the host region and the target region data center.

18. The non-transitory computer-readable medium of claim 16, wherein the data resource is a domain name service record.

19. The non-transitory computer-readable medium of claim 16, wherein the indication comprises a capability published to a capability service of the plurality of services, the capability indicating a successful partial deployment.

20. The non-transitory computer-readable medium of claim 15, wherein the data resource (i) is generated by the first service in the virtual bootstrapping environment and (ii) is durably saved in the data center of the host region.

Images