| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003a [2026/07/21 09:57] – ↷ Links adapted because of a move operation nick_dido | dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003a [2026/07/30 05:22] (current) – [Delivery Phase] nick_dido |
|---|
| The Original Requirement states: | The Original Requirement states: |
| |
| > //The system SHALL provide cloud-agnostic deployment capabilities.//[[dido:02-crusible:99-annexes:annex-b:cr-003|[C3]]] | > //The system SHALL provide cloud-agnostic deployment capabilities.//[[dido:02-crusible:99-annexes:annex-b:cr-002|[C2]]] |
| |
| MO-003a preserves the portion of the Original Requirement that requires [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to perform deployment across multiple Deployment Platforms. | MO-003a preserves the portion of the Original Requirement that requires [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] to deploy Infrastructure Environments across multiple Deployment Platforms. |
| |
| The separate requirements derived from MO-003 address: | The separate requirements derived from MO-003 address: |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b|MO-003b — Common Crucible Description]] | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b|MO-003b — Provider-Independent Crucible Description]] |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003c|MO-003c — Common Infrastructure Baseline]] | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003c|MO-003c — Provider-Independent Infrastructure Baseline]] |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003d|MO-003d — Provider-Specific Dependency Limitation]] | * [[dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003d|MO-003d — Limitation of Provider-Specific Dependencies]] |
| | |
| ===== Assessment ===== | |
| | |
| The Original Requirement uses **provide** without identifying the behavior [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs. | |
| | |
| The phrase **deployment capabilities** does not identify: | |
| | |
| * The subject deployed | |
| * The target Deployment Platforms | |
| * The minimum number of target Deployment Platforms | |
| * The required deployment outcome | |
| * The criteria used to determine whether a Deployment Platform is supported | |
| | |
| MO-003a: | |
| | |
| * Replaces **provide** with the direct action **deploy** | |
| * Identifies Crucible as the responsible actor | |
| * Identifies an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the required deployment outcome | |
| * Requires deployment to at least two supported Deployment Platforms | |
| * Separates cross-platform deployment from common-input and provider-dependency requirements | |
| |
| ===== Rationale ===== | ===== Rationale ===== |
| |
| [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] requires more than deployment to a single platform. | [[dido:99_annexes:annex-b-terms-and-definitions:c:cloud_agnosticism|Cloud Agnosticism]] requires Crucible to operate across more than one Deployment Platform. |
| | |
| Deployment to two or more supported Deployment Platforms provides the minimum observable basis for evaluating whether Crucible performs cross-platform deployment. | |
| | |
| A supported Deployment Platform has an available and approved mechanism through which Crucible performs the required deployment behavior. The applicable lower-level requirements define the provider contracts, provider implementations, platform-specific parameters, acceptance criteria, and deployment controls associated with each supported Deployment Platform. | |
| |
| Cross-platform deployment can include Deployment Platforms associated with: | Deployment to two or more supported Deployment Platforms provides the minimum observable basis for evaluating cross-platform deployment. |
| |
| * Commercial cloud providers | A supported Deployment Platform requires an identified and approved mechanism through which Crucible performs the deployment. |
| * Private cloud environments | |
| * On-premises infrastructure | |
| * Virtualized infrastructure | |
| * Container platforms | |
| * Edge environments | |
| * Connected Environments | |
| * Disconnected Environments | |
| * Air-Gapped Environments | |
| |
| Deployment to multiple platforms does not alone establish full Cloud Agnosticism. The other requirements derived from MO-003 address common deployment inputs and limitation of provider-specific dependencies. | Cross-platform deployment does not alone establish complete Cloud Agnosticism. The other requirements derived from MO-003 address provider-independent deployment information and limitation of provider-specific dependencies. |
| |
| ===== Applies To ===== | ===== Applies To ===== |
| * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployments]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] |
| | * Supported Deployment Platforms |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contracts]] | * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contracts]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] | * [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementations]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environments]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] | * [[dido:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:c:ci_cd_pipeline|CI/CD Pipelines]] | |
| * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] | * [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] | * [[dido:99_annexes:annex-b-terms-and-definitions:p:provenance|Provenance]] |
| Verification confirms that: | Verification confirms that: |
| |
| - Two or more supported Deployment Platforms are identified | - Two or more supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] are identified |
| - Crucible performs an Infrastructure Deployment to each identified Deployment Platform | - The support criteria for each Deployment Platform are identified |
| - Each Infrastructure Deployment creates an Infrastructure Environment | - [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] performs an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]] to each identified Deployment Platform |
| - Each resulting Infrastructure Environment satisfies the applicable deployment acceptance criteria | - Each Infrastructure Deployment creates an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] |
| - Each deployment result identifies the target Deployment Platform | - Each deployment result identifies the target Deployment Platform |
| - Each deployment result identifies the applicable Provider Implementation | - Each deployment result identifies the [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]] used for the Deployment Platform |
| - Each deployment preserves the required Evidence, Provenance, and Traceability | - Each resulting Infrastructure Environment satisfies the deployment acceptance criteria established for the target Deployment Platform |
| | - The verification record preserves [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|Traceability]] among the Controlled Inputs, target Deployment Platform, Provider Implementation, Infrastructure Deployment, and resulting Infrastructure Environment |
| |
| Verification includes: | ===== Referenced By ===== |
| |
| * Supported Deployment Platform inspection | The following pages reference this requirement: |
| * Provider Contract inspection | |
| * Provider Implementation inspection | |
| * Cross-platform deployment tests | |
| * Infrastructure Deployment tests | |
| * Resulting Infrastructure Environment inspection | |
| * Deployment acceptance-criteria evaluation | |
| * Deployment-record inspection | |
| * Evidence inspection | |
| * Provenance inspection | |
| * Traceability inspection | |
| |
| The verification record identifies: | {{backlinks>.#dido:02-crusible}} |
| |
| - Each tested Deployment Platform | ===== Delivery Phase ===== |
| - The support status of each tested Deployment Platform | |
| - The Provider Contract applicable to each tested Deployment Platform | |
| - The Provider Implementation used for each tested Deployment Platform | |
| - The Controlled Inputs used for each deployment | |
| - The deployment result for each tested Deployment Platform | |
| - The resulting Infrastructure Environment for each deployment | |
| - The applicable acceptance criteria | |
| - The observed result | |
| - The generated Evidence | |
| |
| ===== Requirements Realized By ===== | Implemented and Verified |
| |
| This requirement is realized by: | ===== Implementation Status ===== |
| |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-001:start|OR-001 — Operational Roles]] | <todo>Assess whether the current Crucible implementation deploys an Infrastructure Environment to two or more supported Deployment Platforms.</todo> |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-002|OR-002 — Deployment Environments]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-003|OR-003 — Classified and Unclassified Environments]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:02-operational-requirements:or-005|OR-005 — Distributed Environment Management]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-03-deployment-orchestration:start|FR-DEP-001 through FR-DEP-007]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:start|FR-MC-001 through FR-MC-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-05-air-gap-operations:start|FR-AG-001 through FR-AG-005]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-08-devsecops-integration:start|FR-DSO-001 through FR-DSO-006]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:11-interoperability-requirements:start|INT-001 through INT-007]] | |
| * [[dido:02-crusible:99-annexes:annex-c-requirements:13-key-value-proposition-requirements:kvp-006|KVP-006 — Enable Cloud Portability]] | |
| |
| ===== Related Architecture Sections ===== | ===== Requirement Status ===== |
| |
| * [[dido:02-crusible:05-descriptions-composition-and-baselines:start|5. Descriptions, Composition, and Baselines]] | <todo>Review and accept MO-003a as a proposed derived requirement created from the evaluation and decomposition of MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft.</todo> |
| * [[dido:02-crusible:07-infrastructure-and-deployment:start|7. Infrastructure and Deployment]] | |
| * [[dido:02-crusible:08-dependencies-and-air-gap-operations:start|8. Dependencies and Air Gap Operations]] | |
| * [[dido:02-crusible:10-reproducibility-provenance-and-traceability:start|10. Reproducibility, Provenance, and Traceability]] | |
| |
| ===== Referenced By ===== | ---- |
| | ===== Issues ===== |
| |
| The following pages reference this requirement: | The following unresolved issues affect this requirement: |
| |
| {{backlinks>.#dido:02-crusible}} | <todo>Identify the Deployment Platforms that Crucible supports.</todo> |
| |
| ===== Delivery Phase ===== | <todo>Define the criteria used to determine that a Deployment Platform is supported.</todo> |
| |
| Phase 1 and subsequent phases | <todo>Confirm that deployment to two supported Deployment Platforms provides sufficient minimum evidence of cross-platform deployment.</todo> |
| | |
| ===== Implementation Status ===== | |
| | |
| Not Assessed | |
| | |
| Implementation status requires successful Infrastructure Deployment to at least two supported Deployment Platforms. | |
| | |
| ===== Requirement Status ===== | |
| |
| Draft | <todo>Identify the deployment acceptance criteria for each supported Deployment Platform.</todo> |
| |
| This requirement derives from MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft. | <todo>Identify the controlling source that approves the Provider Contract and Provider Implementation used for each supported Deployment Platform.</todo> |
| |
| ---- | ---- |
| This page is a leaf requirement page and omits a trailing '':start'' from its namespace. | This page is a leaf requirement page and omits a trailing '':start'' from its namespace. |
| |
| Changes to the Statement SHALL preserve the cross-platform deployment intent derived from MO-003. | The parent MO-003 page is a non-leaf page and retains a trailing '':start'' in its namespace. |
| | |
| | Changes to the Statement should preserve: |
| | |
| | * [[dido:99_annexes:annex-b-terms-and-definitions:c:crucible|Crucible]] as the responsible actor |
| | * Deployment of an [[dido:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]] as the required outcome |
| | * Deployment to two or more supported [[dido:99_annexes:annex-b-terms-and-definitions:d:deployment_platform|Deployment Platforms]] as the cross-platform obligation |
| |
| The criteria for a supported Deployment Platform should identify: | The criteria for a supported Deployment Platform should identify: |
| |
| * The Deployment Platform | * The Deployment Platform |
| * The applicable Provider Contract | * The approved [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_contract|Provider Contract]] |
| * The approved Provider Implementation | * The approved [[dido:99_annexes:annex-b-terms-and-definitions:p:provider_implementation|Provider Implementation]] |
| * The supported Platform Specific Parameters | * The supported [[dido:99_annexes:annex-b-terms-and-definitions:p:platform_specific_parameter|Platform Specific Parameters]] |
| * The applicable deployment acceptance criteria | * The deployment acceptance criteria |
| * The required deployment Evidence | * The required [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] |
| |
| Material changes should receive review and should update the related verification criteria, requirements realization, related architecture sections, and source records. | Material changes should receive review and should update the verification criteria, source records, and Issues section. |
| |
| To reference this requirement Statement from another wiki page, insert: | To reference this requirement Statement from another wiki page, insert: |