public:99_annexes:annex-b-terms-and-definitions:e:execution_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:e:execution_environment [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:e:execution_environment to public:99_annexes:annex-b-terms-and-definitions:e:execution_environment nick_didopublic:99_annexes:annex-b-terms-and-definitions:e:execution_environment [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Execution Environment ====== ====== Execution Environment ======
  
-[[private:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 9: Line 9:
 The environment may include physical machines, virtual machines, containers, cloud resources, operating-system services, runtime libraries, configuration data, secrets, and external service connections. The environment may include physical machines, virtual machines, containers, cloud resources, operating-system services, runtime libraries, configuration data, secrets, and external service connections.
  
-An Execution Environment differs from a [[private:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]]. An Execution Environment identifies the resources in which software executes. A Target Environment identifies the environment selected to receive a particular build, deployment, or release.+An Execution Environment differs from a [[public:99_annexes:annex-b-terms-and-definitions:t:target_environment|Target Environment]]. An Execution Environment identifies the resources in which software executes. A Target Environment identifies the environment selected to receive a particular build, deployment, or release.
  
 A single Execution Environment may support multiple software products, services, or workloads. A single product may also execute across multiple Execution Environments. A single Execution Environment may support multiple software products, services, or workloads. A single product may also execute across multiple Execution Environments.
Line 23: Line 23:
 ===== Note ===== ===== Note =====
  
-An Execution Environment may operate as a [[private:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]], [[private:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]], or [[private:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].+An Execution Environment may operate as a [[public:99_annexes:annex-b-terms-and-definitions:c:connected_environment|Connected Environment]], [[public:99_annexes:annex-b-terms-and-definitions:d:disconnected_environment|Disconnected Environment]], or [[public:99_annexes:annex-b-terms-and-definitions:a:air-gapped_environment|Air-Gapped Environment]].
  
 The term does not prescribe a physical machine, virtual machine, container, cloud service, or deployment technology. The term does not prescribe a physical machine, virtual machine, container, cloud service, or deployment technology.
  • public/99_annexes/annex-b-terms-and-definitions/e/execution_environment.1789260146.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido