FR-MC-004 — Hybrid-Cloud Deployments

Go to Crucible Multi-Cloud Management Requirements

Crucible SHALL perform Hybrid-Cloud Deployments.

This requirement derives from:

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

The Original Requirement states:

The system shall support Hybrid-Cloud Deployments.[C1]

FR-MC-004:

• Replaces The system with the defined system name Crucible
• Changes shall to the established uppercase normative form SHALL
• Replaces the weak verb support with the observable behavior perform
• Links Hybrid-Cloud Deployments to the controlling definition

No other substantive normalization is required.

A Hybrid-Cloud Deployment combines deployment subjects across cloud and non-cloud environments.

A Hybrid-Cloud Deployment can include:

• A public-cloud environment and an on-premises environment
• A provider-managed cloud environment and a privately operated environment
• Cloud-hosted services and locally hosted workloads
• Cloud computing resources and edge computing resources

The participating environments can differ in administrative authority, network accessibility, security controls, resource models, Provider interfaces, operational constraints, and compliance obligations.

This requirement establishes Hybrid-Cloud Deployment behavior without prescribing:

• The participating environments
• The deployment subjects assigned to each environment
• Cross-environment connectivity
• Identity federation
• Security-boundary behavior
• Synchronization
• Workload placement
• A particular Cloud Provider
• A particular network or orchestration technology

Separate requirements, architecture specifications, workflows, or policies define those subjects and behaviors.

This requirement applies to:

• Crucible
• Hybrid-Cloud Deployments
• Cloud environments
• Non-cloud environments
• Hybrid deployment workflows

Verification confirms that:

1. A Hybrid-Cloud Deployment is selected for testing
2. The tested deployment includes at least one cloud environment
3. The tested deployment includes at least one non-cloud environment
4. Crucible performs the tested Hybrid-Cloud Deployment
5. Deployment subjects are realized in the participating environments
6. The observed behavior demonstrates deployment across cloud and non-cloud environments

The following pages reference this requirement:

Implemented and Verified

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

Confirm that Hybrid-Cloud Deployment has a controlled definition in the shared Terms and Definitions corpus.

Determine whether separate requirements define cross-environment connectivity, security, identity federation, synchronization, and workload placement.

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

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 perform Hybrid-Cloud Deployments.

Do not add specific cloud and non-cloud Infrastructure Environments, workload placement, connectivity, security, identity federation, synchronization, Provider, network, or orchestration 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-004#Statement&noheader&nofooter&noeditbtn}}