{"results":[{"id":"anaconda-boot-parameter-framework","text":"Anaconda installation is controlled through a layered boot parameter framework: inst.ks= for Kickstart automation, inst.repo= for installation source selection (supporting HTTP/FTP/NFS/CDN), inst.stage2= for runtime image location, inst.graphical/text/cmdline for UI mode control, and inst.sshd for remote access during installation.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"bootc-atomic-updates-and-rollback","text":"bootc provides atomic updates (pull new image and reboot) and rollback to previous OS versions if an update causes problems.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-blueprint-toml","text":"Image Builder blueprints are written in TOML format and define packages, groups, and customizations for image builds.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-blueprints-toml-format","text":"Image Builder blueprints are written in TOML format and define packages, groups, and customizations","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-complete-workflow","text":"RHEL Image Builder provides a complete image creation pipeline: TOML blueprint definition, osbuild-composer backend with socket activation, multi-format output, and a push-then-compose CLI workflow.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-composes-edge-images","text":"Image Builder (osbuild-composer) is the supported tool for composing RHEL for Edge images, available via `composer-cli` and Cockpit web UI.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-osbuild-composer","text":"RHEL Image Builder uses `osbuild-composer` as the backend service and `composer-cli` as the command-line interface, enabled via `osbuild-composer.socket`.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-osbuild-composer-backend","text":"`osbuild-composer` is the backend service for RHEL Image Builder and `composer-cli` is its command-line interface","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-output-types","text":"Image Builder supports multiple output formats from a single blueprint including qcow2, vmdk, ami, vhd, iso, and others, listed via `composer-cli compose types`.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-socket-activation","text":"The Image Builder service is enabled with `systemctl enable --now osbuild-composer.socket`","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"image-builder-workflow","text":"The Image Builder workflow is: create blueprint → push blueprint (`composer-cli blueprints push`) → start compose (`composer-cli compose start`) → download image (`composer-cli compose image <UUID>`).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"inst-stage2-locates-runtime-image","text":"`inst.stage2=` specifies the location of the installer runtime image (`install.img`), which is separate from the package repository specified by `inst.repo=`.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"kickstart-installation-sources","text":"Kickstart installations can pull content from local media (DVD/USB), ISO images, Red Hat CDN, or network servers (HTTP, FTP, NFS).","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"quadlet-production-container-management","text":"Quadlet is production-ready for declarative systemd-native container lifecycle management on RHEL 9, supporting container, build, pod, and image unit types with Podman as the runtime.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel-edge-post-deployment-fips-enablement","text":"RHEL for Edge images support enabling FIPS mode after initial deployment using standard `fips-mode-setup --enable` tooling, allowing deferred compliance configuration.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel-edge-uses-rpm-ostree","text":"RHEL for Edge images use rpm-ostree for image-based atomic updates and rollbacks, not traditional RPM/DNF package management.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel-image-mode-bootc-oci-containers","text":"RHEL image mode (bootc) manages the OS as a standard OCI container image, built with Podman/Buildah and stored in container registries.","truth_value":"IN","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel9-complete-provisioning-control-framework","text":"RHEL 9 provides complete provisioning control from boot parameter specification through deployment execution: the installer control framework (inst.ks, inst.repo, inst.stage2, network configuration via ip=/bootdev=) feeds directly into the end-to-end provisioning pipeline (Image Builder blueprints, Kickstart automation, multiple installation methods), giving administrators deterministic control over every provisioning decision.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel9-complete-system-lifecycle-management","text":"RHEL 9 manages the complete temporal system lifecycle: automated provisioning (Image Builder blueprints, Kickstart, Anaconda) for initial deployment, structured patch management (BaseOS/AppStream content split, DNF security update filtering, advisory-driven remediation) for day-2 operations, and dual upgrade paradigms (Leapp sequential in-place upgrades, bootc image-based atomic updates) for major version transitions.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null},{"id":"rhel9-content-gated-provisioning-pipeline","text":"RHEL 9 provisioning depends on a subscription-gated content chain: systems must first register (GUI/TUI, subscription-manager, or activation key) and establish repository access (CDN or Satellite) before the provisioning pipeline (Image Builder blueprints, Kickstart automation, Anaconda installation) can source packages from BaseOS and AppStream.","truth_value":"OUT","justification_count":0,"dependent_count":0,"challenges":[],"last_reviewed":null,"review_result":null}],"count":35,"limit":20,"offset":0}