Re-entry Service Deployment

Abstract

Techniques are described for scheduling and executing multiple releases of a service. Techniques are described for determining that a new capability has been issued in a data center. For a flock for a service for which a first release has been previously scheduled and executed, a second release may be scheduled for the flock in response to identifying the newly issued capability as being an optional capability dependency of the flock for the service. The flock includes a set of one or more resources for providing the service. A second release of the flock is executed. As a result of executing the second release, additional extended capabilities may be added to the service.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This non-provisional application claims priority to U.S. Provisional Patent Application No. 63 / 308,003, "Techniques for Bootstrapping a Region Build," filed February 8, 2022, U.S. Provisional Patent Application No. 63 / 312,814, "Techniques for Implementing Virtual Data Centers," filed February 22, 2022, U.S. Provisional Patent Application No. 63 / 314,927, "Reentrant Service Deployments," filed February 28, 2022, and U.S. Provisional Patent Application No. 18 / 098,617, "Reentrant Service Deployments," filed January 18, 2023, the disclosures of all of which are incorporated herein by reference.

[0002] FIELD OF THEINVENTION The present disclosure relates to techniques for building a data center in a cloud computing environment. More particularly, techniques are described for the creation, provisioning, and deployment of resources and infrastructure to build a data center configured to provide a set of services. [Background technology]

[0003] background Today, cloud infrastructure services utilize many individual services to build a datacenter (e.g., bootstrap various resources in a datacenter in a particular geographic area). In some examples, a region is a logical abstraction that corresponds to a local geographic area in which one or more datacenters are (or will be) located. Building a datacenter may include provisioning and configuring infrastructure resources and deploying code (e.g., for various services) to these resources. Operations to build a datacenter may be collectively referred to as performing a "region build." A region may include any suitable number of datacenters, so a region build may include operations to build multiple datacenters. Conventional tools for building datacenters require significant manual effort. Bootstrapping a service may also depend on other features and / or services in the region that may not be available. As the number of service teams and regions increases, the tasks performed to orchestrate provisioning and deployment increase significantly. Relying heavily on manual effort to bootstrap services and / or build datacenters is time-consuming, introduces risks, and may not scale well. Summary of the Invention

[0004] overview The present disclosure generally relates to building datacenters. More specifically, techniques are described for the creation, provisioning, and deployment of resources and infrastructure for building a datacenter configured to provide a set of services. Techniques are provided for scheduling and executing multiple releases of a service. For a service for which a release has previously been executed, a second release may be scheduled for the service in response to an optional capability dependency of the service being published (available) at the datacenter. Various embodiments are described herein, including methods, systems, non-transitory computer-readable storage media storing one or more processor-executable programs, codes, or instructions, and the like.

[0005] In one embodiment, a first release of the flock for the service is scheduled and executed upon determining that all required capability dependencies of the flock for the service have been published. After executing the first release, a second release of the flock is scheduled upon determining that new capabilities have been published at the data center and identifying the newly published capabilities as optional capability dependencies of the flock for the service. The second release is then executed. The newly published capabilities identify functional units associated with the flock for the service and identify a set of resources associated with the service.

[0006] Required capability dependencies of a flock for a service are identified as capabilities that are published in the data center before a first release of the flock is scheduled and executed. Optional capability dependencies of a flock for a service are identified as capabilities that do not need to be published in the data center before a first release of the flock is scheduled and executed.

[0007] In one example, a flock for a service includes a set of one or more resources for providing the service. The set of resources includes infrastructure components and artifacts associated with the service. In one example, information identifying a flock for a service is declared in a flock configuration of the service. The flock configuration of the service identifies a set of one or more resources associated with the service.

[0008] In one example, a dependency graph is obtained and the dependency graph is used to identify the newly issued capability as an optional capability dependency of the block for the service. In one example, the dependency graph is an acyclic dependency graph.

[0009] In one example, executing the second release includes generating a plan. The plan identifies a current configuration of the datacenter and a target configuration of the datacenter associated with executing the second release. The plan is then executed. In one example, executing the plan results in additional issuance of new capabilities at the datacenter. In one example, in response to executing the plan, metadata associated with a cluster configuration of the service is updated.

[0010] In one example, a cloud infrastructure orchestration system is disclosed. The system determines that a new capability has been issued at a data center, identifies the newly issued capability as an optional capability dependency of a flock for a service, where a first release of the flock has been previously scheduled and executed, and schedules a second release of the flock. In one example, the system adds the second release of the flock to a queue and scans the queue to determine whether one or more unexecuted releases of the flock are present in the queue. At least one of the unexecuted releases may include the second release of the flock. In response to this determination, the system then aggregates the one or more unexecuted releases of the flock in the queue to generate an aggregated release of the flock. The aggregated release of the flock is then executed. In one example, the queue is a general scheduling queue shared by multiple services provided by the data center. In another example, the queue is a flock-specific queue of the flock for the service.

[0011] The above, together with other features and embodiments, will become more apparent with reference to the following specification, claims, and accompanying drawings.

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

[0013] [Figure 1] FIG. 1 is a block diagram of an environment in which a cloud infrastructure orchestration service (CIOS) may operate to dynamically provide bootstrap services in a region, according to at least one embodiment. [Diagram 2] FIG. 1 is a block diagram illustrating an environment and method for building a Virtual Bootstrap Environment (ViBE) according to at least one embodiment. [Diagram 3]1 is a block diagram illustrating an environment and method for bootstrapping a service to a target region using ViBE, according to at least one embodiment. [Figure 4] 1 is a simplified flowchart illustrating a process performed to schedule a reentry release according to one embodiment. [Diagram 5] FIG. 2 is an example diagram of a scheduling queue implemented by the multi-flock orchestrator (MFO) shown in FIG. 1 according to an embodiment. [Figure 6] FIG. 2 is an exemplary diagram of an integrated release in a scheduling queue implemented by the multi-flock orchestrator (MFO) shown in FIG. 1 according to an embodiment. [Figure 7] 1 is a simplified flowchart illustrating the processes performed to generate and execute an integrated release according to one embodiment. [Figure 8] FIG. 1 is a block diagram illustrating a pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 9] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 10] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 11] FIG. 2 is a block diagram illustrating another pattern for implementing a service-based cloud infrastructure system in accordance with at least one embodiment. [Figure 12] FIG. 1 is a block diagram illustrating an exemplary computer system according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] Detailed Description In the following description, for purposes of explanation, specific details are set forth in order to provide a thorough understanding of certain embodiments. It will be apparent, however, that various embodiments may be practiced without these specific details. The drawings and this specification are not intended to be limiting. Use of the word "exemplary" herein means "serving as an example, instance, or illustration." Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs.

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

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

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

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

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

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

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

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

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

[0024] Technical effects This disclosure describes techniques for reducing the time and manual effort required to build one or more data centers in a region. The disclosed techniques significantly reduce the time required to build a data center in a region and reduce the manual coordination required. Whereas previously it took weeks and months to build a data center in a region, by using the techniques described herein, a new data center can be built in a region in a relatively much shorter time.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0092] Re-entry Service Deployment This disclosure generally relates to building datacenters. More particularly, techniques are described for creating, provisioning, and deployment of resources and infrastructure for building a datacenter configured to provide a set of services. Also provided are techniques for releasing services and performing multiple releases. For a service for which a release has been previously scheduled and performed, a second release may be scheduled for the service in response to an optional capability dependency of the service being published (available) in the datacenter.

[0093] In an embodiment, services provided in a data center being constructed may depend on other resources and services. The dependencies may be required or optional dependencies. Resources used by a service are provisioned and deployed in a data center by scheduling and executing a release of the service. A release of a service may be scheduled and executed even if optional dependencies are not met if all required dependencies of the service are met (or published or made available in the data center). As a result of executing the release, resources used by the service are created and deployed. For a service for which a release has already been scheduled and executed as a result of all required dependencies of the service being met, a second release may be scheduled and executed for the service if the optional dependencies of the service are later met. This second release is referred to as a reentry deployment or reentry release. The second release may create additional resources for the service. One or more reentry releases may be scheduled and executed for a service, with each reentry release and its execution potentially enabling additional capabilities of the service.

