NOD-004f — Restart or Recover the Node

Go to NOD-004 — Control the Node Lifecycle

Statement

The DIDO-TE SHALL restart or recover a Node through an identified and authorized lifecycle procedure.

Derived From

, source requirement identifier and obligation to be assigned[DTE6] Structured Information Processing Reference Architecture (SIP-RA)[DTE7] Federated Data Interpretation Systems Reference Architecture (FDIS-RA)

Rationale

A restart returns a Node to an operating state through a controlled stop-and-start sequence or an equivalent procedure defined by the Node Definition or Node Implementation.

Recovery restores a Node from a failed, degraded, interrupted, inconsistent, or otherwise unsuitable state to a known state from which the DIDO-TE resumes lifecycle control. Recovery may include fault isolation, cleanup, restoration of data, reapplication of the Node Configuration, re-establishment of Node Bindings, replacement of resources, and validation of the resulting Node.

Restart and recovery have different purposes. A restart repeats an established operating sequence. Recovery addresses a condition that prevents normal Node operation or produces uncertainty about the Node state.

An uncontrolled restart or recovery may preserve the original fault, introduce configuration drift, duplicate processing, lose or replay data, reconnect the Node to an unintended participant, or contaminate a subsequent Test Execution.

The DIDO-TE reevaluates Node readiness and determines the effect of the interruption, restart, or recovery on applicable Test Results and Evidence before returning the Node to Test Execution.

Applies To

[[dido:99_annex