6.2 Deploy in a Connected Environment [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.
====== 6.2 Deploy in a Connected Environment ======

[[dido:02-crusible:06-connected-operations:start|Go to 6. Connected Operations]]

Within a [[dido:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]], [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] deploys an identified environment to an authorized [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_target|Deployment Target]].

Connected operation allows the deployment activity to interact with the authorized provider services, repositories, registries, and other External Systems required by the applicable deployment.

Connectivity establishes the operating condition. The Deployment Orchestration and Multi-Cloud Management requirements define the deployment capabilities.

===== Identify the Deployment =====

Crucible identifies the deployment to perform and the environment to be realized.

The deployment identifies:

  * The applicable Infrastructure Baseline
  * The selected Machine Images or Container Images
  * The required application artifacts
  * The selected Deployment Target
  * The applicable Provider Implementation
  * The deployment parameters
  * The provider-specific parameters
  * The required infrastructure resources
  * The applicable security and configuration information

Each controlled input retains its identity and revision so the deployed result can be traced to the content used to create it.

===== Select the Deployment Target =====

Crucible selects an authorized Deployment Target that supports the resources and operations required by the deployment.

A connected Deployment Target can provide access to:

  * Compute resources
  * Storage resources
  * Network resources
  * Virtual-machine services
  * Container services
  * Platform services
  * Provider-specific deployment interfaces

The selected Deployment Target can reside in a commercial cloud, private cloud, on-premises environment, or another supported infrastructure environment when the applicable requirements and Provider Implementation support that target.

Selection of a Deployment Target does not independently authorize deployment. The applicable access controls, Security Domain restrictions, and organizational approvals continue to govern the operation.

===== Prepare the Deployment Inputs =====

Crucible makes the controlled deployment inputs available to the applicable deployment operation.

The deployment inputs can include:

  * An Infrastructure Baseline
  * Machine Images
  * Container Images
  * Application artifacts
  * Configuration definitions
  * Network definitions
  * Storage definitions
  * Security configuration
  * Preserved Dependencies
  * Credential references
  * Deployment parameters
  * Provider-specific parameters

A connected deployment can obtain required inputs from authorized external repositories and services when the applicable lifecycle activity permits that access.

Crucible preserves the identity and revision of each input used by the deployment.

===== Resolve Provider-Specific Realization =====

Crucible separates provider-independent deployment intent from provider-specific realization.

The provider-independent deployment content identifies the required resources, relationships, and lifecycle operations.

The applicable Provider Implementation resolves that intent into the interfaces, resource types, identifiers, and parameters required by the selected provider.

Provider-specific information can include:

  * Provider resource types
  * Regions or locations
  * Compute classes
  * Storage classes
  * Network identifiers
  * Image identifiers
  * Service identifiers
  * Provider credentials or credential references
  * Provider-specific configuration parameters

The Provider Implementation does not change the intended deployment outcome merely because the provider uses a different resource model or interface.

===== Perform the Deployment =====

Crucible performs the operations required to realize the environment on the selected Deployment Target.

The deployment can include:

  - Verify the required deployment inputs
  - Establish access to the selected Deployment Target
  - Create or configure infrastructure resources
  - Create network and storage resources
  - Instantiate Machine Images or Container Images
  - Apply the required configuration
  - Deploy application workloads
  - Apply security configuration
  - Execute required post-deployment operations
  - Record the result of each operation

The applicable Infrastructure Baseline and deployment description determine which operations Crucible performs and their required ordering.

===== Coordinate Deployment Operations =====

Crucible coordinates the individual operations that comprise the deployment.

Deployment orchestration preserves the relationships among:

  * The selected Deployment Target
  * The Infrastructure Baseline
  * The Provider Implementation
  * The deployed Images
  * The deployment parameters
  * The individual deployment operations
  * The resources created or changed
  * The resulting deployment status

Crucible records whether each deployment operation completed, failed, or could not proceed.

===== Deploy Across Supported Providers =====

Crucible can apply a consistent deployment lifecycle across supported provider environments.

Provider environments can differ in their:

  * Resource models
  * Interfaces
  * Authentication mechanisms
  * Network services
  * Storage services
  * Image formats
  * Configuration parameters
  * Operational constraints

The Provider Implementation handles provider-specific behavior while Crucible preserves the common deployment intent and lifecycle relationships.

Support for multiple providers does not require every provider to expose identical services or behavior.

===== Deploy to Multiple Targets =====

A deployment can include more than one Deployment Target when the applicable deployment definition requires a distributed environment.

Crucible preserves the identity and deployment result of each target-specific operation.

A connected multi-target deployment can include:

  * Resources in multiple provider environments
  * Resources in multiple geographic locations
  * Resources in separate Security Domains
  * Central and edge resources
  * Different infrastructure types within one operational environment

Each Deployment Target remains independently identifiable even when the deployed resources collectively form one environment.

===== Handle Deployment Failures =====

When a deployment operation fails, Crucible records:

  * The failed operation
  * The affected Deployment Target
  * The inputs supplied to the operation
  * The observed failure
  * The operations completed before the failure
  * The resources created or changed
  * The resulting deployment state

A deployment failure does not authorize substitution of an unidentified resource, unapproved provider, or uncontrolled deployment process.

Any rollback, recovery, remediation, or redeployment activity remains governed by its applicable requirement and deployment definition.

===== Connected Deployment Result =====

The connected deployment result identifies:

  * The deployment identifier
  * The selected Deployment Target or Targets
  * The Infrastructure Baseline and revision
  * The deployed Images and revisions
  * The Provider Implementation and revision
  * The deployment parameters
  * The provider-specific parameters
  * The deployment operations performed
  * The status of each operation
  * The resources created, changed, or removed
  * The resulting deployment status
  * Any failure information
  * 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]]

The deployment result becomes the subject of the applicable validation, assessment, remediation, or subsequent lifecycle activity.

===== Requirements Addressed =====

^ Requirement ^ Statement ^
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-002]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-002#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-003]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-003#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-004#Statement&noheader&nofooter&noeditbtn}} |
| [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005]] | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-005#Statement&noheader&nofooter&noeditbtn}} |

The linked leaf requirement pages remain the canonical sources.

----

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