[0094] In an embodiment, a capability may identify a functional unit associated with a service and represent a set of resources associated with the service. A capability may represent a set of one or more resources, where a resource may be a software or hardware resource, a function, a service, etc. A capability may be identified by a capability label. Examples of capability labels include "Capability_A", "Capability_B", "Capability_C", etc. For example, a capability labeled Capability_A corresponds to resources R1 and R2, and may be denoted as Capability_A={R1,R2}. Similarly, Capability_B={R3}, Capability_C={R4,R5,R6}, etc.

[0095] A capability is considered to be issued (or enabled or available) in a computing environment, such as a datacenter, when all of the resources corresponding to that capability have been created, deployed, and are available for use for their intended purpose in the datacenter. In the above example, Capability_A is considered to be issued with respect to a datacenter when resources R1 and R2 corresponding to Capability_A have been created and deployed in the datacenter and are ready for use for their intended purpose.

[0096] A data center may provide various services. For a service, a set of one or more resources used or required to provide the service is referred to as a flock for the service. A flock may include one or more resources. A flock typically represents a set of managed resources responsible for providing a service. Flock-related information for a service is declared as part of the flock configuration for the service. A flock configuration for a service is typically stored in the form of a file, and is therefore also referred to as a flock configuration file for the service. A flock configuration for a service describes the flocks (e.g., a set of resources including infrastructure components and artifacts associated with the service) associated with the service. A flock configuration for a service may include declarative statements that specify one or more aspects corresponding to a desired state of resources associated with the service. A flock configuration may identify various settings and configurations associated with flock resources and other parameters associated with the service. In one embodiment, a flock configuration includes Terraform code, and a flock configuration file is a Terraform file.

[0097] In a typical datacenter environment configured to provide multiple services, services may have dependencies on other services or resources. For example, service B may require service A to be present before service B can be bootstrapped (potentially from using service A). Service C may require service B to be present before service C can be bootstrapped in the datacenter. Thus, there may be multiple dependencies between services. In one embodiment, these dependencies are explicitly expressed through the use of capabilities. For example, a flocking of a service may identify any capabilities on which the service depends. Capabilities on which a service depends are referred to as the capability dependencies of the service (also referred to as the capability dependencies of the flocking of the service).

[0098] A flock associated with a service (also referred to as a service flock) is described in a flock configuration specified for that service. A flock configuration may be in the form of a flock configuration file. A capability dependency of a service is also referred to as a capability dependency of the flock for that service. A capability dependency of a service (e.g., a capability dependency of a service flock) may be a required capability dependency or an optional capability dependency. A required capability dependency of a service (or a service flock) is one that requires a capability to be published or enabled in a data center before a release can be scheduled for that service or service flock. An optional capability dependency of a service flock is one in which if the optional capability dependency (optional capability) is not published in a data center, a release of that service flock can still be scheduled to run as long as the optional required capability dependency for that flock is satisfied. Thus, an optional capability dependency does not block a release of a service. If the optional capability dependencies become available or published, another release of the service block is scheduled and executed. In this way, a block for a service can potentially be released and executed multiple times (sometimes referred to as reentrancy of service block releases). In general, a release of a service is scheduled and executed when the required capability dependencies of the service have been published, but one or more of the optional capability dependencies may not yet be published. A release and subsequent execution of a service block where one or more of the optional capability dependencies have not been published or are not available will result in the instantiation of a version of the service that may have some, but not all, capabilities. Note that not all service blocks need to have capability dependencies, whether required or optional.

[0099] A service's capability dependencies may be explicitly declared in the service's flock configuration, or may be implicitly determined from the service's flock configuration (by an MFO, as described below). If a capability dependency is explicitly declared in a flock configuration, the flock configuration contains code or metadata that explicitly declares the capability dependency. In other cases, the capability dependency may be inferred from code in the flock configuration (e.g., by the MFO 106, if the MFO 106 reads and parses the flock configuration). A service's flock configuration may identify zero or more required capabilities for the service flocks specified by the flock configuration. Thus, a service is not required to have capability dependencies.

[0100] As a result of the release and execution of a block for a service, one or more capabilities may (but are not necessarily) issued at the datacenter. Information identifying any capabilities issued by the execution of a release of a service block is also declared in the block configuration of the service. In one embodiment (such as the embodiment shown in FIG. 1), the MFO 106 schedules the release of a service block. The release is then executed, for example, by CIOS central 108 and CIOS regional 110 of FIG. 1, and zero or more capabilities may be issued at the datacenter upon successful execution of the release. Thus, the release and corresponding execution of a service block results in additional capabilities being issued at the datacenter.

[0101] In some implementations (such as the embodiment shown in FIG. 1 ), as part of the process of configuring a datacenter in a region where the datacenter will provide a particular set of services, the MFO 106 is provided with a flock configuration of a particular set of services. The MFO 106 then reads and parses these flock configuration files to identify, for each flock described by the flock configuration, the capability dependencies of the flock, if any, and the capabilities issued upon execution of one or more releases of the flock, if any. The MFO 106 then constructs an acyclic dependency graph to represent the various capability dependencies between the flock configurations and the corresponding flocks. The dependency graph also identifies a dependency ordering of the capabilities identified by the multiple flock configurations. The MFO 106 may generate any suitable number of data structures based on the identified dependencies. These data structures (e.g., directed graphs, directed acyclic graphs, linked lists, etc.) may be utilized by CIOS 102 (e.g., MFO 106, CISO central 108, CIOS regional 110) to drive operations to build one or more datacenters in a region (also referred to as executing a region build). The process performed by MFO 106 in analyzing the flock configuration and generating the acyclic dependency graph may also be referred to as static flock analysis.

[0102] The capability dependencies between different flocks specified in the flock configurations corresponding to different services can be illustrated by the following example: A flock configuration (FC_A) for service A specifies a flock (F_A) for service A. FC_A does not identify any capability dependencies of F_A, but does identify that Capability_A is issued upon successful release and execution of flock F_A. A flock configuration (FC_B) can specify information related to a flock (F_B) for service B, indicating that Capability_A is a required capability dependency and that Capability_B is issued upon successful execution of flock F_B for service B. A flock configuration (FC_C) can specify information for a flock (F_C) for service C, indicating that Capability_B is a required capability dependency and that Capability_C is issued to the data center upon successful release and execution of flock F_C for service C. Given these flock configurations, the dependency graph generated by the MFO 106 identifies the following: FC_A(F_A)→Capability_A→FC_B(F_B)→Capability_B→FC_C(F_C)→Capability_C If F_A does not have a capability dependency, then in the datacenter, release and execution of F_A will issue Capability_A, which is a required capability dependency of F_B, release and execution of F_B will issue Capability_B, which is a required capability dependency of F_C, and release and execution of F_C will issue Capability_C. For capabilities, the dependency graph is as follows: Capability_B depends on Capability_A, Capability_C depends on Capability_B, and is represented as Capability_A → Capability_B → Capability_C. Thus, the dependency graph generated by the MFO 106 for the datacenter identifies dependencies between capabilities declared in or inferred from the flock configurations corresponding to various services instantiated in the datacenter.

[0103] For the example dependency relationship (Capability_A → Capability_B → Capability_C), Capability_B is referred to as a direct dependency of Capability_C. Similarly, Capability_A is referred to as a direct dependency of Capability_B. Capability_A is also referred to as an indirect dependency of Capability_C. If Capability_A depends on another capability, then this other capability also has an indirect dependency on Capability_C, and so on. In general, in a hierarchical dependency graph, for a particular capability X in the graph, the parent capability in the graph of capability X is referred to as a direct capability dependency of capability X. All ancestor capabilities in the graph of the parent capability are referred to as indirect capability dependencies of capability X. Capabilities in a dependency graph can have multiple levels of indirect capability dependencies.

[0104] The MFO then schedules the release of each service block based on the availability of the published capabilities at the data center. In the above example, assuming that all the capability dependencies are necessary capability dependencies, where Capability_B depends on Capability_A and Capability_C depends on Capability_B, the MFO will first schedule the release of block F_A for service A. If the release is successful, Capability_A will be published at the data center. Then, the MFO 106 will schedule the release of block F_B for service B after determining that the necessary capability dependency (i.e., Capability_A) of block F_B for service B is satisfied. If the release of service B is successful, Capability_B will be published at the data center. Then, after the MFO 106 determines that the required capability dependency of F_C for service C (i.e., Capability_B) is satisfied, it will schedule a release of F_C for service C, which results in the publication of Capability_C. In this manner, as more releases of flocks are scheduled and executed, more capabilities are published in the data center environment, triggering additional releases in the data center environment.

