Abstract: A cloud infrastructure orchestration service may maintain a service plan and manifest (SPAM) corresponding to a service to be bootstrapped (e.g., provisioned and deployed) to a cloud computing environment (e.g., to a data center). The service plan may specify a deterministic order of releases for performing a process to fully bootstrap the service using one or more build milestones and one or more execution units, each execution unit specifying ordered steps for transitioning between build milestones Each step may reference one or more execution target checkpoint transitions, which in turn reference an alias of a configuration file that defines a release. A manifest may be used to identify the configuration files and artifacts to be used by the releases and to validate the service plan. A SPAM may be used to reduce/eliminate nondeterministic behavior of previous orchestration systems and to provide visualizations of the bootstrapping process at different granularities.

Abstract: A cloud infrastructure orchestration service (CIOS) may track build progress made by any suitable number of regional orchestrators. The cloud infrastructure orchestration system may include any suitable number of regional orchestrators, each regional orchestrator executing in an isolated hosting environment (e.g., a service cell isolated from other service cells). An orchestrator control plane may be configured to generate a build plan for bootstrapping a plurality of services within a data center, the build plan may be generated based at least in part on a service build definition of a plurality of service build definitions, the service build definition specifying a deterministic process for bootstrapping a service of the plurality of services. The orchestrator control plane may instruct a regional orchestrator to perform bootstrapping operations according to the build plan and may track the progress of the bootstrapping operations on an ongoing basis.

Abstract: A cloud-computing service (e.g., a “Puffin Service”) is described. The service may maintain service and skill catalogs corresponding to various services to be deployed to a region (e.g., during a region build). The service may host numerous user interfaces with which various service and skill metadata may be provided. In some embodiments, such data may include one or more dependencies between skills. The data managed by the cloud-computing service may be utilized to build a dependency graph. Navigation of the dependency graph may be performed via one or more user interfaces hosted by the cloud-computing service. An orchestration service (e.g., a Multi-Flock Orchestrator) may manage bootstrapping efforts for any suitable number of services during a region build based at least in part on dependencies between skills.

Abstract: A cloud infrastructure orchestration service (CIOS) may track build progress made by any suitable number of regional orchestrators. An orchestrator control plane may be configured to generate a region build plan for bootstrapping a plurality of services within a data center. The orchestrator control plane may instruct a region orchestrator to execute a build according to the build plan. The region orchestrator may be configured to update an execution state corresponding to the execution of the region build plan as it executes steps of the ordered steps of the region build plan. At any suitable time (e.g., when executing one of the steps fails), intervention data may be received with which a new region build plan may be generated. The new region build plan may be used for subsequent execution of the region build. This may enable run-time corrections to be made.

Abstract: Techniques for responding to a trigger event that threatens an operability of at least a portion of a cloud infrastructure of a cloud environment are disclosed. In response to detecting the occurrence of the trigger event, a system executes a mitigation process for mitigating an effect of the trigger event. The mitigation process includes determining a set of candidate services as candidates for stopping execution of operations in the cloud environment. In addition, the mitigation process generates a ranking of the set of candidate services based on weighting metrics associated with respective service features of the set of candidate services. Further, based on the ranking, the mitigation process selects a service of the set of candidate services and stops execution of operations of the service to at least partially mitigate the effect of the trigger event.

Abstract: Techniques for managing resource constraints of a cloud environment are disclosed. A system receives a request to initiate a provisioning process for provisioning a first service in the cloud environment. The system determines a resource constraint associated with a resource that the first service utilizes. Based on the resource constraint, the system determines a set of candidate services that also utilize the resource as candidates for deprovisioning from the cloud environment. The system identifies respective service features of the set of candidate services and generates a ranking of the set of candidate services based on weighting metrics associated with the respective service features. Based on the ranking, the system selects a second service of the set of candidate services for deprovisioning from the cloud environment. The system deprovisions the second service to alleviate the resource constraint and then provisions the first service by executing the provisioning process.

Abstract: A system for storing women's undergarments is disclosed. The system may include a plurality of brassiere inserts, and one or more underpants storage components. The brassiere inserts may include a first and second cupped feature that have a shape substantially corresponding to the shape of a brassiere, and that nestably engage a brassiere. The brassiere inserts may be removable from the storage unit including the base. The underpants storage component includes cavities into which underpants can be inserted. The system may also include a lid to cover the storage unit and to protect the brassieres stored therein, and a hanger, which gives the user the option of hanging the storage system.