Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-3253

RHEL for Edge support in system roles

    • rhel-system-roles-1.23.0-2.21.el9
    • sst_system_roles
    • 12
    • 22
    • QE ack, Dev ack
    • False
    • Hide

      None

      Show
      None
    • Yes
    • Red Hat Enterprise Linux
    • Enhancement
    • Hide
      .RHEL system roles adds support for RHEL for Edge `rpm-ostree` systems

      With this enhancement, RHEL system roles added full support to RHEL for Edge `rpm-ostree` systems. With that, you can now use RHEL system roles to automate, deploy, and manage your RHEL for Edge (rpm-ostree) systems. You can use the Podman system role to automate the configuration of Podman, including the deployment of containers ready for production workloads across RHEL for Edge (rpm-ostree) systems.
      Show
      .RHEL system roles adds support for RHEL for Edge `rpm-ostree` systems With this enhancement, RHEL system roles added full support to RHEL for Edge `rpm-ostree` systems. With that, you can now use RHEL system roles to automate, deploy, and manage your RHEL for Edge (rpm-ostree) systems. You can use the Podman system role to automate the configuration of Podman, including the deployment of containers ready for production workloads across RHEL for Edge (rpm-ostree) systems.
    • Proposed

      All system roles should be able to manage rpm-ostree (RHEL for Edge) systems. Roles should publish the list of packages necessary to be built into the rpm-ostree image so that the role works with the given parameters. Roles should ensure that the pkg_mgr fact is correct for rpm-ostree systems. Roles should ensure that the 'package' module works correctly with rpm-ostree systems.

            rmeggins@redhat.com Richard Megginson
            rmeggins@redhat.com Richard Megginson
            Richard Megginson Richard Megginson
            Jakub Haruda Jakub Haruda
            Eliane Pereira Eliane Pereira
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: