MO-003b — Provider-Independent Crucible Description

Go to MO-003 — Cloud-Agnostic Deployment

Crucible SHALL use the same identified version of the provider-independent Crucible Description for each selected Deployment Platform.

This requirement derives from:

• MO-003 — Cloud-Agnostic Deployment

The Original Requirement states:

The system SHALL provide cloud-agnostic deployment capabilities.[C2]

MO-003b preserves the portion of the Original Requirement that requires common provider-independent deployment intent across the selected Deployment Platforms.

The separate requirements derived from MO-003 address:

• MO-003a — Cross-Platform Deployment
• MO-003c — Provider-Independent Infrastructure Baseline
• MO-003d — Limitation of Provider-Specific Dependencies

A provider-independent Crucible Description allows the same deployment intent to apply across multiple Deployment Platforms.

Using the same identified version prevents a change of Deployment Platform from implicitly changing the provider-independent deployment intent.

The Crucible Description should express the required deployment without embedding the proprietary interfaces, services, data formats, software development kits, or operational mechanisms of a particular Cloud Provider.

Platform-specific information remains separate from the provider-independent Crucible Description. A Provider Implementation translates the provider-independent deployment intent into mechanisms supported by the selected Deployment Platform.

Using the same identified version supports:

• Consistent deployment intent
• Controlled comparison of deployment results
• Change control
• Detection of provider-specific information within provider-independent content
• Reuse across supported Deployment Platforms
• Provenance
• Traceability

This requirement does not require use of the same Infrastructure Baseline. MO-003c addresses that outcome.

This requirement applies to:

• Crucible
• Cloud Agnosticism
• Crucible Descriptions
• Crucible Description identifiers
• Crucible Description versions
• Platform Independent Information
• Platform Specific Information
• Platform Specific Parameters
• Deployment Platforms
• Provider Contracts
• Provider Implementations
• Infrastructure Deployments
• Artifacts
• Evidence
• Provenance
• Traceability

Verification confirms that:

1. Two or more selected Deployment Platforms are identified
2. The provider-independent Crucible Description is identified
3. Each deployment uses a Crucible Description with the same identifier
4. Each deployment uses the same identified version of the Crucible Description
5. The Crucible Description contains provider-independent deployment intent
6. Changing the selected Deployment Platform does not require modification of the identified Crucible Description version
7. Platform Specific Information remains separate from the provider-independent Crucible Description
8. Each deployment record identifies the Crucible Description identifier and version used for the selected Deployment Platform
9. The verification record preserves Traceability among the Crucible Description, selected Deployment Platform, Provider Implementation, platform-specific information, and deployment result

The following pages reference this requirement:

Implemented and Verified

Assess whether deployments to the selected Deployment Platforms use the same identified version of the provider-independent Crucible Description.

Review and accept MO-003b as a proposed derived requirement created from the evaluation and decomposition of MO-003 in the Crucible System Requirements Specification, Version 1.1 Draft.

The following unresolved issues affect this requirement:

Define the provider-independent information that the Crucible Description must contain.

Define the provider-specific information that must remain separate from the Crucible Description.

Identify the controlling source that defines the boundary between provider-independent and provider-specific information.

Determine whether changing the selected Deployment Platform may require any controlled transformation of the Crucible Description without creating a new Crucible Description version.

Define the identifier and versioning rules used to determine that each deployment uses the same Crucible Description.

This requirement page should retain the stable requirement identifier MO-003b.

This page is a leaf requirement page and omits a trailing :start from its namespace.

The parent MO-003 page is a non-leaf page and retains a trailing :start in its namespace.

Changes to the Statement should preserve:

• Crucible as the responsible actor
• The provider-independent Crucible Description as the common source of deployment intent
• Use of the same identified Crucible Description version across the selected Deployment Platforms
• Separation of provider-independent and provider-specific information

The unresolved boundary between provider-independent and provider-specific information should remain recorded in the Issues section until a controlling source defines it.

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:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:01-mission-objectives:mo-003:mo-003b#Statement&noheader&nofooter&noeditbtn}}

Do not rename this page after an external citation unless a redirect or move plan is in place.