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:i:image_catalog [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:i:image_catalog [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Image Catalog ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Image [[public: | ||
| + | |||
| + | The catalog may record image identities, versions, operating systems, processor architectures, | ||
| + | |||
| + | An Image Catalog supports image selection by allowing deployment and composition processes to compare image requirements with the characteristics of available images. | ||
| + | |||
| + | Within Crucible, the Image Catalog may connect a built image with its provider-specific realizations, | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from artifact catalog, image registry, configuration management, cloud-image management, and software inventory usage and specialized for the Crucible architecture and operational model. | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Image Catalog records information about Machine Images. It does not necessarily store the image content itself. | ||
| + | |||
| + | An Image Catalog differs from a container registry or package repository because its primary purpose is to describe and govern Machine Images and their realizations. | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An Image Catalog records a hardened [[public: | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||