[0105] Reentry release and deployment occurs when a flock for a service has at least one optional capability dependency. Optional capability dependencies may be explicitly declared in the flock configuration of the service or may be inferred from the flock configuration of the service. In some cases, optional dependencies are usually bound to conditional statements (e.g., if COUNT is greater than 1 then X, otherwise Y). As mentioned above, the identification of whether a dependency is required or optional is performed by MFO during static flock analysis.

[0106] As mentioned above, if all required capability dependencies are published, a release of a flock for a service is scheduled and executed even if one or all optional capability dependencies of the service flock are not published. For example, in the above example, if a required capability dependency, Capability_A, of flock F_B for service B is published, a release of F_B is scheduled and executed. Now, assume that the flock configuration FC_B of service B further specifies that flock F_B has an additional optional capability dependency "Capability_D". Capability_D may be issued in the data center after the release of F_B has already been scheduled and executed after Capability_A is published. If Capability_D is then published, another release (reentry release) is scheduled and executed for flock F_B. An initial release and execution of F_B when only the required capability dependency Capability_A is issued, but not the optional capability dependency Capability_D, may result in the instantiation of a version of service B that may have some, but not all, capabilities. If the optional capability dependency Capability_D is satisfied, a reentry release and execution of flock F_B may result in the instantiation of a version of service B that has all capabilities.

[0107] In one embodiment, MFO 106 may schedule a release by preparing a block "path" for the service, either for an initial release if required capability dependencies are issued or for a reentry release if optional capability dependencies are issued. The release / path may identify a particular execution target. MFO 106 then provides the prepared release / path to CIOS Central 108 for execution. CIOS Central 108 then executes the release / path in coordination with CIOS Regional 110. In one embodiment, execution of the release / path involves preparation of a "plan" for the release and then execution of the plan. As part of the preparation of the plan, the current state of the target system (e.g., target data center) with respect to the services for which execution will occur is determined, and the final desired state of the target system (as indicated in the release) is determined. A plan is then generated for the transition of the target system from the current state to the final state. This plan is then applied (through the use of an apply command) or executed. Assuming the execution is successful, the execution may result in zero or more capabilities being published in the datacenter. These capabilities may satisfy dependencies (necessary or optional) of some other flocks.

[0108] Below is an example of a flock configuration section that declares required and optional capabilities.

[0109] ad = module.service_availability_domain.availability_domain pool = module.service_availability_domain.pool_name } resource "odo_deployment" deploy_tenancy_creator { ad = module.service_availability_domain.availability_domain alias = "${local.serviceName}${local.serviceSuffix}" artifact { url = local.artifact_versions["tenancy-creator"].uri build_tag ​​= local.artifact_versions["tenancy-creator"].version type = local.artifact_versions["tenancy-creator"].type } node_ids = [ data.odo_nodes.deployment_node.nodes[0].resource_id ] } |resource "capability" "tenancy_creator_initial_tenancies_created" { name = "tenancy_creator_initial_tenancies_created" depends_on = [ odo_deployment.deploy_tenancy_creator ] } # If you have dependencies that you don't need for bootstrap, run this # Note: This is a data source, not a resource data "capability" "get_alarm_available" { # This field is the name of the actual capability that is depended upon. name = "telemetry_alarm" } / / Example resource resource "telemetry_alarm" heartbeatAlarm { # Here, the "count=" pattern delays resource construction until the underlying service is available. count = data.capability.get_alarm_available.available ? 1 : 0 compartment_id = var.compartment_id display_name = "Missing Host Heartbeat in Fleet - ${var.fleet_name}" query = "ServiceHostReporter.heartbeat[1m].groupBy(host).absent()" pending_duration = var.pending_duration project = var.project_name fleet = var.fleet_name severity = var.severity.normal is_enabled = true body = < <BODY FIG. 4 is a simplified flowchart 400 illustrating a process performed to schedule a reentry release, according to one embodiment. The process illustrated in FIG. 4 may be implemented in software (e.g., code, instructions, programs) executed by one or more processing units (e.g., processors, cores) of the respective systems, may be implemented using hardware, or a combination thereof. The software may be stored in a non-transitory storage medium (e.g., memory device). The method presented in FIG. 4 and described below is exemplary and not intended to be limiting. FIG. 4 depicts various process steps occurring in a particular order or sequence, but is not intended to be limiting. In an alternative embodiment, the process may be performed in some different order, or some steps may be performed in parallel. In an embodiment (such as the embodiment shown in FIG. 1), the process illustrated in FIG. 4 may be performed by MFO 106 in coordination with CIOS Central 108, CIOS Regional 110, and Capability Service 112.

[0110] In the embodiment shown in FIG. 1, processing may be triggered when the MFO 106 determines that a new capability has been issued (e.g., made available) at the data center. For example, in the embodiment shown in FIG. 1, the capability service 112 is responsible for tracking issued capabilities. When a new capability is issued, such as by a successful execution of a release of blocks for various services at the data center, the capability service 112 tracks the issued capability and makes the information available to other systems. For example, when a new capability is issued, the MFO 106 receives a signal from the capability service 112 that a new capability has been issued, which may include information identifying the new capability. In another embodiment, the MFO 106 may query the capability service 112 and receive a response identifying the newly issued capability (or a list of all issued capabilities) that includes the new specific capability determined in 402.

[0111] In some other embodiments, other techniques may be used to track issued capabilities for a data center. For example, a registry or database may be maintained that identifies issued capabilities. The MFO 106 may query this registry or database to find out what new capabilities have been issued (or may receive a signal when new capabilities are added to this database or registry).

[0112] At 404, the MFO 106 may determine that the newly issued capabilities identified at 402 are optional capability dependencies of the particular flock for a particular service for which a release of the particular flock was previously scheduled and successfully executed. As a result of the scheduling and subsequent execution of a previous release, the particular service is already functioning with some capabilities in the datacenter. In one embodiment, the MFO 106 determines that the newly issued capabilities are optional capability dependencies of the particular service and its associated flocks using an acyclic dependency graph that the MFO 106 generated by performing a static flock analysis (e.g., analyzing and retrieving flock configurations associated with services supported by the datacenter).

[0113] At 406, the MFO 106 schedules a new "re-entry" release for the particular flock. In one embodiment, as part of the process of 406, if the MFO 106 determines that a release is necessary to progress the data center build, the resulting planning, approvals, and applications are captured in an encapsulated model called a path. The MFO 106 then drives the release using the path. In such an embodiment, as part of 406, the MFO 106 creates a path for the release being scheduled.

[0114] At 408 , the cooperating CIOS central 110 and CIOS regional 110 execute the release scheduled by the MFO 106 at 406 .

[0115] Assuming the release of 408 is successful, metadata associated with the particular flock may be updated by the MFO 106 to indicate successful execution at 410. In one embodiment, metadata associated with the flock configuration of the particular flock may be updated.

[0116] Additionally, if execution is successful and a new capability (or capabilities) are issued at 412, this information may be persisted and provided to interested system components. For example, the capability service 112 may be notified of the newly issued capability. If a registry or database is used to track services issued for the data center, the registry or database may be updated with information indicating the issuance of the new capability.

[0117] A successful execution of a release may result in zero or more new capabilities being issued to the datacenter. Thus, this particular service may already be functioning in the datacenter with certain capabilities due to one or more previous successful release executions, but now additional capabilities may have been added due to the successful execution of the reentry release in 408.

[0118] As an example, the service may be an identity management service configured to provide authentication and authorization functionality at a data center. The flocking of the identity management service may identify one or more required and optional capability dependencies of the service. If the MFO 106 determines that all of the required capability dependencies of the service have been satisfied (e.g., published at the data center), it may schedule an initial release of the service even if one or more of the optional capability dependencies of the service have not been satisfied (e.g., one or more of the optional capability dependencies have not been published at the data center) at the time of scheduling the release. Upon successful execution of this release by the CIOS central 108 and the CIOS regional 110, an identity management service may be instantiated for the data center to provide certain authentication and authorization functionality. If the MFO 106 determines at a later time that the optional capability dependencies of the identity management service have been newly published, it may schedule a new re-entry release of the service per the above-described process shown in FIG. 4. Depending on the successful implementation of the new release (e.g., 408 above), additional capabilities may be added to the identity management service. For example, after the implementation of the new reentry release, the identity management service may be able to perform authorization using certain technologies (such as OAUTH 2.0 (Open Authorization) authorization) that were not possible after the initial release.

