public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Infrastructure Configuration ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An Infrastructure Configuration represents the desired state of an [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environment]].
 +
 +The representation identifies the infrastructure elements and conditions required for the environment, including:
 +
 +  * Infrastructure resources
 +  * Configuration values
 +  * Relationships among resources
 +  * Applicable constraints
 +  * Required inputs and parameters
 +  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] references
 +
 +An Infrastructure Configuration describes the state that the Infrastructure Environment is required to achieve or preserve. The Infrastructure Configuration does not need to prescribe the sequence of operations used to create that state.
 +
 +An Infrastructure Configuration may serve as:
 +
 +  * A controlled input to [[public:99_annexes:annex-b-terms-and-definitions:p:provisioning|Provisioning]]
 +  * An input to [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_deployment|Infrastructure Deployment]]
 +  * A basis for comparing the desired and observed states
 +  * A reusable configuration artifact
 +  * A child or parent configuration within an inheritance relationship
 +  * A version-controlled record of infrastructure intent
 +
 +An Infrastructure Configuration differs from an Infrastructure Environment:
 +
 +  * The Infrastructure Configuration represents the required state
 +  * The Infrastructure Environment is the infrastructure context represented, created, operated, or evaluated
 +
 +===== Definition =====
 +
 +//configuration that specifies the desired state of an identified infrastructure environment through infrastructure resources, configuration values, relationships, constraints, and applicable baseline references//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +An Infrastructure Configuration may use a declarative, machine-readable representation.
 +
 +The term does not require a particular configuration language, file format, provisioning technology, cloud provider, virtualization platform, container platform, or operating system.
 +
 +A resolved Infrastructure Configuration may combine values inherited from a parent Infrastructure Configuration with explicit values defined by a child Infrastructure Configuration.
 +
 +===== Example =====
 +
 +An Infrastructure Configuration for a production environment specifies the required compute resources, storage resources, network relationships, access-control settings, resource parameters, operational constraints, and applicable Infrastructure Baseline.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>