Abstract: Techniques are described for performing an automated region build. An orchestration service (e.g., a Multi-Flock Orchestrator) may managing bootstrapping efforts for any suitable number of services within a region corresponding to one or more data centers. Each service can be associated with a respective set of resources (e.g., infrastructure components, software artifacts, etc.). The orchestration service can identify dependencies between services based on corresponding configuration files associated with the services. The orchestration service can determine, based on the identified dependencies, an order by which operations for bootstrapping the services are to be performed. The orchestration service can incrementally instruct other system components (e.g., a provisioning and deployment manager) to perform operations for bootstrapping the plurality of services in accordance with determined order.

Abstract: Techniques are described for automating the creating, provisioning, and deployment of resources and infrastructure for building a data center that is configured to provide a set of services. Techniques are described for scheduling and executing multiple releases for a service. For a service for which a first release has been previously scheduled and executed, a second release may be scheduled for the service in response to an optional capability dependency for the service being published in a data center. The second release for the flock is then executed. As a result of the execution of the second release, additional enhanced capabilities may be added to the service.

Abstract: Techniques are described for identifying resources within a region of a cloud-computing environment. A Resource Identification Service (RIS) may be configured to obtain a flock configuration file comprising resource discovery data associated with a service. The resource discovery data may indicate a set of parameters with which a previously existing resource of the cloud-computing environment is to be identified. RIS may execute operations to identify the previously existing resource based at least in part on matching attributes associated with previously existing resource to the set of parameters of the resource discovery data. The RIS may identify, from the flock configuration file, a set of import operations to perform to obtain an identifier corresponding to the previously existing resource. The identifier may be provided to cause the previously existing resource to be utilized in a region build.

Abstract: Techniques are described for monitoring the health of services in a computing environment such as a data center. More particularly, the present disclosure describes techniques for monitoring the health and availability of capabilities in a computing environment such as a data center by enabling alarms to be associated with the capabilities. A capability refers to a set of resources in a data center. By providing the ability to associate an alarm with a capability, the health or availability of the associated capability can be monitored or ascertained by tracking the state of the alarm associated with the capability. For example, if the alarm associated with a particular capability is triggered, it may indicate that the particular capability and the one or more resources corresponding to the particular capability are not in a healthy state. Accordingly, by monitoring alarms associated with capabilities, the health of the associated capabilities can be ascertained.

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

Abstract: A test environment is provided for testing of a flock configuration. A configuration file of a service is parsed to identify one or more capabilities for executing a release of the configuration file of the service. The one or more capabilities correspond to operations performed with respect to one or more resource types. A capability-aware-proxy server included in the test environment is configured based on the one or more capabilities identified from the configuration file of the service. The release of the configuration file of the service is executed in the test environment in accordance with the configured capability aware-proxy server. The capability aware-proxy server generates a response message corresponding to an execution result of the release of the configuration file of the service.

Abstract: Techniques are described for identifying resources within a region of a cloud computing environment that may be leveraged during a region build. A Multi-Flock Orchestrator (MFO) may be configured to obtain configuration files corresponding to services to be bootstrapped within the region during a region build process. MFO may determine an order by which the services are to be bootstrapped and transmits a first request in accordance with the order. Planning data may be received (e.g., indicating an intent to create a new resource). MFO may obtain (e.g., via a Resource Identification Service) an identifier corresponding to a previously created resource. MFO can modify the planning data with the identifier and transmits a second request comprising the modified planning data. Transmitting the second request can cause resource corresponding to the flock configuration file to be bootstrapped within the region using the resource corresponding to the identifier.

Abstract: Techniques are described for identifying resources within a region of a cloud-computing environment. A Resource Identification Service (RIS) may be configured to obtain a flock configuration file comprising resource discovery data associated with a service. The resource discovery data may indicate a set of parameters with which a previously existing resource of the cloud-computing environment is to be identified. RIS may execute operations to identify the previously existing resource based at least in part on matching attributes associated with previously existing resource to the set of parameters of the resource discovery data. The RIS may identify, from the flock configuration file, a set of import operations to perform to obtain an identifier corresponding to the previously existing resource. The identifier may be provided to cause the previously existing resource to be utilized in a region build.