[0119] As described above, multiple releases may be scheduled and executed for a service. An initial release may be scheduled by the MFO 106 after all the required capability dependencies of the service as indicated in the service's flock configuration are satisfied and made available or published. This initial release and execution may add certain capabilities to the service. One or more subsequent releases may be scheduled and executed for the service once the service's optional capability dependencies become available in the data center. As a result of these one or more subsequent releases and executions, additional extended capabilities may be added to the service. Thus, when the service's optional capability dependencies are published, the flock configuration corresponding to the service is revisited and additional releases are scheduled and executed for the service (i.e., the flock corresponding to the service). This is referred to as reentrancy of service deployment because the same service (or the same service flock) is provisioned and deployed multiple times over time.

[0120] As discussed above, successful execution of the release at 408 may result in zero or more additional capabilities being issued to the data center. In some cases, the new capability issued as a result of execution of 408 may be another optional capability dependency of the same service (i.e., the same service block). In such a situation, the MFO 106 may determine that the second optional capability dependency of the service has been satisfied and, in response, may schedule yet another re-entry release of the service block and may follow the process of FIG. 4 for execution of the second re-entry release.

[0121] Release / Path Consolidation In some situations, multiple capabilities may be issued in a small time window where the issued capabilities are optional capability dependencies of the flock for the service. In this scenario, the MFO 106 may schedule multiple releases over time for the same service flock and create multiple paths for the releases if optional capability dependencies become available. In one embodiment, the MFO may be configured to implement a scheduling queue for scheduling multiple releases for a service flock in a data center. When a release is scheduled for a particular flock for a particular service, the MFO 106 creates a path for that flock and adds the path to the scheduling queue. The CIOS central 108 then selects a release from the queue that is scheduled for execution (e.g., a path corresponding to the release), starting from the release at the top of the queue, and executes the release in coordination with the CIOS regional 110.

[0122] The MFO may be configured to implement various types of scheduling queues for scheduling multiple releases for a service block. FIG. 5 is an exemplary diagram of a scheduling queue implemented by the MFO shown in FIG. 1 according to an embodiment. In one embodiment, the MFO may be configured to generate a generic scheduling queue 502 that is shared by different service blocks in a data center. For example, in the embodiment shown in FIG. 5, the generic scheduling queue 502 is shared by service A and service B in a data center and includes releases (SA, R1) 504 and (SA, R2) 508 scheduled for execution of the block for service A, and releases (SB, R1) 506 and (SB, R2) 510 scheduled for execution of the block for service B.

[0123] In an embodiment, the MFO may be configured to generate flock-specific queues for different service flocks in a data center. For example, as shown in FIG. 5, scheduling queue 512 is a flock-specific queue for service A that includes releases (SA, R1) 504 and (SA, R2) 508 scheduled for execution of flocks for service A. Scheduling queue 514 is a flock-specific queue for service B that includes releases (SB, R1) 506 and (SB, R2) 510 scheduled for execution of flocks for service B. Scheduling queues 502, 512, and 514 shown in FIG. 5 are for illustrative purposes only and are not meant to be limiting. In an alternative embodiment, the scheduling queues may be configured to store more or fewer scheduled releases for service flocks in a data center.

[0124] In the queue structures described above (i.e., scheduling queues 502, 512, and 514), for a particular queue, there may be multiple outstanding releases (multiple paths) in the queue for a particular flock, depending on the rate at which releases are scheduled to the queue and selected from the queue for execution by the MFO 106. In one embodiment, a determination that multiple outstanding releases exist in a queue (e.g., a flock-specific queue or a generic scheduling queue) may cause the MFO 106 to consolidate the multiple releases (paths) for the flock in the queue into a single consolidated release / path, if possible, and replace two or more releases / paths in the queue with the consolidated release / path for the flock. 5, a determination that there are two releases (SA,R1) 504 and (SA,R2) 508 scheduled for execution of a flock for service A in the scheduling queue 502 may cause the MFO 106 to, if possible, consolidate the two releases (paths) for the flock in the queue 502 into a single consolidated release / path and replace two or more releases / paths in the queue with the consolidated release / path. In some cases, the consolidated release / path may also be consolidated with another release / path in the queue.

[0125] 6 is an exemplary diagram of a combined release in a scheduling queue implemented by the MFO shown in FIG. 1, according to one embodiment. As shown in FIG. 6, a determination that there are two releases (SA, R1) 504 and (SA, R2) 508 scheduled for execution in a queue (e.g., generic scheduling queue 502) may cause the MFO 106 to combine the two releases (paths) in the queue into a single combined release / path, if possible, and replace the two or more releases / paths in the queue with combined release / path 604. Similarly, a determination that there are two releases (SB, R1) 506 and (SB, R2) 510 scheduled for execution in generic queue 502 of blocks for service B may cause the MFO 106 to combine the two releases (paths) in the queue into a single combined release / path, if possible, and replace the two or more releases / paths in the queue with combined release / path 606.

[0126] The consolidation is performed for efficiency. In many cases, the time required to execute a consolidated release / path is less than the total time required to execute the consolidated releases / paths individually. Also, in many cases, the compute, memory, and networking resources used to execute a consolidated release / path are less than the compute, memory, and networking resources required to execute the consolidated releases / paths individually. This is primarily due to the processing involved in executing a release / path. In one embodiment, executing a release involves generating a plan from the current configuration to the target configuration expressed in the release, and then executing this plan. Because creating and executing a plan is compute and memory intensive and time consuming, it is more efficient to consolidate multiple unexecuted paths into one path, and then create and apply a single plan. for example, At time T1, capability C1 is issued. At time T2, the MFO creates the first pass / release (P1) of a flock for service A (call it flock A) for which C1 is an optional capability dependency, and places it in a queue specific to flock A or a generic queue as described above. At time T3 (close to T1), capability C2 is issued. At time T4, the MFO creates a second pass / release (P2) for Flock A, where C2 is another optional capability dependency, and places it in the same queue as Flock A. Then, the MFO determines that two unexecuted paths P1 and P2 are in the queue for block A. Then, the MFO merges P1 and P2 into a single path P3, replaces P1 and P2 in the queue with the merged path P3, and provides path P3 to the CIOS for planning and execution.

[0127] FIG. 7 is a simplified flowchart 700 illustrating a process performed to generate and execute an integrated release, according to one embodiment. The process illustrated in FIG. 7 may be implemented in software (e.g., code, instructions, programs) executed by one or more processing units (e.g., processors, cores) of the respective systems, may be implemented using hardware, or a combination thereof. The software may be stored in a non-transitory storage medium (e.g., memory device). The method presented in FIG. 7 and described below is exemplary and not intended to be limiting. FIG. 7 shows various process steps occurring in a particular order or sequence, but this is not intended to be limiting. In an alternative embodiment, the process may be performed in some different order, or some steps may be performed in parallel. In some embodiments (such as the embodiment shown in FIG. 1), the process illustrated in FIG. 7 may be performed by MFO 106 in coordination with CIOS Central 108, CIOS Regional 110, and Capability Service 112.

[0128] In the embodiment shown in Figure 7, processing may be triggered when the MFO 106 determines that a new capability has been published (e.g., made available) at the data center. For example, in the embodiment shown in Figure 1, the capability service 112 is responsible for tracking published capabilities.

[0129] At 704, the MFO 106 may determine that the newly issued capability identified at 702 is an optional capability dependency of the particular block for a particular service for which the release of the particular block was previously scheduled and successfully executed.

[0130] At 706, the MFO 106 schedules a new “re-entry” release for the particular flock in response to the optional capability dependency being issued and adds the new release to a queue. As previously described, the MFO may add the new release to a general scheduling queue (e.g., 502) shared by multiple service flocks or to a queue specific to a particular flock for a particular service (e.g., 512 or 514).

[0131] At 708, the MFO 106 scans the queue to determine whether there are any pending releases in the queue for the particular flock. In one example, at least one of the pending releases includes a new release of the flock scheduled by the MFO at 706.

[0132] At 710, the MFO 106 generates a consolidated release of the flock by consolidating the unexecuted releases (ie, the unexecuted passes) of the flock.

[0133] At 712, MFO provides an integrated release to CIOS for planning and execution.

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

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

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

