Latest revision as of 15:30, 14 October 2024

PyTorch 2.4

Summary

PyTorch is a popular python library for deep learning using GPUs and CPUs. It is frequently associated with various AI implementations and other neural network based projects. This change will update PyTorch to the latest upstream version (2.4).

Owner

Name: Tom Rix
Email: trix@redhat.com

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-10-14
Announced
Discussion thread
FESCo issue: #3257
Tracker bug: #2304171
Release notes tracker: #115

Detailed Description

Update the base Fedora PyTorch from 2.2 to the latest upstream 2.4. The big change for 2.4 is the integration with the ROCm stack to provide open accelerated AI on AMD GPU's.

Feedback

Benefit to Fedora

Fedora AI is keeping pace with the fast moving AI by updating PyTorch to match what is available *right now* in the upsteam with features needed to do real AI development for open source.

Scope

Proposal owners: Update base to 2.4 when upstream releases.

Other developers:

Release engineering: N/A (not needed for this Change)

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with the Fedora Strategy: "Innovation & Leadership in Technology: We integrate programming language stack ecosystems" by including the latest release of PyTorch, Fedora will have the latest release of a popular software stack in AI/ML.

Upgrade/compatibility impact

There should be no backwards incompatible changes with the 2.4 release.

Early Testing (Optional)

Do you require 'QA Blueprint' support? N

How To Test

Testing can be done with CPU only but that may lead to very long test times. Testing with ROCm compatible hardware is recommended.

Running through some of the PyTorch Examples is a good way for basic testing of PyTorch. Running through the tests contained in other torch-related packages (e.g python-torchvision) could also be helpful.

User Experience

Users will be able to continue to use PyTorch installed from the Fedora repos - the upgrades to llvm require a newer ROCm and that newer ROCm is only supported by the latest PyTorch release.

Other than being able to continue to use PyTorch from the Fedora repos, the user-noticeable changes will be minimal.

Dependencies

There are no RPMs affected by this change that are not included in the change.

Contingency Plan

Fedora currently ships with the latest public 2.3 release with all of the accelerated features.

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
Contingency deadline: N/A (not a System Wide Change)
Blocks release? No, not a System Wide Change.

Documentation

N/A (not a System Wide Change)

Release Notes

@@ Line 1: / Line 1: @@
-{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.<br/> '''Copy the source to a ''new page'' before making changes!  DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.'''}}
+= PyTorch 2.4 =
-{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ documentation].}}
-{{admon/tip | Report issues | To report an issue with this template, file an issue in the [https://pagure.io/fedora-pgm/pgm_docs pgm_docs repo].}}
-<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-= Change Proposal Name <!-- The name of your change proposal --> = PyTorch 2.4
-{{Change_Proposal_Banner}}
 == Summary ==
-Update PyTorch to the latest upstream version 2.4
+PyTorch is a popular python library for deep learning using GPUs and CPUs. It is frequently associated with various AI implementations and other neural network based projects. This change will update PyTorch to the latest upstream version (2.4).
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
@@ Line 29: / Line 19: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF41]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 47: / Line 37: @@
 ON_QA -> change is fully code complete
 -->
-* [Announced]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/5LTWELNZN376VYFTGLDFANG5LRNSNPP5/ Announced]
-* [<will be assigned by the Wrangler> Discussion thread]
+* [https://discussion.fedoraproject.org/t/f41-change-proposal-pytorch-2-4-self-contained/126069 Discussion thread]
-* FESCo issue: <will be assigned by the Wrangler>
+* FESCo issue: [https://pagure.io/fesco/issue/3257 #3257]
-* Tracker bug: <will be assigned by the Wrangler>
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2304171 #2304171]
-* Release notes tracker: <will be assigned by the Wrangler>
+* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/115 #115]
 == Detailed Description ==
 <!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 Update the base Fedora PyTorch from 2.2 to the latest upstream 2.4.  The big change for 2.4 is the integration with the ROCm stack to provide open accelerated AI on AMD GPU's.
 == Feedback ==
 <!-- Summarize the feedback from the community and address why you chose not to accept proposed alternatives. This section is optional for all change proposals but is strongly suggested. Incorporating feedback here as it is raised gives FESCo a clearer view of your proposal and leaves a good record for the future. If you get no feedback, that is useful to note in this section as well. For innovative or possibly controversial ideas, consider collecting feedback before you file the change proposal. -->
 == Benefit to Fedora ==
-Fedora AI is keeping pace with the fast moving AI by updating PyTorch to match what is evaluable *right now* in the upsteam with features needed to do real AI development for open source.
+Fedora AI is keeping pace with the fast moving AI by updating PyTorch to match what is available *right now* in the upsteam with features needed to do real AI development for open source.
 <!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
@@ Line 90: / Line 81: @@
 == Scope ==
-* Proposal owners:
+* Proposal owners: Update base to 2.4 when upstream releases.
-Update base to 2.4 when upstream releases.
 <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
@@ Line 97: / Line 87: @@
 <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: [https://pagure.io/releng/issues #Releng issue number] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 107: / Line 97: @@
 <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
-* Alignment with the Fedora Strategy:
+* Alignment with the Fedora Strategy: "Innovation & Leadership in Technology: We integrate programming language stack ecosystems" by including the latest release of PyTorch, Fedora will have the latest release of a popular software stack in AI/ML.
 <!-- Does your proposal align with the current Fedora Strategy: https://discussion.fedoraproject.org/t/fedora-strategy-2028-february-march-planning-work-and-roadmap-til-flock/43618 ? It's okay if it doesn't, but it's something to consider -->
@@ Line 113: / Line 103: @@
 <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+There should be no backwards incompatible changes with the 2.4 release.
 == Early Testing (Optional) ==
 <!-- This is an optional step for system-wide changes to avail of. If you would like to build an initial proof of concept of your change and have a member of Fedora QA help you write and/or run some initial basic tests on your code, please email tests@fedoraproject.org and include the link to your change proposal. This step is *optional*. -->
-Do you require 'QA Blueprint' support? Y/N <!-- Optional Step for System-Wide Changes only -->
+Do you require 'QA Blueprint' support? N <!-- Optional Step for System-Wide Changes only -->
 == How To Test ==
-Requires AMD GPU
+Testing can be done with CPU only but that may lead to very long test times. Testing with ROCm compatible hardware is recommended.
-Run the PyTorch examples and other package ex/ python-torchvision unit tests.
+Running through some of the PyTorch Examples is a good way for basic testing of PyTorch. Running through the tests contained in other torch-related packages (e.g python-torchvision) could also be helpful.
 <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  This can be based off of the above section if early testing has been completed. If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
@@ Line 151: / Line 142: @@
   - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
 -->
+Users will be able to continue to use PyTorch installed from the Fedora repos - the upgrades to llvm require a newer ROCm and that newer ROCm is only supported by the latest PyTorch release.
+Other than being able to continue to use PyTorch from the Fedora repos, the user-noticeable changes will be minimal.
 == Dependencies ==
@@ Line 156: / Line 151: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+There are no RPMs affected by this change that are not included in the change.
 == Contingency Plan ==
@@ Line 165: / Line 160: @@
 * Contingency deadline: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
-* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Blocks release? No, not a System Wide Change.<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Search

Changes/PyTorch2.4: Difference between revisions