Sle16 upgrade jsc#docteam 1888 #572
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| # This file originates from the project https://github.com/openSUSE/doc-kit | ||
| # This file can be edited downstream. | ||
|
|
||
| MAIN="sle16-upgrade.asm.xml" | ||
| SRC_DIR="articles" | ||
| IMG_SRC_DIR="images" | ||
|
|
||
| ## Profiling | ||
| PROFOS="sles4sap" | ||
| #PROFCONDITION="16.0" | ||
| # Use the STRUCTID if there are several structures in one assembly file | ||
| #STRUCTID="STRUCTURE-ID" | ||
| #PROFARCH="x86_64;zseries;power;aarch64" | ||
|
|
||
| DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" | ||
|
|
||
| STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" | ||
| FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,18 @@ | ||
| # This file originates from the project https://github.com/openSUSE/doc-kit | ||
| # This file can be edited downstream. | ||
|
|
||
| MAIN="sle16-upgrade.asm.xml" | ||
| SRC_DIR="articles" | ||
| IMG_SRC_DIR="images" | ||
|
|
||
| ## Profiling | ||
| PROFOS="sles" | ||
| #PROFCONDITION="16.0" | ||
| # Use the STRUCTID if there are several structures in one assembly file | ||
| #STRUCTID="STRUCTURE-ID" | ||
| #PROFARCH="x86_64;zseries;power;aarch64" | ||
|
|
||
| DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" | ||
|
|
||
| STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" | ||
| FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse-ns" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,226 @@ | ||
| <?xml version="1.0" encoding="UTF-8" standalone="no"?> | ||
| <!-- This file originates from the project https://github.com/openSUSE/doc-kit --> | ||
| <!-- This file can be edited downstream. --> | ||
| <!DOCTYPE assembly | ||
| [ | ||
| <!ENTITY % entities SYSTEM "../common/generic-entities.ent"> | ||
| <!ENTITY dms "Distribution Migration System"> | ||
| <!ENTITY dmsa "DMS"> | ||
| %entities; | ||
| ]> | ||
| <!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> --> | ||
| <!-- point back to this document with a similar comment added to your legacy doc piece --> | ||
| <!-- refer to README.md for file and id naming conventions --> | ||
| <assembly version="5.2" xml:lang="en" | ||
| xmlns:xlink="http://www.w3.org/1999/xlink" | ||
| xmlns:trans="http://docbook.org/ns/transclusion" | ||
| xmlns:its="http://www.w3.org/2005/11/its" | ||
| xmlns:xi="http://www.w3.org/2001/XInclude" | ||
| xmlns="http://docbook.org/ns/docbook"> | ||
| <!-- resources section references all topic chunks used in the final article | ||
| --> | ||
| <!-- R E S O U R C E S --> | ||
| <resources> | ||
| <!-- Glue files --> | ||
| <!-- | ||
| <resource xml:id="_glue-sle16-upgrade" href="../glues/sle16-upgrade.xml"> | ||
| <description>Glue about upgrade vs. fresh install</description> | ||
| </resource> | ||
| --> | ||
| <resource xml:id="_glue-sle16-upgrade-more-info" href="../glues/sle16-upgrade-more-info.xml"> | ||
| <description>SLE 16 upgrade more information (Link to DMS docs)</description> | ||
| </resource> | ||
| <!-- | ||
| <resource xml:id="_glue-sle16-upgrade-whats-next" href="../glues/sle16-upgrade-whats-next.xml"> | ||
| <description>Glue what's next</description> | ||
| </resource> | ||
| --> | ||
| <!-- Concept files --> | ||
| <resource xml:id="_concept-sle16-upgrade-lifecycle-support" href="../concepts/sle16-upgrade-lifecycle.xml"> | ||
| <description>SLE 16 lifecycle and upgrade paths.</description> | ||
| </resource> | ||
| <resource xml:id="_concept-sle16-upgrade-distribution-migration-system" href="../concepts/sle16-upgrade-dms.xml"> | ||
| <description>Conceptual overview of the distribution migration system</description> | ||
| </resource> | ||
| <!-- Tasks --> | ||
| <!-- This is largely based on sle_update_preperation.xml from SLE 15 --> | ||
| <resource xml:id="_task-sle16-upgrade-prepare" href="../tasks/sle16-upgrade-prepare.xml"> | ||
| <description>Preparing the upgrade</description> | ||
| </resource> | ||
| <resource xml:id="_task-sle16-upgrade" href="../tasks/sle16-upgrade.xml"> | ||
| <description>The actual DMS upgrade</description> | ||
| </resource> | ||
| <resource xml:id="_task-sle16-upgrade-finish" href="../tasks/sle16-upgrade-finish.xml"> | ||
| <description>Finishing the upgrade</description> | ||
| </resource> | ||
| <!-- References --> | ||
| <!-- | ||
| <resource xml:id="_reference-example" href="../references/reference.xml"> | ||
| <description>Reference example</description> | ||
| </resource> | ||
| --> | ||
| <!-- Legal --> | ||
| <resource href="../common/legal.xml" xml:id="_legal"> | ||
| <description>Legal Notice</description> | ||
| </resource> | ||
| <resource href="../common/license_gfdl1.2.xml" xml:id="_gfdl"> | ||
| <description>GNU Free Documentation License</description> | ||
| </resource> | ||
| </resources> | ||
| <!-- S T R U C T U R E --> | ||
| <structure renderas="article" xml:id="article-example" xml:lang="en"> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <merge> | ||
| <title>Upgrading to &productname; 16</title> | ||
| <!-- Create revision history to enable versioning: adjust the placeholder revhistory ID, | ||
| for each entry add the date of when the updated article will be published, | ||
| list most recent date/entry at the top --> | ||
| <!-- Check https://documentation.suse.com/style/current/single-html/docu_styleguide/#sec-revhistory for detailed instructions--> | ||
| <revhistory xml:id="rh-USE-ROOT-ID"> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <revision><date>2025-10-24</date> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <revdescription> | ||
| <para> | ||
| Updated for the initial release of &productname; &productnumber; | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| </para> | ||
| </revdescription> | ||
| </revision> | ||
| <revision><date>2025-10-16</date> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| <revdescription> | ||
| <para> | ||
| Initial draft version | ||
| </para> | ||
| </revdescription> | ||
| </revision> | ||
| </revhistory> | ||
| <!-- TODO: provide a listing of possible and validatable meta entry values. Maybe in our geekodoc repo? --> | ||
| <!-- add author's e-mail --> | ||
| <meta name="maintainer" content="[email protected]" its:translate="no"/> | ||
| <meta name="architecture"> | ||
| <phrase>&x86-64;</phrase> | ||
| <phrase>&power;</phrase> | ||
| </meta> | ||
| <!-- enter one or more product names and version --> | ||
| <meta name="productname" its:translate="no"> | ||
| <productname version="16.0">&productname;</productname> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| </meta> | ||
| <meta name="title" its:translate="yes">Upgrading to &productname; 16</meta> | ||
| <meta name="description" its:translate="yes">How to upgrade to &productname; 16</meta> | ||
| <meta name="social-descr" its:translate="yes">Upgrade to &productname; 16</meta> | ||
| <!-- suitable categories has to be identical with the category selected in the docserv config --> | ||
| <!-- Only used for Best practices ATM--> | ||
| <!-- | ||
| <meta name="category" its:translate="no"> | ||
| <phrase>Systems Management</phrase> | ||
| </meta> | ||
| --> | ||
| <!-- Determines "filter by task" filter value --> | ||
| <!-- either add link to list or list of tasks--> | ||
| <meta name="task" its:translate="no"> | ||
| <phrase>Upgrade & Update</phrase> | ||
| </meta> | ||
| <meta name="series" its:translate="no">Products & Solutions</meta> | ||
| <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager"> | ||
| <dm:bugtracker> | ||
| <dm:url>https://bugzilla.suse.com/enter_bug.cgi</dm:url> | ||
| <dm:component>Documentation</dm:component> | ||
| <dm:product><!--Bugzilla product string--> | ||
| <dm:product os="sles" condition="16.0">SUSE Linux Enterprise Server 16.0</dm:product> | ||
| <dm:product os="sles4sap" condition="16.0">SUSE Linux Enterprise Server for SAP Applications 16.0</dm:product> | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| </dm:product> | ||
| <dm:assignee>[email protected]</dm:assignee> | ||
| </dm:bugtracker> | ||
| <dm:translation>yes</dm:translation> | ||
| </dm:docmanager> | ||
| <abstract> | ||
| <variablelist> | ||
| <varlistentry> | ||
| <term>WHAT?</term> | ||
| <listitem> | ||
| <para> | ||
| This article describes the upgrade to &productname; &productnumber;. | ||
| </para> | ||
| </listitem> | ||
| </varlistentry> | ||
| <varlistentry> | ||
| <term>WHY?</term> | ||
| <listitem> | ||
| <para> | ||
| Learn how to upgrade to &productname; &productnumber;. | ||
| </para> | ||
| </listitem> | ||
| </varlistentry> | ||
| <varlistentry> | ||
| <term>EFFORT</term> | ||
| <listitem> | ||
| <para> | ||
| 15 Minutes of reading. The time of the upgrade itself depends on the size of the | ||
| installation, the speed of the system and your internet connection. | ||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
| </para> | ||
| </listitem> | ||
| </varlistentry> | ||
| <varlistentry> | ||
| <term>GOAL</term> | ||
| <listitem> | ||
| <para> | ||
| Learn how to upgrade a system from &productnameshort; 15 to &productnumber;. | ||
| </para> | ||
| </listitem> | ||
| </varlistentry> | ||
| <varlistentry> | ||
| <term>REQUIREMENTS</term> | ||
| <listitem> | ||
| <itemizedlist> | ||
| <listitem> | ||
| <para> | ||
| A system with &productname; 15 SP7. Upgrades from other &productnameshort; | ||
| versions are not supported for &productnameshort; 16.0. | ||
| </para> | ||
| </listitem> | ||
| <listitem> | ||
| <para> | ||
| The system must be registered in order to access the package repositories. | ||
| </para> | ||
| </listitem> | ||
| </itemizedlist> | ||
| </listitem> | ||
| </varlistentry> | ||
| </variablelist> | ||
| </abstract> | ||
| </merge> | ||
| <!-- pull in all the topic files you need --> | ||
| <!-- pick the appropriate type of include to match your needs --> | ||
| <!-- pull in a topic as is --> | ||
| <!-- <module resourceref="_glue-sle16-upgrade" renderas="section"/> --> | ||
| <!-- pull in a topic and switch the title --> | ||
| <module resourceref="_concept-sle16-upgrade-lifecycle-support" renderas="section"> | ||
| <merge> | ||
| <title>Lifecycle and upgrade paths</title> | ||
| </merge> | ||
| </module> | ||
| <module resourceref="_concept-sle16-upgrade-distribution-migration-system" renderas="section"> | ||
|
|
||
| </module> | ||
| <module resourceref="_task-sle16-upgrade-prepare" renderas="section"> | ||
| <merge> | ||
| <title>Preparing the upgrade</title> | ||
| </merge> | ||
| </module> | ||
| <module resourceref="_task-sle16-upgrade" renderas="section"> | ||
| <merge> | ||
| <title>Performing the upgrade</title> | ||
| </merge> | ||
| </module> | ||
| <module resourceref="_task-sle16-upgrade-finish" renderas="section"> | ||
| <merge> | ||
| <title>Finishing the upgrade</title> | ||
| </merge> | ||
| </module> | ||
| <!-- <module resourceref="_reference-example" renderas="section"/> --> | ||
| <module resourceref="_glue-sle16-upgrade-more-info" renderas="section"/> | ||
| <!-- <module resourceref="_glue-sle16-upgrade-whats-next" renderas="section"/> --> | ||
| <module resourceref="_legal"/> | ||
| <module resourceref="_gfdl"> | ||
| <output renderas="appendix"/> | ||
| </module> | ||
| </structure> | ||
| <!-- TODO: second structure! --> | ||
| </assembly> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,119 @@ | ||||||||||||||
| <?xml version="1.0" encoding="UTF-8"?> | ||||||||||||||
| <!-- This file originates from the project https://github.com/openSUSE/doc-kit --> | ||||||||||||||
| <!-- This file can be edited downstream. --> | ||||||||||||||
| <!DOCTYPE topic | ||||||||||||||
| [ | ||||||||||||||
| <!ENTITY % entities SYSTEM "../common/generic-entities.ent"> | ||||||||||||||
| %entities; | ||||||||||||||
| ]> | ||||||||||||||
| <!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> --> | ||||||||||||||
| <!-- point back to this document with a similar comment added to your legacy doc piece --> | ||||||||||||||
| <!-- refer to README.md for file and id naming conventions --> | ||||||||||||||
| <!-- metadata is dealt with on the assembly level --> | ||||||||||||||
| <topic xml:id="concept-sle16-upgrade-upgrade-distribution-migration-systemt" | ||||||||||||||
| role="concept" xml:lang="en" | ||||||||||||||
| xmlns="http://docbook.org/ns/docbook" version="5.2" | ||||||||||||||
| xmlns:its="http://www.w3.org/2005/11/its" | ||||||||||||||
| xmlns:xi="http://www.w3.org/2001/XInclude" | ||||||||||||||
| xmlns:xlink="http://www.w3.org/1999/xlink" | ||||||||||||||
| xmlns:trans="http://docbook.org/ns/transclusion"> | ||||||||||||||
| <info> | ||||||||||||||
| <!-- can be changed via merge in the assembly --> | ||||||||||||||
| <title>Distribution migration system</title> | ||||||||||||||
| <!--add author's email address--> | ||||||||||||||
| <meta name="maintainer" content="[email protected]" its:translate="no"/> | ||||||||||||||
| <!-- can be changed via merge in the assembly --> | ||||||||||||||
| <abstract> | ||||||||||||||
| <para> | ||||||||||||||
| The distribution migration system provides an upgrade path for an installed &productname; | ||||||||||||||
| system from one major version to another, for example, from &productnameshort; 15 SP7 to | ||||||||||||||
| &productnameshort; 16.0. | ||||||||||||||
| </para> | ||||||||||||||
| </abstract> | ||||||||||||||
| </info> | ||||||||||||||
| <section xml:id="concept-sle16-upgrade-distribution-migration-systemt"> | ||||||||||||||
| <title>Concept</title> | ||||||||||||||
| <para> | ||||||||||||||
| While previous versions of &productname; were upgraded from the @leanos;, &productnameshort; | ||||||||||||||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||
| 16 is uses the distribution migration system. This upgrade is done via the network using the &zypper; migration | ||||||||||||||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||
| workflow, which sends a request to the repository server, asking for an upgrade path. | ||||||||||||||
| Supported repository servers are the &scc; (SCC) and repository mirroring tool (&rmt;). The | ||||||||||||||
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||||||||||||||
| request response contains the list of repositories required to upgrade the system. This | ||||||||||||||
| requires the system to be upgraded to be registered. Additionally, the server providing the | ||||||||||||||
| updates must have the necessary channels available and those channels must be up to date. | ||||||||||||||
|
||||||||||||||
| request response contains the list of repositories required to upgrade the system. This | |
| requires the system to be upgraded to be registered. Additionally, the server providing the | |
| updates must have the necessary channels available and those channels must be up to date. | |
| request response contains the list of repositories required to upgrade the system. The | |
| system must be upgraded to be registered. Additionally, the server providing the | |
| updates must have the required channels available and up to date. |
There was a problem hiding this comment.
No, exactly the opposite. The system doesn't have to be upgraded in order to register but it has to be registered in order to get upgraded with this procedure.
There was a problem hiding this comment.
Clarified: "This requires the system to be registered before the upgrade."
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
cwickert marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.