[0137] In some examples, IaaS deployment is the process of putting a new application or a new version of an application onto a prepared application server, etc. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed below the hypervisor layer (e.g., server, storage, network hardware, and virtualization) by the cloud provider. Thus, the customer may be responsible for handling (e.g., on self-service virtual machines (which can be spun up on demand)), middleware, and / or application deployment, etc.

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

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

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

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

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

[0143] VCN 806 may include a local peering gateway (LPG) 810 that may be communicatively coupled to a secure shell (SSH) VCN 812 via an LPG 810 included in the SSH VCN 812. The SSH VCN 812 may include an SSH subnet 814, and the SSH VCN 812 may be communicatively coupled to a control plane VCN 816 via an LPG 810 included in the control plane VCN 816. The SSH VCN 812 may also be communicatively coupled to a data plane VCN 818 via the LPG 810. The control plane VCN 816 and the data plane VCN 818 may be included in a service tenancy 819, which may be owned and / or operated by the IaaS provider.

[0144] The control plane VCN 816 may include a control plane demilitarized zone (DMZ) tier 820 that operates as a perimeter network (e.g., a portion of an enterprise network between an enterprise intranet and an external network). DMZ-based servers may help limit liability and limit intrusions. The DMZ tier 820 may also include one or more load balancer (LB) subnets 822, a control plane app tier 824 that may include an app subnet 826, and a control plane data tier 828 that may include a database (DB) subnet 830 (e.g., a front-end DB subnet and / or a back-end DB subnet). The LB subnet 822 included in the control plane DMZ tier 820 may be communicatively coupled to the app subnet 826 included in the control plane app tier 824 and an Internet gateway 834 that may be included in the control plane VCN 816, and the app subnet 826 may be communicatively coupled to the DB subnet 830, a service gateway 836, and a network address translation (NAT) gateway 838 included in the control plane data tier 828. The control plane VCN 816 may include a service gateway 836 and a NAT gateway 838 .

[0145] The control plane VCN 816 can include a data plane mirrored app layer 840 that can include an app subnet 826. The app subnet 826 included in the data plane mirrored app layer 840 can include a virtual network interface controller (VNIC) 842 that can run a compute instance 844. The compute instance 844 can communicatively couple the app subnet 826 of the data plane mirrored app layer 840 to the app subnet 826 that can be included in the data plane app layer 846.

[0146] The data plane VCN 818 may include a data plane app layer 846, a data plane DMZ layer 848, and a data plane data layer 850. The data plane DMZ layer 848 may include a LB subnet 822, which may be communicatively coupled to an app subnet 826 of the data plane app layer 846 and an Internet gateway 834 of the data plane VCN 818. The app subnet 826 may be communicatively coupled to a service gateway 836 of the data plane VCN 818 and a NAT gateway 838 of the data plane VCN 818. Additionally, the data plane data layer 850 may include a DB subnet 830, which may be communicatively coupled to the app subnet 826 of the data plane app layer 846.

[0147] The Internet gateways 834 of the control plane VCNs 816 and data plane VCNs 818 may be communicatively coupled to a metadata management service 852, which may be communicatively coupled to the public Internet 854. The public Internet 854 may be communicatively coupled to a NAT gateway 838 of the control plane VCNs 816 and data plane VCNs 818. The service gateways 836 of the control plane VCNs 816 and data plane VCNs 818 may be communicatively coupled to cloud services 856.

[0148] In some examples, a service gateway 836 in the control plane VCN 816 or the data plane VCN 818 can make application programming interface (API) calls to cloud services 856 without going through the public Internet 854. API calls from the service gateway 836 to the cloud services 856 can be unidirectional. The service gateway 836 can make API calls to the cloud services 856, and the cloud services 856 can send the requested data to the service gateway 836. However, the cloud services 856 do not have to initiate the API calls to the service gateway 836.

[0149] In some examples, the secure host tenancy 804 may be directly connected to an otherwise isolated service tenancy 819. The secure host subnet 808 may communicate with the SSH subnet 814 through the LPG 810, which may allow bidirectional communication through an otherwise isolated system. By connecting the secure host subnet 808 to the SSH subnet 814, the secure host subnet 808 is accessible to other entities in the service tenancy 819.

[0150] The control plane VCN 816 may enable configuration or provisioning of desired resources by users of the service tenancy 819. The desired resources provisioned in the control plane VCN 816 may be deployed or used in the data plane VCN 818. In some examples, the control plane VCN 816 may be isolated from the data plane VCN 818, and a data plane mirror app layer 840 of the control plane VCN 816 may communicate with a data plane app layer 846 of the data plane VCN 818 via a VNIC 842 that may be included in the data plane mirror app layer 840 and the data plane app layer 846.

[0151] In some examples, a user or customer of the system may make a request (e.g., perform a create, read, update, or delete (CRUD) operation) over the public Internet 854, which may send the request to the metadata management service 852. The metadata management service 852 may send the request to the control plane VCN 816 through the Internet Gateway 834. The request may be received by the LB Subnet 822 in the control plane DMZ layer 820. The LB Subnet 822 may determine that the request is valid, and in response to this determination, the LB Subnet 822 may send the request to the app Subnet 826 in the control plane app layer 824. If the request is validated and a call to the public Internet 854 is required, the call to the public Internet 854 may be sent to the NAT Gateway 838, which may make the call to the public Internet 854. Metadata that may be desirable to store with the request may be stored in the DB Subnet 830.

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

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

[0154] In another embodiment, the LB subnet 822 included in the control plane VCN 816 can be configured to receive signals from the service gateway 836. In this embodiment, the control plane VCN 816 and the data plane VCN 818 can be configured to be called by the IaaS provider's customers without calling the public internet 854. The IaaS provider's customers may desire this embodiment because databases they use can be stored in a service tenancy 819 that is controlled by the IaaS provider and can be isolated from the public internet 854.

[0155] 9 is a block diagram 900 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 902 (e.g., service operator 802 of FIG. 8 ) may be communicatively coupled to a virtual cloud network (VCN) 906 (e.g., VCN 806 of FIG. 8 ) and a secure host tenancy 904 (e.g., secure host tenancy 804 of FIG. 8 ), which may include a secure shell (SSH) VCN 912 (e.g., SSH VCN 812 of FIG. 8 ). The VCN 906 may comprise a local peering gateway (LPG) 910, which may be communicatively coupled to an SSH VCN 912 via an LPG 810 (e.g., LPG 810 of FIG. 8 ) included in the SSH VCN 912 (e.g., SSH VCN 812 of FIG. 8 ). SSH VCN 912 can include an SSH subnet 914 (e.g., SSH subnet 814 in FIG. 8 ), and SSH VCN 912 can be communicatively coupled to a control plane VCN 916 via an LPG 910 that is included in a control plane VCN 916 (e.g., control plane VCN 816 in FIG. 8 ). The control plane VCN 916 can be included in a service tenancy 919 (e.g., service tenancy 819 in FIG. 8 ), and the data plane VCN 918 (e.g., data plane VCN 818 in FIG. 8 ) can be included in a customer tenancy 921, which can be owned or operated by a user or customer of the system.

[0156] The control plane VCN 916 may include a control plane DMZ tier 920 (e.g., control plane DMZ tier 820 of FIG. 8 ) that may include a LB subnet 922 (e.g., LB subnet 822 of FIG. 8 ), a control plane app tier 924 (e.g., control plane app tier 824 of FIG. 8 ) that may include an app subnet 926 (e.g., app subnet 826 of FIG. 8 ), and a control plane data tier 928 (e.g., control plane data tier 828 of FIG. 8 ) that may include a DB subnet 930 (e.g., similar to database (DB) subnet 830 of FIG. 8 ). The LB subnet 922 included in the control plane DMZ layer 920 may be communicatively coupled to an app subnet 926 included in the control plane app layer 924 and an Internet gateway 934 (e.g., Internet gateway 834 in FIG. 8 ) that may be included in the control plane VCN 916, and the app subnet 926 may be communicatively coupled to a DB subnet 930, a service gateway 936 (e.g., service gateway 836 in FIG. 8 ), and a network address translation (NAT) gateway 938 (e.g., NAT gateway 838 in FIG. 8 ) included in the control plane data layer 928. The control plane VCN 916 may comprise the service gateway 936 and the NAT gateway 938.

