| 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-005 [2026/07/20 08:25] – ↷ Links adapted because of a move operation nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005 [2026/07/30 05:48] (current) – nick_dido |
|---|
| ===== Statement ===== | ===== Statement ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] SHALL deploy an identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] 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:p:platform_service|Platform Services]]. |
| |
| ===== Source Statement ===== | ===== Derived From ===== |
| |
| > The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]. | This requirement derives from: |
| |
| ===== Source ===== | * Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-005 |
| |
| Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-005. | The Original Requirement states: |
| |
| ===== Assessment ===== | > //The system shall deploy [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]].//[[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-005: |
| |
| 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 **Platform Services** 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 | |
| * **[[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]]** identifies a class of deployment subjects, but does not identify the target Infrastructure Environment | |
| * The source statement does not define which [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] apply to a particular deployment | |
| * The source statement does not prescribe a platform, provider, deployment tool, service implementation, or deployment method | |
| * The source statement does not independently require activation, validation, rollback, compliance assessment, monitoring, or lifecycle recording | |
| | |
| 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 [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] as the deployment subject | |
| * Identifies the target Infrastructure Environment | |
| * Preserves implementation independence | |
| * Retains one primary required behavior | |
| | |
| The applicable [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]] or deployment specification identifies the [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] and its required configuration. | |
| | |
| **[[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]]** should receive a glossary definition because it identifies a distinct deployment subject used by this requirement. | |
| |
| ===== Rationale ===== | ===== Rationale ===== |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] supplies a shared capability used by applications, [[dido:99_annexes:annex-b-terms-and-definitions:w:workload|Workloads]], operators, or other platform components. | A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Service]] provides a shared capability used by applications, workloads, operators, or other platform components. |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] may include: | Deploying Platform Services enables Crucible to establish shared platform capabilities through separately governed deployment workflows. |
| |
| * Identity services | This requirement establishes Platform Service deployment without prescribing: |
| * Authorization services | |
| * Name-resolution services | |
| * Secret-management services | |
| * Key-management services | |
| * Logging services | |
| * Monitoring services | |
| * Messaging services | |
| * Data services | |
| * Repository services | |
| * Policy-enforcement services | |
| * Service-discovery services | |
| * Configuration-distribution services | |
| |
| A [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] may operate: | * The Platform Services included in a particular deployment |
| | * The target Infrastructure Environment |
| | * The Deployment Target |
| | * The deployment platform |
| | * The service implementation |
| | * Service activation |
| | * Service availability |
| | * Service scaling |
| | * Monitoring |
| | * Deployment validation |
| | * Deployment rollback |
| | * Compliance assessment |
| |
| * As a [[dido:99_annexes:annex-b-terms-and-definitions:c:containerized_workload|Containerized Workload]] | Separate requirements define those subjects and behaviors. |
| * On a [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]] | |
| * Through a provider-managed service | |
| * As a component of a [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Cluster]] | |
| * Through another platform-specific realization | |
| | |
| [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] deployment contributes to: | |
| | |
| * Consistent shared platform capabilities | |
| * Repeatable platform establishment | |
| * Automated service deployment | |
| * Controlled service configuration | |
| * [[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 ===== |
| * [[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:p:platform_service|Platform Services]] | * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service|Platform Services]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]]configurations | * Platform Service deployment operations |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]]deployment workflows | |
| * [[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]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:container_platform|Container Platforms]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:k:kubernetes_cluster|Kubernetes Clusters]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machines]] | |
| * [[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 an identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] | 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 identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] exists in the target Infrastructure Environment after successful deployment | |
| |
| Verification may include: | - One or more Platform Services are selected for deployment |
| | - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] executes a deployment operation for the selected Platform Services |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] deployment testing | - The completed deployment produces the selected Platform Services |
| * Target-environment inspection | - The resulting Platform Services can be identified as outputs of the tested deployment |
| * Service-state inspection | |
| * Platform-interface inspection | |
| * Provider-interface inspection | |
| * Deployment-output inspection | |
| * Deployment-log inspection | |
| * Automated [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]] testing | |
| | |
| The verification record SHALL identify: | |
| | |
| - The deployed [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] | |
| - The target Infrastructure Environment | |
| - The deployment operation | |
| - The deployment result | |
| - The observed [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] 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-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-002|FR-DEP-002 — Deploy Virtual Machines]] | |
| * [[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-004|FR-DEP-004 — Deploy Containerized Workloads]] | |
| * [[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-005''. | The following pages reference this requirement: |
| |
| Incoming [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|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 automated infrastructure and platform deployment through a Phase 1 [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipeline]]. | |
| | |
| FR-DEP-005 establishes the required behavior for deploying an identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] to a target Infrastructure Environment. | |
| | |
| Requirements governing infrastructure resources, Virtual Machines, Kubernetes Clusters, Containerized Workloads, rollback, and validation define separate behavior. | |
| | |
| ===== Delivery Phase ===== | |
| | |
| Phase 1 | |
| |
| ===== Implementation Status ===== | ===== Implementation Status ===== |
| |
| Not Assessed | Implemented and Verified |
| | |
| Implementation status requires verification that [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] deploys an identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]] to a target Infrastructure Environment. | |
| |
| ===== Requirement Status ===== | ===== Requirement Status ===== |
| |
| Draft | <todo>Review and approve FR-DEP-005 as a leaf requirement.</todo> |
| | |
| The source System Requirements Specification identifies Version 1.1 as a draft. | |
| |
| ---- | ---- |
| ===== Notes for Editors ===== | ===== Issues ===== |
| |
| This requirements page should retain the stable requirement identifier 'FR-DEP-005'. | <todo>Determine whether separate requirements identify the configuration used for each Platform Service 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 Platform Service 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 the deployment of an identified [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_service]]. | This requirement page retains the stable requirement identifier ''FR-DEP-005''. |
| |
| Requirements for service activation, availability, scaling, monitoring, rollback, validation, compliance assessment, 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 Platform Services. |
| |
| Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list. | Do not add a target Infrastructure Environment, Deployment Target, deployment platform, service implementation, activation, availability, scaling, monitoring, 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: |
| {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005#Statement&noheader&nofooter&noeditbtn}} | {{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:fr-dep-005#Statement&noheader&nofooter&noeditbtn}} |
| </code> | </code> |
| |
| Do not rename this page after an external citation unless a redirect or move plan is in place. | |
| |
| ---- | ---- |