FR-MC-001 — Cloud Provider Abstraction

Go to Crucible Multi-Cloud Management Requirements

Crucible SHALL provide Cloud Provider Abstraction.

This requirement derives from:

• Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-001

The Original Requirement states:

The system shall support cloud provider abstraction.[C1]

FR-MC-001:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Replaces the weak verb support with provide
• Capitalizes Cloud Provider Abstraction as the named architectural capability

No other substantive normalization is required.

Cloud providers expose different resource types, service identifiers, configuration parameters, identity models, network models, storage models, regions, interfaces, and operational constraints.

Cloud Provider Abstraction allows deployment information that expresses common intent to remain separate from parameters required by a particular Cloud Provider.

This separation reduces provider coupling and supports reuse of deployment information across Provider Implementations.

This requirement does not require every deployment capability to have an identical representation across Cloud Providers. Provider-specific extensions can represent capabilities that do not have a common provider-independent representation.

This requirement applies to:

• Crucible
• Cloud Provider Abstraction
• Cloud Providers
• Cloud deployment information
• Cloud-provider-specific parameters
• Provider Implementations

Verification confirms that:

1. A tested deployment contains information that expresses deployment intent
2. Crucible separates the tested deployment intent from parameters required by a particular Cloud Provider
3. A provider-specific parameter can change without requiring modification of unrelated provider-independent deployment information
4. The observed behavior demonstrates Cloud Provider Abstraction

The following pages reference this requirement:

Implemented and Verified

Review and approve FR-MC-001 as a leaf requirement.

Determine whether Cloud Provider Abstraction requires a controlled definition in the shared Terms and Definitions corpus.

Determine whether separate requirements define the boundary between provider-independent deployment information and provider-specific parameters.

This requirement page retains the stable requirement identifier FR-MC-001.

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

The Statement preserves the approved source intent by requiring Crucible to provide Cloud Provider Abstraction.

Do not add provider substitution, cross-provider deployment, identical provider capabilities, Hybrid-Cloud Deployment, Edge Deployment, or provider-specific extension obligations unless the controlling requirement changes through an approved requirements process.

To reference this requirement Statement from another wiki page, insert:

{{section>dido:02-crusible:99-annexes:annex-c-requirements:03-functional-requirements:03-04-multi-cloud-management:fr-mc-001#Statement&noheader&nofooter&noeditbtn}}