[0157] The control plane VCN 916 may include a data plane mirror app layer 940 (e.g., data plane mirror app layer 840 of FIG. 8 ), which may include an app subnet 926. The app subnet 926 included in the data plane mirror app layer 940 may include a virtual network interface controller (VNIC) 942 (e.g., VNIC 842) on which a compute instance 944 (e.g., similar to compute instance 844 of FIG. 8 ) may run. The compute instance 944 may facilitate communication between the app subnet 926 of the data plane mirror app layer 940 and the app subnet 926 included in the data plane app layer 946 via the VNIC 942 included in the data plane mirror app layer 940 and the VNIC 942 included in the data plane app layer 946 (e.g., data plane app layer 846 of FIG. 8 ).

[0158] An internet gateway 934 included in the control plane VCN 916 may be communicatively coupled to a metadata management service 952 (e.g., metadata management service 852 of FIG. 8 ), which may be communicatively coupled to a public internet 954 (e.g., public internet 854 of FIG. 8 ). The public internet 954 may be communicatively coupled to a NAT gateway 938 included in the control plane VCN 916. A service gateway 936 included in the control plane VCN 916 may be communicatively coupled to cloud services 956 (e.g., cloud services 856 of FIG. 8 ).

[0159] In some examples, the data plane VCN 918 may be included in the customer tenancy 921. In this case, the IaaS provider may provide a control plane VCN 916 for each customer, and the IaaS provider may configure a unique compute instance 944 for each customer, which is included in the service tenancy 919. Each compute instance 944 may enable communication between the control plane VCN 916 in the service tenancy 919 and the data plane VCN 918 in the customer tenancy 921. The compute instance 944 may enable deployment or use of resources provisioned in the control plane VCN 916 in the service tenancy 919 in the data plane VCN 918 in the customer tenancy 921.

[0160] In another example, an IaaS provider customer may have a database that resides in customer tenancy 921. In this example, control plane VCN 916 may include data plane mirror app layer 940, which may include app subnet 926. Data plane mirror app layer 940 may reside in data plane VCN 918, but may not reside in data plane VCN 918. That is, data plane mirror app layer 940 may be accessible to customer tenancy 921, but may not reside in data plane VCN 918, and may not be owned or operated by the IaaS provider customer. Data plane mirror app layer 940 may be configured to make calls to data plane VCN 918, but may not be configured to make calls to any entities included in control plane VCN 916. A customer may desire deployment or use of resources in the data plane VCN 918 that have been provisioned in the control plane VCN 916, and the data plane mirror app layer 940 may facilitate the deployment or other use of the resources that the customer desires.

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

[0162] In some embodiments, calls made by the service gateway 936 allow the cloud services 956 to access services that may not be in the public internet 954, the control plane VCN 916, or the data plane VCN 918. The connection between the cloud services 956 and the control plane VCN 916 or the data plane VCN 918 may not be live or continuous. The cloud services 956 may be on different networks owned or operated by the IaaS provider. The cloud services 956 may be configured to receive calls from the service gateway 936 or may not be configured to receive calls from the public internet 954. Some cloud services 956 may be isolated from other cloud services 956, and the control plane VCN 916 may be isolated from cloud services 956 that may not be in the same region as the control plane VCN 916. For example, the control plane VCN 916 may be located in “Region 1” and the cloud service “Deployment 8” may be located in Region 1 and Region 2. If a call to deployment 8 is made by a service gateway 936 included in a control plane VCN 916 located in region 1, the call may be sent to the deployment 8 in region 1. In this example, the control plane VCN 916 or the deployment 8 in region 1 may not be communicatively coupled to or in communication with the deployment 8 in region 2.

[0163] 10 is a block diagram 1000 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 1002 (e.g., service operator 802 of FIG. 8 ) may be communicatively coupled to a secure host tenancy 1004 (e.g., secure host tenancy 804 of FIG. 8 ), which may include a virtual cloud network (VCN) 1006 (e.g., VCN 806 of FIG. 8 ) and a secure host subnet 1008 (e.g., secure host subnet 808 of FIG. 8 ). The VCN 1006 may comprise an LPG 1010, which may be communicatively coupled to an SSH VCN 1012 via an LPG 1010 (e.g., LPG 810 of FIG. 8 ) included in the SSH VCN 1012 (e.g., SSH VCN 812 of FIG. 8 ). SSH VCN 1012 may include an SSH subnet 1014 (e.g., SSH subnet 814 in FIG. 8 ), and SSH VCN 1012 may be communicatively coupled to a control plane VCN 1016 via an LPG 1010 included in the control plane VCN 1016 (e.g., control plane VCN 816 in FIG. 8 ) and to a data plane VCN 1018 via an LPG 1010 included in the data plane VCN 1018 (e.g., data plane VCN 818 in FIG. 8 ). The control plane VCN 1016 and the data plane VCN 1018 may be included in a service tenancy 1019 (e.g., service tenancy 819 in FIG. 8 ).

[0164] The control plane VCN 1016 may include a control plane DMZ tier 1020 (e.g., control plane DMZ tier 820 of FIG. 8 ) that may include a load balancer (LB) subnet 1022 (e.g., LB subnet 822 of FIG. 8 ), a control plane app tier 1024 (e.g., control plane app tier 824 of FIG. 8 ) that may include an app subnet 1026 (e.g., similar to app subnet 826 of FIG. 8 ), and a control plane data tier 1028 (e.g., control plane data tier 828 of FIG. 8 ) that may include a DB subnet 1030. The LB subnet 1022 included in the control plane DMZ tier 1020 may be communicatively coupled to an app subnet 1026 included in the control plane app tier 1024 and an Internet gateway 1034 (e.g., Internet gateway 834 in FIG. 8 ) that may be included in the control plane VCN 1016, and the app subnet 1026 may be communicatively coupled to a DB subnet 1030, a service gateway 1036 (e.g., service gateway in FIG. 8 ), and a network address translation (NAT) gateway 1038 (e.g., NAT gateway 838 in FIG. 8 ) included in the control plane data tier 1028. The control plane VCN 1016 may comprise the service gateway 1036 and the NAT gateway 1038.

[0165] The data plane VCN 1018 may include a data plane app layer 1046 (e.g., data plane app layer 846 of FIG. 8 ), a data plane DMZ layer 1048 (e.g., data plane DMZ layer 848 of FIG. 8 ), and a data plane data layer 1050 (e.g., data plane data layer 850 of FIG. 8 ). The data plane DMZ layer 1048 may include a LB subnetwork 1022 that may be communicatively coupled to a trusted app subnetwork 1060 and a non-trusted app subnetwork 1062 of the data plane app layer 1046 and an Internet gateway 1034 included in the data plane VCN 1018. The trusted app subnetwork 1060 may be communicatively coupled to a service gateway 1036 included in the data plane VCN 1018, a NAT gateway 1038 included in the data plane VCN 1018, and a DB subnetwork 1030 included in the data plane data layer 1050. The untrusted app subnet 1062 may be communicatively coupled to a service gateway 1036 included in the data plane VCN 1018 and a DB subnet 1030 included in the data plane data layer 1050. The data plane data layer 1050 may include a DB subnet 1030 that may be communicatively coupled to a service gateway 1036 included in the data plane VCN 1018.

[0166] The untrusted app subnet 1062 may include one or more primary VNICs 1064(1)-1064(N), which may be communicatively coupled to tenant virtual machines (VMs) 1066(1)-1066(N). Each tenant VM 1066(1)-1066(N) may be communicatively coupled to a respective app subnet 1067(1)-1067(N), which may be included in a respective container egress VCN 1068(1)-1068(N), which may be included in a respective customer tenancy 1070(1)-1070(N). Each secondary VNIC 1072(1)-1072(N) may facilitate communication between the untrusted app subnet 1062 included in the data plane VCN 1018 and the app subnets included in the respective container egress VCNs 1068(1)-1068(N). Each container egress VCN 1068(1)-1068(N) may include a NAT gateway 1038 that may be communicatively coupled to the public Internet 1054 (e.g., public Internet 854 in FIG. 8).

[0167] An Internet gateway 1034 included in the control plane VCN 1016 and the data plane VCN 1018 may be communicatively coupled to a metadata management service 1052 (e.g., metadata management system 852 of FIG. 8 ), which may be communicatively coupled to the public Internet 1054. The public Internet 1054 may be communicatively coupled to a NAT gateway 1038 included in the control plane VCN 1016 and the data plane VCN 1018. A service gateway 1036 included in the control plane VCN 1016 and the data plane VCN 1018 may be communicatively coupled to cloud services 1056.

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

