dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target [2026/07/22 13:02] – ↷ Page name changed from dido:99_annexes:annex-b-terms-and-definitions:d:deployment_targe to dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target nick_didodido:99_annexes:annex-b-terms-and-definitions:d:deployment_target [2026/07/22 13:04] (current) nick_dido
Line 5: Line 5:
 ===== Discussion ===== ===== Discussion =====
  
-A Deployment Target identifies a specific destination to which [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] can deploy an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+A Deployment Target identifies a specific configured destination to which [[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 deployment destination rather than a general technology, vendor, or platform category.+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: For example:
  
-  * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services]] identifies a Cloud Provider and Deployment Platform +  * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]] identifies a Deployment Platform 
-  * An identified AWS account, region, virtual networkand resource boundary can constitute a Deployment Target +  * An identified AWS account, region, virtual private cloud, subnet set, resource boundary, and authorization context can constitute a Deployment Target 
-  * Microsoft Azure identifies a Cloud Provider and Deployment Platform +  * [[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, and network boundary can constitute a Deployment Target +  * An identified Azure tenant, subscription, region, resource group, network boundary, and authorization context can constitute a Deployment Target 
-  * Google Cloud Platform identifies a Cloud Provider and Deployment Platform +  * [[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, and network boundary can constitute a Deployment Target +  * An identified Google Cloud organization, project, region, network boundary, resource boundary, and authorization context can constitute a Deployment Target 
-  * VMware vSphere identifies a virtualization platform +  * [[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, and network can constitute a Deployment Target +  * 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 container platform +  * [[dido:99_annexes:annex-b-terms-and-definitions:r:openshift|Red Hat OpenShift Container Platform]] identifies a Deployment Platform 
-  * An identified OpenShift cluster, namespace, project, and resource boundary can constitute a Deployment Target +  * 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 +  * [[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 group of physical servers, networks, storage resources, and management interfaces can constitute a Deployment Target+  * An identified set of physical servers, networks, storage resources, management interfaces, and authorization boundaries can constitute a Deployment Target
  
-A Deployment Target can operate within a:+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:c:connected_environment|Connected Environment]]
Line 30: Line 34:
   * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]   * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]
  
-A Deployment Target can identify:+A Deployment Target record can identify:
  
-  * The Deployment Platform +  * A unique Deployment Target identifier 
-  * The Cloud Provider or infrastructure operator +  * A human-readable name 
-  * The account, tenant, subscription, project, or organizational boundary +  * A description 
-  * The geographic region, site, facility, or zone+  * 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 network boundary
   * The compute-resource boundary   * The compute-resource boundary
   * The storage-resource boundary   * The storage-resource boundary
 +  * The operational environment
 +  * The connectivity classification
   * The security classification   * The security classification
   * The compliance profile   * The compliance profile
-  * The operational environment +  * The supported processor architectures 
-  * The Provider Implementation +  * The supported operating systems 
-  * The credentials or authorization mechanism +  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] 
-  * The authorized repositories and external resources +  * The supported [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]] 
-  * The Deployment Target status+  * 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 ===== ===== Definition =====
  
-*specific destination, identified by its platform and deployment boundaries, to which Crucible can deploy an Infrastructure Environment*+//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 ===== ===== Source =====
  
   * Dido Solutions, Crucible architecture and requirements terminology   * 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 ===== ===== Note =====
  
-A Deployment Platform identifies the technology or platform type used for deployment. A Deployment Target identifies a specific configured destination that uses that Deployment Platform.+A Deployment Platform identifies 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. Multiple Deployment Targets can use the same Deployment Platform.
  
-A Deployment Target does not identify the Infrastructure Environment deployed to itThe Deployment Target identifies the destination. The Infrastructure Environment identifies the deployed and managed realization.+A Deployment Target can use more than one platform layerFor 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 can expose only the resources and capabilities authorized for its operational environment.+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 ===== ===== Example =====
Line 69: Line 109:
 An AWS Deployment Target identifies: An AWS Deployment Target identifies:
  
-  * The AWS account +  * A Deployment Target identifier 
-  * The AWS region +  * [[dido:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]] as the Deployment Platform 
-  * The virtual private cloud+  * An AWS account 
 +  * An AWS region 
 +  * virtual private cloud
   * The permitted subnets   * The permitted subnets
   * The permitted availability zones   * The permitted availability zones
-  * The identity role used by Crucible+  * 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 authorized Artifact repositories
 +  * The supported Machine Images
 +  * The supported Infrastructure Baselines
   * The security and compliance constraints   * The security and compliance constraints
-  * The Provider Implementation used for deployment+  * 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.
  
 ---- ----
  • dido/99_annexes/annex-b-terms-and-definitions/d/deployment_target.1784750554.txt.gz
  • Last modified: 2026/07/22 13:02
  • by nick_dido