public:99_annexes:annex-b-terms-and-definitions:o:offline_repository

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:99_annexes:annex-b-terms-and-definitions:o:offline_repository [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1public:99_annexes:annex-b-terms-and-definitions:o:offline_repository [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido
Line 1: Line 1:
 +====== Offline Repository ======
  
 +[[public:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
 +
 +===== Discussion =====
 +
 +An Offline Repository is a repository that makes controlled content available within an environment without requiring direct access to the original external source.
 +
 +The repository may provide operating-system packages, software packages, container images, provider packages, source content, compliance content, or other dependencies needed for build, deployment, maintenance, or recovery.
 +
 +An Offline Repository is populated through an approved transfer, synchronization, import, replication, or staging process.
 +
 +Within Crucible, a [[public:99_annexes:annex-b-terms-and-definitions:t:transfer_bundle|Transfer Bundle]] may populate an Offline Repository inside a [[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]].
 +
 +===== Definition =====
 +
 +//repository that makes controlled content available without requiring direct access to the original external source//
 +
 +===== Source =====
 +
 +Generalized from package management, software distribution, disconnected operations, repository mirroring, and infrastructure management and specialized for the Crucible architecture and operational model.
 +
 +===== Note =====
 +
 +Offline describes the repository’s independence from the original external source during use. It does not mean that the repository cannot operate on an internal network.
 +
 +An Offline Repository should preserve sufficient identity, version, integrity, and provenance information to support controlled use of its contents.
 +
 +===== Example =====
 +
 +An air-gapped enclave imports a Transfer Bundle and creates an Offline Repository containing the [[public:99_annexes:annex-b-terms-and-definitions:r:rhel]] 9 packages required to rebuild and update approved Machine Images without external network access.
 +
 +----
 +
 +<WRAP centeralign>
 +© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.
 +</WRAP>