[0169] In some examples, a customer of an IaaS provider may grant temporary network access to the IaaS provider to request functionality provided in the data plane app layer 1046. The code to perform this functionality may be configured to run in VMs 1066(1)-1066(N) and may not be configured to run anywhere else on the data plane VCN 1018. Each VM 1066(1)-1066(N) may be connected to one customer tenancy 1070. Each container 1071(1)-1071(N) contained in VMs 1066(1)-1066(N) may be configured to run code. In this case, there may be double isolation (the containers 1071(1)-1071(N) executing the code may be contained in VMs 1066(1)-1066(N) contained in at least the untrusted app subnet 1062), which may help prevent erroneous or unwanted code from damaging the IaaS provider's network or a different customer's network. The containers 1071(1)-1071(N) may be communicatively coupled to the customer tenancy 1070 and may be configured to send or receive data to the customer tenancy 1070. The containers 1071(1)-1071(N) may not be configured to send or receive data to any other entity in the data plane VCN 1018. Upon completion of the code execution, the IaaS provider may disable or discard the containers 1071(1)-1071(N).

[0170] In some embodiments, the Trusted App Subnet 1060 may execute code that may be owned or operated by the IaaS provider. In this embodiment, the Trusted App Subnet 1060 may be communicatively coupled to the DB Subnet 1030 and may be configured to perform CRUD operations on the DB Subnet 1030. The Non-Trusted App Subnet 1062 may be communicatively coupled to the DB Subnet 1030, but in this embodiment, may be configured to perform read operations on the DB Subnet 1030. The Containers 1071(1)-1071(N) included in each customer's VMs 1066(1)-1066(N) that may execute code from the customer may not be communicatively coupled to the DB Subnet 1030.

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

[0172] 11 is a block diagram 1100 illustrating another example pattern of an IaaS architecture, according to at least one embodiment. A service operator 1102 (e.g., service operator 802 of FIG. 8 ) may be communicatively coupled to a secure host tenancy 1104 (e.g., secure host tenancy 804 of FIG. 8 ), which may include a virtual cloud network (VCN) 1106 (e.g., VCN 806 of FIG. 8 ) and a secure host subnet 1108 (e.g., secure host subnet 808 of FIG. 8 ). The VCN 1106 may comprise an LPG 1110, which may be communicatively coupled to an SSH VCN 1112 via an LPG 1110 (e.g., LPG 810 of FIG. 8 ) included in the SSH VCN 1112 (e.g., SSH VCN 812 of FIG. 8 ). SSH VCN 1112 may include an SSH subnet 1114 (e.g., SSH subnet 814 in FIG. 8 ), and SSH VCN 1112 may be communicatively coupled to a control plane VCN 1116 via an LPG 1110 included in the control plane VCN 1116 (e.g., control plane VCN 816 in FIG. 8 ) and to a data plane VCN 1118 via an LPG 1110 included in the data plane VCN 1118 (e.g., data plane VCN 818 in FIG. 8 ). The control plane VCN 1116 and the data plane VCN 1118 may be included in a service tenancy 1119 (e.g., service tenancy 819 in FIG. 8 ).

[0173] The control plane VCN 1116 may include a control plane DMZ layer 1120 (e.g., control plane DMZ layer 820 of FIG. 8 ) that may include a LB subnet 1122 (e.g., LB subnet 822 of FIG. 8 ), a control plane app layer 1124 (e.g., control plane app layer 824 of FIG. 8 ) that may include an app subnet 1126 (e.g., app subnet 826 of FIG. 8 ), and a control plane data layer 1128 (e.g., control plane data layer 828 of FIG. 8 ) that may include a DB subnet 1130 (e.g., DB subnet 1030 of FIG. 10 ). The LB subnet 1122 included in the control plane DMZ layer 1120 may be communicatively coupled to an app subnet 1126 included in the control plane app layer 1124 and an Internet gateway 1134 (e.g., Internet gateway 834 in FIG. 8 ) that may be included in the control plane VCN 1116, and the app subnet 1126 may be communicatively coupled to a DB subnet 1130, a service gateway 1136 (e.g., service gateway in FIG. 8 ), and a network address translation (NAT) gateway 1138 (e.g., NAT gateway 838 in FIG. 8 ) included in the control plane data layer 1128. The control plane VCN 1116 may comprise the service gateway 1136 and the NAT gateway 1138.

[0174] The data plane VCN 1118 can include a data plane app layer 1146 (e.g., data plane app layer 846 in FIG. 8 ), a data plane DMZ layer 1148 (e.g., data plane DMZ layer 848 in FIG. 8 ), and a data plane data layer 1150 (e.g., data plane data layer 850 in FIG. 8 ). The data plane DMZ layer 1148 can include a trusted app subnet 1160 (e.g., trusted app subnet 1060 in FIG. 10 ) and a non-trusted app subnet 1162 (e.g., non-trusted app subnet 1062 in FIG. 10 ) of the data plane app layer 1146 and a LB subnet 1122 that can be communicatively coupled to an Internet gateway 1134 included in the data plane VCN 1118. The trusted app subnet 1160 may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118, a NAT gateway 1138 included in the data plane VCN 1118, and a DB subnet 1130 included in the data plane data layer 1150. The untrusted app subnet 1162 may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118 and a DB subnet 1130 included in the data plane data layer 1150. The data plane data layer 1150 may comprise a DB subnet 1130 that may be communicatively coupled to a service gateway 1136 included in the data plane VCN 1118.

[0175] The untrusted app subnet 1162 may include primary VNICs 1164(1)-1164(N), which may be communicatively coupled to tenant virtual machines (VMs) 1166(1)-1166(N) residing within the untrusted app subnet 1162. Each tenant VM 1166(1)-1166(N) may execute code in a container 1167(1)-1167(N), respectively, and may be communicatively coupled to an app subnet 1126, which may be included in a data plane app layer 1146, which may be included in a container egress VCN 1168. The secondary VNICs 1172(1)-1172(N), respectively, may facilitate communication between the untrusted app subnet 1162, which is included in the data plane VCN 1118, and the app subnet, which is included in the container egress VCN 1168. The container egress VCN may include a NAT gateway 1138 that may be communicatively coupled to the public Internet 1154 (e.g., the public Internet 854 in FIG. 8).

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

[0177] In some examples, the pattern illustrated by the architecture of block diagram 1100 of FIG. 11 may be an exception to the pattern illustrated by the architecture of block diagram 1000 of FIG. 10 and may be desirable for customers of an IaaS provider when the IaaS provider cannot communicate directly with the customer (e.g., in a non-connected region). Each of the containers 1167(1)-1167(N) contained in a VM 1166(1)-1166(N) for each customer may be accessible in real time by the customer. The containers 1167(1)-1167(N) may be configured to make calls to each of the secondary VNICs 1172(1)-1172(N) contained in the app subnet 1126 of the data plane app tier 1146, which may be contained in the container egress VCN 1168. Secondary VNICs 1172(1)-1172(N) can send the call to NAT gateway 1138, which may send the call to public Internet 1154. In this example, containers 1167(1)-1167(N) that are accessible in real time by customers may be isolated from control plane VCN 1116 and may be isolated from other entities included in data plane VCN 1118. Containers 1167(1)-1167(N) may also be isolated from resources of other customers.

[0178] In another example, a customer can use containers 1167(1)-1167(N) to call cloud service 1156. In this example, the customer can execute code in containers 1167(1)-1167(N) that requests a service from cloud service 1156. Containers 1167(1)-1167(N) can send the request to secondary VNICs 1172(1)-1172(N), which can send the request to a NAT gateway, which can send the request to public internet 1154. Public internet 1154 can send the request to LB subnet 1122 included in control plane VCN 1116 via internet gateway 1134. In response to determining that the request is valid, the LB subnet can send the request to the app subnet 1126, which can send the request to the cloud service 1156 via the service gateway 1136.

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

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

[0181] 12 illustrates an exemplary computer system 1200 upon which various embodiments may be implemented. System 1200 may be used to implement any of the computer systems described above. As shown in the figure, computer system 1200 includes a processing unit 1204 that communicates with a number of peripheral subsystems via a bus subsystem 1202. The peripheral subsystems may include a processing acceleration unit 1206, an I / O subsystem 1208, a storage subsystem 1218, and a communication subsystem 1224. The storage subsystem 1218 includes a tangible computer readable storage medium 1222 and a system memory 1210.

