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

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_blueprint [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Infrastructure Blueprint ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An Infrastructure Blueprint defines a reusable infrastructure pattern that can be applied to two or more [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment|Infrastructure Environments]].
 +
 +The blueprint identifies common infrastructure structure and intent without binding that structure to one environment instance. The blueprint may identify:
 +
 +  * Infrastructure resource types
 +  * Relationships among resources
 +  * Required configuration properties
 +  * Configurable parameters
 +  * Applicable constraints
 +  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]] references
 +  * Required security and operational characteristics
 +
 +An Infrastructure Blueprint differs from an [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]:
 +
 +  * The Infrastructure Blueprint defines reusable infrastructure structure and common configuration intent
 +  * The Infrastructure Configuration specifies the desired state of an identified Infrastructure Environment
 +
 +Applying an Infrastructure Blueprint may produce or contribute to an Infrastructure Configuration for a particular Infrastructure Environment.
 +
 +Environment-specific values may be supplied through parameters, inherited configuration, or explicit overrides without changing the reusable blueprint content.
 +
 +===== Definition =====
 +
 +//reusable specification of infrastructure resources, relationships, configurable properties, and constraints applicable to two or more infrastructure environments//
 +
 +===== Source =====
 +
 +Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +
 +===== Note =====
 +
 +An Infrastructure Blueprint does not represent a deployed Infrastructure Environment.
 +
 +An Infrastructure Blueprint may use a declarative and 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.
 +
 +Changes to environment-specific parameters do not constitute changes to the Infrastructure Blueprint when the reusable blueprint content remains unchanged.
 +
 +===== Example =====
 +
 +An Infrastructure Blueprint specifies a common application environment comprising compute, storage, network, access-control, logging, and monitoring resources. Development, test, and production Infrastructure Configurations apply the same blueprint with different capacity, address, retention, and access values.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>