Deployment Target [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Deployment Target ======

[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]

===== Discussion =====

A Deployment Target identifies a specific configured destination to which a [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]] can deliver an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].

A Deployment Target represents a concrete destination rather than a general technology, vendor, infrastructure category, or [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]].

For example:

  * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]] identifies a Deployment Platform
  * An identified AWS account, region, virtual private cloud, subnet set, resource boundary, and authorization context can constitute a Deployment Target
  * [[dido:99_annexes:annex-b-terms-and-definitions:m:microsoft_azure|Microsoft Azure]] identifies a Deployment Platform
  * An identified Azure tenant, subscription, region, resource group, network boundary, and authorization context can constitute a Deployment Target
  * [[dido:99_annexes:annex-b-terms-and-definitions:g:google_cloud_platform|Google Cloud Platform]] identifies a Deployment Platform
  * An identified Google Cloud organization, project, region, network boundary, resource boundary, and authorization context can constitute a Deployment Target
  * [[dido:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere|VMware vSphere]] identifies a Deployment Platform
  * An identified vCenter instance, data center, cluster, resource pool, datastore set, network set, and authorization context can constitute a Deployment Target
  * [[dido:99_annexes:annex-b-terms-and-definitions:r:openshift|Red Hat OpenShift Container Platform]] identifies a Deployment Platform
  * An identified OpenShift cluster, project or namespace boundary, resource quota, network boundary, and authorization context can constitute a Deployment Target
  * [[dido:99_annexes:annex-b-terms-and-definitions:b:bare-metal_infrastructure|Bare-Metal Infrastructure]] identifies an infrastructure category that can provide a Deployment Platform
  * An identified set of physical servers, networks, storage resources, management interfaces, and authorization boundaries can constitute a Deployment Target

A Deployment Target forms part of a [[dido:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]].

The Target Environment identifies the broader organizational, operational, security, compliance, connectivity, and physical context. The Deployment Target identifies the specific configured destination within that context to which the Deployment applies.

A Deployment Target can exist 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]]

A Deployment Target record can identify:

  * A unique Deployment Target identifier
  * A human-readable name
  * A description
  * The [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]]
  * The platform, cloud, or infrastructure operator
  * The Provider Implementation
  * The account, tenant, subscription, project, cluster, site, or organizational boundary
  * The geographic region, availability zone, facility, or physical location
  * The network boundary
  * The compute-resource boundary
  * The storage-resource boundary
  * The operational environment
  * The connectivity classification
  * The security classification
  * The compliance profile
  * The supported processor architectures
  * The supported operating systems
  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]]
  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]]
  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] capabilities
  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback|Deployment Rollback]] capabilities
  * The authorized [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Stores]]
  * The authorized Artifact repositories
  * The authorized external resources
  * The credential or authorization reference
  * The responsible owner or authority
  * The approval status
  * The availability status
  * The lifecycle status
  * The effective date
  * The review or expiration date
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
  * The associated [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]

A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_description|Deployment Description]] identifies the requirements of a proposed Deployment. A Deployment Target identifies the destination whose recorded capabilities, constraints, authorization, and status can be evaluated against those requirements.

A [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target_catalog|Deployment Target Catalog]] records the Deployment Targets available for discovery, evaluation, and selection.

===== Definition =====

//specific configured destination, identified by its Deployment Platform, resource boundaries, operating conditions, and authorization context, to which a Deployment can deliver an Infrastructure Environment//

===== Source =====

  * Dido Solutions, Crucible architecture and requirements terminology
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_description|Deployment Description]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]]
  * [[dido:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]]

===== Note =====

A Deployment Platform identifies a platform type or technology. A Deployment Target identifies a specific configured destination that uses that Deployment Platform.

Multiple Deployment Targets can use the same Deployment Platform.

A Deployment Target can use more than one platform layer. For example, an OpenShift Deployment Target can use Amazon Web Services, Microsoft Azure, Google Cloud Platform, VMware vSphere, or Bare-Metal Infrastructure as its underlying platform.

A Deployment Target does not identify the [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] deployed to it:

  * The Deployment Target identifies the destination
  * The Deployment Description identifies the Deployment requirements
  * The Deployment creates or changes the Infrastructure Environment

The presence of a Deployment Target in a Deployment Target Catalog does not by itself authorize its use. The Deployment Target record identifies its approval, availability, lifecycle, security, and compliance status.

A Deployment Target should reference an authorized credential-management mechanism rather than contain reusable credentials, private keys, passwords, or access tokens directly.

===== Example =====

An AWS Deployment Target identifies:

  * A Deployment Target identifier
  * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]] as the Deployment Platform
  * An AWS account
  * An AWS region
  * A virtual private cloud
  * The permitted subnets
  * The permitted availability zones
  * The compute- and storage-resource boundaries
  * The identity role used for Deployment
  * The authorized [[dido:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Stores]]
  * The authorized Artifact repositories
  * The supported Machine Images
  * The supported Infrastructure Baselines
  * The security and compliance constraints
  * The Provider Implementation
  * The approval and availability status
  * The responsible authority

[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] compares a Deployment Description with the recorded capabilities and constraints of the Deployment Target before performing the Deployment.

----

<WRAP centeralign>
© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
</WRAP>