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

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
dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004 [2026/07/20 08:25] – ↷ Links adapted because of a move operation nick_didodido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004 [2026/07/30 05:47] (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:c:containerized_workload|Containerized Workload]] to a target [[dido:99_annexes:annex-b-terms-and-definitions:c:container_platform|Container Platform]].+[[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]].
  
-===== Source Statement =====+===== Derived From =====
  
-> The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]].+This requirement derives from:
  
-===== Source =====+  * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-004
  
-Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-004.+The Original Requirement states:
  
-===== Assessment =====+> //The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]].//[[dido:02-crusible:99-annexes:annex-b:cr-001|[C1]]]
  
-The source statement expresses a direct functional behavior but requires normative-language normalization and identification of the deployment target.+FR-DEP-004:
  
-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 **Containerized Workloads** 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 +
-  * **Containerized workloads** identify the deployment subject but do not identify the target platform +
-  * The source statement does not prescribe a container runtime, orchestration platform, [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Image]] format, provider, or deployment method +
-  * The source statement does not independently require workload validation, availability, scaling, rollback, or compliance assessment +
- +
-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** +
-  * Identifies a containerized workload as the deployment subject +
-  * Identifies a target container platform +
-  * Preserves implementation independence +
-  * Retains one primary required behavior +
- +
-**Containerized Workload** and **Container Platform** should receive glossary definitions because they identify distinct architectural subjects used by this and related requirements.+
  
 ===== Rationale ===== ===== Rationale =====
  
-A containerized workload comprises one or more container instances and the configuration required to perform an application, service, processing, or platform function.+A [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workload]] uses one or more containers to perform an application, service, processing, or platform function.
  
-Containerized-workload deployment may use:+Deploying Containerized Workloads enables Crucible to establish container-based workloads through separately governed deployment workflows.
  
-  * One or more [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] +This requirement establishes Containerized Workload deployment without prescribing:
-  * Workload configuration +
-  * Runtime parameters +
-  * Identity and access configuration +
-  * Network configuration +
-  * Storage configuration +
-  * Resource requirements +
-  * Security controls +
-  * Service-discovery configuration +
-  * Scaling configuration+
  
-The applicable deployment specification determines which inputs apply.+  * The [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] 
 +  * The target Container Platform 
 +  * The container runtime 
 +  * The orchestration platform 
 +  * The workload configuration 
 +  * Workload availability 
 +  * Workload scaling 
 +  * Deployment validation 
 +  * Deployment rollback 
 +  * Compliance assessment
  
-Containerized-workload deployment contributes to: +Separate requirements define those subjects and behaviors.
- +
-  * Repeatable workload creation +
-  * Consistent runtime configuration +
-  * Automated application and service deployment +
-  * Workload portability +
-  * [[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 72: Line 51:
  
   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]   * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]]
-  * Containerized workloads +  * [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workloads]] 
-  * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_image|Container Images]] +  * Containerized Workload deployment operations
-  * Container instances +
-  * Container platforms +
-  * Container runtimes +
-  * Kubernetes Clusters +
-  * Workload configuration +
-  * Workload deployment workflows +
-  * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]] +
-  * [[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 containerized workload +Verification confirms that:
-  - Verification SHALL confirm that the deployment operation targets an identified container platform +
-  - Verification SHALL confirm that the containerized workload exists on the target container platform after successful deployment+
  
-Verification may include: +  - One or more Containerized Workloads are selected for deployment 
- +  - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for the selected Containerized Workloads 
-  * Containerized-workload deployment testing +  - The completed deployment produces the selected Containerized Workloads 
-  * Container-platform inspection +  - The resulting Containerized Workloads can be identified as outputs of the tested deployment
-  * Container-runtime inspection +
-  * Workload-state inspection +
-  * Deployment-output inspection +
-  * Deployment-log inspection +
-  * Automated CI/CD Pipeline testing +
- +
-The verification record SHALL identify: +
- +
-  - The deployed containerized workload +
-  - The target container platform +
-  - The deployment operation +
-  - The deployment result +
-  - The observed workload 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:start|MO-001]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-002:start|MO-002]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:start|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-002|FR-IMG-002 — Build Container 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-02-image-management:fr-img-006|FR-IMG-006 — Image Promotion Workflows]] +
-  * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-003|FR-DEP-003 — Deploy Kubernetes Clusters]] +
-  * [[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: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-004''. +The following pages reference this requirement:
- +
-Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list. +
- +
-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 Container Images and deploys platform and application components through an automated CI/CD Pipeline. +
- +
-FR-DEP-004 establishes the required behavior for deploying a containerized workload to a target container platform. +
- +
-Requirements governing Container Image building, Kubernetes Cluster deployment, platform services, rollback, and validation define separate behavior. +
- +
-===== Delivery Phase =====+
  
-Phase 1+{{backlinks>.#dido:02-crusible}}
  
 ===== Implementation Status ===== ===== Implementation Status =====
  
-Not Assessed +Implemented and Verified
- +
-Implementation status requires verification that Crucible deploys a containerized workload to a target container platform.+
  
 ===== Requirement Status ===== ===== Requirement Status =====
  
-Draft +<todo>Review and approve FR-DEP-004 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-004''.+<todo>Determine whether separate requirements identify the Container Images and configuration used for each Containerized Workload deployment.</todo>
  
-Changes to the Statement SHALL preserve the approved intent of the source requirement.+<todo>Determine whether separate requirements identify the Container Platform, Deployment Target, or Infrastructure Environment for each Containerized Workload 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 containerized workload.+This requirement page retains the stable requirement identifier ''FR-DEP-004''.
  
-Requirements for Container Image building, Image Promotion, scaling, availability, rollback, validation, and workload 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 Containerized Workloads.
  
-Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.+Do not add Container Images, a target Container Platform, a container runtime, an orchestration platform, workload configuration, availability, scaling, rollback, validation, compliance-assessment, or retirement obligations 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 182: Line 100:
 {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004#Statement&noheader&nofooter&noeditbtn}} {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-004#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-004.1784561106.txt.gz
  • Last modified: 2026/07/20 08:25
  • by nick_dido