Feature Overview

Leapp Upgrades as a self service experience will be provided at console.redhat.com as part of the Inventory management capabilities. 

Goals

For Users:  An intuitive and convenient way to perform large scale major release upgrades of RHEL (7🠆8, 8🠆9) as a hosted self-service experience with no additional infrastructure required.

For Red Hat:  As directed in the RHEL BU and Linux Platform Engineering 2022 key strategic initiatives, this feature will align with the following objectives:

• Retain RHEL renewals providing upgrades for life cycle management
• Upgrades to support workloads
• Deliver more value of subscription as services
• Grow the adoption of Insights

Supporting Materials

• Linux F2F 2Q2022 - RHEL Vision (Gunnar’s message of Services & Platform)
• Services Vision - Satellite Services vs HMS (Stef’s slides 6-12)
• Services F2F Preso March, 2022

User stories and use cases

As a current or potential enterprise customer, I have hundreds or thousands of RHEL systems that I must upgrade to a newer version of RHEL.  I need tools and automation to:

• prepare and register these systems for upgrade
• analyze and evaluate which systems are safe to proceed and which have remediation actions
• pre-built recommended remediation automation
• help me perform bulk upgrades of many systems

Requirements

A list of specific needs or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the feature shifts.  If a non MVP requirement slips, it does not shift the feature.

Insights Inventory workflow

1. MVP From the Inventory at console.redhat.com, users can initiate a pre-assessment analysis to review a system’s eligibility for upgrades
2. See Chapter 4. Reviewing the pre-upgrade report Red Hat Enterprise Linux 8 

1. MVP From the Inventory at console.redhat.com, users can review the pre-assessment report to review inhibitors and guidance on remediations.
2. MVP From the Insights Inventory, users can initiate the upgrade of a system.
3. [future feature?] From the Insights Inventory, users can apply recommended remediations as appropriate.
4. [future feature?] From the Insights Inventory, users can initiate the pre-assessment analysis of many systems.
5. [future feature?] From the Insights Inventory, users can initiate the upgrade of many systems.
6. [future feature?] Insights can proactively assess a system for upgrade eligibility.

Out of Scope

• Disconnected systems that cannot register to Insights.
• RHEL 6🠆7

Background, and strategic fit

See the strategic fit as defined in the opening Goals section, as well as the 2022 Strategic Goals and 3 Year Roadmap presentation, particularly slide 14

RHEL Leapp Upgrades tool

Existing documentation regarding how the Leapp Upgrade utility enables users to register via subscription-manager and perform the upgrades pulling content from the RH CDN.

• Upgrading from RHEL 7 to RHEL 8 Red Hat Enterprise Linux 8 
• Upgrade from Red Hat Enterprise Linux 7 to 8 with Leapp 

Bulk Upgrades with Red Hat Satellite

Integration of Leapp upgrades in Satellite has already been implemented and documented here.

• [Chapter 5. Upgrading Hosts from RHEL 7 to RHEL 8 Red Hat Satellite 6.10 | Red Hat Customer Portal|https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/managing_hosts/upgrading-hosts-from-rhel7-to-rhel8_managing-hosts]
• Enginerring demo
• 001_leapp
• https://primetime.bluejeans.com/a2m/events/playback/b15a0317-44b3-44fd-9306-f51a4c97ab84 

Screenshot of single node pre-assessment and remediation options in Web Console UI

Assumptions

• Systems must register using subscription-manager or rhc tools.
• Systems must register using insights-client

Customer Considerations

• TBD

Documentation Considerations

TBD

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

<What does success look like?>

< Does this feature have doc impact?  Possible values are: New Content, Updates to existing content,  Release Note, or No Doc Impact>

 <If unsure and no Technical Writer is available, please contact Content Strategy. If yes, complete the following.>

• <What concepts do customers need to understand to be successful in [action]?>
• <How do we expect customers will use the feature? For what purpose(s)?>
• <What reference material might a customer want/need to complete [action]?>
• <Is there source material that can be used as reference for the Technical Writer in writing the content? If yes, please link if available. >
• <What is the doc impact (New Content, Updates to existing content, or Release Note)?>

Interoperability Considerations

< Which other products and versions in our portfolio does this feature impact? >

<If other products will be impacted set the ‘LP_Interop’ label on the Feature>

< What interoperability test scenarios should be factored by the layered product(s)? >

SMEs & Stakeholders

Questions