| |
| dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration [2026/08/08 12:40] – created nick_dido | dido:99_annexes:annex-b-terms-and-definitions:n:node_configuration [2026/08/08 12:44] (current) – nick_dido |
|---|
| ===== Discussion ===== | ===== Discussion ===== |
| |
| A Node Configuration establishes how a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] operates within a particular environment or execution context. | A Node Configuration establishes how a [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]] operates within a particular [[dido:99_annexes:annex-b-terms-and-definitions:e:environment|Environment]] or execution context. |
| |
| The Node Configuration identifies the applicable Configuration Parameters, assigns or references their Configuration Values, establishes required Node Bindings, and records the rules governing value resolution and application. | The Node Configuration identifies the applicable Configuration Parameters, assigns or references their [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_value|Configuration Values]], identifies their [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration_source|Configuration Sources]], establishes required Node Bindings, and specifies the rules governing value resolution and application. |
| |
| A Node Configuration remains distinct from a Node Definition and a Node Implementation. The Node Definition specifies the required characteristics and behaviour of the Node. The Node Implementation realizes those characteristics and behaviour. The Node Configuration assigns the settings and relationships applicable to a particular Node instance. | A Node Configuration remains distinct from a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_definition|Node Definition]] and a [[dido:99_annexes:annex-b-terms-and-definitions:n:node_implementation|Node Implementation]]. The Node Definition specifies the required characteristics and behaviour of the Node. The Node Implementation realizes those characteristics and behaviour. The Node Configuration assigns the settings and relationships applicable to a particular Node instance. |
| |
| A Node Configuration also remains distinct from a Test Input. A Node Configuration establishes the operating conditions of the Node, while a Test Input supplies data or stimuli consumed during Test Execution. | A Node Configuration also remains distinct from a [[dido:99_annexes:annex-b-terms-and-definitions:t:test_input|Test Input]]. The Node Configuration establishes the operating conditions of the Node. The Test Input supplies data or stimuli consumed during [[dido:99_annexes:annex-b-terms-and-definitions:t:test_execution|Test Execution]]. |
| |
| ===== Definition ===== | ===== Definition ===== |
| |
| A Node Configuration includes identifiers, versions, sources, constraints, value-resolution rules, application rules, security controls, and other information required to reproduce and validate the configured Node. | A Node Configuration includes identifiers, versions, sources, constraints, value-resolution rules, application rules, security controls, and other information required to reproduce and validate the configured Node. |
| | |
| | A Node Configuration associates protected values with a [[dido:99_annexes:annex-b-terms-and-definitions:c:credential|Credential]], [[dido:99_annexes:annex-b-terms-and-definitions:c:cryptographic_material|Cryptographic Material]], or other applicable information classification. |
| |
| A material change to a Node Configuration produces a distinguishable configuration revision. | A material change to a Node Configuration produces a distinguishable configuration revision. |
| ===== Example ===== | ===== Example ===== |
| |
| A Node Configuration for a DDS publishing Node identifies the DDS domain, topic, partition, Quality of Service profile, network interface, security credentials, logging level, and destination bindings assigned to the Node. | A Node Configuration for a [[dido:99_annexes:annex-b-terms-and-definitions:d:dds|DDS]] publishing Node identifies the DDS domain, topic, partition, Quality of Service profile, network interface, security Credential, logging level, and destination bindings assigned to the Node. |
| |
| ---- | ---- |