dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002

Differences

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

Link to this comparison view

Next revision		 Previous revision
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002 [2026/07/17 09:09] – created nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002 [2026/07/30 05:45] (current) – nick_dido
Line 5: Line 5:
 ===== Statement ===== ===== Statement =====
  
-[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy a [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] to a target [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall deploy virtual machines.+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-002
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-002.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|virtual machines]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses a direct functional behavior but requires terminology and normative-language normalization.+FR-DEP-002:
  
-The following Specification Discipline and Authoring findings apply:+  * Replaces **The system** with the defined system name [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] 
 +  * Changes **shall** to the established uppercase normative form **SHALL** 
 +  * Links **Virtual Machines** to the controlling definition
  
-  * **The system** does not use the defined system name +No other substantive normalization is required.
-  * **shall** does not follow the established uppercase normative convention +
-  * **Virtual machines** should use the defined [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] concept +
-  * The source statement does not identify the target Infrastructure Environment +
-  * The source statement does not prescribe a virtualization platform, [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] format, provider, or deployment method +
-  * The source statement does not independently require validation, rollback, compliance assessment, or runtime activation +
- +
-The normalized Statement: +
- +
-  * Replaces **The system** with [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] +
-  * Retains the direct and testable verb **deploy** +
-  * Uses the defined Virtual Machine concept +
-  * Identifies the target Infrastructure Environment +
-  * Retains one primary required behavior+
  
 ===== Rationale ===== ===== Rationale =====
  
-A [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] provides an isolated computing subject through virtualized processor, memory, storage, network, and related resources.+A [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] provides a computing environment through virtualized processor, memory, storage, network, and related resources.
  
-Virtual Machine deployment may use:+Deploying Virtual Machines enables Crucible to create virtualized computing resources through separately governed deployment workflows.
  
-  * A selected [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] +This requirement establishes the Virtual Machine deployment behavior without prescribing:
-  * Virtual processor configuration +
-  * Virtual memory configuration +
-  * Virtual storage configuration +
-  * Virtual network configuration +
-  * Identity and access configuration +
-  * Security configuration +
-  * Startup parameters +
-  * Provider-specific parameters+
  
-The applicable [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] determines which inputs apply.+  * The [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] 
 +  * The target Infrastructure Environment 
 +  * The virtualization platform 
 +  * The Virtual Machine configuration 
 +  * Runtime activation 
 +  * Deployment validation 
 +  * Deployment rollback 
 +  * Compliance assessment
  
-Virtual Machine deployment contributes to: +Separate requirements define those subjects and behaviors.
- +
-  * Repeatable computing-resource creation +
-  * Consistent Virtual Machine configuration +
-  * Automated workload hosting +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:r:reproducibility|Reproducibility]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]]+
  
 ===== Applies To ===== ===== Applies To =====
Line 69: Line 50:
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
   * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]]   * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]]
-  * [[dido:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Images]] +  * Virtual Machine deployment operations
-  * Virtualized computing resources +
-  * Virtualization platforms +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configurations]] +
-  * Virtual Machine deployment workflows +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]]+
  
 ===== Verification ===== ===== Verification =====
  
-  - Verification SHALL confirm that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for a [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] +Verification confirms that:
-  - Verification SHALL confirm that the deployment operation targets an identified [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] +
-  - Verification SHALL confirm that the Virtual Machine exists in the target Infrastructure Environment after successful deployment+
  
-Verification may include: +  - One or more Virtual Machines are selected for deployment 
- +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for the selected Virtual Machines 
-  * Virtual Machine deployment testing +  - The completed deployment produces the selected Virtual Machines 
-  * Virtualization-platform inspection +  - The resulting Virtual Machines can be identified as outputs of the tested deployment
-  * Target-environment inspection +
-  * Virtual Machine state inspection +
-  * Deployment-output inspection +
-  * Deployment-log inspection +
-  * Automated CI/CD Pipeline testing +
- +
-The verification record SHALL identify: +
- +
-  - The deployed Virtual Machine +
-  - The target Infrastructure Environment +
-  - The deployment operation +
-  - The deployment result +
-  - The observed Virtual Machine state +
-  - The generated [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] +
- +
-===== Outgoing Traceability ===== +
- +
-This requirement realizes: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-001|MO-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002|MO-002]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003|MO-003]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-006|MO-006]] +
- +
-This requirement relates to: +
- +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-001|FR-IMG-001 — Build Virtual Machine Images]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-02-image-management:fr-img-003|FR-IMG-003 — Immutable Infrastructure Workflows]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-001|FR-DEP-001 — Deploy Infrastructure Resources]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-006|FR-DEP-006 — Deployment Rollback]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-007|FR-DEP-007 — Deployment Validation]] +
-  * [[dido:02-crusible:06-machine-images-and-image-layers:start|6. Machine Images and Image Layers]] +
-  * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]]+
  
 ===== Referenced By ===== ===== Referenced By =====
  
-The wiki Backlinks function provides the current list of pages that reference ''FR-DEP-002''.+The following pages reference this requirement:
  
-Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list. +{{backlinks>.#dido:02-crusible}}
- +
-Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship. +
- +
-===== ConOps Relationship ===== +
- +
-The Crucible Concept of Operations describes a Phase 1 workflow that builds controlled Machine Images and deploys infrastructure through an automated CI/CD Pipeline. +
- +
-FR-DEP-002 establishes the required behavior for deploying a Virtual Machine to a target Infrastructure Environment. +
- +
-Requirements governing Machine Image building, Image Promotion, rollback, and validation define separate behavior. +
- +
-===== Delivery Phase ===== +
- +
-Phase 1+
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that Crucible deploys a Virtual Machine to a target Infrastructure Environment.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-DEP-002 as a leaf requirement.</todo>
- +
-The source System Requirements Specification identifies Version 1.1 as a draft.+
  
 ---- ----
-===== Notes for Editors =====+===== Issues =====
  
-This requirement page should retain the stable requirement identifier ''FR-DEP-002''.+<todo>Determine whether separate requirements identify the Machine Image and configuration used for each Virtual Machine deployment.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements identify the Deployment Target or Infrastructure Environment for each Virtual Machine deployment.</todo>
  
-The Source Statement should preserve the original wording from the controlling System Requirements Specification.+---- 
 +===== Notes for Editors =====
  
-The Statement should remain limited to deployment of a Virtual Machine.+This requirement page retains the stable requirement identifier ''FR-DEP-002''.
  
-Requirements for Machine Image building, Image Promotion, runtime activation, rollback, validation, and retirement should remain in their applicable requirement pages.+This page is a leaf requirement page and omits a trailing '':start'' from its namespace.
  
-Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.+The Statement preserves the approved source intent by requiring Crucible to deploy Virtual Machines.
  
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+Do not add a Machine Image, target Infrastructure Environment, Deployment Target, virtualization platform, runtime-activation, rollback, validation, compliance-assessment, or retirement obligation unless the controlling requirement changes through an approved requirements process.
  
 To reference this requirement Statement from another wiki page, insert: To reference this requirement Statement from another wiki page, insert:
Line 176: Line 98:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-002#Statement&noheader&nofooter&noeditbtn}}
 </code> </code>
- 
-Do not rename this page after an external citation unless a redirect or move plan is in place. 
  
 ---- ----
  • dido/02-crusible/99-annexes/annex-c-requirements/03-functional-requirements/03-03-deployment-orchestration/fr-dep-002.1784304585.txt.gz
  • Last modified: 2026/07/17 09:09
  • by nick_dido