Feature Overview

This feature introduces a mechanism to break down the update process for RHOSO compute nodes running RHEL 9.4 into two distinct phases: updating OpenStack-related RPM packages and updating system-related RPM packages. By enabling this separation, operators gain finer control over the update process, reducing risks and simplifying troubleshooting in the event of issues.

Goals

• Who benefits from this feature? Cloud operators and administrators responsible for maintaining RHOSO compute nodes.

• How do they benefit? This feature provides:
  • Granular control over updates, enabling focused application of changes to OpenStack-related or system-related components.
  • Enhanced troubleshooting capabilities by isolating potential issues to a specific category of packages.
  • Reduced downtime and operational risks during updates.

• Difference from the current state: Currently, a single command (“dnf update all”) updates all RPM packages at once, creating challenges in identifying and mitigating issues. The current state relies on a task in the playbook that it's part of the edpm.update process:

- name: Apply packages updates
  become: true
  ansible.builtin.dnf:  # noqa: package-latest
    name: "*"
    state: latest
    update_cache: true
    exclude: "{{ _exclude_packages }}"
  tags:
    - edpm_update

With the proposed feature, updates are segmented for better manageability.

Requirements A list of specific needs or objectives that the feature must deliver.

Background, and Strategic Fit

This feature aligns with Red Hat’s focus on providing robust, enterprise-grade tools that empower operators with greater control over their environments. It supports customer demands for higher reliability and minimal disruption during updates.

Assumptions

• Prerequisites include properly tagged OpenStack and system RPM packages.

• Dependencies such as “dnf” and associated repositories are correctly configured.

Customer Considerations

• Environment Compatibility: Must work with existing RHEL 9.4 configurations and RHOSO deployments.

Documentation Considerations

• Docs Required:
  • Update the "Update guide"procedure.
  • Release notes highlighting the feature introduction.

• Key Concepts:
  • The distinction between OpenStack-related and system-related packages update.

Questions