WO2023154680A1 - Environnement d'amorçage virtuel pour construire des centres de données régionaux - Google Patents

Environnement d'amorçage virtuel pour construire des centres de données régionaux Download PDF

Info

Publication number
WO2023154680A1
WO2023154680A1 PCT/US2023/062056 US2023062056W WO2023154680A1 WO 2023154680 A1 WO2023154680 A1 WO 2023154680A1 US 2023062056 W US2023062056 W US 2023062056W WO 2023154680 A1 WO2023154680 A1 WO 2023154680A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
region
virtual
vcn
data
Prior art date
Application number
PCT/US2023/062056
Other languages
English (en)
Inventor
Michel Belleau
David Charles Podjaski
Saad Mazahir
Erik Joseph Miller
Original Assignee
Oracle International Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US18/105,779 external-priority patent/US20230251888A1/en
Application filed by Oracle International Corporation filed Critical Oracle International Corporation
Publication of WO2023154680A1 publication Critical patent/WO2023154680A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5061—Partitioning or combining of resources
    • G06F9/5072—Grid computing

Definitions

  • This disclosure relates to building regional data centers. More specifically, this disclosure describes techniques for using a virtual bootstrap environment to deploy resources to data center infrastructure during the building of a regional data center.
  • Cloud infrastructure providers may offer cloud computing infrastructure and related services in numerous geographical areas worldwide.
  • the cloud infrastructure provider may operate one or more data centers corresponding to a localized geographical area. These data centers may be included as part of a "region," a logical abstraction of the geographical area and the computing resources of the one or more data centers. Building new regions can include provisioning the computing resources, configuring infrastructure, and deploying code to those resources.
  • Conventional techniques for building a region involve significant manual operations. Bootstrapping existing services into a new region may be challenging since a service may depend on the functionality of other existing services and/or resources in the region. Relying on manual operations to bootstrap services and/or build regions incurs substantial time costs, risks associated with manual configuration errors, and may not scale well. BRIEF SUMMARY
  • Embodiments of the present disclosure relate to creating a bootstrapping environment to support building a region.
  • the region build can include bootstrapping (e.g., provisioning and/or deploying) resources (e.g., infrastructure components, artifacts, etc.) for any suitable number of services in a region (e.g., a geographical location associated with one or more data centers).
  • the bootstrapping environment may be a virtual environment (e.g., a virtual cloud network) within an existing region.
  • the virtual bootstrapping environment (ViBE) may therefore be constructed and configured in the existing region in advance of the region build process.
  • Services may be deployed to the ViBE to support bootstrapping operations into a target region (e.g., the region to be built in the region build process).
  • the services in the ViBE may be used to provision computing resources (e.g., bare metal computing hosts, virtual machines, storage, etc.) in the target region.
  • the services in the ViBE may also be used to deploy services to the target region, including instances of the services in the ViBE.
  • a cloud infrastructure orchestration service in conjunction with the ViBE, the new region may be built intelligently and automatically.
  • One embodiment is directed to a computer-implemented method that can include generating, by a distributed computing system of a cloud service provider, a virtual cloud network in a host region.
  • the method can further include implementing a virtual bootstrapping environment in the virtual cloud network and deploying a first service in the virtual bootstrapping environment.
  • the method can include establishing a network connection between the virtual cloud network and a target region.
  • one or more additional services, including a second service may be deployed in the virtual bootstrapping environment.
  • the second service can be used to provision infrastructure resources in the target region.
  • the host region can include a host data center, while the target region can include a target data center.
  • the method can also include deploying resources of the virtual bootstrapping environment to the target region.
  • the first service may be used to deploy the resources, and the resources may be deployed via the network connection.
  • the resources may be deployed onto the infrastructure resources provisioned using the second service.
  • the network connection can include a virtual private network connection that uses one or more IPSec tunnels.
  • Another embodiment is directed to a computing device comprising one or more processors and instructions that, when executed by the one or more processors, cause the computing device to perform the method(s) disclosed herein.
  • Still another embodiment is directed to a non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors of a computing cluster, cause the computing cluster to perform the method(s) disclosed herein.
  • 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.
  • CIOS Cloud Infrastructure Orchestration Service
  • FIG. 2 is a block diagram for illustrating an environment and method for building a virtual bootstrap environment (ViBE), according to at least one embodiment.
  • ViBE virtual bootstrap environment
  • FIG. 3 is a block diagram for illustrating an environment and method for bootstrapping services to a target region utilizing the ViBE, according to at least one embodiment.
  • FIG. 4 is a simplified diagram depicting a target region and multiple host regions for supporting a ViBE, according to at least one embodiment.
  • FIG. 5 is a block diagram depicting an example flow for executing operations for provisioning and deploying services to a region, according to at least one embodiment.
  • FIG. 6 is a block diagram depicting an example architecture of a network connection between a ViBE and a target region, according to at least one embodiment.
  • FIG. 7 is another block diagram depicting an example architecture of a network connection between a remote access tenancy and a ViBE, according to at least one embodiment.
  • FIG. 8 illustrates an example method for bootstrapping a region using services in a ViBE, according to at least one embodiment.
  • FIG. 9 is a block diagram illustrating one pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 10 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 11 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 12 is a block diagram illustrating another pattern for implementing a cloud infrastructure as a service system, according to at least one embodiment.
  • FIG. 13 is a block diagram illustrating an example computer system, according to at least one embodiment.
  • cloud service is generally used to refer to a service or functionality that is made available by a CSP to users or customers on demand (e.g., via a subscription model) using systems and infrastructure (cloud infrastructure) provided by the CSP.
  • cloud infrastructure systems and infrastructure
  • the servers and systems that make up the CSP's infrastructure, and which are used to provide a cloud service to a customer are separate from the customer's own on-premises servers and systems. Customers can thus avail themselves of cloud services provided by the CSP without having to purchase separate hardware and software resources for the services.
  • Cloud services are designed to provide a subscribing customer easy, scalable, and on-demand access to applications and computing resources without the customer having to invest in procuring the infrastructure that is used for providing the services or functions.
  • Various different types or models of cloud services may be offered such as Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), Infrastructure-as-a-Service (laaS), and others.
  • SaaS Software-as-a-Service
  • PaaS Platform-as-a-Service
  • laaS Infrastructure-as-a-Service
  • a customer can subscribe to one or more cloud services provided by a CSP.
  • the customer can be any entity such as an individual, an organization, an enterprise, and the like.
  • a CSP is responsible for providing the infrastructure and resources that are used for providing cloud services to subscribing customers.
  • the resources provided by the CSP can include both hardware and software resources. These resources can 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), identity, and other resources.
  • 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
  • identity e.g., identity, and other resources.
  • the resources provided by a CSP for providing a set of cloud services CSP are organized into data centers.
  • a data center may be configured to provide a particular set of cloud services.
  • the CSP is responsible for equipping the data center with infrastructure and resources that are used to provide that particular set of cloud services.
  • a CSP
  • Data centers provided by a CSP may be hosted in different regions.
  • a region is a localized geographic area and may be identified by a region name. Regions are generally independent of each other and can be separated by vast distances, such as across countries or even continents. Regions are grouped into realms. Examples of regions for a CSP may include US West, US East, Australia East, Australia Southeast, and the like.
  • a region can include one or more data centers, where the data centers are located within a certain geographic area corresponding to the region. As an example, the data centers in a region may be located in a city within that region.
  • data centers in the US West region may be located in San Jose, California; data centers in the US East region may be located in Ashburn, Virginia; data centers in the Australia East region may be located in Sydney, Australia; data centers in the Australia Southeast region may be located in Melbourne, Australia; and the like.
  • Data centers within a region may be organized into one or more availability domains, which are used for high availability and disaster recovery purposes.
  • An availability domain can include one or more data centers within a region.
  • Availability domains within a region are isolated from each other, fault tolerant, and are architected in such a way that data centers in multiple availability domains are very unlikely to fail simultaneously.
  • the availability domains within a region may be structured in a manner such that a failure at one availability domain within the region is unlikely to impact the availability of data centers in other availability domains within the same region.
  • the CSP creates a tenancy for the customer.
  • the tenancy is like an account that is created for the customer.
  • a tenancy for a customer exists in a single realm and can access all regions that belong to that realm. The customer’s users can then access the services subscribed to by the customer under this tenancy.
  • a CSP builds or deploys data centers to provide cloud services to its customers.
  • the CSP typically builds new data centers in new regions or increases the capacity of existing data centers to service the customers’ growing demands and to better serve the customers.
  • a data center is built in close geographical proximity to the location of customers serviced by that data center. Geographical proximity between a data center and customers serviced by that data center lends to more efficient use of resources and faster and more reliable services being provided to the customers.
  • a CSP typically builds new data centers in new regions in geographical areas that are geographically proximal to the customers serviced by the data centers. For example, for a growing customer base in Germany, a CSP may build one or more data centers in a new region in Germany.
  • region build is used to refer to building one or more data centers in a region. Building a data center in a region involves provisioning or creating a set of new resources that are needed or used for providing a set of services that the data center is configured to provide.
  • the end result of the region build process is the creation of a data center in a region, where the data center is capable of providing a set of services intended for that data center and includes a set of resources that are used to provide the set of services.
  • the present disclosure describes techniques for reducing build time, reducing computing resource waste, and reducing risk related to building one or more data centers in a region. Instead of weeks and months needed to build a data center in a region in the past, the techniques described herein can be used to build a new data center in a region in a relatively much shorter time, while reducing the risk of errors over conventional approaches.
  • a Cloud Infrastructure Orchestration Service is disclosed herein that is configured to bootstrap (e.g., provision and deploy) services into a new data center based on predefined configuration files that identify the resources (e.g., infrastructure components and software to be deployed) for implementing a given change to the data center.
  • the CIOS can parse and analyze configuration files (e.g., flock configs) to identify dependencies between resources, execution targets, phases, and flocks.
  • the CIOS may generate specific data structures from the analysis and may use these data structures to drive operations and to manage an order by which services are bootstrapped to a region.
  • the CIOS may utilize these data structures to identify when it can bootstrap a service, when bootstrapping is blocked, and/or when bootstrapping operations associated with a previously blocked service can resume.
  • the CIOS can identify circular dependencies within the data structures and execute operations to eliminate/resolve these circular dependencies prior to task execution. Using these techniques, the CIOS substantially reduces the risk of executing tasks prior to the availability of the resources on which those tasks depend.
  • the CIOS may optimize parallel processing to execute changes to a data center while ensuring that tasks are not initiated until the functionality on which those tasks depend is available in the region. In this manner, the CIOS enables a region build to be performed more efficiently, which greatly reduces the time required to build a data center and the wasteful computing resource use found in conventional approaches.
  • a “region” is a logical abstraction corresponding to a geographical location.
  • a region can include any suitable number of one or more execution targets.
  • an execution target could correspond to a data center.
  • An “execution target” refers to a smallest unit of change for executing a release.
  • a “release” refers to a representation of an intent to orchestrate a specific change to a service (e.g., deploy version 8, “add an internal DNS record,” etc.).
  • an execution target represents an “instance” of a service.
  • a single service can be bootstrapped to each of one or more execution targets.
  • An execution target may be associated with a set of devices (e.g., a data center).
  • Bootstrapping is intended to refer to the collective tasks associated with provisioning and deployment of any suitable number of resources (e.g., infrastructure components, artifacts, etc.) corresponding to a single service.
  • resources e.g., infrastructure components, artifacts, etc.
  • a “service” refers to functionality provided by a set of resources.
  • a set of resources for a service includes any suitable combination of infrastructure, platform, or software (e.g., an application) hosted by a cloud provider that can be configured to provide the functionality of a service.
  • a service can be made available to users through the Internet.
  • An “artifact” refers to code being deployed to an infrastructure component or a Kubemetes engine cluster, this may include software (e.g., an application), configuration information (e.g., a configuration file) for an infrastructure component, or the like.
  • 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 include declarative statements that specify one or more aspects corresponding to a desired state of the resources of the service.
  • Service state refers to a point-in-time snapshot of every resource (e.g., infrastructure resources, artifacts, etc.) associated with the service.
  • the service state indicates status corresponding to provisioning and/or deployment tasks associated with service resources.
  • laaS provisioning refers to acquiring computers or virtual hosts for use, and even installing needed libraries or services on them.
  • provisioning a device refers to evolving a device to a state in which it can be utilized by an end-user for their specific use.
  • a device that has undergone the provisioning process may be referred to as a “provisioned device.”
  • Preparing the provisioned device (installing libraries and daemons) may be part of provisioning; this preparation is different from deploying new applications or new versions of an application onto the prepared device. In most cases, deployment does not include provisioning, and the provisioning may need to be performed first.
  • the device Once prepared, the device may be referred to as “an infrastructure component.”
  • laaS deployment refers to the process of providing and/or installing a new application, or a new version of an application, onto a provisioned infrastructure component.
  • the infrastructure component Once the infrastructure component has been provisioned (e.g., acquired, assigned, prepared, etc.), additional software may be deployed (e.g., provided to and installed on the infrastructure component).
  • the infrastructure component can be referred to as a “resource” after provisioning and deployment has concluded. Examples of resources may include, but are not limited to, virtual machines, databases, object storage, block storage, load balancers, and the like.
  • a “capability” identifies a unit of functionality associated with a service.
  • the unit could be a portion, or all, of the functionality to be provided by the service.
  • a capability can be published indicating that a resource is available for authorization/authentication processing (e.g., a subset of the functionality to be provided by the resource).
  • a capability can be published indicating the full functionality of the service is available. Capabilities can be used to identify functionality on which a resource or service depends and/or functionality of a resource or service that is available for use.
  • a “virtual bootstrap environment” refers to a virtual cloud network that is provisioned in the overlay of an existing region (e.g., a “host region”). Once provisioned, a ViBE is connected to a new region using a communication channel (e.g., an IPSec Tunnel VPN).
  • a communication channel e.g., an IPSec Tunnel VPN.
  • Certain essential core services like a deployment orchestrator, a public key infrastructure (PKI) service, and the like can be provisioned in a ViBE. These services can provide the capabilities required to bring the hardware online, establish a chain of trust to the new region, and deploy the remaining services in the new region.
  • Utilizing the virtual bootstrap environment can prevent circular dependencies between bootstrapping resources by utilizing resources of the host region. Services can be staged and tested in the ViBE prior to the physical region (e.g., the target region) being available.
  • a “Cloud Infrastructure Orchestration Service” may refer to a system configured to manage provisioning and deployment operations for any suitable number of services as part of a region build.
  • a Multi-Flock Orchestrator 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).
  • An MFO tracks relevant events for each service of the region build and takes actions in response to those events.
  • a “host region” refers to a region that hosts a virtual bootstrap environment (ViBE).
  • ViBE virtual bootstrap environment
  • a host region may be used to bootstrap a ViBE.
  • a “target region” refers to a region under build.
  • “Publishing a capability” refers to “publishing” as used in a “publisher-subscriber” computing design or otherwise providing an indication that a particular capability is available (or unavailable).
  • the capabilities are “published” (e.g., collected by a capabilities service, provided to a capabilities service, pushed, pulled, etc.) to provide an indication that functionality of a resource/service is available.
  • capabilities may be published/transmitted via an event, a notification, a data transmission, a function call, an API call, or the like.
  • An event (or other notification/data transmission/etc.) indicating availability of a particular capability can be broadcasted/addressed (e.g., published) to a capabilities service.
  • a “Capabilities Service” may be a flock configured to model dependencies between different flocks.
  • a capabilities service may be provided within a Cloud Infrastructure Orchestration Service and may define what capabilities, services, and/or features have been made available in a region.
  • a “Real-time Regional Data Distributor” (RRDD) may be a service or system configured to manage region data. This region data can be injected into flock configs to dynamically create execution targets for new regions.
  • CIOS Cloud Infrastructure Orchestration Service
  • Such techniques can be configured to manage bootstrapping (e.g., provisioning and deploying software to) infrastructure components within a cloud environment (e.g., a region).
  • the CIOS can include computing components (e.g., a CIOS Central and a CIOS Regional, both of which will be described in further detail below) that may be configured to manage bootstrapping tasks (provisioning and deployment) for a given service and a Multi-Flock Orchestrator (also described in further detail below) configured to initiate/manage region builds (e.g., bootstrapping operations corresponding to multiple services).
  • the CIOS enables region building and world-wide infrastructure provisioning and code deployment with minimal manual run-time effort from service teams (e.g., beyond an initial approval and/or physical transportation of hardware, in some instances).
  • the high-level responsibilities of the CIOS include, but are not limited to, coordinating region builds, providing users with a view of the current state of resources managed by the CIOS (e.g., of a region, across regions, world-wide, etc.), and managing bootstrapping operations for bootstrapping resources within a region.
  • the CIOS may provide view reconciliation, where a view of a desired state (e.g., a desired configuration) of resources may be reconciled with a current/actual state (e.g., a current configuration) of the resources.
  • view reconciliation may include obtaining state data to identify what resources are actually running and their current configuration and/or state. Reconciliation can be performed at a variety of granularities, such as at a service level.
  • the CIOS can perform plan generation, where differences between the desired and current state of the resources are identified. Part of plan generation can include identifying the operations that would need to be executed to bring the resources from the current state to the desired state.
  • the CIOS may present a generated plan to a user for approval.
  • the CIOS can mark the plan as approved or rejected based on user input from the user. Thus, users can spend less time reasoning about the plan and the plans are more accurate because they are machine generated. Plans are almost too detailed for human consumption; however, the CIOS can provide this data via a sophisticated user interface (UI).
  • UI user interface
  • the CIOS can handle execution of change management by executing the approved plan.
  • the CIOS can handle rolling back to a previous service version by generating a plan that returns the service to a previous (e.g., pre-release) state (e.g., when CIOS detects service health degradation while executing).
  • the CIOS can measure service health by monitoring alarms and executing integration tests.
  • the CIOS can help teams quickly define roll-back behavior in the event of service degradation, which it can later execute.
  • the CIOS can generate and display plans and can track approval.
  • the CIOS can combine the functionality of provisioning and deployment in a single system that coordinates these tasks across a region build.
  • the CIOS also supports the discovery of flocks (e.g., service resources such as flock config(s) corresponding to any suitable number of services), artifacts, resources, and dependencies.
  • the CIOS can discover dependencies between execution tasks at every level (e.g., resource level, execution target level, phase level, service level, etc.) through a static analysis (e.g., including parsing and processing content) of one or more configuration files. Using these dependencies, the CIOS can generate various data structures from these dependencies that can be used to drive task execution (e.g., tasks regarding provisioning of infrastructure resources and deployment of artifacts across the region).
  • level e.g., resource level, execution target level, phase level, service level, etc.
  • static analysis e.g., including parsing and processing content
  • 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 can include, but is not limited to, the following components: Real-time Regional Data Distributor (RRDD) 104, Multi-Flock Orchestrator (MFO) 106, CIOS Central 108, CIOS Regional 110, and Capabilities Service 112.
  • RRDD Real-time Regional Data Distributor
  • MFO Multi-Flock Orchestrator
  • Specific functionality of CIOS Central 108 and CIOS Regional 110 is provided in more detail in U.S. Application No. 17/016,754, entitled “Techniques for Deploying Infrastructure Resources with a Declarative Provisioning Tool,” the entire contents of which are incorporated in its entirety for all purposes.
  • any suitable combination of the components of CIOS 102 may be provided as a service.
  • some portion of CIOS 102 may be deployed to a region (e.g., a data center represented by host region 103).
  • CIOS 102 may include any suitable number of cloud services (not depicted in FIG. 1) discussed in further detail in U.S. Application No. 17/016,754 and below with respect to FIGS. 2 and 3.
  • RRDD Real-time Regional Data Distributor
  • RRDD Real-time Regional Data Distributor
  • the region data may be in any suitable form (e.g., JSON format, data objects/containers, XML, etc.).
  • Region data maintained by RRDD 104 may include any suitable number of subsets of data which can individually be referenceable by a corresponding identifier.
  • an identifier “all regions” can be associated with a data structure (e.g., a list, a structure, an object, etc.) that includes a metadata for all defined regions.
  • an identifier such as “realms” can be associated with a data structure that identifies metadata for a number of realms and a set of regions corresponding to each realm.
  • the region data may maintain any suitable attribute of one or more realm(s), region(s), availability domains (ADs), execution target(s) (ETs), and the like, such as identifiers, DNS suffixes, states (e.g., a state of a region), and the like.
  • the RRDD 104 may be configured to manage a region state as part of the region data.
  • a region state may include any suitable information indicating a state of bootstrapping within a region.
  • some example region states can include “initial,” “building,” “production,” “paused,” or “deprecated.” The “initial” state may indicate a region that has not yet been bootstrapped.
  • a “building” state may indicate that bootstrapping of one or more flocks within the region has commenced.
  • a “production” state may indicate that bootstrapping has been completed and the region is ready for validation.
  • a “paused” state may indicate that CIOS Central 108 or CIOS Regional 110 has paused internal interactions with the regional stack, likely due to an operational issue.
  • a “deprecated” state may indicate the region has been deprecated and is likely unavailable and/or will not be contacted again.
  • CIOS Central 108 is configured to provide any suitable number of user interfaces with which users (e.g., user 109) may interact with CIOS 102.
  • users can make changes to region data via a user interface provided by CIOS Central 108.
  • CIOS Central 108 may additionally provide a variety of interfaces that enable users to: view changes made to flock configs and/or artifacts, generate and view plans, appro ve/reject plans, view status on plan execution (e.g., corresponding to tasks involving infrastructure provisioning, deployment, region build, and/or desired state of any suitable number of resources managed by CIOS 102.
  • CIOS Central 108 may implement a control plane configured to manage any suitable number of CIOS Regional 110 instances.
  • CIOS Central 108 can provide one or more user interfaces for presenting region data, enabling the user 109 to view and/or change region data.
  • CIOS Central 108 can be configured to invoke the functionality of RRDD 104 via any suitable number of interfaces.
  • CIOS Central 108 may be configured to manage region data, either directly or indirectly (e.g., via RRDD 104).
  • CIOS Central 108 may be configured to compile flock configs to inject region data as variables within the flock configs.
  • Each instance of CIOS Regional 110 may correspond to a component or module configured to execute bootstrapping tasks that are associated with a single service of a region.
  • CIOS Regional 110 can receive desired state data from CIOS Central 108.
  • desired state data may include a flock config that declares (e.g., via declarative statements) a desired state of resources associated with a service.
  • CIOS Central 108 can maintain cunent state data indicating any suitable aspect of the current state of the resources associated with a service.
  • CIOS Regional 110 can identify, through a comparison of the desired state data and the current state data, that changes are needed to one or more resources.
  • CIOS Regional 110 can determine that one or more infrastructure components need to be provisioned, one or more artifacts deployed, or any suitable change needed to the resources of the service to bring the state of those resources in line with the desired state.
  • CIOS Regional 110 may publish data indicating various capabilities of a resource as they become available.
  • a “capability” identifies a unit of functionality associated with a service. The unit could be a portion, or all of the functionality to be provided by the service.
  • a capability can be published indicating that a resource is available for authorization/authentication processing (e.g., a subset of the functionality to be provided by the resource).
  • a capability can be published indicating the full functionality of the service is available. Capabilities can be used to identify functionality on which a resource or service depends and/or functionality of a resource or service that is available for use.
  • Capabilities Service 112 is configured to maintain capabilities data that indicates 1) what capabilities of various services are currently available, 2) whether any resource/service is waiting on a particular capability, 3) what particular resources and/or services are waiting on a given capability, or any suitable combination of the above.
  • Capabilities Service 112 may provide an interface with which capabilities data may be requested.
  • Capabilities Service 112 may provide one or more interfaces (e.g., application programming interfaces) that enable Capabilities Service 112 to transmit capabilities data to MFO 106 and/or CIOS Regional 110 (e.g., each instance of CIOS Regional 110).
  • MFO 106 and/or any suitable component or module of CIOS Regional 110 may be configured to request capabilities data from Capabilities Service 112.
  • Multi-Flock Orchestrator (MFO) 106 may be configured to drive region build efforts.
  • MFO 106 can manage information that describes what flock/flock config versions and/or artifact versions are to be utilized to bootstrap a given service within a region (or to make a unit of change to a target region).
  • MFO 106 may be configured to monitor (or be otherwise notified of) changes to the region data managed by Real-time Regional Data Distributor 104.
  • receiving an indication that region data has been changed may cause a region build to be triggered by MFO 106.
  • MFO 106 may collect various flock configs and artifacts to be used for a region build.
  • the flock configs may be configured to be region agnostic. That is, the flock configs may not explicitly identify what regions to which the flock is to be bootstrapped.
  • MFO 106 may trigger a data injection process through which the collected flock configs are recompiled (e.g., by CIOS Central 108). During recompilation, operations may be executed (e.g., by CIOS Central 108) to cause the region data maintained by Real-time Regional Data Distributor 104 to be injected into the config files.
  • Flock configs can reference region data through variables/parameters without requiring hard-coded identification of region data. The flock configs can be dynamically modified at run time using this data injection rather than having the region data be hardcoded, and therefore, and more difficult to change.
  • Multi-Flock Orchestrator 106 can perform a static flock analysis in which the flock configs are parsed to identify dependencies between resources, execution targets, phases, and flocks, and in particular to identify circular dependencies that need to be removed.
  • MFO 106 can generate any suitable number of data structures based on the dependencies identified.
  • These data structures e.g., directed acyclic graph(s), linked lists, etc.
  • these data structures may collectively define an order by which services are bootstrapped within a region. An example of such a data structure is discussed further below with respect to Build Dependency Graph 338 of FIG. 3.
  • MFO may be configured to notify any suitable service teams that changes are required to the corresponding flock config to correct these circular dependencies.
  • MFO 106 can be configured to traverse one or more data structures to manage an order by which services are bootstrapped to a region. MFO 106 can identify (e.g., using data obtained from Capabilities Service 112) capabilities available within a given region at any given time. MFO 106 can use this data to identify when CIOS Regional 110 can bootstrap a service, when bootstrapping is blocked, and/or when bootstrapping operations associated with a previously blocked service can resume.
  • MFO 106 can perform a variety of releases in which instructions are transmitted by MFO 106 to CIOS Central 108 to perform bootstrapping operations corresponding to any suitable number of flock configs.
  • MFO 106 may be configured to identify that one or more flock configs may require multiple releases due to circular dependencies found within the graph. As a result, MFO 106 may transmit multiple instruction sets to CIOS Central 108 for a given flock config to break the circular dependencies identified in the graph.
  • a user can request that a new region (e.g., target region 114) be built. This can involve bootstrapping resources corresponding to a variety of services.
  • target region 114 may not be communicatively available (and/or secure) at a time at which the region build request is initiated. Rather than delay bootstrapping until such time as target region 114 is available and configured to perform bootstrapping operations, CIOS 102 may initiate the region build using a virtual bootstrap environment 116.
  • Virtual bootstrap environment (ViBE) 116 may be an overlay network that is hosted by host region 103 (a preexisting region that has previously been configured with a core set of services and which is communicatively available and secure).
  • MFO 106 can leverage resources of the host region 103 to bootstrap resources to the ViBE 116 (generally referred to as “building the ViBE”).
  • MFO 106 can provide instructions through CIOS Central 108 that cause an instance of CIOS Regional 110 within a host region (e.g., host region 103) to bootstrap another instance of CIOS Regional within the ViBE 116.
  • CIOS Regional within the ViBE is available for processing, bootstrapping the services for the target region 114 can continue within the ViBE 116.
  • target region 114 is available to perform bootstrapping operations, the previously bootstrapped services within ViBE 116 may be migrated to target region 114. Utilizing these techniques, CIOS 102 can greatly improve the speed at which a region is built by drastically reducing the need for any manual input and/or configuration to be provided.
  • FIG. 2 is a block diagram for illustrating an environment 200 and method for building 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 the overlay of an existing region (e.g., host region 204, an example of the host region 103 of FIG. 1 and in an embodiment is a Host Region Service Enclave).
  • ViBE 202 represents an environment in which services can be staged for a target region (e.g., a region under build such as target region 114 of FIG. 1) before the target region becomes available.
  • a target region e.g., a region under build such as target region 114 of FIG.
  • a core set of services may be bootstrapped. While those core set of services exist in the host region 204, they do not yet exist in the ViBE (nor the target region). These essential core services provide the functionality needed to provision devices, establish a chain of trust to the new region, and deploy remaining services (e.g., flocks) into a region.
  • the ViBE 202 may be a tenancy that is deployed in a host region 204. It can be thought of as a virtual region.
  • the ViBE 202 can be connected to the target region so that services in the ViBE can interact with the services and/or infrastructure components of the target region. This will enable deployment of production level services, instead of self-contained seed services as in previous systems, and will require connectivity over the internet to the target region. Conventionally, a seed service was deployed as part of a container collection and used to bootstrap dependencies necessary to build out the region.
  • resources may be bootstrapped (e.g., provisioned and deployed) into the ViBE 202 and connected to the service enclave of a region (e.g., host region 204) in order to provision hardware and deploy services until the target region is self-sufficient and can be communicated with directly.
  • a region e.g., host region 204
  • Utilizing the ViBE 202 allows for standing up the dependencies and services needed to be able to provision/prepare infrastructure and deploy software while making use of the host region's resources in order to break circular dependencies of core services.
  • Multi-Flock Orchestrator (MFO) 206 may be configured to perform operations to build (e.g., configure) ViBE 202.
  • MFO 206 can obtain applicable flock configs corresponding to various resources to be bootstrapped to the new region (in this case, a ViBE region, ViBE 202).
  • MFO 206 may obtain a flock config (e.g., a “ViBE flock config”) that identifies aspects of bootstrapping Capabilities Service 208 and Worker 210.
  • MFO 206 may obtain another flock config corresponding to bootstrapping Domain Name Service (DNS) 212 to ViBE 202.
  • DNS Domain Name Service
  • MFO 206 may instruct CIOS Central 214 (e.g., an example of CIOS Central 108 and CIOS Central 214 of FIGS. 1 and 2, respectively).
  • MFO 206 may transmit a request (e.g., including the ViBE flock config) to request bootstrapping of the Capabilities Service 208 and Worker 210 that, at this time do not yet exist in the ViBE 202.
  • CIOS Central 214 may have access to all flock configs.
  • MFO 206 may transmit an identifier for the ViBE flock config rather than the file itself, and CIOS Central 214 may independently obtain an identifier from storage (e.g., from DB 308 or flock DB 312 of FIG. 3).
  • CIOS Central 214 may provide the ViBE flock config via a corresponding request to CIOS Regional 216.
  • CIOS Regional 216 may parse the ViBE flock config to identify and execute specific infrastructure provisioning and deployment operations at step 3.
  • the CIOS Regional 216 may utilize additional corresponding services for provisioning and deployment.
  • CIOS Regional 216 CIOS Regional may instruct deployment orchestrator 218 (e.g., an example of a core service, or other write, build, and deploy applications software, of the host region 204) to execute instructions that in turn cause Capabilities Service 208 and Worker 210 to be bootstrapped within ViBE 202.
  • a capability may be transmitted to the Capabilities Service 208 (from the CIOS Regional 216, Deployment Orchestrator 218 via the Worker 210 or otherwise) indicating that resources corresponding to the ViBE flock are available.
  • Capabilities Service 208 may persist this data.
  • the Capabilities Service 208 adds this information to a list it maintains available capabilities with the ViBE.
  • the capability provided to Capabilities Service 208 at step 5 may indicate the Capabilities Service 208 and Worker 210 are available for processing.
  • MFO 206 may identify that the capability indicating that Capabilities Service
  • the MFO 206 may instruct CIOS Central 214 to bootstrap a DNS service (e.g., DNS 212) to the ViBE 202.
  • DNS 212 a DNS service
  • the instructions may identify or include a particular flock config corresponding to the DNS service.
  • the CIOS Central 214 may instruct the CIOS Regional 216 to deploy DNS 212 to the ViBE 202.
  • the DNS flock config for the DNS 212 is provided by the CIOS Central 214.
  • Worker 210 which is now deployed in the ViBE 202, may be assigned by CIOS Regional 216 to the task of deploying DNS 212.
  • Worker 210 may execute a declarative infrastructure provisioner in the manner described above in connection with FIG. 3 to identify (e.g., from comparing the flock config (the desired state) to a current state of the (currently nonexisting) resources associated with the flock) a set of operations that need to be executed to deploy DNS 212.
  • the Deployment Orchestrator 218 may instruct Worker 210 to deploy DNS 212 in accordance with the operations identified at step 9. As depicted, Worker 210 proceeds with executing operations to deploy DNS 212 to ViBE 202 at step 11. At step 12, Worker 210 notifies Capabilities Service 208 that DNS 212 is available in ViBE 202. MFO 206 may subsequently identify that the resources associated with the ViBE flock config and the DNS flock config are available and may proceed to bootstrap any suitable number of additional resources to the ViBE.
  • steps 1-12 After steps 1-12 are concluded, the process for building the ViBE 202 can be considered complete and the ViBE 202 can be considered built.
  • FIG. 3 is a block diagram for illustrating an environment 300 and method for bootstrapping services to a target region utilizing the ViBE, according to at least one embodiment.
  • user 302 may utilize any suitable user interface provided by CIOS Central 304 (an example of CIOS Central 108 and CIOS Central 214 of FIG. 1 and 2, respectively) to modify region data.
  • CIOS Central 304 an example of CIOS Central 108 and CIOS Central 214 of FIG. 1 and 2, respectively
  • user 302 may create a new region to which a number of services are to be bootstrapped.
  • CIOS Central 304 may execute operations to send the change to RRDD 306 (e.g., an example of RRDD 104 of FIG. 1).
  • RRDD 306 may store the received region data in database 308, a data store configured to store region data including any suitable identifier, attribute, state, etc. of a region, AD, realm, ET, or the like.
  • updater 307 may be utilized to store region data in database 308 or any suitable data store from which such updates may be accessible (e.g., to service teams).
  • updater 307 may be configured to notify (e.g., via any suitable electronic notification) of updates made to database 308.
  • MFO 310 (an example of the MFO 106 and 206 of FIGS. 1 and 2, respectively) may detect the change in region data.
  • MFO 310 may be configured to poll RRDD 306 for changes in region data.
  • RRDD 306 may be configured to publish or otherwise notify MFO 310 of region changes.
  • detecting the change in region data may trigger MFO 310 to obtain a version set (e.g., a version set associated with a particular identifier such as a “golden version set” identifier), identifying a particular version for each flock (e.g., service) that is to be bootstrapped to the new region and a particular version for each artifact corresponding to that flock.
  • the version set may be obtained from DB 312. As flocks evolve and change, the versions fortheir corresponding configs and artifacts used for region build may change.
  • flock DB 312 may identify which versions of flock configs and artifacts to use for building a region (e.g., a ViBE region, a Target Region/non-ViBE Region, etc.).
  • the flock configs e.g., all versions of the flock configs
  • artifacts e.g., all versions of the artifacts
  • MFO 310 may request CIOS Central 304 to recompile of each of the flock configs associated with the version set with the current region data.
  • the request may indicate a version for each flock config and/or artifact corresponding to those flock configs.
  • CIOS Central 304 may obtain current region data from the DB 308 (e.g., directly, or via Real-time Regional Data Distributor 306) and retrieve any suitable flock config and artifact in accordance with the versions requested by MFO 310.
  • CIOS Central 304 may recompile the flock configs with the region data obtained at step 7 to inject the flock configs with current region data.
  • CIOS Central 304 may return the compiled flock configs to MFO 310.
  • CIOS Central 304 may simply indicate compilation is done, and MFO 310 may access the recompiled flock configs via RRDD 306.
  • MFO 310 may perform a static analysis of the recompiled flock configs. As part of the static analysis, MFO 310 may parse the flock configs (e.g., using a library associated with a declarative infrastructure provisioner (e.g., Terraform, or the like)) to identify dependencies between flocks. From the analysis and the dependencies identified, MFO 310 can generate Build Dependency Graph 338.
  • Build Dependency Graph 338 may be an acyclic directed graph that identifies an order by which flocks are to be bootstrapped (and/or changes indicated in flock configs are to be applied) to the new region. Each node in the graph may correspond to bootstrapping any suitable portion of a particular flock.
  • the specific bootstrapping order may be identified based at least in part on the dependencies.
  • the dependencies may be expressed as an attribute of the node and/or indicated via edges of the graph that connect the nodes.
  • MFO 310 may traverse the graph (e.g., beginning at a starting node) to drive the operations of the region build.
  • MFO 310 may utilize a cycle detection algorithm to detect the presence of a cycle (e.g., service A depends on service B and vice versa).
  • MFO 310 can identify orphaned capabilities dependencies. For example, MFO 310 can identify orphaned nodes of the Build Dependency Graph 338 that do not connect to any other nodes. MFO 310 may identify falsely published capabilities (e.g., when a capability was prematurely published, and the corresponding functionality is not actually yet available). MFO 310 can detect from the graph that one or more instances of publishing the same capability exist.
  • MFO 310 may be configured to notify or otherwise present this information to users (e.g., via an electronic notification, a user interface, or the like).
  • MFO 310 may be configured to force delete/recreate resources to break circular dependencies and may once again provide instructions to CIOS Central 304 to perform bootstrapping operations for those resources and/or corresponding flock configs.
  • a starting node may correspond to bootstrapping the ViBE flock
  • a second node may correspond to bootstrapping DNS.
  • the steps 10-15 correspond to deploying (via deployment orchestrator 317, an example of the deployment orchestrator 218 of FIG. 2) a 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.
  • the MFO 310 recommences traversal of the Build Dependency Graph 338 to identify next operations to be executed.
  • MFO 310 may continue traversing the Build Dependency Graph 338 to identify that a DNS flock is to be deployed.
  • Steps 16-21 may be executed to deploy DNS 322 (an example of the DNS 212 of FIG. 2). These operations may generally correspond to steps 7-12 of FIG. 2.
  • a capability may be stored indicating that DNS 322 is available.
  • MFO 310 may recommence traversal of the Build Dependency Graph 338. On this traversal, the MFO 310 may identify that any suitable portion of an instance of CIOS Regional (e.g., an example of CIOS Regional 314) is to be deployed to the ViBE 316.
  • steps 16-21 may be substantially repeated with respect to deploying CIOS Regional (ViBE) 326 (an instance of CIOS Regional 314, CIOS Regional 110 of FIG. 1) and Worker 328 to the ViBE 316.
  • a capability may be transmitted to the Capabilities Service 318 that CIOS Regional (ViBE) 326 is available.
  • MFO 310 may recommence traversal of the Build Dependency Graph 338. On this traversal, the MFO 310 may identify that a deployment orchestrator (e.g., Deployment Orchestrator 330, an example of the Deployment Orchestrator 317) is to be deployed to the ViBE 316. In some embodiments, steps 16-21 may be substantially repeated with respect to deploying Deployment Orchestrator 330. Information that identifies a capability may be transmitted to the Capabilities Service 318, indicating that Deployment Orchestrator 330 is available.
  • a deployment orchestrator e.g., Deployment Orchestrator 330, an example of the Deployment Orchestrator 31
  • ViBE 316 may be considered available for processing subsequent requests.
  • MFO 310 may instruct subsequent bootstrapping requests to be routed to ViBE components rather than utilizing host region components (components of host region 332).
  • MFO 310 can continue traversing the Build Dependency Graph 338, at each node instructing flock deployment to the ViBE 316 via CIOS Central 304.
  • CIOS Central 304 may request CIOS Regional (ViBE) 326 to deploy resources according to the flock config.
  • Target Region 334 may become available. Indication that the Target Region is available may be identifiable from region data for the Target Region 334 being provided by the user 302 (e.g., as an update to the region data).
  • the availability of Target Region 334 may depend on establishing a network connection between the Target Region 334 and external networks (e.g., the Internet).
  • the network connection may be supported over a public network (e.g., the Internet), but use software security tools (e.g., IPSec) to provide one or more encrypted tunnels (e.g., IPSec tunnels such as tunnel 336) from the ViBE 316 to Target Region 334.
  • IPSec software security tools
  • IPSec refers to a protocol suite for authenticating and encrypting network traffic over a network that uses Internet Protocol (IP), and can include one or more available implementations of the protocol suite (e.g., Openswan, Libreswan, strongSwan, etc.).
  • IP Internet Protocol
  • the network may connect the ViBE 316 to the service enclave of the Target Region 334.
  • the initial network connection to the Target Region 334 may be on a connection (e.g., an out-of-band VPN tunnel) sufficient to allow bootstrapping of networking services until an IPSec gateway may be deployed on an asset (e.g., bare-metal asset) in the Target Region 334.
  • a connection e.g., an out-of-band VPN tunnel
  • asset e.g., bare-metal asset
  • Deployment Orchestrator 330 can deploy the IPSec gateway at the asset within Target Region 334.
  • the Deployment Orchestrator 330 may then deploy VPN hosts at the Target Region 334 configured to terminate IPSec tunnels from the ViBE 316.
  • the bootstrapping operations may begin with services in the ViBE 316 provisioning resources in the Target Region 334 to support hosting instances of core services as they are deployed from the ViBE 316.
  • a host provisioning service may provision hypervisors on infrastructure (e.g., bare-metal hosts) in the Target Region 334 to allocate computing resources for VMs.
  • the host provisioning service may publish information indicating a capability that indicates that the physical resources in the Target Region 334 have been allocated. The capability may be published to Capabilities Service 318 via CIOS Regional (ViBE) 326 (e.g., by Worker 328).
  • CIOS Regional (ViBE) 326 can orchestrate the deployment of instances of core services from the ViBE 316 to the Target Region 334.
  • This deployment may be similar to the processes described above for building the ViBE 316, but using components of the ViBE (e.g., CIOS Regional (ViBE) 326, Worker 328, Deployment Orchestrator 330) instead of components of the Host Region 332 service enclave.
  • the deployment operations may generally correspond to steps 16-21 described above.
  • the DNS record associated with that service may correspond to the instance of the service in the ViBE 316.
  • the DNS record associated with the service may be updated at a later time to complete deployment of the service to the Target Region 334. Said another way, the instance of the service in the ViBE 316 may continue to receive traffic (e.g., requests) to the service until the DNS record is updated.
  • a service may deploy partially into the Target Region 334 and publish information indicating a capability (e.g., to Capabilities Service 318) that the service is partially deployed.
  • a service running in the ViBE 316 may be deployed into the Target Region 334 with a corresponding compute instance, load balancer, and associated applications and other software, but may need to wait for database data to migrate to the Target Region 334 before being completely deployed.
  • the DNS record (e.g., managed by DNS 322) may still be associated with the service in the ViBE 316. Once data migration for the service is complete, the DNS record may be updated to point to the operational service deployed in the Target Region 334.
  • the deployed service in the Target Region 334 may then receive traffic (e.g., requests) for the service, while the instance of the service in the ViBE 316 may no longer receive traffic for the service.
  • a CSP may build or deploy data centers to provide cloud services to its customers in new regions.
  • the regions may correspond to a general geographic area, which may be preferably in proximity to new customers or customers with expanding service needs (e.g., customer growth in requiring scale-up of cloud services, expansion of cloud services to a new geographic area, etc.).
  • a CIOS e.g., CIOS 102 of FIG. 1
  • ViBE e.g., ViBE 316 of FIG. 3
  • the ViBE may be created in advance or in parallel with the building of the data centers in the new region.
  • a ViBE may be built in advance (e.g., days, weeks, etc.) of the completion of the new data center. Operators may deploy core services to the ViBE to support the deployment of services to the new data center once the physical infrastructure of the new data center is ready to host cloud services. By creating the ViBE in advance of (or in parallel with) the build of a region's data center, the core services deployed therein may be evaluated for deployment readiness (e.g., production testing, resolving dependencies, etc.).
  • FIG. 4 is a simplified diagram depicting regions 400 of a CSP, including a plurality of host regions (e.g., host region 404, host region 406-410) suitable for hosting a ViBE (e.g., ViBE 402, which may be an example of any of the previous ViBEs described herein, including ViBE 316 of FIG. 3).
  • a host region may be any data center configured to provide any cloud infrastructure services (e.g., CIOS Central 304 or the like).
  • Target region 412 may be a new region to be built and can include one or more data centers hosting the physical computing, storage, and networking infrastructure for providing cloud services.
  • a ViBE may be created in any suitable host region.
  • a ViBE may be a tenancy (e.g., similar to a customer account) of a CSP.
  • a tenancy may span multiple regions.
  • a tenancy may be able to access resources (e.g., compute, storage, services, etc.) in one or more regions.
  • resources e.g., compute, storage, services, etc.
  • a ViBE tenancy may be able to access resources in one or more regions, so that a ViBE may be created in one or more host regions to support region builds for one or more target regions.
  • the ViBE tenancy may be used to create a ViBE in each of host regions 404-410.
  • Each ViBE in different regions may support a region build for a corresponding target region (e.g., target region 412).
  • one ViBE in a host region e.g., host region 404 may be used for the region build of one target region (e.g., target region 412).
  • a suitable host region for a ViBE used to build a target region may be selected based on network proximity between the host region and the target region (e.g., low-latency network connection).
  • a suitable host region may be located within the same jurisdiction (e.g., same country, same geopolitical region, etc.) as the target region. Because different jurisdictions may have different regulations for handling customer data, a suitable host region to build a target region using a ViBE may be a host region located within the same jurisdiction as the target region.
  • host region 404 and target region 412 may both be in one jurisdiction, indicated by border 414 (e.g., a national border, a regional border, etc.), while host region 410 is in a different jurisdiction.
  • Host region 410 may have better network connectivity with target region 412, but host region 404 may be selected as the host region for ViBE 402 to build target region 412 since it is in the same jurisdiction as target region 412.
  • FIG. 5 is a block diagram depicting an environment 500 and example method for bootstrapping services to a target region using a ViBE.
  • Operations described herein with respect to FIG. 5 may be considered an extension of the method described above with respect to FIG. 3.
  • MFO 510 an example of MFO 310 of FIG. 3
  • MFO 510 may deploy a service (e.g., service 502) into the target region 534 by instructing CIOS Central 504 to bootstrap the service into the target region similarly to how services (e.g., Deployment Orchestrator 530, an example of Deployment Orchestrator 330 of FIG. 3) were deployed into the ViBE.
  • a service e.g., service 502
  • CIOS Central 504 may deploy a service into the target region 534 by instructing CIOS Central 504 to bootstrap the service into the target region similarly to how services (e.g., Deployment Orchestrator 530, an example of Deployment Orchestrator 330 of FIG. 3) were
  • 5 may be implemented in hardware, computer instructions, or a combination thereof.
  • the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations.
  • computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular data types.
  • the order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be omitted or combined in any order and/or in parallel to implement the processes.
  • a network connection may be established between the ViBE 516 in the host region 532 and the target region 534.
  • a network service 509 e.g., one of the core services deployed to the ViBE 516) may perform operations to establish the network connection.
  • the network connection can include one or more tunnels 536 (an example of tunnels 336 of FIG. 3).
  • the tunnels 536 may be encrypted tunnels (e.g., IPSec tunnels).
  • the network connection may form one or more virtual private network (VPN) connections between a network hosting the ViBE 516 (e.g., a virtual cloud network (VCN) of host region 532) and a service enclave (e.g., a VCN of target region 534) of the target region 534.
  • VPN virtual private network
  • the network service 509 may publish a capability to Capabilities Service 518 indicating that the ViBE 516 is connected to the Target Region 534.
  • Steps 3-11 may be executed to deploy service 502 into the target region 534.
  • the operations of steps 3, 4, 5, and 11 may generally correspond to steps 7, 8, 9, and 12 of FIG. 2.
  • Steps 6-7 include operations related to provisioning infrastructure resources at the Target Region 534, while steps 8-10 may be similar to an iteration of steps 10 and 11 of FIG. 2 to deploy a service into the Target Region 534.
  • the steps described below include infrastructure provisioning (e.g., steps 6-7) as a portion of a method using CIOS to provision infrastructure resources as a preliminary part of deploying a service (e.g., a service according to a flock config using a declarative provisioning tool).
  • provisioning infrastructure resources e.g., infrastructure resources 503 may be performed as a separate operation under the direction of CIOS Central 504 and MFO 510.
  • a host provisioning service (e.g., host provisioning service 506) may be deployed to the ViBE 516 and capable of provisioning infrastructure resources in the Target Region 534 before a deployment orchestration service (e.g., Deployment Orchestrator 530) is fully deployed in the ViBE 516 to support deployment of services to the Target Region 534.
  • a deployment orchestration service e.g., Deployment Orchestrator 530
  • MFO 510 may begin provisioning infrastructure resources at the Target Region 534 using host provisioning service 506 without an accompanying deployment of a service.
  • the MFO 510 may instruct CIOS Central 504 to deploy service 502 to the Target Region 534.
  • Service 502 may require infrastructure resources 503 to be provisioned at the target region 534.
  • service 502 may execute with one or more compute instances executing on one or more VMs in the target region.
  • the instructions to deploy service 502 may identify or include resources (e.g., infrastructure resources 503) to provision in the target region 534. Provisioning resources can include configuring one or more hosts (e.g., one or more virtual machines (VMs)) in a computing environment of the Target Region 534.
  • the instructions to deploy service 502 may also identify or include a flock config corresponding to the service 502.
  • CIOS Central 504 may instruct CIOS Regional (ViBE) 526 to provision infrastructure resources 503 and deploy service 502 to the Target Region 534.
  • the flock config for service 502 is provided by the CIOS Central 504.
  • Worker 528 may be assigned by CIOS Regional (ViBE) 526 to the task of provisioning infrastructure resources 503 and deploying service 502.
  • Worker 528 may execute a declarative provisioner to identify (e.g., by comparing the flock config to a current state of the resources associated with the flock) a set of operations that need to be executed to deploy service 502.
  • the Worker 528 may instruct the host provisioning service 506 to provision infrastructure resources 503 in the Target Region 534 in accordance with the operations identified at step 5, which may be done by host provisioning service 506 at step 7.
  • the Worker 528 may instruct a compute control plane 508 and Deployment Orchestrator 530 to launch instances and deploy service 502 to the launched instances, respectively.
  • the Compute Control Plane 508 and Deployment orchestrator 530 may do the instructed launching and deployment tasks at step 10.
  • the Worker 528 may post one or more capabilities to Capabilities Service 518 that Service 502 is available.
  • MFO 510 may then identify that the resources associated with the Service 502 flock config are available and may proceed with further bootstrapping operations.
  • the completion of infrastructure provisioning (step 7), launching an instance (step 8), and deploying a service (step 9) may each result in a corresponding capability posted to Capabilities Service 518.
  • provisioning infrastructure for a service would include updating a corresponding DNS record using DNS 522 (an example of DNS 322 of FIG. 3) to point to the newly provisioned resources for the service (e.g., point to an associated network address).
  • DNS 522 an example of DNS 322 of FIG. 3
  • the deployment of the corresponding service may occur separately from the provisioning of its underlying infrastructure (e.g., steps 6-8 may occur prior to the completion of steps 9 and 10).
  • updating the DNS record early may result in services in the ViBE 516 and/or the Host Region 532 attempting to access a service in the Target Region 534 before Capabilities Service 518 is available to serve traffic.
  • the capability posted to Capabilities Service 518 at step 11 may indicate that the deployment is partially complete (e.g., "Service 502 Partial Scaleout").
  • MFO 510 can then identify the partially complete state of the deployed service and perform another pass through CIOS Central 504 and CIOS Regional (ViBE) 526 to have Worker 528 update the DNS 522.
  • FIG. 6 is a block diagram depicting an example architecture of an environment 600 having a network connection between a ViBE (e.g., ViBE VCN 604) in a host region (e.g., Host Region 632) and a target region (e.g., Target Region 634). Because the depicted architecture relates to network connectivity, the ViBE in FIG. 6 is shown as a VCN in a ViBE Tenancy 602 within the Host Region 632. ViBE VCN 604 may be an example of ViBE 516 of FIG. 5. Detailed examples of the relationship between tenancies and VCNs are provided below with respect to FIGS. 9-12.
  • the ViBE VCN 604 can include similar services as ViBE 516 of FIG. 5, such that like- numbered components may be similar to one another.
  • Deployment Orchestrator 630 may be an example of Deployment Orchestrator 530
  • Host Provisioning Service 606 may be an example of Host Provisioning Service 506, and so on.
  • the ViBE VCN 604 can include one or more networking gateways, including Network Address Translation (NAT) Gateway 612, Service Gateway 614, and Internet Gateway 616.
  • the gateways may be logical connections (e.g., a virtual router or other suitable software implementation) between one or more network resources in the ViBE VCN 604 and an external network.
  • the gateways may route traffic (e.g., according to a routing table for the VCN) inbound to and outbound from network addresses of hosts within the ViBE VCN 604 (e.g., hosts of the ViBE services).
  • the NAT Gateway 612 may be configured to route traffic to and from resources in the ViBE VCN 604 that do not have public network addresses (e.g., public IP addresses).
  • the Service Gateway 614 may be configured to route traffic to and from one or more cloud services 620 provided by the CSP without exposing that traffic to a public internet (e.g., Public Internet 624).
  • the Internet Gateway 616 may be configured to route traffic to and from resources having an exposed public network address.
  • CIOS Regional (ViBE) 626 may have a public address within the ViBE VCN 604 for communication with CIOS Central 638.
  • CIOS Central 638 may be included in a VCN associated with a CIOS Tenancy 636 or another tenancy of the CSP.
  • CIOS Tenancy 636 may be included in Host Region 632 or another region of the CSP.
  • the incoming public traffic to the ViBE VCN 604 may be limited to connections between CIOS Central 638 and CIOS Regional (ViBE) 626 to improve security.
  • Connections to the Internet Gateway 616 may pass through a Load Balancer 618, which can be configured to apply a load balancing policy for managing (e.g., throttling, restricting, etc.) traffic to any public network addresses of ViBE VCN 604 resources (e.g., CIOS Regional (ViBE) 626).
  • the Load Balancer 618 may also be configured to restrict available ports and provide authentication of inbound connections via a security protocol (e.g., mutual transport layer security (mTLS)).
  • a security protocol e.g., mutual transport layer security (mTLS)
  • the cloud services 620 can include services available from the CSP.
  • cloud services 620 can include an identity service (e.g., an identity cloud service) to perform authentication and authorization procedures, a key-value storage service, and a deployment orchestration service (e.g., Deployment Orchestrator 317 of FIG. 3).
  • an identity service e.g., an identity cloud service
  • a deployment orchestration service e.g., Deployment Orchestrator 317 of FIG. 3
  • services in the ViBE VCN 604 may communicate with cloud services 620 to perform operations related to the ViBE VCN 604.
  • Deployment Orchestrator 630 may communicate with a storage service of cloud services 620 to store data created by Deployment Orchestrator 630.
  • the NAT Gateway 612 may be stateful.
  • a stateful NAT gateway may accept outbound traffic (e.g., requests from services in ViBE VCN 604) but reject inbound traffic that is not a response to outbound traffic (e.g., reject inbound connections).
  • one or more of the services (e.g., Deployment Orchestrator 630) in the ViBE VCN 604 may establish an encrypted network connection (e.g., an IPSec tunnel) with the Target Region 634.
  • the service in the ViBE VCN 604 can send outbound traffic through NAT Gateway 612 to the Target Region 634 (e.g., to Security Gateway 642) and receive an inbound response (e.g., key exchange for IPSec).
  • the state of the encrypted network connection may be preserved by the NAT Gateway 612 to permit ongoing two-way traffic over the connection, while continuing to block inbound traffic from the Public Internet 624 that is not in response to outbound traffic.
  • the Host Region 632 may connect to the Target Region 634 over Public Internet 624, which may be any suitable public network (e.g., the Internet).
  • the Target Region 634 can include a Network Gateway 640, which may be any suitable gateway for establishing connections between the Target Region 634 and the Public Internet 624.
  • the Target Region 634 can also include a Security Gateway 642, Region Network Fabric 644, and one or more services (e.g., Service A 646, Service N 648), which may be services bootstrapped to the Target Region 634 from the ViBE VCN 604 according to the processes described previously.
  • Service A 646 may be an instance of Deployment Orchestrator 630 after deployment from the ViBE VCN 604 to the Target Region 634.
  • the Security Gateway 642 may be configured to implement a security protocol (e.g., IPSec).
  • the security protocol may be any suitable protocol for establishing a secure (e.g., encrypted, authenticated, etc.) connection between the Security Gateway 642 and services in the ViBE VCN 604.
  • the Security Gateway 642 may terminate one or more IPSec tunnels established over the network connection between the ViBE VCN 604 and the Target Region 634.
  • the termination of an IPSec tunnel may be the endpoint where enciypted traffic (e.g., IPSec encrypted IP packets) is decrypted according to the encryption protocol.
  • the decrypted traffic may then be routed to destinations (e.g., Service A 646, Service N 648, other hosts, etc.) in the Target Region 634.
  • the Region Network Fabric 644 can include physical and virtual network infrastructure within the Target Region 634.
  • the Region Network Fabric 644 can include physical switches, routers, and the like, as well as virtual networking components (e.g., virtual routers, virtual gateways).
  • the Region Network Fabric 644 may be the network for the service enclave of the Target Region 634.
  • FIG. 7 is a diagram showing an example architecture of an environment 700 having a network connection between a Remote Access Tenancy 704 and a ViBE Tenancy 706. As shown in FIG. 7, components may be similar to components described elsewhere herein.
  • ViBE VCN 708 may be an example of ViBE VCN 604
  • NAT Gateway 712 may be an example of NAT Gateway 612
  • ViBE Tenancy 706 may be an example of ViBE Tenancy 602, and so on.
  • ViBE Service(s) 702 may include the services described above that are deployed to a ViBE as part of creating the ViBE and/or bootstrapping services into a target region (e.g., Target Region 734).
  • operations personnel may perform manual operations with one or more of the ViBE Service(s) 702.
  • personnel may access the service in the ViBE to perform tests, modify or update service configurations, obtain service information, or perform any other suitable task for interacting with the service.
  • a new core service may be identified for future ViBE bootstrapping to target regions.
  • operations personnel may test the new core service after its deployment into a ViBE before connecting the ViBE to a target region.
  • the creation of the ViBE VCN 708 in a host region allows the ViBE Service(s) 702 to be deployed as if in a production environment (e.g., in a target region) prior to using the ViBE to deploy those services to the target region.
  • ViBE VCN 708 is typically secured from inbound connections (e.g., by NAT Gateway 712)
  • access to ViBE Service(s) 702 may use a Remote Access Tenancy 704 that connects to a Jump VCN 718 in the ViBE Tenancy 706.
  • the Remote Access Tenancy 704 may be in the host region hosting the ViBE VCN 708 or another region.
  • the Remote Access Tenancy 704 may include an Access VCN 710 that includes hosts for supporting secure connections to the Jump VCN 718.
  • the Jump VCN 718 can include a Jump Subnet 720 that can include intermediate hosts.
  • the intermediate hosts in the Jump VCN may be deployed for each ViBE instance (e.g., each ViBE VCN in a host region).
  • the Jump VCN 718 can also include a virtual network interface card (VNIC) to interface with a VNIC in the ViBE VCN 708.
  • VNIC virtual network interface card
  • a network connection 724 may be made between the Jump VCN 718 and the ViBE VCN 708.
  • Connection between the Access VCN 710 and the Jump VCN may be via Gateway 714 and Gateway 716, which may be local peering gateways (LPG).
  • LPG local peering gateways
  • FIG. 8 illustrates an example method 800 for creating a ViBE and deploying one or more resources (e.g., one or more services) from the ViBE to a target region, according to some embodiments.
  • the method 800 may be performed by one or more components of a distributed computing system (e.g., a cloud computing system), including one or more components of the Cloud Infrastructure Orchestration Service 102 of FIG. 1.
  • a computer-readable storage medium comprising computer-readable instructions that, upon execution by one or more processors of a distributed computing system, cause the computing device to perform the method 800.
  • the operations of method 800 may be performed in any suitable order, and method 800 may include more or fewer operations than those depicted in FIG. 8.
  • Some or all of the method 800 may be performed under the control of one or more computer systems configured with executable instructions and may be implemented as code (e.g., executable instructions, one or more computer programs, or one or more applications) executing collectively on one or more processors, by hardware or combinations thereof.
  • the code may be stored on a computer-readable storage medium, for example, in the form of a computer program comprising a plurality of instructions executable by one or more processors.
  • the computer-readable storage medium may be non-transitory.
  • the method 800 may begin at block 802 when a virtual cloud network (VCN) may be generated in a host region.
  • VCN virtual cloud network
  • the VCN may be a Virtual Bootstrap Environment (ViBE) VCN (e.g., ViBE VCN 604).
  • the host region can include one or more data centers of a cloud service provider.
  • a virtual bootstrap environment may be implemented in the VCN.
  • the ViBE may be configured to stage one or more services for deployment to a target region.
  • a first service may be deployed into the ViBE.
  • Deployment of the first service may be implemented by a Multi Flock Orchestrator (MFO) (e.g., MFO 106 of FIG. 1) of the CIOS (e.g., CIOS 102 of FIG. 1).
  • MFO Multi Flock Orchestrator
  • the MFO may leverage one or more services in a service enclave of the host region (e.g., Deployment Orchestrator 218 of FIG. 2) to deploy the first service in the ViBE.
  • a network connection between the VCN and a target region may be established.
  • the network connection may be a virtual private network connection that implements a security protocol (e.g., IPSec).
  • IPSec a security protocol
  • the target region may include one or more data centers containing physical computing infrastructure suitable for hosting cloud services in accordance with the techniques of this disclosure.
  • resources of the ViBE may be deployed to the target region over the network connection.
  • the resources can include resources of one or more services in the ViBE, including instances of the first service or another service.
  • the resources may also include infrastructure components, artifacts, and the like. Deploying the resources may use the first service.
  • the first service may be an instance of a deployment orchestration service (e.g., Deployment Orchestrator 530 of FIG. 5) in the ViBE.
  • the resources may be deployed using the first service in conjunction with MFO and/or other CIOS components (e.g., CIOS Central 504 of FIG. 5).
  • laaS infrastructure as a service
  • laaS can be configured to provide virtualized computing resources over a public network (e.g., the Internet).
  • a cloud computing provider can host the infrastructure components (e.g., servers, storage devices, network nodes (e.g., hardware), deployment software, platform virtualization (e.g., a hypervisor layer), or the like).
  • an laaS provider may also supply a variety of services to accompany those infrastructure components (e.g., billing, monitoring, logging, load balancing and clustering, etc.).
  • these services may be policy-driven, laaS users may be able to implement policies to drive load balancing to maintain application availability and performance.
  • laaS customers may access resources and services through a wide area network (WAN), such as the Internet, and can use the cloud provider's services to install the remaining elements of an application stack.
  • WAN wide area network
  • the user can log in to the laaS platform to create virtual machines (VMs), install operating systems (OSs) on each VM, deploy middleware such as databases, create storage buckets for workloads and backups, and even install enterprise software into that VM.
  • VMs virtual machines
  • OSs install operating systems
  • middleware such as databases
  • storage buckets for workloads and backups
  • enterprise software enterprise software into that VM.
  • Customers can then use the provider's services to perform various functions, including balancing network traffic, troubleshooting application issues, monitoring performance, managing disaster recovery, etc.
  • a cloud computing model may require the participation of a cloud provider.
  • the cloud provider may, but need not be, a third-party service that specializes in providing (e.g., offering, renting, selling) laaS.
  • An entity might also opt to deploy a private cloud, becoming its own provider of infrastructure services.
  • laaS deployment is the process of putting a new application, or a new version of an application, onto a prepared application server or the like. It may also include the process of preparing the server (e.g., installing libraries, daemons, etc.). This is often managed by the cloud provider, below the hypervisor layer (e.g., the servers, storage, network hardware, and virtualization).
  • the customer may be responsible for handling (OS), middleware, and/or application deployment (e.g., on self-service virtual machines (e.g., that can be spun up on demand) or the like.
  • laaS provisioning may refer to acquiring computers or virtual hosts for use, and even installing needed libraries or services on them. In most cases, deployment does not include provisioning, and the provisioning may need to be performed first.
  • an infrastructure may have many interconnected elements. For example, there may be one or more virtual private clouds (VPCs) (e.g., a potentially on-demand pool of configurable and/or shared computing resources), also known as a core network. In some examples, there may also be one or more inbound/outbound traffic group rules provisioned to define how the inbound and/or outbound traffic of the network will be set up and one or more virtual machines (VMs). Other infrastructure elements may also be provisioned, such as a load balancer, a database, or the like. As more and more infrastructure elements are desired and/or added, the infrastructure may incrementally evolve.
  • VPCs virtual private clouds
  • VMs virtual machines
  • Other infrastructure elements may also be provisioned, such as a load balancer, a database, or the like. As more and more infrastructure elements are desired and/or added, the infrastructure may incrementally evolve.
  • continuous deployment techniques may be employed to enable deployment of infrastructure code across various virtual computing environments. Additionally, the described techniques can enable infrastructure management within these environments.
  • service teams can write code that is desired to be deployed to one or more, but often many, different production environments (e.g., across various different geographic locations, sometimes spanning the entire world).
  • the infrastructure on which the code will be deployed may need to first be set up.
  • the provisioning can be done manually, a provisioning tool may be utilized to provision the resources, and/or deployment tools may be utilized to deploy the code once the infrastructure is provisioned.
  • FIG. 9 is a block diagram 900 illustrating an example pattern of an laaS architecture, according to at least one embodiment.
  • Service operators 902 can be communicatively coupled to a secure host tenancy 904 that can include a virtual cloud network (VCN) 906 and a secure host subnet 908.
  • VCN virtual cloud network
  • the service operators 902 may be using one or more client computing devices, which may be portable handheld devices (e.g., an iPhone®, cellular telephone, an iPad®, computing tablet, a personal digital assistant (PDA)) or wearable devices (e.g., a Google Glass® head mounted display), 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, and the like, and being Internet, e-mail, short message service (SMS), Blackberry®, or other communication protocol enabled.
  • the client computing devices can be general purpose personal computers including, by way of example, personal computers and/or laptop computers running various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems.
  • the client computing devices can be workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems, including without limitation the variety of GNU/Linux operating systems, such as for example, Google Chrome OS.
  • client computing devices may be any other electronic device, such as a thin-client computer, an Internet-enabled gaming system (e.g., a Microsoft Xbox gaming console with or without a Kinect® gesture input device), and/or a personal messaging device, capable of communicating over a network that can access the VCN 906 and/or the Internet.
  • the VCN 906 can include a local peering gateway (LPG) 910 that can be communicatively coupled to a secure shell (SSH) VCN 912 via an LPG 910 contained in the SSH VCN 912.
  • the SSH VCN 912 can include an SSH subnet 914, and the SSH VCN 912 can be communicatively coupled to a control plane VCN 916 via the LPG 910 contained in the control plane VCN 916.
  • the SSH VCN 912 can be communicatively coupled to a data plane VCN 918 via an LPG 910.
  • the control plane VCN 916 and the data plane VCN 918 can be contained in a service tenancy 919 that can be owned and/or operated by the laaS provider.
  • the control plane VCN 916 can include a control plane demilitarized zone (DMZ) tier
  • the DMZ tier 920 that acts as a perimeter network (e.g., portions of a corporate network between the corporate intranet and external networks).
  • the DMZ-based servers may have restricted responsibilities and help keep breaches contained.
  • the DMZ tier 920 can include one or more load balancer (LB) subnet(s) 922, a control plane app tier 924 that can include app subnets) 926, a control plane data tier 928 that can include database (DB) subnet(s) 930 (e.g., frontend DB subnet(s) and/or backend DB subnet(s)).
  • LB load balancer
  • the LB subnet(s) 922 contained in the control plane DMZ tier 920 can be communicatively coupled to the app subnet(s) 926 contained in the control plane app tier 924 and an Internet gateway 934 that can be contained in the control plane VCN 916, and the app subnet(s) 926 can be communicatively coupled to the DB subnet(s) 930 contained in the control plane data tier 928 and a service gateway 936 and a network address translation (NAT) gateway 938.
  • the control plane VCN 916 can include the service gateway 936 and the NAT gateway 938.
  • the control plane VCN 916 can include a data plane mirror app tier 940 that can include app subnet(s) 926.
  • the app subnets) 926 contained in the data plane mirror app tier 940 can include a virtual network interface controller (VNIC) 942 that can execute a compute instance 944.
  • the compute instance 944 can communicatively couple the app subnet(s) 926 of the data plane mirror app tier 940 to app subnets) 926 that can be contained in a data plane app tier 946.
  • the data plane VCN 918 can include the data plane app tier 946, a data plane DMZ tier 948, and a data plane data tier 950.
  • the data plane DMZ tier 948 can include LB subnet(s) 922 that can be communicatively coupled to the app subnet(s) 926 of the data plane app tier 946 and the Internet gateway 934 of the data plane VCN 918.
  • the app subnet(s) 926 can be communicatively coupled to the service gateway 936 of the data plane VCN 918 and the NAT gateway 938 of the data plane VCN 918.
  • the data plane data tier 950 can also include the DB subnet(s) 930 that can be communicatively coupled to the app subnet(s) 926 of the data plane app tier 946.
  • the Internet gateway 934 of the control plane VCN 916 and of the data plane VCN 918 can be communicatively coupled to a metadata management service 952 that can be communicatively coupled to public Internet 954.
  • Public Internet 954 can be communicatively coupled to the NAT gateway 938 of the control plane VCN 916 and of the data plane VCN 918.
  • the service gateway 936 of the control plane VCN 916 and of the data plane VCN 918 can be communicatively couple to cloud services 956.
  • the service gateway 936 of the control plane VCN 916 or of the data plane VCN 918 can make application programming interface (API) calls to cloud services 956 without going through public Internet 954.
  • the API calls to cloud services 956 from the service gateway 936 can be one-way: the service gateway 936 can make API calls to cloud services 956, and cloud services 956 can send requested data to the service gateway 936.
  • cloud services 956 may not initiate API calls to the service gateway 936.
  • the secure host tenancy 904 can be directly connected to the service tenancy 919, which may be otherwise isolated.
  • the secure host subnet 908 can communicate with the SSH subnet 914 through an LPG 910 that may enable two-way communication over an otherwise isolated system. Connecting the secure host subnet 908 to the SSH subnet 914 may give the secure host subnet 908 access to other entities within the service tenancy 919.
  • the control plane VCN 916 may allow users of the service tenancy 919 to set up or otherwise provision desired resources. Desired resources provisioned in the control plane VCN 916 may be deployed or otherwise used in the data plane VCN 918.
  • the control plane VCN 916 can be isolated from the data plane VCN 918, and the data plane mirror app tier 940 of the control plane VCN 916 can communicate with the data plane app tier 946 of the data plane VCN 918 via VNICs 942 that can be contained in the data plane mirror app tier 940 and the data plane app tier 946.
  • users of the system, or customers can make requests, for example create, read, update, or delete (CRUD) operations, through public Internet 954 that can communicate the requests to the metadata management service 952.
  • the metadata management service 952 can communicate the request to the control plane VCN 916 through the Internet gateway 934.
  • the request can be received by the LB subnet(s) 922 contained in the control plane DMZ tier 920.
  • the LB subnets) 922 may determine that the request is valid, and in response to this determination, the LB subnet(s) 922 can transmit the request to app subnet(s) 926 contained in the control plane app tier 924.
  • the call to public Internet 954 may be transmitted to the NAT gateway 938 that can make the call to public Internet 954.
  • Memory that may be desired to be stored by the request can be stored in the DB subnet(s) 930.
  • the data plane mirror app tier 940 can facilitate direct communication between the control plane VCN 916 and the data plane VCN 918. For example, changes, updates, or other suitable modifications to configuration may be desired to be applied to the resources contained in the data plane VCN 918.
  • the control plane VCN 916 can directly communicate with, and can thereby execute the changes, updates, or other suitable modifications to configuration to, resources contained in the data plane VCN 918.
  • the control plane VCN 916 and the data plane VCN 918 can be contained in the service tenancy 919. In this case, the user, or the customer, of the system may not own or operate either the control plane VCN 916 or the data plane VCN 918.
  • the laaS provider may own or operate the control plane VCN 916 and the data plane VCN 918, both of which may be contained in the service tenancy 919.
  • This embodiment can enable isolation of networks that may prevent users or customers from interacting with other users’, or other customers’, resources. Also, this embodiment may allow users or customers of the system to store databases privately without needing to rely on public Internet 954, which may not have a desired level of threat prevention, for storage.
  • the LB subnet(s) 922 contained in the control plane VCN 916 can be configured to receive a signal from the service gateway 936.
  • the control plane VCN 916 and the data plane VCN 918 may be configured to be called by a customer of the laaS provider without calling public Internet 954.
  • Customers of the laaS provider may desire this embodiment since database(s) that the customers use may be controlled by the laaS provider and may be stored on the service tenancy 919, which may be isolated from public Internet 954.
  • FIG. 10 is a block diagram 1000 illustrating another example pattern of an laaS architecture, according to at least one embodiment.
  • Service operators 1002 e.g., service operators 902 of FIG. 9 can be communicatively coupled to a secure host tenancy 1004 (e.g., the secure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1006 (e.g., the VCN 906 of FIG. 9) and a secure host subnet 1008 (e.g., the secure host subnet 908 of FIG. 9).
  • VCN 1006 can include a local peering gateway (LPG) 1010 (e.g., the LPG 910 of FIG.
  • LPG local peering gateway
  • the SSH VCN 1012 can include an SSH subnet 1014 (e.g., the SSH subnet 914 of FIG. 9), and the SSH VCN 1012 can be communicatively coupled to a control plane VCN 1016 (e.g., the control plane VCN 916 of FIG. 9) via an LPG 1010 contained in the control plane VCN 1016.
  • the control plane VCN 1016 can be contained in a service tenancy 1019 (e.g., the service tenancy 919 of FIG. 9), and the data plane VCN 1018 (e.g., the data plane VCN 918 of FIG. 9) can be contained in a customer tenancy 1021 that may be owned or operated by users, or customers, of the system.
  • the control plane VCN 1016 can include a control plane DMZ tier 1020 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include LB subnet(s) 1022 (e.g., LB subnet(s) 922 of FIG. 9), a control plane app tier 1024 (e.g., the control plane app tier 924 of FIG. 9) that can include app subnet(s) 1026 (e.g., app subnet(s) 926 of FIG. 9), a control plane data tier 1028 (e.g., the control plane data tier 928 of FIG.
  • a control plane DMZ tier 1020 e.g., the control plane DMZ tier 920 of FIG. 9
  • LB subnet(s) 1022 e.g., LB subnet(s) 922 of FIG. 9
  • a control plane app tier 1024 e.g., the control plane app tier 924 of FIG. 9
  • the LB subnets) 1022 contained in the control plane DMZ tier 1020 can be communicatively coupled to the app subnet(s) 1026 contained in the control plane app tier 1024 and an Internet gateway 1034 (e.g., the Internet gateway 934 of FIG. 9) that can be contained in the control plane VCN 1016, and the app subnet(s) 1026 can be communicatively coupled to the DB subnet(s) 1030 contained in the control plane data tier 1028 and a service gateway 1036 (e.g., the service gateway of FIG. 9) and a network address translation (NAT) gateway 1038 (e.g., the NAT gateway 938 of FIG. 9).
  • the control plane VCN 1016 can include the service gateway 1036 and the NAT gateway 1038.
  • the control plane VCN 1016 can include a data plane mirror app tier 1040 (e.g., the data plane mirror app tier 940 of FIG. 9) that can include app subnets) 1026.
  • the app subnet(s) 1026 contained in the data plane mirror app tier 1040 can include a virtual network interface controller (VNIC) 1042 (e.g., the VNIC of 942) that can execute a compute instance 1044 (e.g., similar to the compute instance 944 of FIG. 9).
  • VNIC virtual network interface controller
  • the compute instance 1044 can facilitate communication between the app subnet(s) 1026 of the data plane mirror app tier 1040 and the app subnet(s) 1026 that can be contained in a data plane app tier 1046 (e.g., the data plane app tier 946 of FIG. 9) via the VNIC 1042 contained in the data plane mirror app tier 1040 and the VNIC 1042 contained in the data plane app tier 1046.
  • a data plane app tier 1046 e.g., the data plane app tier 946 of FIG. 9
  • the Internet gateway 1034 contained in the control plane VCN 1016 can be communicatively coupled to a metadata management service 1052 (e.g., the metadata management service 952 of FIG. 9) that can be communicatively coupled to public Internet 1054 (e.g., public Internet 954 of FIG. 9).
  • Public Internet 1054 can be communicatively coupled to the NAT gateway 1038 contained in the control plane VCN 1016.
  • the service gateway 1036 contained in the control plane VCN 1016 can be communicatively couple to cloud services 1056 (e.g., cloud services 956 of FIG. 9).
  • the data plane VCN 1018 can be contained in the customer tenancy 1021.
  • the laaS provider may provide the control plane VCN 1016 for each customer, and the laaS provider may, for each customer, set up a unique compute instance 1044 that is contained in the service tenancy 1019.
  • Each compute instance 1044 may allow communication between the control plane VCN 1016, contained in the service tenancy 1019, and the data plane VCN 1018 that is contained in the customer tenancy 1021.
  • the compute instance 1044 may allow resources, which are provisioned in the control plane VCN 1016 that is contained in the service tenancy 1019, to be deployed or otherwise used in the data plane VCN 1018 that is contained in the customer tenancy 1021.
  • the customer of the laaS provider may have databases that live in the customer tenancy 1021.
  • the control plane VCN 1016 can include the data plane mirror app tier 1040 that can include app subnet(s) 1026.
  • the data plane mirror app tier 1040 can reside in the data plane VCN 1018, but the data plane mirror app tier 1040 may not live in the data plane VCN 1018. That is, the data plane mirror app tier 1040 may have access to the customer tenancy 1021, but the data plane mirror app tier 1040 may not exist in the data plane VCN 1018 or be owned or operated by the customer of the laaS provider.
  • the data plane mirror app tier 1040 may be configured to make calls to the data plane VCN 1018 but may not be configured to make calls to any entity contained in the control plane VCN 1016.
  • the customer may desire to deploy or otherwise use resources in the data plane VCN 1018 that are provisioned in the control plane VCN 1016, and the data plane mirror app tier 1040 can facilitate the desired deployment, or other usage of resources, of the customer.
  • the customer of the laaS provider can apply filters to the data plane VCN 1018.
  • the customer can determine what the data plane VCN 1018 can access, and the customer may restrict access to public Internet 1054 from the data plane VCN 1018.
  • the laaS provider may not be able to apply filters or otherwise control access of the data plane VCN 1018 to any outside networks or databases. Applying filters and controls by the customer onto the data plane VCN 1018, contained in the customer tenancy 1021, can help isolate the data plane VCN 1018 from other customers and from public Internet 1054.
  • cloud services 1056 can be called by the service gateway 1036 to access services that may not exist on public Internet 1054, on the control plane VCN 1016, or on the data plane VCN 1018.
  • the connection between cloud services 1056 and the control plane VCN 1016 or the data plane VCN 1018 may not be live or continuous.
  • Cloud services 1056 may exist on a different network owned or operated by the laaS provider.
  • Cloud services 1056 may be configured to receive calls from the service gateway 1036 and may be configured not to receive calls from public Internet 1054.
  • Some cloud services 1056 may be isolated from other cloud services 1056, and the control plane VCN 1016 may be isolated from cloud services 1056 that may not be in the same region as the control plane VCN 1016.
  • FIG. 11 is a block diagram 1100 illustrating another example pattern of an laaS architecture, according to at least one embodiment.
  • Service operators 1102 e.g., service operators 902 of FIG.
  • a secure host tenancy 1104 (e.g., the secure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1106 (e.g., the VCN 906 of FIG. 9) and a secure host subnet 1108 (e.g., the secure host subnet 908 of FIG. 9).
  • VCN 1106 can include an LPG 1110 (e.g., the LPG 910 of FIG. 9) that can be communicatively coupled to an SSH VCN 1112 (e.g., the SSH VCN 912 of FIG. 9) via an LPG 1110 contained in the SSH VCN 1112.
  • the SSH VCN 1112 can include an SSH subnet 1114
  • the SSH VCN 1112 can be communicatively coupled to a control plane VCN 1116 (e.g., the control plane VCN 916 of FIG. 9) via an LPG 1110 contained in the control plane VCN 1116 and to a data plane VCN 1118 (e.g., the data plane 918 of FIG. 9) via an LPG 1110 contained in the data plane VCN 1118.
  • the control plane VCN 1116 and the data plane VCN 1118 can be contained in a service tenancy 1119 (e.g., the service tenancy 919 of FIG. 9).
  • the control plane VCN 1116 can include a control plane DMZ tier 1120 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include load balancer (LB) subnets) 1122 (e.g., LB subnet(s) 922 of FIG. 9), a control plane app tier 1124 (e.g., the control plane app tier 924 of FIG. 9) that can include app subnet(s) 1126 (e.g., similar to app subnet(s) 926 of FIG. 9), a control plane data tier 1128 (e.g., the control plane data tier 928 of FIG. 9) that can include DB subnet(s) 1130.
  • LB load balancer
  • the LB subnet(s) 1122 contained in the control plane DMZ tier 1120 can be communicatively coupled to the app subnet(s) 1126 contained in the control plane app tier 1124 and to an Internet gateway 1134 (e.g., the Internet gateway 934 of FIG. 9) that can be contained in the control plane VCN 1116, and the app subnet(s) 1126 can be communicatively coupled to the DB subnets) 1130 contained in the control plane data tier 1128 and to a service gateway 1136 (e.g., the service gateway of FIG. 9) and a network address translation (NAT) gateway 1138 (e.g., the NAT gateway 938 of FIG. 9).
  • the control plane VCN 1116 can include the service gateway 1136 and the NAT gateway 1138.
  • the data plane VCN 1118 can include a data plane app tier 1146 (e.g., the data plane app tier 946 of FIG. 9), a data plane DMZ tier 1148 (e.g., the data plane DMZ tier 948 of FIG. 9), and a data plane data tier 1150 (e.g., the data plane data tier 950 of FIG. 9).
  • the data plane DMZ tier 1148 can include LB subnet(s) 1122 that can be communicatively coupled to trusted app subnet(s) 1160 and untrusted app subnet(s) 1162 of the data plane app tier 1146 and the Internet gateway 1134 contained in the data plane VCN 1118.
  • the trusted app subnet(s) 1160 can be communicatively coupled to the service gateway 1136 contained in the data plane VCN 1118, the NAT gateway 1138 contained in the data plane VCN 1118, and DB subnet(s) 1130 contained in the data plane data tier 1150.
  • the untrusted app subnet(s) 1162 can be communicatively coupled to the service gateway 1136 contained in the data plane VCN 1118 and DB subnets) 1130 contained in the data plane data tier 1150.
  • the data plane data tier 1150 can include DB subnet(s) 1130 that can be communicatively coupled to the service gateway 1136 contained in the data plane VCN 1118.
  • the untrusted app subnet(s) 1162 can include one or more primary VNICs 1164(1)-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1166(1)-(N). Each tenant VM 1166(1)-(N) can be communicatively coupled to a respective app subnet 1167(1)-(N) that can be contained in respective container egress VCNs 1168(1)-(N) that can be contained in respective customer tenancies 1170(l)-(N). Respective secondary VNICs 1172(1)-(N) can facilitate communication between the untrusted app subnet(s) 1162 contained in the data plane VCN 1118 and the app subnet contained in the container egress VCNs 1168(1)-(N). Each container egress VCNs 1168(1)-(N) can include a NAT gateway 1138 that can be communicatively coupled to public Internet 1154 (e.g., public Internet 954 of FIG. 9).
  • public Internet 1154 e.g., public Internet 954 of FIG. 9
  • the Internet gateway 1134 contained in the control plane VCN 1116 and contained in the data plane VCN 1118 can be communicatively coupled to a metadata management service 1152 (e.g., the metadata management system 952 of FIG. 9) that can be communicatively coupled to public Internet 1154.
  • Public Internet 1154 can be communicatively coupled to the NAT gateway 1138 contained in the control plane VCN 1116 and contained in the data plane VCN 1118.
  • the service gateway 1136 contained in the control plane VCN 1116 and contained in the data plane VCN 1118 can be communicatively couple to cloud services 1156.
  • the data plane VCN 1118 can be integrated with customer tenancies 1170. This integration can be useful or desirable for customers of the laaS provider in some cases such as a case that may desire support when executing code.
  • the customer may provide code to run that may be destructive, may communicate with other customer resources, or may otherwise cause undesirable effects.
  • the laaS provider may determine whether to run code given to the laaS provider by the customer.
  • the customer of the laaS provider may grant temporary network access to the laaS provider and request a function to be attached to the data plane tier app 1146.
  • Code to run the function may be executed in the VMs 1166(1)-(N), and the code may not be configured to run anywhere else on the data plane VCN 1118.
  • Each VM 1166(1)-(N) may be connected to one customer tenancy 1170.
  • VMs 1166(1 )-(N) may be configured to run the code.
  • there can be a dual isolation e.g., the containers 1171(1)-(N) running code, where the containers 1171(1)-(N) may be contained in at least the VM 1166(1)-(N) that are contained in the untrusted app subnet(s) 1162), which may help prevent incorrect or otherwise undesirable code from damaging the network of the laaS provider or from damaging a network of a different customer.
  • the containers 1171(1)- (N) may be communicatively coupled to the customer tenancy 1170 and may be configured to transmit or receive data from the customer tenancy 1170.
  • the containers 1171(1)-(N) may not be configured to transmit or receive data from any other entity in the data plane VCN 1118.
  • the laaS provider may kill or otherwise dispose of the containers 1171(1)-(N).
  • the trusted app subnet(s) 1160 may run code that may be owned or operated by the laaS provider.
  • the trusted app subnet(s) 1160 may be communicatively coupled to the DB subnet(s) 1130 and be configured to execute CRUD operations in the DB subnet(s) 1130.
  • the untrusted app subnet(s) 1162 may be communicatively coupled to the DB subnet(s) 1130, but in this embodiment, the untrusted app subnets) may be configured to execute read operations in the DB subnet(s) 1130.
  • the containers 1171(1)-(N) that can be contained in the VM 1166(1)-(N) of each customer and that may run code from the customer may not be communicatively coupled with the DB subnet(s) 1130.
  • control plane VCN 1116 and the data plane VCN 1118 may not be directly communicatively coupled. In this embodiment, there may be no direct communication between the control plane VCN 1116 and the data plane VCN 1118. However, communication can occur indirectly through at least one method.
  • An LPG 1110 may be established by the laaS provider that can facilitate communication between the control plane VCN 1116 and the data plane VCN 1118.
  • the control plane VCN 1116 or the data plane VCN 1118 can make a call to cloud services 1156 via the service gateway 1136.
  • a call to cloud services 1156 from the control plane VCN 1116 can include a request for a service that can communicate with the data plane VCN 1118.
  • FIG. 12 is a block diagram 1200 illustrating another example pattern of an laaS architecture, according to at least one embodiment.
  • Service operators 1202 e.g., service operators 902 of FIG. 9 can be communicatively coupled to a secure host tenancy 1204 (e.g., the secure host tenancy 904 of FIG. 9) that can include a virtual cloud network (VCN) 1206 (e.g., the VCN 906 of FIG. 9) and a secure host subnet 1208 (e.g., the secure host subnet 908 of FIG. 9).
  • VCN 1206 can include an LPG 1210 (e.g., the LPG 910 of FIG.
  • the SSH VCN 1212 can include an SSH subnet 1214 (e.g., the SSH subnet 914 of FIG. 9), and the SSH VCN 1212 can be communicatively coupled to a control plane VCN 1216 (e.g., the control plane VCN 916 of FIG. 9) via an LPG 1210 contained in the control plane VCN 1216 and to a data plane VCN 1218 (e.g., the data plane 918 of FIG. 9) via an LPG 1210 contained in the data plane VCN 1218.
  • the control plane VCN 1216 and the data plane VCN 1218 can be contained in a service tenancy 1219 (e.g., the service tenancy 919 of FIG. 9).
  • the control plane VCN 1216 can include a control plane DMZ tier 1220 (e.g., the control plane DMZ tier 920 of FIG. 9) that can include LB subnet(s) 1222 (e.g., LB subnet(s) 922 of FIG. 9), a control plane app tier 1224 (e.g., the control plane app tier 924 of FIG. 9) that can include app subnet(s) 1226 (e.g., app subnet(s) 926 of FIG. 9), a control plane data tier 1228 (e.g., the control plane data tier 928 of FIG.
  • a control plane DMZ tier 1220 e.g., the control plane DMZ tier 920 of FIG. 9
  • LB subnet(s) 1222 e.g., LB subnet(s) 922 of FIG. 9
  • a control plane app tier 1224 e.g., the control plane app tier 924 of FIG. 9
  • the LB subnet(s) 1222 contained in the control plane DMZ tier 1220 can be communicatively coupled to the app subnet(s) 1226 contained in the control plane app tier 1224 and to an Internet gateway 1234 (e.g., the Internet gateway 934 of FIG. 9) that can be contained in the control plane VCN 1216, and the app subnet(s) 1226 can be communicatively coupled to the DB subnet(s) 1230 contained in the control plane data tier 1228 and to a service gateway 1236 (e.g., the service gateway of FIG. 9) and a network address translation (NAT) gateway 1238 (e.g., the NAT gateway 938 of FIG. 9).
  • the control plane VCN 1216 can include the service gateway 1236 and the NAT gateway 1238.
  • the data plane VCN 1218 can include a data plane app tier 1246 (e.g., the data plane app tier 946 of FIG. 9), a data plane DMZ tier 1248 (e.g., the data plane DMZ tier 948 of FIG. 9), and a data plane data tier 1250 (e.g., the data plane data tier 950 of FIG. 9).
  • the data plane DMZ tier 1248 can include LB subnet(s) 1222 that can be communicatively coupled to trusted app subnet(s) 1260 (e.g., trusted app subnet(s) 1160 of FIG.
  • untrusted app subnet(s) 1262 e.g., untrusted app subnet(s) 1162 of FIG. 11
  • the trusted app subnet(s) 1260 can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218, the NAT gateway 1238 contained in the data plane VCN 1218, and DB subnet(s) 1230 contained in the data plane data tier 1250.
  • the untrusted app subnet(s) 1262 can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218 and DB subnets) 1230 contained in the data plane data tier 1250.
  • the data plane data tier 1250 can include DB subnet(s) 1230 that can be communicatively coupled to the service gateway 1236 contained in the data plane VCN 1218.
  • the untrusted app subnet(s) 1262 can include primary VNICs 1264(1 )-(N) that can be communicatively coupled to tenant virtual machines (VMs) 1266(1)-(N) residing within the untrusted app subnet(s) 1262.
  • VMs virtual machines
  • Each tenant VM 1266(1)-(N) can run code in a respective container 1267(1)-(N) and be communicatively coupled to an app subnet 1226 that can be contained in a data plane app tier 1246 that can be contained in a container egress VCN 1268.
  • Respective secondary VNICs 1272(1)-(N) can facilitate communication between the untrusted app subnet(s) 1262 contained in the data plane VCN 1218 and the app subnet contained in the container egress VCN 1268.
  • the container egress VCN can include a NAT gateway 1238 that can be communicatively coupled to public Internet 1254 (e.g., public Internet 954 of FIG. 9).
  • the Internet gateway 1234 contained in the control plane VCN 1216 and contained in the data plane VCN 1218 can be communicatively coupled to a metadata management service 1252 (e.g., the metadata management system 952 of FIG. 9) that can be communicatively coupled to public Internet 1254.
  • Public Internet 1254 can be communicatively coupled to the NAT gateway 1238 contained in the control plane VCN 1216 and contained in the data plane VCN 1218.
  • the service gateway 1236 contained in the control plane VCN 1216 and contained in the data plane VCN 1218 can be communicatively couple to cloud services 1256.
  • the pattern illustrated by the architecture of block diagram 1200 of FIG. 12 may be considered an exception to the pattern illustrated by the architecture of block diagram 1100 of FIG. 11 and may be desirable for a customer of the laaS provider if the laaS provider cannot directly communicate with the customer (e.g., a disconnected region).
  • the respective containers 1267(1)-(N) that are contained in the VMs 1266(1)-(N) for each customer can be accessed in real-time by the customer.
  • the containers 1267(1)-(N) may be configured to make calls to respective secondaiy VNICs 1272(1)-(N) contained in app subnet(s) 1226 of the data plane app tier 1246 that can be contained in the container egress VCN 1268.
  • the secondary VNICs 1272(1)-(N) can transmit the calls to the NAT gateway 1238 that may transmit the calls to public Internet 1254.
  • the containers 1267(1)-(N) that can be accessed in realtime by the customer can be isolated from the control plane VCN 1216 and can be isolated from other entities contained in the data plane VCN 1218.
  • the containers 1267(1)-(N) may also be isolated from resources from other customers.
  • the customer can use the containers 1267(1)-(N) to call cloud services 1256.
  • the customer may run code in the containers 1267(1)-(N) that requests a service from cloud services 1256.
  • the containers 1267(1)-(N) can transmit this request to the secondaiy VNICs 1272(1)-(N) that can transmit the request to the NAT gateway that can transmit the request to public Internet 1254.
  • Public Internet 1254 can transmit the request to LB subnet(s) 1222 contained in the control plane VCN 1216 via the Internet gateway 1234.
  • the LB subnet(s) can transmit the request to app subnet(s) 1226 that can transmit the request to cloud services 1256 via the service gateway 1236.
  • laaS architectures 900, 1000, 1100, 1200 depicted in the figures may have other components than those depicted. Further, the embodiments shown in the figures are only some examples of a cloud infrastructure system that may incorporate an embodiment of the disclosure. In some other embodiments, the laaS systems may have more or fewer components than shown in the figures, may combine two or more components, or may have a different configuration or arrangement of components.
  • the laaS systems described herein may include a suite of applications, middleware, and database service offerings that are delivered to a customer in a self-service, subscription-based, elastically scalable, reliable, highly available, and secure manner.
  • An example of such an laaS system is the Oracle Cloud Infrastructure (OCI) provided by the present assignee.
  • OCI Oracle Cloud Infrastructure
  • FIG. 13 illustrates an example computer system 1300, in which various embodiments may be implemented.
  • the system 1300 may be used to implement any of the computer systems described above.
  • computer system 1300 includes a processing unit 1304 that communicates with a number of peripheral subsystems via a bus subsystem 1302. These peripheral subsystems may include a processing acceleration unit 1306, an I/O subsystem 1308, a storage subsystem 1318 and a communications subsystem 1324.
  • Storage subsystem 1318 includes tangible computer-readable storage media 1322 and a system memory 1310.
  • Bus subsystem 1302 provides a mechanism for letting the various components and subsystems of computer system 1300 communicate with each other as intended.
  • Bus subsystem 1302 is shown schematically as a single bus, alternative embodiments of the bus subsystem may utilize multiple buses.
  • Bus subsystem 1302 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
  • bus architectures may include an Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus, which can be implemented as a Mezzanine bus manufactured to the IEEE P1386.1 standard.
  • ISA Industry Standard Architecture
  • MCA Micro Channel Architecture
  • EISA Enhanced ISA
  • VESA Video Electronics Standards Association
  • PCI Peripheral Component Interconnect
  • Processing unit 1304 which can be implemented as one or more integrated circuits (e.g., a conventional microprocessor or microcontroller), controls the operation of computer system 1300.
  • processors may be included in processing unit 1304. These processors may include single core or multicore processors.
  • processing unit 1304 may be implemented as one or more independent processing units 1332 and/or 1334 with single or multicore processors included in each processing unit. In other embodiments, processing unit 1304 may also be implemented as a quad-core processing unit formed by integrating two dualcore processors into a single chip.
  • processing unit 1304 can execute a variety of programs in response to program code and can maintain multiple concurrently executing programs or processes. At any given time, some or all of the program code to be executed can be resident in processors) 1304 and/or in storage subsystem 1318. Through suitable programming, processor(s) 1304 can provide various functionalities described above.
  • Computer system 1300 may additionally include a processing acceleration unit 1306, which can include a digital signal processor (DSP), a special-purpose processor, and/or the like.
  • DSP digital signal processor
  • I/O subsystem 1308 may include user interface input devices and user interface output devices.
  • User interface input devices may include a keyboard, pointing devices such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, a button, a switch, a keypad, audio input devices with voice command recognition systems, microphones, and other types of input devices.
  • User interface input devices may include, for example, motion sensing and/or gesture recognition devices such as the Microsoft Kinect® motion sensor that enables users to control and interact with an input device, such as the Microsoft Xbox® 360 game controller, through a natural user interface using gestures and spoken commands.
  • User interface input devices may also include eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®). Additionally, user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.
  • eye gesture recognition devices such as the Google Glass® blink detector that detects eye activity (e.g., ‘blinking’ while taking pictures and/or making a menu selection) from users and transforms the eye gestures as input into an input device (e.g., Google Glass®).
  • user interface input devices may include voice recognition sensing devices that enable users to interact with voice recognition systems (e.g., Siri® navigator), through voice commands.
  • voice recognition systems e.g., Siri® navigator
  • User interface input devices may also include, without limitation, three dimensional (3D) mice, joysticks or pointing sticks, gamepads and graphic tablets, and audio/visual devices such as speakers, digital cameras, digital camcorders, portable media players, webcams, image scanners, fingerprint scanners, barcode reader 3D scanners, 3D printers, laser rangefinders, and eye gaze tracking devices. Additionally, user interface input devices may include, for example, medical imaging input devices such as computed tomography, magnetic resonance imaging, position emission tomography, medical ultrasonography devices. User interface input devices may also include, for example, audio input devices such as MIDI keyboards, digital musical instruments and the like.
  • User interface output devices may include a display subsystem, indicator lights, or nonvisual displays such as audio output devices, etc.
  • the display subsystem may be a cathode ray tube (CRT), a flat-panel device, such as that using a liquid crystal display (LCD) or plasma display, a projection device, a touch screen, and the like.
  • CTR cathode ray tube
  • LCD liquid crystal display
  • plasma display a projection device
  • touch screen a touch screen
  • output device is intended to include all possible types of devices and mechanisms for outputting information from computer system 1300 to a user or other computer.
  • user interface output devices may include, without limitation, a variety of display devices that visually convey text, graphics and audio/video information such as monitors, printers, speakers, headphones, automotive navigation systems, plotters, voice output devices, and modems.
  • Computer system 1300 may comprise a storage subsystem 1318 that provides a tangible non-transitory computer-readable storage medium for storing software and data constructs that provide the functionality of the embodiments described in this disclosure.
  • the software can include programs, code, instructions, scripts, etc., that when executed by one or more cores or processors of processing unit 1304 provide the functionality described above.
  • Storage subsystem 1318 may also provide a repository for storing data used in accordance with the present disclosure.
  • storage subsystem 1318 can include various components including a system memory 1310, computer-readable storage media 1322, and a computer-readable storage media reader 1320.
  • System memory 1310 may store program instructions that are loadable and executable by processing unit 1304.
  • System memory 1310 may also store data that is used during the execution of the instructions and/or data that is generated during the execution of the program instructions.
  • Various different kinds of programs may be loaded into system memory 1310 including but not limited to client applications, Web browsers, mid-tier applications, relational database management systems (RDBMS), virtual machines, containers, etc.
  • RDBMS relational database management systems
  • System memory 1310 may also store an operating system 1316.
  • operating system 1316 may include various versions of Microsoft Windows®, Apple Macintosh®, and/or Linux operating systems, a variety of commercially-available UNIX® or UNIX-like operating systems (including without limitation the variety of GNU/Linux operating systems, the Google Chrome® OS, and the like) and/or mobile operating systems such as iOS, Windows® Phone, Android® OS, BlackBerry® OS, and Palm® OS operating systems.
  • the virtual machines along with their guest operating systems (GOSs) may be loaded into system memory 1310 and executed by one or more processors or cores of processing unit 1304.
  • GOSs guest operating systems
  • System memory 1310 can come in different configurations depending upon the type of computer system 1300.
  • system memory 1310 may be volatile memory (such as random access memory (RAM)) and/or non-volatile memory (such as read-only memory (ROM), flash memory, etc.).
  • RAM random access memory
  • ROM read-only memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • system memory 1310 may include a basic input/output system (BIOS) containing basic routines that help to transfer information between elements within computer system 1300, such as during start-up.
  • BIOS basic input/output system
  • Computer-readable storage media 1322 may represent remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing, storing, computer-readable information for use by computer system 1300 including instructions executable by processing unit 1304 of computer system 1300.
  • Computer-readable storage media 1322 can include any appropriate media known or used in the art, including storage media and communication media, such as but not limited to, volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage and/or transmission of information.
  • This can include tangible computer- readable storage media such as RAM, ROM, electronically erasable programmable ROM (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disk (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other tangible computer readable media.
  • computer-readable storage media 1322 may include a hard disk drive that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive that reads from or writes to a removable, nonvolatile magnetic disk, and an optical disk drive that reads from or writes to a removable, nonvolatile optical disk such as a CD ROM, DVD, and Blu-Ray® disk, or other optical media.
  • Computer-readable storage media 1322 may include, but is not limited to, Zip® drives, flash memory cards, universal serial bus (USB) flash drives, secure digital (SD) cards, DVD disks, digital video tape, and the like.
  • Computer-readable storage media 1322 may also include, solid-state drives (SSD) based on non-volatile memory such as flash-memory based SSDs, enterprise flash drives, solid state ROM, and the like, SSDs based on volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • SSD solid-state drives
  • volatile memory such as solid state RAM, dynamic RAM, static RAM, DRAM-based SSDs, magnetoresistive RAM (MRAM) SSDs, and hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • MRAM magnetoresistive RAM
  • hybrid SSDs that use a combination of DRAM and flash memory based SSDs.
  • the disk drives and their associated computer-readable media may provide non-volatile storage of computer-readable instructions, data structures, programs, and other data for computer system 1300.
  • Machine-readable instructions executable by one or more processors or cores of processing unit 1304 may be stored on a non-transitory computer-readable storage medium.
  • a non-transitory computer-readable storage medium can include physically tangible memory or storage devices that include volatile memory storage devices and/or non-volatile storage devices. Examples of non-transitory computer-readable storage medium include magnetic storage media (e.g., disk or tapes), optical storage media (e.g., DVDs, CDs), various types of RAM, ROM, or flash memory, hard drives, floppy drives, detachable memory drives (e.g., USB drives), or other type of storage device.
  • Communications subsystem 1324 provides an interface to other computer systems and networks. Communications subsystem 1324 serves as an interface for receiving data from and transmitting data to other systems from computer system 1300. For example, communications subsystem 1324 may enable computer system 1300 to connect to one or more devices via the Internet.
  • communications subsystem 1324 can include radio frequency (RF) transceiver components for accessing wireless voice and/or data networks (e.g., using cellular telephone technology, advanced data network technology, such as 3G, 4G or EDGE (enhanced data rates for global evolution), WiFi (IEEE 802.11 family standards, or other mobile communication technologies, or any combination thereof), global positioning system (GPS) receiver components, and/or other components.
  • RF radio frequency
  • communications subsystem 1324 can provide wired network connectivity (e.g., Ethernet) in addition to or instead of a wireless interface.
  • communications subsystem 1324 may also receive input communication in the form of structured and/or unstructured data feeds 1326, event streams 1328, event updates 1330, and the like on behalf of one or more users who may use computer system 1300.
  • communications subsystem 1324 may be configured to receive data feeds 1326 in real-time from users of social networks and/or other communication services such as Twitter® feeds, Facebook® updates, web feeds such as Rich Site Summary (RSS) feeds, and/or real-time updates from one or more third party information sources.
  • RSS Rich Site Summary
  • communications subsystem 1324 may also be configured to receive data in the form of continuous data streams, which may include event streams 1328 of real-time events and/or event updates 1330, that may be continuous or unbounded in nature with no explicit end.
  • continuous data streams may include, for example, sensor data applications, financial tickers, network performance measuring tools (e.g., network monitoring and traffic management applications), clickstream analysis tools, automobile traffic monitoring, and the like.
  • Communications subsystem 1324 may also be configured to output the structured and/or unstructured data feeds 1326, event streams 1328, event updates 1330, and the like to one or more databases that may be in communication with one or more streaming data source computers coupled to computer system 1300.
  • Computer system 1300 can be one of various types, including a handheld portable device (e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA), a wearable device (e.g., a Google Glass® head mounted display), a PC, a workstation, a mainframe, a kiosk, a server rack, or any other data processing system.
  • a handheld portable device e.g., an iPhone® cellular phone, an iPad® computing tablet, a PDA
  • a wearable device e.g., a Google Glass® head mounted display
  • PC personal computer
  • workstation e.g., a workstation
  • mainframe e.g., a mainframe
  • kiosk e.g., a server rack
  • server rack e.g., a server rack, or any other data processing system.
  • Processes can communicate using a variety of techniques including but not limited to conventional techniques for inter process communication, and different pairs of processes may use different techniques, or the same pair of processes may use different techniques at different times.
  • Embodiments may be implemented by using a computer program product, comprising computer program/instructions which, when executed by a processor, cause the processor to perform any of the methods described in the disclosure.
  • Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is intended to be understood within the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Mathematical Physics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Sont divulguées des techniques pour établir un environnement d'amorçage virtuel. Un environnement informatique distribué peut générer un réseau en nuage virtuel à l'intérieur d'une région hôte correspondant à un ou plusieurs centres de données. Le système informatique distribué peut ensuite mettre en œuvre un environnement d'amorçage virtuel à l'intérieur du réseau en nuage virtuel. Un premier service peut être déployé dans l'environnement d'amorçage virtuel. Une connexion réseau peut être établie entre la région hôte et une région cible. Le premier service dans l'environnement d'amorçage virtuel peut ensuite déployer des ressources dans la région cible sur la connexion de réseau.
PCT/US2023/062056 2022-02-08 2023-02-06 Environnement d'amorçage virtuel pour construire des centres de données régionaux WO2023154680A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US202263308003P 2022-02-08 2022-02-08
US63/308,003 2022-02-08
US202263312814P 2022-02-22 2022-02-22
US63/312,814 2022-02-22
US202263314945P 2022-02-28 2022-02-28
US63/314,945 2022-02-28
US18/105,779 2023-02-03
US18/105,779 US20230251888A1 (en) 2022-02-08 2023-02-03 Virtual bootstrap environment for building regional data centers

Publications (1)

Publication Number Publication Date
WO2023154680A1 true WO2023154680A1 (fr) 2023-08-17

Family

ID=85570180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/062056 WO2023154680A1 (fr) 2022-02-08 2023-02-06 Environnement d'amorçage virtuel pour construire des centres de données régionaux

Country Status (1)

Country Link
WO (1) WO2023154680A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170228227A1 (en) * 2012-03-02 2017-08-10 Vmware, Inc. Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud infrastructure
WO2021150307A1 (fr) * 2020-01-20 2021-07-29 Oracle International Corporation Techniques de déploiement de ressources d'infrastructure avec un outil d'approvisionnement déclaratif

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170228227A1 (en) * 2012-03-02 2017-08-10 Vmware, Inc. Single, logical, multi-tier application blueprint used for deployment and management of multiple physical applications in a cloud infrastructure
WO2021150307A1 (fr) * 2020-01-20 2021-07-29 Oracle International Corporation Techniques de déploiement de ressources d'infrastructure avec un outil d'approvisionnement déclaratif

Similar Documents

Publication Publication Date Title
US11539754B2 (en) Techniques for generating network security policies for application components deployed in a computing environment
US20230251871A1 (en) Techniques for migrating services from a virtual bootstrap environment
US20230254287A1 (en) Techniques for a virtual bootstrap environment in a distributed virtual private network
US11736579B1 (en) Techniques for resource discovery
WO2023154683A1 (fr) Techniques de migration de services à partir d'un environnement d'amorçage virtuel
US20230251888A1 (en) Virtual bootstrap environment for building regional data centers
US20230251909A1 (en) Region seed establishment
US20230251872A1 (en) Techniques for managing region build dependencies
US20230251870A1 (en) Techniques for resource discovery while building data centers
US20230251956A1 (en) Regional capability aware proxy testing
US20230251876A1 (en) Data management techniques for cloud regions
WO2023154680A1 (fr) Environnement d'amorçage virtuel pour construire des centres de données régionaux
US20230251873A1 (en) User interface for critical path resources
US20230251851A1 (en) User interface for on-deck capabilities
US20230273816A1 (en) Reentrant service deployments
US20230305858A1 (en) Techniques for building data centers in cloud regions
US20230251852A1 (en) Techniques for building data centers in cloud regions with version sets
US20230251921A1 (en) Associating capabilities and alarms
WO2023154681A1 (fr) Techniques pour un environnement d'amorçage virtuel dans un réseau privé virtuel distribué
WO2023154660A1 (fr) Établissement d'élément de développement de région
WO2023154211A1 (fr) Techniques permettant de gérer des dépendances de construction de région
WO2023154671A1 (fr) Test de mandataire sensible à la capacité régionale
WO2023154226A1 (fr) Techniques de gestion de données pour régions en nuage
US20240311517A1 (en) Techniques for validating cloud regions built at a prefab factory
US20240314038A1 (en) Static network fabric at a prefab factory

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23710590

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202447054763

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 2023710590

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2023710590

Country of ref document: EP

Effective date: 20240909