Differences

This shows you the differences between two versions of the page.

--- public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_definition [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1
+++ public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_definition [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
@@ Line 1: / Line 1: @@
+====== Infrastructure Definition ======
+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
+===== Discussion =====
+An Infrastructure Definition is a machine-processable specification of infrastructure resources, relationships, constraints, configuration, and lifecycle behavior.
+The definition may identify compute resources, storage, networking, identity, security controls, monitoring, provider settings, dependencies, topology, capacity, and deployment conditions.
+An Infrastructure Definition provides input to an automated provisioning or deployment process. The resulting deployed infrastructure is a realization of the definition rather than the definition itself.
+An [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline|Infrastructure Baseline]] may contain one or more Infrastructure Definitions together with supporting configuration, procedures, validation rules, and metadata.
+===== Definition =====
+//machine-processable specification of infrastructure resources, relationships, constraints, configuration, and lifecycle behavior//
+===== Source =====
+Generalized from [[public:99_annexes:annex-b-terms-and-definitions:i:iac|Infrastructure as Code (IaC)]], deployment automation, systems modeling, and cloud orchestration usage and specialized for the Crucible architecture and operational model.
+===== Note =====
+An Infrastructure Definition describes intended infrastructure. It does not identify the complete realized state of a deployed environment unless the applicable language and process explicitly record that state.
+The definition may remain independent of a specific [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] by declaring [[public:99_annexes:annex-b-terms-and-definitions:i:image_requirement|Image Requirements]].
+===== Example =====
+An Infrastructure Definition specifies three compute nodes, two subnets, a load balancer, storage volumes, identity rules, and network security controls for a Kubernetes deployment.
+----
+<WRAP centeralign>
+© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
+</WRAP>