Abstract: Techniques are described for performing an automated region build. An orchestration service (e.g., a Multi-Flock Orchestrator (MFO)) may be configured to bootstrap any suitable number of services within a region corresponding to one or more data centers. Each service can be associated with a respective set of resources (e.g., infrastructure components to be provisioned, software artifacts to be deployed, etc.). The WO can obtain configuration files corresponding to the services to be bootstrapped and perform a static analysis the configuration files to identify one or more dependencies between the services. Circular dependencies can be identified and resolved before region build. A graph may be generated that maintains the dependencies identified and indicates a corresponding order with which bootstrapping tasks are to be performed. The WO may traverse the graph to incrementally instruct, according to the identified dependencies, a provisioning and deployment manager to bootstrap services in the region.

Abstract: Techniques are described for performing an automated region build using a version set that identifies versions of configuration files and/or artifacts with which the region build is to be performed. A Multi-Flock Orchestrator (MFO) may be configured to maintain multiple version sets identifying a respective set of configuration files associated with various services to be bootstrapped. The MFO may execute a validation process using one version set. A second version set may be identified from the first based on identifying configuration files that successfully passed the validation process. The automated region build can be performed using the second version set.

Abstract: The present embodiments relate to determining a critical path that identifies an order for bootstrapping a subset of resources within a data center under build. A cloud infrastructure orchestration service (CIOS) can identify from configuration files associated with resources to be bootstrapped within the data set, a set of capabilities. The CIOS can identify a first set of capabilities on which publishing each respective capability depends. User input can be received identifying a selected flock. The CIOS can identify the unpublished capabilities on which capabilities corresponding to the selected flock depend. Those unpublished capabilities can be ranked and provided via a visualization to the user. The unpublished capabilities can be ranked according to identifying, for a respective unpublished capability, a set of capabilities that are capable of being published responsive to publishing the respective unpublished capability.

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

Abstract: Techniques are described for performing an automated region build with real time region data. Region data including region identifiers and execution target identifiers for the region may be maintained. When a modification of the region data is detected (or new region data is detected), configuration files corresponding to bootstrapping resources (e.g., at the execution targets) within the region may be obtained. Operations are executed to cause the configuration files to be updated. This may include recompiling or otherwise injecting region data into the configuration files. A region build may be executed to bootstrap resources within the region using the updated configuration files.

Abstract: Techniques for transferring data to a secure computing region that is isolated from any public networks is disclosed. In some embodiments, one or more artifacts for the secure computing region are packaged. As part of the packaging, one or more data packets and metadata for the one or more artifacts can be generated. The metadata indicates corresponding destination components for the one or more artifacts within the secure computing region. The data packet(s) are received and transmitted by a first data diode endpoint device. The first data diode endpoint device is configured to transmit data to the secure computing region via a second data diode endpoint device, the second data diode endpoint device being configured to restrict data from being transmitted to a destination outside of the secure computing region. The transmission of the one or more data packets may be monitored by the system.

Abstract: Some examples enable profile-based management of multiple communication channels and associated communication services on an electronic device. For example, role-based profiles may be used to manage and filter communications from various contacts. A profile may be set on the electronic device, such as in response to a user input, or automatically based on a determined context of the electronic device. For instance, the context may be determined from one or more of a physical location of the electronic device, a time of day, a day of the week, or a detected activity of the user. Further, some examples include a unified communication interface that may enable a user to select a contact to receive a communication, and the electronic device may select a communication channel for communicating with the selected contact based at least in part on the profile currently set for the electronic device.

Abstract: Described are methods and systems of providing directed interaction from one or more presenter devices to one or more participant devices. Directed interaction allows one or more presenters to change application state, device settings, or both on the participant devices. Within the constraints imposed by the presenter device, the participant devices may be able to change content presentation, position, and so forth. The participant devices may also generate participant status data, which may be provided to the presenter devices.