FR-MC-003 — Deployment Portability Across Cloud Providers

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL deploy the same provider-independent deployment intent to at least two cloud providers by changing only the applicable provider-specific parameters and provider implementation.

Source Statement

The system shall support deployment portability across cloud providers.

Source

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

Assessment

The source statement identifies a portability objective but does not state an observable portability test.

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 verbDeployment portability does not identify what remains unchangedAcross cloud providers does not specify the minimum number of providers needed to demonstrate portabilityThe source statement does not require identical provider services or identical implementation detailsThe source statement does not prescribe particular cloud providersThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior deployIdentifies the provider-independent deployment intent that remains unchangedRequires deployment to at least two cloud providersLimits expected changes to provider-specific parameters and the provider implementationPreserves provider-specific realizationThe phrase at least two establishes the minimum observable condition needed to verify “across cloud providers.”

Rationale

Cloud Portability requires more than storing provider-neutral descriptions. Crucible must use common deployment intent to produce acceptable deployments through more than one cloud provider.

Portability does not require:

Identical provider resource identifiersIdentical service namesIdentical provider APIsIdentical physical infrastructureIdentical costsIdentical performanceAvailability of every provider-specific service on every providerPortability requires preservation of the applicable deployment intent and acceptance criteria while provider-specific realization details vary.

Applies To

This requirement applies to:

Provider-independent deployment intentProvider-specific parametersProvider ImplementationsCloud providersInfrastructure BaselinesAcceptance CriteriaDeployment workflows

Verification

Verification SHALL confirm that one provider-independent deployment intent is selected for testingVerification SHALL confirm that Crucible deploys the selected intent to at least two cloud providersVerification SHALL confirm that each provider deployment uses the applicable provider implementationVerification SHALL confirm that differences in deployment input are limited to identified provider-specific parametersVerification SHALL confirm that the provider-independent deployment intent remains unchangedVerification SHALL confirm that each resulting deployment satisfies the common Acceptance CriteriaVerification may include:

Cross-provider deployment testsProvider implementation testsDeployment-input comparisonInfrastructure Baseline comparisonProvider-parameter comparisonDeployment-result comparisonAcceptance testingThe verification record SHALL identify:

The provider-independent deployment intentThe tested cloud providersThe provider implementationsThe provider-specific parametersThe common Acceptance CriteriaThe provider-specific Acceptance CriteriaThe observed deployment resultsThe 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-003.

Incoming Traceability should be derived dynamically from backlinks.

ConOps Relationship

The Crucible Concept of Operations describes provider-independent deployment information combined with provider-specific parameters and provider implementations.

FR-MC-003 establishes the observable cross-provider deployment behavior required for Cloud Portability.

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-003.

The Statement should remain limited to deployment of the same provider-independent intent through at least two cloud providers.

Portability should not be interpreted as requiring identical provider-specific realizations.

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-003#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.