Service plans and manifests for data center orchestration

Abstract

A cloud infrastructure orchestration service may maintain a service plan and manifest (SPAM) corresponding to a service being bootstrapped (e.g., provisioned and deployed) to a cloud computing environment (e.g., a data center). The service plan may specify a deterministic order of releases for executing the process to fully bootstrap the service using one or more build milestones and one or more execution units, each execution unit specifying ordered steps to transition between build milestones. Each step may refer to one or more execution target checkpoint migrations, which themselves refer to aliases of configuration files defining the release. A manifest may be used to identify configuration files and artifacts to be used by the release and to authenticate the service plan. SPAM may be used to mitigate / eliminate the non-deterministic behavior of previous orchestration systems and to provide visualization of the bootstrap process at different granularities.

Images