Deployment Target Catalog

Go up to Terms and Definitions

A Deployment Target Catalog is a controlled collection of records describing the Deployment Targets available for 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 Deployment Platform from a specific configured Deployment Target
• A Deployment Target from the Infrastructure Environment deployed to it
• The capabilities offered by a Deployment Target from the requirements expressed by a Deployment Description
• Authorized Deployment Targets from unavailable, unapproved, suspended, or retired Deployment Targets

A Deployment Target Catalog can contain Deployment Targets based on:

• Amazon Web Services (AWS)
• Microsoft Azure
• Google Cloud Platform
• VMware vSphere
• Red Hat OpenShift Container Platform
• Bare-Metal Infrastructure

A catalog can include Deployment Targets operating in a:

• Connected Environment
• Disconnected Environment
• Air-Gapped Environment

Each Deployment Target record can identify:

• A unique Deployment Target identifier
• A human-readable name
• A description
• The 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 Machine Images
• The supported Infrastructure Baselines
• The supported Deployment Operations
• The supported Deployment Validation capabilities
• The supported Deployment Rollback capabilities
• The authorized 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 Provenance
• The associated Traceability

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.

*controlled collection of records that identify and describe Deployment Targets available for Deployment*

• Dido Solutions, Crucible architecture and requirements terminology
• Deployment
• Deployment Description
• Deployment Platform
• Deployment Target

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 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.

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.