[0182] Bus subsystem 1202 provides a mechanism for allowing the various components and subsystems of computer system 1200 to communicate with each other as desired. Although bus subsystem 1202 is shown diagrammatically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses. Bus subsystem 1202 may be any of a number of types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. For example, such architectures may include an Industry Standard Architecture (ISA) bus, which may be implemented as a mezzanine bus manufactured in accordance with the IEEE P1386.1 standard, a MicroChannel Architecture (MCA) bus, an Enhanced ISA (EISA) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus.

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

[0184] In various embodiments, the processing unit 1204 may execute various programs in response to program code and may maintain multiple simultaneously executing programs or processes. At any given time, some or all of the program code being executed may reside on the processor 1204 and / or on the storage subsystem 1218. With suitable programming, the processor 1204 may provide the various functions discussed above. The computer system 1200 may also include a processing acceleration unit 1206, which may include a digital signal processor (DSP), a special purpose processor, and / or the like.

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

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

[0187] User interface output devices may include non-visual displays such as a display subsystem, indicator lights, or audio output devices. The display subsystem may be a flat panel device such as one using a cathode ray tube (CRT), a liquid crystal display (LCD) or a plasma display, a projection device, a touch screen, etc. In general, use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from computer system 1200 to a user or to another computer. For example, user interface output devices may include, but are not limited to, a variety of display devices that visually convey text, graphics, and audio / video information, such as monitors, printers, speakers, headphones, automobile navigation systems, plotters, audio output devices, and modems.

[0188] Computer system 1200 may also include a storage subsystem 1218 that includes software elements illustrated here as currently located within system memory 1210. System memory 1210 may store program instructions that can be loaded and executed by processing unit 1204, as well as data generated during the execution of these programs.

[0189] Depending on the configuration and type of computer system 1200, system memory 1210 may be volatile (such as random access memory (RAM)) and / or non-volatile (such as read-only memory (ROM), flash memory, etc.). RAM typically contains data and / or program modules immediately accessible to and / or currently being operated on and executed by processing unit 1204. In some embodiments, system memory 1210 may include a number of different types of memory, such as static random access memory (SRAM) or dynamic random access memory (DRAM). In some embodiments, ROM may typically store a basic input / output system (BIOS) containing the basic routines that help transfer information between elements within computer system 1200, such as during start-up. Also, by way of non-limiting example, system memory 1210 illustrates application programs 1212, program data 1214, and operating system 1216, which may include client applications, web browsers, mid-tier applications, relational database management systems (RDBMS), and the like. By way of example, operating systems 1216 may include various versions of Microsoft Windows, Apple Macintosh, and / or Linux operating systems, various commercially available UNIX or UNIX-like operating systems (including, but not limited to, various GNU / Linux operating systems, Google Chrome OS, etc.), and / or mobile operating systems such as iOS, Windows Phone, Android OS, BlackBerry OS, and Palm OS operating systems.

[0190] Storage subsystem 1218 may also provide a tangible computer readable storage medium for storing basic programming and data constructs that provide the functionality of some embodiments. Storage subsystem 1218 may store software (programs, code modules, instructions) that, when executed by a processor, provide the functionality described above. These software modules or instructions may be executed by processing unit 1204. Storage subsystem 1218 may also provide a repository for storing data used in accordance with the present disclosure.

[0191] Storage subsystem 1200 may also include a computer readable storage medium reader 1220 that may be further coupled to a computer readable storage medium 1222. Together, optionally, computer readable storage medium 1222, in combination with system memory 1210, may comprehensively represent remote, local, fixed, and / or removable storage devices, as well as storage media for temporarily and / or permanently containing, storing, transmitting, and retrieving computer readable information.

[0192] Additionally, the computer readable storage medium 1222 containing the code or portions of code may include any suitable medium known or used in the art (including storage media and communication media), including, but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing and / or transmitting information. This may include tangible computer readable storage media, such as RAM, ROM, Electronically Erasable Programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media. This may also include non-tangible computer readable media, such as a data signal, data transmission, or any other medium usable to transmit the desired information and accessible by computer system 1200.

[0193] By way of example, the computer readable storage medium 1222 may include hard disk drives that read from and write to non-removable, non-volatile magnetic media, magnetic disk drives that read from and write to removable, non-volatile magnetic disks, and optical disk drives that read from and write to removable, non-volatile optical disks, such as CD ROMs, DVDs, Blu-Ray disks, or other optical media. The computer readable storage medium 1222 may include, but is not limited to, Zip drives, flash memory cards, Universal Serial Bus (USB) flash drives, Secure Digital (SD) cards, DVD disks, digital video tapes, and the like. The computer readable storage medium 1222 may also include flash memory-based SSDs, enterprise flash drives, solid-state drives (SSDs) based on non-volatile memory, such as solid-state ROMs, solid-state RAMs, dynamic RAMs, static RAMs, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory-based SSDs. The disk drives and their associated computer-readable media may provide non-volatile storage of computer readable instructions, data structures, program modules, and other data for the computer system 1200.

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

[0195] Also, in some embodiments, the communications subsystem 1224 can receive incoming communications in the form of structured and / or unstructured data feeds 1226, event streams 1228, event updates 1230, etc., on behalf of one or more users who may be using the computer system 1200.

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

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

[0198] The communications subsystem 1224 may also be configured to output structured and / or unstructured data feeds 1226, event streams 1228, event updates 1230, etc. to one or more databases that may be in communication with one or more streaming data source computers coupled to the computer system 1200.

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

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

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

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

[0203] The embodiments may be realised by using a computer program product comprising a computer program / instructions which, when executed by a processor, cause the processor to perform any of the methods described in the present disclosure.

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

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

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

[0207] Preferred embodiments of the present disclosure are described herein, including the best mode known for carrying out the present disclosure. Modifications of these preferred embodiments may become apparent to those skilled in the art upon reading the above description. Such modifications may be adopted by those skilled in the art as necessary, and the present disclosure may be practiced differently from the specific descriptions herein. Accordingly, the present disclosure includes all modifications and equivalents of the subject matter recited in the claims appended hereto as permitted by applicable law. Moreover, unless otherwise indicated herein, the present disclosure includes any combination of the above-described elements in all possible variations thereof.

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

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

Claims

1. 1. A method comprising: determining that a new capability has been issued at the data center; identifying the newly issued capability as an optional capability dependency of the block for the service; Including, a first release of the flock has been previously scheduled and executed, the flock including a set of one or more resources for providing the service; The method comprises: scheduling a second release of the floc in response to said identifying; performing the second release of the flocs; The method further comprises:

2. The method of claim 1 , wherein the first release is scheduled and executed when all of the flock's required capability dependencies have been published.

3. The method of claim 2 , wherein the required capability dependencies of the flock are identified as capabilities that were published at the data center before the first release of the flock was scheduled and executed.

4. The method of claim 1 , wherein the optional capability dependencies of the flock are identified as capabilities that do not need to be issued at the data center before the first release of the flock is scheduled and executed.

5. The method of claim 1 , wherein the set of one or more resources includes infrastructure components and artifacts associated with the service.

6. The method of claim 1 , wherein information identifying the flock for the service is declared in a flock configuration of the service, and the flock configuration of the service identifies the set of one or more resources associated with the service.

7. The method of claim 1 , wherein the newly published capability identifies a functional unit associated with the block of the service and identifies the set of one or more resources associated with the service.

8. The method comprises: Obtaining a dependency graph; using the dependency graph to identify the newly issued capability as an optional capability dependency of the block for the service; further comprising The method of claim 1 , wherein the dependency graph is an acyclic dependency graph.

9. Executing the second release includes: generating a plan; the plan identifies a current configuration of the data center and a target configuration of the data center associated with the execution of the second release; Implementing said plan The method of claim 1 further comprising:

10. The method of claim 9 , wherein executing the plan results in additional issuance of new capabilities at the data center.

11. The method of claim 9 , further comprising updating metadata associated with a flock configuration of the flock for the service in response to executing the plan.

12. A cloud infrastructure orchestration system, comprising: Memory and one or more processors configured to perform the processing; 12. A cloud infrastructure orchestration system comprising: a cloud infrastructure orchestration system for orchestrating a cloud infrastructure comprising: a cloud infrastructure orchestration system for orchestrating a cloud infrastructure;

13. A program that causes one or more processors to execute the method described in any one of claims 1 to 11.

Images