Differences

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

--- dido:99_annexes:annex-b-terms-and-definitions:m:machine_image [2026/07/13 11:36] – created nick_dido
+++ dido:99_annexes:annex-b-terms-and-definitions:m:machine_image [2026/07/17 08:29] (current) – [Definition] nick_dido
@@ Line 9: / Line 9: @@
 The image may contain an operating system, partitions, filesystems, packages, services, users, security settings, configuration data, drivers, and installed capabilities.
-A Machine Image may serve as the source for a virtual machine, cloud compute instance, physical-machine installation, or later image layer.
+A Machine Image may serve as the source for a virtual machine, a cloud compute instance, a physical machine installation, or a later image layer.
-Within Crucible, a Machine Image results from a controlled image build and may be hardened, scanned, signed, converted, registered with a provider, and recorded in an image catalogue.
+Within Crucible, a Machine Image results from a controlled image build and may be hardened, scanned, signed, converted, registered with a provider, and recorded in an image catalog.
 ===== Definition =====
-//deployable digital representation of the storage content and system configuration required to instantiate a physical or virtual computing machine//
+//[[dido:99_annexes:annex-b-terms-and-definitions:i:image|image]] that packages the software, configuration, files, metadata, and other content required to instantiate a [[dido:99_annexes:annex-b-terms-and-definitions:v:virtual_machine|Virtual Machine]]//
 ===== Source =====
@@ Line 23: / Line 23: @@
 ===== Note =====
-A Machine Image differs from an [[dido:99_annexes:annex-b-terms-and-definitions:i:image_baseline|Image Baseline]]. The Image Baseline defines the controlled inputs and process used to produce the image, while the Machine Image is the resulting deployable artefact.
+A Machine Image differs from an [[dido:99_annexes:annex-b-terms-and-definitions:i:image_baseline|Image Baseline]]. The Image Baseline defines the controlled inputs and process used to produce the image, while the Machine Image is the resulting deployable artifact.
 A Machine Image may require provider-specific conversion or registration before deployment to a particular platform.
@@ Line 29: / Line 29: @@
 ===== Example =====
-Crucible builds a RHEL 9 Machine Image containing an installed operating system, configured filesystems, required packages, security settings, and compliance remediation. A Provider Plugin uploads and registers the image for use by a cloud deployment.
+Crucible builds a [[dido:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 Machine Image containing an installed operating system, configured filesystems, required packages, security settings, and compliance remediation. A Provider Plugin uploads and registers the image for use by a cloud deployment.
 ----