public:99_annexes:annex-b-terms-and-definitions:d:deployment_target_catalog

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:d:deployment_target_catalog [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:deployment_target_catalog [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Deployment Target Catalog ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +A Deployment Target [[public:99_annexes:annex-b-terms-and-definitions:c:catalog_entry|Catalog]] is a controlled collection of records describing the [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Targets]] available for [[public:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]].
 +
 +Each catalog record identifies one concrete Deployment Target and the information required to determine whether the Deployment Target can receive a proposed Deployment.
 +
 +A Deployment Target Catalog distinguishes:
 +
 +  * A general [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]] from a specific configured Deployment Target
 +  * A Deployment Target from the [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] deployed to it
 +  * The capabilities offered by a Deployment Target from the requirements expressed by a [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_description|Deployment Description]]
 +  * Authorized Deployment Targets from unavailable, unapproved, suspended, or retired Deployment Targets
 +
 +A Deployment Target Catalog can contain Deployment Targets based on:
 +
 +  * [[public:99_annexes:annex-b-terms-and-definitions:a:aws|Amazon Web Services (AWS)]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:m:microsoft_azure|Microsoft Azure]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:g:google_cloud_platform|Google Cloud Platform]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere|VMware vSphere]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:r:openshift|Red Hat OpenShift Container Platform]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:b:bare-metal_infrastructure|Bare-Metal Infrastructure]]
 +
 +A catalog can include Deployment Targets operating in a:
 +
 +  * [[public:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]]
 +
 +Each Deployment Target record can identify:
 +
 +  * A unique Deployment Target identifier
 +  * A human-readable name
 +  * A description
 +  * The [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]]
 +  * The Cloud Provider, platform operator, or infrastructure operator
 +  * The Provider Implementation or Provider Plugin
 +  * 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 [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]]
 +  * The supported [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baselines]]
 +  * The supported [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_operation|Deployment Operations]]
 +  * The supported [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_validation|Deployment Validation]] capabilities
 +  * The supported [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_rollback|Deployment Rollback]] capabilities
 +  * The authorized [[public: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 [[public:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]]
 +  * The associated [[public:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] can compare the requirements contained in a Deployment Description with the capabilities, constraints, authorization, and status recorded for each Deployment Target.
 +
 +The catalog provides controlled information for Deployment Target discovery and selection. The catalog does not itself perform a Deployment.
 +
 +===== Definition =====
 +
 +*controlled collection of records that identify and describe Deployment Targets available for Deployment*
 +
 +===== Source =====
 +
 +  * Dido Solutions, Crucible architecture and requirements terminology
 +  * [[public:99_annexes:annex-b-terms-and-definitions:d:deployment|Deployment]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_description|Deployment Description]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platform]]
 +  * [[public:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]]
 +
 +===== Note =====
 +
 +A Deployment Target Catalog records concrete Deployment Targets. It does not catalog only general Deployment Platform types.
 +
 +Multiple Deployment Target records can reference the same Deployment Platform.
 +
 +A single Deployment Target record can identify multiple capabilities, constraints, authorizations, and operational conditions.
 +
 +The presence of a Deployment Target in the catalog does not by itself authorize its use. The Deployment Target record identifies its approval, availability, lifecycle, security, and compliance status.
 +
 +A Deployment Target Catalog should reference an authorized credential-management mechanism rather than contain reusable credentials, private keys, passwords, or access tokens directly.
 +
 +A Deployment Target Catalog differs from a Deployment Description:
 +
 +  * A Deployment Description identifies what a Deployment requires
 +  * A Deployment Target Catalog identifies the destinations available to satisfy those requirements
 +
 +A Deployment Target Catalog differs from a [[public:99_annexes:annex-b-terms-and-definitions:d:dependency_store|Dependency Store]]. A Dependency Store contains or makes Dependencies available, while a Deployment Target Catalog records the destinations that may use those Dependencies during Deployment.
 +
 +===== Example =====
 +
 +A Deployment Target Catalog contains the following approved Deployment Target records:
 +
 +  * An AWS Deployment Target in a Connected Environment for development
 +  * A VMware vSphere Deployment Target in a Disconnected Environment for integration testing
 +  * An OpenShift Deployment Target in an Air-Gapped Environment for production
 +  * A Bare-Metal Infrastructure Deployment Target in a secure facility for validation
 +
 +Each record identifies:
 +
 +  * The Deployment Target identifier
 +  * The Deployment Platform
 +  * The operational and connectivity environment
 +  * The resource boundaries
 +  * The supported Infrastructure Baselines
 +  * The supported Machine Images
 +  * The authorized Dependency Stores and Artifact repositories
 +  * The security and compliance constraints
 +  * The Provider Implementation
 +  * The approval and availability status
 +  * The responsible authority
 +
 +Crucible compares a Deployment Description with these records and selects a Deployment Target whose recorded capabilities and constraints satisfy the Deployment requirements.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>