FR-DEP-002 — Deploy Virtual Machines

Go to Crucible Deployment Orchestration Requirements

Statement

Crucible SHALL deploy Virtual Machines.

Derived From

This requirement derives from:

Crucible System Requirements Specification, Version 1.1 Draft, Functional Requirements, FR-DEP-002The Original Requirement states:

The system shall deploy virtual machines.[C1]

FR-DEP-002:

Replaces The system with the defined system name CrucibleChanges shall to the established uppercase normative form SHALLLinks Virtual Machines to the controlling definitionNo other substantive normalization is required.

Rationale

A Virtual Machine provides a computing environment through virtualized processor, memory, storage, network, and related resources.

Deploying Virtual Machines enables Crucible to create virtualized computing resources through separately governed deployment workflows.

This requirement establishes the Virtual Machine deployment behavior without prescribing:

The Machine ImageThe target Infrastructure EnvironmentThe virtualization platformThe Virtual Machine configurationRuntime activationDeployment validationDeployment rollbackCompliance assessmentSeparate requirements define those subjects and behaviors.

Applies To

This requirement applies to:

Virtual Machine deployment operations

Verification

Verification confirms that:

One or more Virtual Machines are selected for deploymentCrucible executes a deployment operation for the selected Virtual MachinesThe completed deployment produces the selected Virtual MachinesThe resulting Virtual Machines can be identified as outputs of the tested deployment

Referenced By

The following pages reference this requirement:

Implementation Status

Implemented and Verified

Requirement Status

Issues

Notes for Editors

This requirement page retains the stable requirement identifier FR-DEP-002.

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 deploy Virtual Machines.

Do not add a Machine Image, target Infrastructure Environment, Deployment Target, virtualization platform, runtime-activation, rollback, validation, compliance-assessment, or retirement obligation 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-03-deployment-orchestration:fr-dep-002#Statement&noheader&nofooter&noeditbtn}}

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.