Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-002-provision-a-node:nod-002d-allocate-node-resources [2026/08/17 14:20] – removed - external edit (Unknown date) 127.0.0.1 | dido:03-dido-te:99-annexes:annex-c-requirements:03-functional-requirements:03-02-node-requirements:nod-002-provision-a-node:nod-002d-allocate-node-resources [2026/08/17 14:20] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== NOD-002d — Allocate Node Resources ====== | ||
| + | [[dido: | ||
| + | |||
| + | ===== Statement ===== | ||
| + | |||
| + | The [[dido: | ||
| + | |||
| + | ===== Derived From ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Rationale ===== | ||
| + | |||
| + | A Node requires computing, memory, storage, network, device, timing, software, operating-system, | ||
| + | |||
| + | Controlled allocation establishes the capacity, performance, | ||
| + | |||
| + | Missing, insufficient, | ||
| + | |||
| + | ===== Applies To ===== | ||
| + | |||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * Node Definition | ||
| + | * Node Implementation | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | * [[dido: | ||
| + | |||
| + | ===== Verification ===== | ||
| + | |||
| + | Verification confirms that: | ||
| + | |||
| + | * Each Node resource requirement has a unique identity. | ||
| + | * Each allocated Test Resource has a unique identity. | ||
| + | * Each mandatory resource requirement maps to one or more allocated Test Resources. | ||
| + | * Each allocated Test Resource has an identified type, quantity, capacity, performance, | ||
| + | * Each allocation satisfies the minimum resource requirements defined for provisioning. | ||
| + | * Each allocation remains within the applicable maximum limits. | ||
| + | * The allocation identifies each resource as dedicated, exclusive, shared, reserved, limited, persistent, or temporary when the distinction affects Node behaviour. | ||
| + | * The allocation satisfies applicable quotas, reservations, | ||
| + | * The allocation satisfies applicable security, integrity, access-control, | ||
| + | * Resources required during provisioning remain distinguishable from resources required during configuration, | ||
| + | * The DIDO-TE verifies the availability and suitability of each mandatory Test Resource before provisioning uses it. | ||
| + | * The DIDO-TE verifies that shared resources have sufficient available capacity. | ||
| + | * The DIDO-TE detects conflicting, | ||
| + | * The DIDO-TE detects a missing, unavailable, | ||
| + | * The DIDO-TE prevents provisioning from proceeding when an unsatisfied resource requirement affects the validity of the provisioned Node. | ||
| + | * The allocation identifies the permitted duration and applicable release conditions for each Test Resource. | ||
| + | * The allocation identifies resources requiring cleanup, restoration, | ||
| + | * The DIDO-TE records the actual Test Resources allocated to the Node. | ||
| + | * The DIDO-TE records the identities, characteristics, | ||
| + | * The DIDO-TE records any approved difference between the required and allocated resources. | ||
| + | * Each approved difference identifies its authority, rationale, scope, duration, and expected effect. | ||
| + | * The DIDO-TE maintains [[dido: | ||
| + | * A missing, insufficient, | ||
| + | |||
| + | Verification includes: | ||
| + | |||
| + | * Inspection of the Node resource requirements | ||
| + | * Inspection of allocated Test Resource identities, types, capacities, locations, availability, | ||
| + | * Comparison of required resources with allocated Test Resources | ||
| + | * Confirmation that minimum and maximum allocation limits remain satisfied | ||
| + | * Confirmation of applicable reservations, | ||
| + | * Verification of Test Resource availability before provisioning | ||
| + | * Verification of sufficient capacity for shared resources | ||
| + | * A negative assessment involving a missing or unavailable mandatory resource | ||
| + | * A negative assessment involving an insufficient or incompatible allocation | ||
| + | * A negative assessment involving a conflicting or unauthorised allocation | ||
| + | * Confirmation that an unsatisfied mandatory allocation prevents invalid provisioning | ||
| + | * Inspection of approved allocation differences | ||
| + | * Inspection of allocation, release, restoration, | ||
| + | |||
| + | ===== Referenced By ===== | ||
| + | |||
| + | {{backlinks> | ||
| + | |||
| + | ===== Related Architecture Sections ===== | ||
| + | |||
| + | * Add links to the architecture sections governing Test Resources, resource allocation, capacity, isolation, Test Environment composition, | ||
| + | |||
| + | ===== Delivery Phase ===== | ||
| + | |||
| + | Assign the applicable delivery phase. | ||
| + | |||
| + | ===== Requirement Status ===== | ||
| + | |||
| + | Draft | ||
| + | |||
| + | ===== Statement Reference ===== | ||
| + | |||
| + | Use the following syntax to reference this requirement’s Statement section from another DokuWiki page: | ||
| + | |||
| + | <code dokuwiki> | ||
| + | {{section> | ||
| + | </ | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||