| Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform [2026/07/13 11:05] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform [2026/07/22 13:01] (current) – nick_dido |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| A Deployment Platform is a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform|Platform]] selected to receive, host, configure, operate, and manage deployed software, machine images, services, or infrastructure components. | A Deployment Platform is a [[dido:99_annexes:annex-b-terms-and-definitions:p:platform|Platform]] that provides the technical capabilities required to receive, host, configure, operate, and manage deployed software, [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]], services, or infrastructure components. |
| |
| The Deployment Platform provides the technical and operational capabilities required by the deployment, including compute, storage, networking, identity, security, monitoring, orchestration, and lifecycle management. | A Deployment Platform can provide capabilities for: |
| |
| A Deployment Platform forms part of a [[dido:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]]. The Target Environment identifies the broader destination and operating context, while the Deployment Platform provides the managed capabilities on which the deployed artefacts operate. | * Compute |
| | * Storage |
| | * Networking |
| | * Identity and access management |
| | * Security enforcement |
| | * Configuration management |
| | * Monitoring and observability |
| | * Orchestration |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback|Deployment Rollback]] |
| | * Operational lifecycle management |
| |
| Within the Crucible architecture, a declarative description identifies deployment requirements, and a provider plugin maps those requirements to the capabilities of the selected Deployment Platform. | A Deployment Platform identifies a technology or platform category. It does not identify a specific configured destination. |
| | |
| | A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]] identifies a specific destination that uses a Deployment Platform. Multiple Deployment Targets can use the same Deployment Platform. |
| | |
| | Examples include: |
| | |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:m:microsoft_azure|Microsoft Azure]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:g:google_cloud_platform|Google Cloud Platform]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere|VMware vSphere]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:r:openshift|Red Hat OpenShift Container Platform]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:b:bare-metal_infrastructure|Bare-Metal Infrastructure]] |
| | |
| | A Deployment Platform can operate within a: |
| | |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]] |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]] |
| | |
| | The connectivity classification describes the operating conditions of a Deployment Target or Target Environment. It does not define the Deployment Platform itself. |
| | |
| | A Deployment Platform forms part of a [[dido:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]]. The Target Environment identifies the broader destination and operating context, including its organizational, operational, security, compliance, connectivity, and resource boundaries. |
| | |
| | A Deployment Platform can host one or more [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_environment|Execution Environments]]. An Execution Environment provides the runtime conditions in which deployed software or services execute. |
| | |
| | Within the Crucible architecture: |
| | |
| | * A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_description|Deployment Description]] identifies the requirements for a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] |
| | * A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target_catalog|Deployment Target Catalog]] identifies the available Deployment Targets |
| | * A Deployment Target identifies a specific configured destination |
| | * The Deployment Target identifies the Deployment Platform that provides its platform capabilities |
| | * A Provider Implementation maps provider-independent deployment requirements to the interfaces and resource model of the Deployment Platform |
| |
| ===== Definition ===== | ===== Definition ===== |
| |
| //[[dido:99_annexes:annex-b-terms-and-definitions:p:platform|platform]] selected to receive, host, configure, operate, and manage deployed software, machine images, services, or infrastructure components// | //[[dido:99_annexes:annex-b-terms-and-definitions:p:platform|platform]] that provides the technical capabilities required to receive, host, configure, operate, and manage deployed software, Machine Images, services, or infrastructure components// |
| |
| ===== Source ===== | ===== Source ===== |
| |
| Generalized from software deployment, platform engineering, infrastructure automation, and cloud-computing usage and specialized for the Crucible architecture and operational model. | Generalized from software deployment, platform engineering, infrastructure automation, virtualization, container orchestration, and cloud-computing usage and specialized for the Crucible architecture and operational model. |
| |
| ===== Note ===== | ===== Note ===== |
| |
| A Deployment Platform may be cloud-based, on-premises, virtualized, container-based, disconnected, or air-gapped. | A Deployment Platform identifies a platform type or technology. A Deployment Target identifies a specific configured destination that uses the Deployment Platform. |
| |
| A Deployment Platform may host one or more [[dido:99_annexes:annex-b-terms-and-definitions:e:execution_environment|Execution Environments]]. | For example: |
| | |
| | * Amazon Web Services is a Deployment Platform |
| | * An identified AWS account, region, virtual private cloud, and resource boundary form a Deployment Target |
| | * VMware vSphere is a Deployment Platform |
| | * An identified vCenter instance, data center, cluster, resource pool, datastore, and network form a Deployment Target |
| | * Red Hat OpenShift Container Platform is a Deployment Platform |
| | * An identified OpenShift cluster and its deployment boundary form a Deployment Target |
| | |
| | A Deployment Platform can itself operate on another Deployment Platform. |
| | |
| | For example, Red Hat OpenShift Container Platform can operate on: |
| | |
| | * Amazon Web Services |
| | * Microsoft Azure |
| | * Google Cloud Platform |
| | * VMware vSphere |
| | * Bare-Metal Infrastructure |
| | |
| | In this case, OpenShift provides the container platform, while the underlying platform provides the compute, storage, and networking infrastructure. |
| | |
| | The Deployment Platform does not identify: |
| | |
| | * A specific account, tenant, subscription, project, cluster, or site |
| | * A specific geographic region or facility |
| | * A specific network or resource boundary |
| | * A specific security or compliance authorization |
| | * A specific set of deployment credentials |
| | * A deployed [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] |
| | |
| | Those characteristics belong to the Deployment Target, Target Environment, or Infrastructure Environment. |
| |
| ===== Example ===== | ===== Example ===== |
| |
| An Oracle Cloud Infrastructure tenancy containing compute, networking, storage, load balancing, and identity services acts as the Deployment Platform for a Crucible-deployed Kubernetes cluster. | VMware vSphere acts as a Deployment Platform. |
| | |
| | A Deployment Target based on VMware vSphere identifies: |
| | |
| | * A specific vCenter instance |
| | * A data center |
| | * A cluster |
| | * A resource pool |
| | * One or more datastores |
| | * One or more networks |
| | * The authorized identity used for Deployment |
| | * The security and compliance constraints |
| | * The operational and connectivity environment |
| | |
| | [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] uses a Provider Implementation to translate a Deployment Description into the platform-specific operations required to create an Infrastructure Environment on that Deployment Target. |
| |
| ---- | ---- |