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

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 [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:d:deployment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Deployment ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +Deployment is the controlled process of placing, configuring, integrating, verifying, and making a system, service, software artifact, [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]], or infrastructure capability available within a [[public:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]].
 +
 +The process may include resource creation, artifact transfer, installation, configuration, service activation, dependency resolution, verification, registration, and operational handover.
 +
 +Deployment differs from an [[public:99_annexes:annex-b-terms-and-definitions:i:image_build|Image Build]]. An Image Build produces a Machine Image, while Deployment places or realizes an artifact or capability in a Target Environment.
 +
 +[[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] is a specialized Deployment that realizes infrastructure resources from an Infrastructure Definition.
 +
 +===== Definition =====
 +
 +//controlled process of placing, configuring, integrating, verifying, and making a system, service, software artifact, machine image, or infrastructure capability available within a target environment//
 +
 +===== Source =====
 +
 +Generalized from software engineering, systems engineering, release management, platform engineering, and infrastructure automation usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Deployment does not necessarily imply release to production or approval for operational use. A Deployment may target development, test, staging, production, recovery, connected, disconnected, or air-gapped environments.
 +
 +A successful Deployment does not by itself establish compliance, accreditation, or [[public:99_annexes:annex-b-terms-and-definitions:o:operational_approval|Operational Approval]].
 +
 +===== Example =====
 +
 +Crucible uploads a verified Machine Image, creates the required infrastructure, configures [[public:99_annexes:annex-b-terms-and-definitions:k:kubernetes]] services, verifies node status, and makes the resulting cluster available in the selected Target Environment.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>