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:c:capability_image [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:c:capability_image to public:99_annexes:annex-b-terms-and-definitions:c:capability_image nick_didopublic:99_annexes:annex-b-terms-and-definitions:c:capability_image [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 ====== Capability Image ====== ====== Capability Image ======
  
-[[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 =====
  
-A Capability Image is a [[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] that extends another image by adding a defined operational, platform, service, or workload capability.+A Capability Image is a [[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|Machine Image]] that extends another image by adding a defined operational, platform, service, or workload capability.
  
 The added capability may include software packages, runtime services, configuration, policies, agents, orchestration components, monitoring tools, or workload-specific dependencies. The added capability may include software packages, runtime services, configuration, policies, agents, orchestration components, monitoring tools, or workload-specific dependencies.
Line 11: Line 11:
 A Capability Image preserves the inherited foundation of its source image while adding the elements needed for a particular role. A Capability Image preserves the inherited foundation of its source image while adding the elements needed for a particular role.
  
-Within Crucible, a Capability Image may build on a [[private:99_annexes:annex-b-terms-and-definitions:h:hardened_image|Hardened Image]] so that workload-specific functionality does not replace the shared operating-system and security foundation.+Within Crucible, a Capability Image may build on a [[public:99_annexes:annex-b-terms-and-definitions:h:hardened_image|Hardened Image]] so that workload-specific functionality does not replace the shared operating-system and security foundation.
  
 ===== Definition ===== ===== Definition =====
  
-//[[private:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] that extends another image by adding a defined operational, platform, service, or workload capability//+//[[public:99_annexes:annex-b-terms-and-definitions:m:machine_image|machine image]] that extends another image by adding a defined operational, platform, service, or workload capability//
  
 ===== Source ===== ===== Source =====
Line 23: Line 23:
 ===== Note ===== ===== Note =====
  
-A Capability Image identifies a realized image artifact. A [[private:99_annexes:annex-b-terms-and-definitions:c:capability_layer|Capability Layer]] identifies the controlled set of changes used to add the capability.+A Capability Image identifies a realized image artifact. A [[public:99_annexes:annex-b-terms-and-definitions:c:capability_layer|Capability Layer]] identifies the controlled set of changes used to add the capability.
  
 A Capability Image may provide one capability or a compatible combination of capabilities. A Capability Image may provide one capability or a compatible combination of capabilities.
  • public/99_annexes/annex-b-terms-and-definitions/c/capability_image.1789260135.txt.gz
  • Last modified: 2026/09/12 17:42
  • by nick_dido