FR-MC-004 — Hybrid-Cloud Deployments

Go to Crucible Multi-Cloud Management Requirements

Statement

Crucible SHALL perform an Infrastructure Deployment across an identified combination of cloud and non-cloud Infrastructure Environments.

Source Statement

The system shall support hybrid-cloud deployments.

Source

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

Assessment

The source statement identifies a deployment topology but does not state the required deployment 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 verbHybrid-cloud deployment requires a controlled definitionThe source statement does not identify the participating Infrastructure EnvironmentsThe source statement does not prescribe public-cloud, private-cloud, on-premises, provider, network, or orchestration technologyThe normalized Statement:

Replaces The system with CrucibleReplaces support with performIdentifies Infrastructure Deployment as the required activityIdentifies a combination of cloud and non-cloud Infrastructure EnvironmentsPreserves implementation independenceHybrid-Cloud Deployment should receive a glossary definition.

Rationale

A Hybrid-Cloud Deployment distributes related deployment subjects across cloud and non-cloud Infrastructure Environments.

A Hybrid-Cloud Deployment may combine:

A public-cloud environment and an on-premises environmentA provider-managed cloud environment and a privately operated environmentCloud-hosted services and locally hosted workloadsCloud computing resources and edge computing resourcesThe participating environments may differ in:

Administrative authorityNetwork accessibilitySecurity controlsResource modelsProvider interfacesOperational constraintsCompliance obligationsThe deployment must identify the subjects assigned to each environment and the relationships that cross environment boundaries.

Applies To

This requirement applies to:

Hybrid-Cloud DeploymentsCloud Infrastructure EnvironmentsNon-cloud Infrastructure EnvironmentsInfrastructure ResourcesVirtual MachinesKubernetes ClustersContainerized WorkloadsPlatform ServicesCross-environment relationships

Verification

Verification SHALL confirm that the tested deployment identifies at least one cloud Infrastructure EnvironmentVerification SHALL confirm that the tested deployment identifies at least one non-cloud Infrastructure EnvironmentVerification SHALL confirm that the tested deployment identifies the deployment subjects assigned to each Infrastructure EnvironmentVerification SHALL confirm that Crucible deploys the identified subjects to their assigned Infrastructure EnvironmentsVerification SHALL confirm that the resulting deployment satisfies the applicable cross-environment Acceptance CriteriaVerification may include:

Hybrid-Cloud Deployment testingEnvironment-topology inspectionCross-environment connectivity testingIdentity-boundary testingDeployment-state inspectionAcceptance testingThe verification record SHALL identify:

The participating Infrastructure EnvironmentsThe cloud environmentThe non-cloud environmentThe assigned deployment subjectsThe cross-environment relationshipsThe 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-004.

Incoming Traceability should be derived dynamically from backlinks.

ConOps Relationship

FR-MC-004 establishes deployment across cloud and non-cloud Infrastructure Environments while preserving a coordinated deployment description and traceability relationship.

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

The Statement should remain limited to Infrastructure Deployment across an identified combination of cloud and non-cloud Infrastructure Environments.

Requirements for connectivity, security, identity federation, synchronization, and workload placement should remain separate.

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

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.