FR-MC-001 — Cloud Provider Abstraction

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL separate Cloud Provider independent deployment information from cloud-provider-specific parameters.

Source Statement

The system shall support Cloud Provider abstraction.

Source

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

Assessment

The source statement expresses the approved architectural intent but does not provide a fully testable behavior.

The following Specification Discipline and Authoring findings apply:

The system does not use the defined system nameshall does not follow the established uppercase normative conventionSupport is a weak verbCloud provider abstraction names an architectural approach without identifying the required separationThe source statement does not identify which information remains provider independentThe source statement does not identify which information may vary by providerThe source statement does not prescribe a provider, cloud service model, programming language, interface, or implementation technologyThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior separateIdentifies cloud-provider-independent deployment informationIdentifies cloud-provider-specific parametersPreserves implementation independenceRetains one primary required behaviorThe normalized Statement does not require every deployment capability to remain identical across providers. Provider-specific extensions may address capabilities that do not have a common provider-independent representation.

Rationale

Cloud providers expose different:

Resource typesService namesConfiguration parametersIdentity modelsNetwork modelsStorage modelsRegions and location identifiersManagement interfacesOperational constraintsCloud Provider Abstraction separates common deployment intent from the details required by a particular provider.

Cloud-provider-independent deployment information may identify:

Required computing capacityRequired storage capabilityRequired network relationshipsRequired security characteristicsRequired identity relationshipsRequired Platform ServicesRequired Acceptance CriteriaCloud-provider-specific parameters may identify:

Provider resource typesProvider service identifiersProvider regionsProvider account or project identifiersProvider network identifiersProvider storage classesProvider machine typesProvider-specific security configurationThis separation contributes to:

Provider substitutionReusable deployment intentReduced provider couplingReproducibilityTraceability

Applies To

This requirement applies to:

Cloud-provider-independent deployment informationCloud-provider-specific parametersCrucible DescriptionsInfrastructure ConfigurationsInfrastructure BaselinesProvider ImplementationsCloud deployment workflowsCloud providers

Verification

Verification SHALL confirm that a tested deployment identifies cloud-provider-independent deployment informationVerification SHALL confirm that the tested deployment identifies cloud-provider-specific parameters separately from the cloud-provider-independent deployment informationVerification SHALL confirm that changing a cloud-provider-specific parameter does not require modification of unrelated cloud-provider-independent deployment informationVerification SHALL confirm that cloud-provider-independent components do not contain unidentified provider-specific deployment behaviorVerification may include:

Deployment-description inspectionConfiguration-boundary inspectionProvider-parameter inspectionProvider-substitution testingStatic dependency analysisProvider implementation testingCross-provider deployment testingThe verification record SHALL identify:

The tested deployment informationThe cloud-provider-independent informationThe cloud-provider-specific parametersThe tested cloud providersThe observed separationThe generated Evidence

Outgoing Traceability

This requirement realizes:

This requirement relates to:

Referenced By

The wiki Backlinks function provides the current list of pages that reference FR-MC-001.

Incoming Traceability should be derived dynamically from backlinks rather than maintained as a duplicate manual list.

ConOps Relationship

The Crucible Concept of Operations describes common deployment intent combined with platform-specific information before deployment.

FR-MC-001 establishes the separation between cloud-provider-independent deployment information and cloud-provider-specific parameters.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Requirement Status

Draft

Notes for Editors

This requirement page should retain the stable requirement identifier FR-MC-001.

Changes to the Statement SHALL preserve the approved intent of the source requirement.

The Statement should remain limited to separation of cloud-provider-independent deployment information from cloud-provider-specific parameters.

Requirements for provider extensions, cross-provider deployment, Hybrid-Cloud Deployment, and Edge Deployment should remain in their applicable requirement pages.

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

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

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