Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Deployment Platform ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Deployment Platform is a [[public: | ||
| + | |||
| + | A Deployment Platform can provide capabilities for: | ||
| + | |||
| + | * Compute | ||
| + | * Storage | ||
| + | * Networking | ||
| + | * Identity and access management | ||
| + | * Security enforcement | ||
| + | * Configuration management | ||
| + | * Monitoring and observability | ||
| + | * Orchestration | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * Operational lifecycle management | ||
| + | |||
| + | A Deployment Platform identifies a technology or platform category. It does not identify a specific configured destination. | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | Examples include: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | |||
| + | A Deployment Platform can operate within a: | ||
| + | |||
| + | * [[public: | ||
| + | * [[public: | ||
| + | * [[public: | ||
| + | |||
| + | 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 [[public: | ||
| + | |||
| + | A Deployment Platform can host one or more [[public: | ||
| + | |||
| + | Within the Crucible architecture: | ||
| + | |||
| + | * A [[public: | ||
| + | * A [[public: | ||
| + | * 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 ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from software deployment, platform engineering, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Deployment Platform identifies a platform type or technology. A Deployment Target identifies a specific configured destination that uses the Deployment Platform. | ||
| + | |||
| + | 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, | ||
| + | * 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 [[public: | ||
| + | |||
| + | Those characteristics belong to the Deployment Target, Target Environment, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | 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 | ||
| + | |||
| + | [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||