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

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment to public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment nick_didopublic:99_annexes:annex-b-terms-and-definitions:i:infrastructure_environment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Infrastructure Environment ====== ====== Infrastructure Environment ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 19: Line 19:
   * Configuration values   * Configuration values
   * Relationships among resources   * Relationships among resources
-  * Applicable [[private:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]+  * Applicable [[public:99_annexes:annex-b-terms-and-definitions:b:baseline|Baselines]]
   * Operational constraints   * Operational constraints
   * Environment-specific parameters   * Environment-specific parameters
  
-Examples of Infrastructure Environments include development, integration, test, staging, production, training, classified, unclassified, connected, disconnected, and [[private:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].+Examples of Infrastructure Environments include development, integration, test, staging, production, training, classified, unclassified, connected, disconnected, and [[public:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environments]].
  
-An Infrastructure Environment differs from an [[private:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]:+An Infrastructure Environment differs from an [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_configuration|Infrastructure Configuration]]:
  
   * The Infrastructure Environment is the infrastructure context being described, created, operated, or evaluated   * The Infrastructure Environment is the infrastructure context being described, created, operated, or evaluated
Line 44: Line 44:
 The term does not require a particular deployment technology, cloud provider, virtualization platform, container platform, operating system, or physical infrastructure. The term does not require a particular deployment technology, cloud provider, virtualization platform, container platform, operating system, or physical infrastructure.
  
-An Infrastructure Environment may inherit configuration from another Infrastructure Environment or may use a shared [[private:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]], but the environment remains independently identifiable.+An Infrastructure Environment may inherit configuration from another Infrastructure Environment or may use a shared [[public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_blueprint|Infrastructure Blueprint]], but the environment remains independently identifiable.
  
 ===== Example ===== ===== Example =====
  • public/99_annexes/annex-b-terms-and-definitions/i/infrastructure_environment.1789260154.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido