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

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_baseline [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_baseline [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Infrastructure Baseline ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An Infrastructure Baseline is a [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] that identifies the controlled definitions, inputs, constraints, relationships, and processes used to provision, configure, verify, and manage infrastructure.
 +
 +The Infrastructure Baseline may identify requirements for compute, storage, networking, identity, security, monitoring, provider, topology, capacity, image, and lifecycle.
 +
 +An Infrastructure Baseline defines the intended infrastructure configuration independently of a particular deployed instance. A deployment realizes the Baseline within a selected [[public:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]].
 +
 +Within Crucible, an Infrastructure Baseline may reside in a versioned repository that a [[public:99_annexes:annex-b-terms-and-definitions:c:crucible_description|Crucible Description]] references and pins to an exact revision.
 +
 +===== Definition =====
 +
 +//[[public:99_annexes:annex-b-terms-and-definitions:b:baseline|baseline]] that identifies the controlled definitions, inputs, constraints, relationships, and processes used to provision, configure, verify, and manage infrastructure//
 +
 +===== Source =====
 +
 +Generalized from infrastructure as code, configuration management, deployment automation, and systems-engineering usage and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +An Infrastructure Baseline differs from deployed infrastructure. The Baseline defines the approved configuration, while a deployment realizes that configuration in a Target Environment.
 +
 +An Infrastructure Baseline may remain independent of a specific Machine Image by declaring image requirements that a composition or deployment process resolves.
 +
 +===== Example =====
 +
 +An Infrastructure Baseline defines the compute nodes, virtual networks, subnets, load balancer, storage, identity rules, security controls, and deployment procedures required for a Kubernetes platform.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>