Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:m:machine_image [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:m:machine_image [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Machine Image ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Machine Image is a deployable digital representation of the storage content and system configuration required to instantiate a physical or virtual computing machine. | ||
| + | |||
| + | The image may contain an operating system, partitions, filesystems, | ||
| + | |||
| + | A Machine Image may serve as the source for a virtual machine, a cloud compute instance, a physical machine installation, | ||
| + | |||
| + | 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 ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from virtualization, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Machine Image differs from an [[public: | ||
| + | |||
| + | A Machine Image may require provider-specific conversion or registration before deployment to a particular platform. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | Crucible builds a [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||