FR-MC-003 — Deployment Portability Across Cloud Providers

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL deploy the same Platform Independent Information to at least two cloud Providers by varying only the applicable Platform Specific Information.

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 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 verb that does not identify the required behaviorDeployment portability does not identify which deployment information remains unchangedAcross cloud providers does not identify the minimum number of Providers needed to demonstrate portabilityThe source statement does not distinguish Platform Independent Information from Platform Specific InformationThe source statement does not require identical Provider services, resource types, interfaces, or physical implementationsThe source statement does not prescribe particular cloud ProvidersThe normalized Statement:

Replaces The system with CrucibleReplaces support with the direct behavior deployUses the defined Platform Independent Information conceptUses the defined Platform Specific Information conceptIdentifies the information that remains unchangedRequires deployment through at least two cloud ProvidersLimits deployment-input variation to the applicable Platform Specific InformationPreserves Provider-specific realizationRetains one primary required behaviorThe phrase at least two establishes the minimum observable condition required to demonstrate deployment across more than one cloud Provider.

The normalized Statement does not require identical Provider resources, service names, interfaces, prices, performance characteristics, or physical implementations.

Rationale

Cloud Portability requires Crucible to preserve applicable deployment intent while realizing that intent through different cloud Providers.

Platform Independent Information expresses deployment information without depending on the implementation details of a particular Provider.

Platform Specific Information supplies the Provider-specific values, mappings, identifiers, constraints, and other details required to realize that information through a particular Provider.

Platform Specific Information may include:

Provider resource typesProvider service identifiersProvider regionsProvider account or project identifiersProvider network identifiersProvider storage classesProvider machine typesProvider authentication parametersProvider-specific security parametersProvider-specific service configurationCloud Portability does not require:

Identical Provider resource identifiersIdentical Provider service namesIdentical Provider interfacesIdentical physical infrastructureIdentical costsIdentical performanceIdentical operational constraintsAvailability of every Provider-specific capability through every ProviderCloud Portability requires preservation of the applicable Platform Independent Information while Platform Specific Information varies for each Provider.

The applicable Acceptance Criteria determine whether each Provider-specific deployment constitutes an acceptable realization of the same Platform Independent Information.

Applies To

This requirement applies to:

Cloud deployment workflows

Verification

Verification SHALL confirm that one set of Platform Independent Information is selected for testingVerification SHALL confirm that at least two cloud Providers are selected for testingVerification SHALL confirm that the same Platform Independent Information is used for each tested ProviderVerification SHALL confirm that differences in deployment input are limited to identified Platform Specific InformationVerification SHALL confirm that Crucible deploys the selected Platform Independent Information through each tested ProviderVerification SHALL confirm that each resulting deployment satisfies the applicable common Acceptance CriteriaVerification may include:

Cross-Provider deployment testsPlatform Independent Information comparisonPlatform Specific Information comparisonProvider Plugin testsProvider Contract conformance testsInfrastructure Baseline comparisonDeployment-result comparisonAcceptance testingThe verification record SHALL identify:

The tested Platform Independent InformationThe tested cloud ProvidersThe applicable Platform Specific Information for each ProviderThe applicable Provider Plugin for each ProviderThe applicable Provider ContractThe common Acceptance CriteriaAny 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 rather than maintained as a duplicate manual list.

Backlinks identify incoming references but do not define the semantics of each relationship. Referencing pages should identify whether the relationship represents realization, refinement, verification, dependency, or another defined traceability relationship.

ConOps Relationship

The Crucible Concept of Operations separates Platform Independent Information from Platform Specific Information.

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

The same Platform Independent Information remains applicable to each deployment, while the Platform Specific Information varies according to the selected Provider.

Provider Plugins and Provider Contracts may realize the Provider-specific behavior governed by FR-MC-002.

Delivery Phase

Phase 1

Implementation Status

Not Assessed

Implementation status requires verification that Crucible deploys the same Platform Independent Information to at least two cloud Providers by varying only the applicable Platform Specific Information.

Requirement Status

Draft

The source System Requirements Specification identifies Version 1.1 as a draft.

Notes for Editors

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

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

The Source Statement should preserve the original wording from the controlling System Requirements Specification.

The Statement should remain limited to deploying the same Platform Independent Information to at least two cloud Providers by varying only the applicable Platform Specific Information.

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

Provider Plugin and Provider Contract obligations should remain governed by FR-MC-002 unless the controlling source adds those obligations directly to FR-MC-003.

Verification criteria should test only the behavior stated in the normalized Statement and should not introduce additional normative obligations.

Incoming Traceability should use the wiki Backlinks function rather than a manually maintained list.

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.