FR-MC-005 — Edge Deployments

Go to Crucible Multi-Cloud Management Requirements

Crucible SHALL perform Edge Deployments.

This requirement derives from:

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

The Original Requirement states:

The system shall support edge deployments.[C1]

FR-MC-005:

• 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
• Capitalizes Edge Deployments as the named deployment capability

No other substantive normalization is required.

An Edge Deployment places computing capabilities near a source or consumer of data, an operational process, a physical location, or another location where local processing provides an architectural benefit.

An Edge Deployment can involve:

• Infrastructure Resources
• Virtual Machines
• Kubernetes Clusters
• Containerized Workloads
• Platform Services

This requirement establishes Edge Deployment behavior without prescribing:

• The deployment subjects
• The target Edge Environment
• An edge platform
• A device class
• A Cloud Provider
• A network architecture
• An orchestration mechanism
• A connectivity model
• Disconnected operation
• Air-gapped operation
• Resource constraints
• Synchronization behavior

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

This requirement applies to:

• Crucible
• Edge Deployments
• Edge deployment workflows

Verification confirms that:

1. An Edge Deployment is selected for testing
2. The target of the tested deployment exhibits the characteristics defined for an Edge Deployment
3. Crucible performs the tested Edge Deployment
4. The deployed subjects can be identified in the target environment
5. The observed behavior demonstrates Edge Deployment

The following pages reference this requirement:

Implemented and Verified

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

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

Determine whether Edge Environment requires a controlled definition in the shared Terms and Definitions corpus.

Determine whether separate requirements define connectivity, synchronization, resource constraints, and network isolation for Edge Deployments.

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

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 Edge Deployments.

Do not treat Edge Deployment as synonymous with deployment to a Disconnected Environment or Air-Gapped Environment.

Do not add specific deployment subjects, an Edge Environment, dependency capture, disconnected operation, synchronization, resource constraints, network isolation, platform, device, Provider, or connectivity 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-005#Statement&noheader&nofooter&noeditbtn}}