FR-MC-001 — Cloud Provider Abstraction

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL provide Cloud Provider Abstraction.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-MC-001The Original Requirement states:

The system shall support cloud provider abstraction.[C1]

FR-MC-001:

Replaces The system with the defined system name CrucibleChanges shall to the established uppercase normative form SHALLReplaces the weak verb support with provideCapitalizes Cloud Provider Abstraction as the named architectural capabilityNo other substantive normalization is required.

Rationale

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.

Applies To

This requirement applies to:

Cloud Provider AbstractionCloud ProvidersCloud deployment informationCloud-provider-specific parametersProvider Implementations

Verification

Verification confirms that:

A tested deployment contains information that expresses deployment intentCrucible separates the tested deployment intent from parameters required by a particular Cloud ProviderA provider-specific parameter can change without requiring modification of unrelated provider-independent deployment informationThe observed behavior demonstrates Cloud Provider Abstraction

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

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}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.