ironic/doc/source/admin/features.rst
Julia Kreger db4412d570 OCI container adjacent artifact support
Adds support to use an OCI url for references to artifacts
to deploy.

- Identification of a disk image from the container registry.
- Determination of an image_url which IPA leverages to download
  content. Content cannot be compressed at this point in time.
- Ironic can download the file locally, and with a patch to
  detect and enable Zstandard compression, can extract the
  URL, starting from either an OCI container URL with a Tag,
  or a specific manifest digest, which will then download the
  file for use.
- User driven auth seems to be good.
- Tags work with Quay, however not OpenShift due to what appears
  to be additional request validation.

Closes-Bug: 2085565
Change-Id: I17f7ba57e0ec1a5451890838f153746f5f8e5182
2025-02-06 11:38:21 -08:00

30 lines
957 B
ReStructuredText

Bare Metal Service Features
===========================
.. toctree::
:maxdepth: 1
Hardware Inspection <inspection>
Deployment <node-deployment>
Cleaning <cleaning>
Adoption <adoption>
Retirement <retirement>
RAID Configuration <raid>
BIOS Settings <bios>
Firmware Updates <firmware-updates>
Node Rescuing <rescue>
Booting from Volume <boot-from-volume>
Configuring Web or Serial Console <console>
Enabling Notifications <notifications>
Node Multi-Tenancy <node-multitenancy>
Booting a Ramdisk or an ISO <ramdisk-boot>
Hardware Burn-in <hardware-burn-in>
Vendor Passthru <vendor-passthru>
Servicing <servicing>
Windows Images <building-windows-images>
Deploying without BMC Credentials <agent-power>
Layer 3 or DHCP-less Ramdisk Booting <dhcp-less>
Deploying with Anaconda <anaconda-deploy-interface>
Node History <node-history>
OCI Container Registry Support <oci-container-registry>