FR-MC-003 — Deployment Portability Across Cloud Providers

Go to Crucible Multi-Cloud Management Requirements

Crucible SHALL provide deployment portability across Cloud Providers.

This requirement derives from:

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

The Original Requirement states:

The system shall support deployment portability across cloud providers.[C1]

FR-MC-003:

• 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
• Links Cloud Providers to the controlling definition

No other substantive normalization is required.

Deployment portability allows deployment intent to be realized through more than one Cloud Provider without requiring the deployment intent to be redesigned for each Provider.

Cloud Providers expose different:

• Resource types
• Service identifiers
• Configuration parameters
• Identity models
• Network models
• Storage models
• Regions
• Management interfaces
• Operational constraints

Deployment portability does not require Cloud Providers to expose identical resources, services, interfaces, costs, performance characteristics, or physical implementations.

This requirement establishes deployment portability without prescribing:

• A minimum number of tested Cloud Providers
• Platform Independent Information
• Platform Specific Information
• Provider Plugins
• Provider Contracts
• Identical Provider-specific realizations
• Particular Cloud Providers
• Common Acceptance Criteria

Separate requirements, architecture specifications, or verification profiles define those subjects.

This requirement applies to:

• Crucible
• Deployment portability
• Cloud Providers
• Cloud deployment workflows

Verification confirms that:

1. A deployment is selected for portability testing
2. Two or more Cloud Providers are selected for testing
3. Crucible deploys the selected deployment through each tested Cloud Provider
4. The resulting deployments preserve the deployment intent selected for the portability test
5. Provider-specific differences do not prevent the selected deployment from being realized through each tested Cloud Provider
6. The observed behavior demonstrates deployment portability across Cloud Providers

The following pages reference this requirement:

Implemented and Verified

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

Determine whether Deployment Portability requires a controlled definition in the shared Terms and Definitions corpus.

Determine whether a separate verification profile should define the minimum number and types of Cloud Providers used to demonstrate deployment portability.

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

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 deployment portability across Cloud Providers.

Do not add Platform Independent Information, Platform Specific Information, Provider Plugin, Provider Contract, common Acceptance Criteria, identical Provider realization, or a particular minimum number of Cloud Providers to the Statement unless the controlling requirement changes through an approved requirements process.

Verification may use two or more Cloud Providers because portability across Providers cannot be demonstrated with only one Provider. This verification condition does not add a particular Provider or Provider technology to the normative Statement.

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