Skip to content

Commit

Permalink
xmlformat.
Browse files Browse the repository at this point in the history
  • Loading branch information
@lvicoun
lvicoun committed Nov 11, 2022
1 parent f94dc44 commit e2861e0
Showing 1 changed file with 122 additions and 112 deletions.
234 changes: 122 additions & 112 deletions xml/slemicro_update_procedure.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,82 +7,87 @@
<chapter version="5.0" xml:id="cha-upgrade-procedure-slemicro"
xmlns="http://docbook.org/ns/docbook"
xmlns:xi="http://www.w3.org/2001/XInclude"
xmlns:xlink="http://www.w3.org/1999/xlink">
xmlns:xlink="http://www.w3.org/1999/xlink">
<title>Upgrading the system</title>
<info>
<dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">
<dm:bugtracker></dm:bugtracker>
<dm:translation>yes</dm:translation>
</dm:docmanager>
<abstract>
<para>
SUSE offers a command-line tool to upgrade a running system to a new version. The tool provides support for “rollback” to an older release. This chapter explains how to upgrade your system step by step.
<para>
SUSE offers a command-line tool to upgrade a running system to a new
version. The tool provides support for “rollback” to an older release. This
chapter explains how to upgrade your system step by step.
</para>
</abstract>
</info>

</abstract>
</info>
<para>
&suse; releases new version of &slema; at regular intervals. To make it easy
for customers to migrate to a new minor version and minimize downtime,
&suse; supports migrating online while the system is running.
</para>

<para>
&slema; uses <emphasis>transactional updates</emphasis> to upgrade from one
version to the next. This has the following advantages:
</para>

<itemizedlist>
<listitem>
<para>
The system is always in a defined state until the first RPM is updated.
</para>
</listitem>
<listitem>
<para>
Canceling is possible until the first RPM is updated.
</para>
</listitem>
<listitem>
<para>
Simple recovery if there is an error.
</para>
</listitem>
<listitem>
<para>
It is possible to do a <quote>rollback</quote> via system tools&mdash;no
backup or restore needed.
</para>
</listitem>
<listitem>
<para>
Use of all active repositories.
</para>
</listitem>
</itemizedlist>

<sect1 xml:id="sec-run-transactional-update">
&suse; releases new version of &slema; at regular intervals. To make it easy
for customers to migrate to a new minor version and minimize downtime, &suse;
supports migrating online while the system is running.
</para>
<para>
&slema; uses <emphasis>transactional updates</emphasis> to upgrade from one
version to the next. This has the following advantages:
</para>
<itemizedlist>
<listitem>
<para>
The system is always in a defined state until the first RPM is updated.
</para>
</listitem>
<listitem>
<para>
Canceling is possible until the first RPM is updated.
</para>
</listitem>
<listitem>
<para>
Simple recovery if there is an error.
</para>
</listitem>
<listitem>
<para>
It is possible to do a <quote>rollback</quote> via system tools&mdash;no
backup or restore needed.
</para>
</listitem>
<listitem>
<para>
Use of all active repositories.
</para>
</listitem>
</itemizedlist>
<sect1 xml:id="sec-run-transactional-update">
<title>Upgrading to a new release</title>


<important>
<title>Upgrading to a new release and <command>wicked</command></title>
<para>
&slema; 5.3 introduced NetworkManager as the default tool to manage networking. However, when you perform an upgrade from previous releases, the default network framework remains <command>wicked</command>. Automated migration from <command>wicked</command> to &nm; or the migration of the <command>wicked</command> configuration is not supported. However, you can switch from <command>wicked</command> to &nm; as desribed in <xref linkend="proc-wicked-switch"/>.
</para>
</important>
<important>
<title>Upgrading to a new release and <command>wicked</command></title>
<para>
&slema; 5.3 introduced NetworkManager as the default tool to manage
networking. However, when you perform an upgrade from previous releases,
the default network framework remains <command>wicked</command>. Automated
migration from <command>wicked</command> to &nm; or the migration of the
<command>wicked</command> configuration is not supported. However, you can
switch from <command>wicked</command> to &nm; as desribed in
<xref linkend="proc-wicked-switch"/>.
</para>
</important>

<note>
<title>&suse; Linux Enterprise Live Patching</title>
<para>
If you have the &suse; Linux Enterprise Live Patching extension enabled, the extension is not affected during the upgrade procedure.
If you have the &suse; Linux Enterprise Live Patching extension enabled,
the extension is not affected during the upgrade procedure.
</para>
</note>

<para>
If your system is registered with the &scc;, make sure
to have an Internet connection during the following procedure:
If your system is registered with the &scc;, make sure to have an Internet
connection during the following procedure:
</para>

<procedure xml:id="proc-upgrade-registered">
<title>Upgrade to a newer version</title>
<step>
Expand Down Expand Up @@ -124,69 +129,75 @@
</procedure>

<para>
If your system is not registered, proceed as follows:
If your system is not registered, proceed as follows:
</para>

<procedure xml:id="proc-unregistered-upgrade">
<title>Upgrading an unregistered system</title>
<step>
<para>Change the URL of the update
repositories to point to the &productnumber;. </para>
</step>
<step>
<para>
Run the following command:
</para>
<screen>&prompt.root;transactional-update dup</screen>
</step>
<title>Upgrading an unregistered system</title>
<step>
<para>
Change the URL of the update repositories to point to the &productnumber;.
</para>
</step>
<step>
<para>
Run the following command:
</para>
<screen>&prompt.root;transactional-update dup</screen>
</step>
</procedure>

<para>
After you complete the upgrade procedure, if needed, you can to switch from <command>wicked</command> to &nm; without performing a fresh installation. To do so, proceed as follows:
After you complete the upgrade procedure, if needed, you can to switch from
<command>wicked</command> to &nm; without performing a fresh installation.
To do so, proceed as follows:
</para>
<procedure xml:id="proc-wicked-switch">
<title>Switching from <command>wicked</command> to &nm;</title>
<step>
<para>
Run the following command to create a new snapshot where you perform all other changes to the system:
</para>
<screen>&prompt.root;transactional-update shell</screen>
</step>
<step>
<para>
Install &nm;:
</para>
<screen>&prompt.root;zypper in NetworkManager</screen>
</step>
<step>
<para>
Remove <command>wicked</command> from the system:
</para>
<screen>&prompt.root;zypper rm wicked-service</screen>
</step>
<step>
<para>
Enable the &nm; service:
</para>
<screen>&prompt.root;systemctl enable NetworkManager</screen>

</step>
<step>
<para>If needed, configure the service according to your needs.</para>
</step>
<step>
<para>
Close the <command>transactonal-update</command> shell:
</para>
<screen>&prompt.root;exit</screen>
</step>
<step>
<para>
Reboot your system to switch to the new snapshot.
</para>
</step>
<procedure xml:id="proc-wicked-switch">
<title>Switching from <command>wicked</command> to &nm;</title>
<step>
<para>
Run the following command to create a new snapshot where you perform all
other changes to the system:
</para>
<screen>&prompt.root;transactional-update shell</screen>
</step>
<step>
<para>
Install &nm;:
</para>
<screen>&prompt.root;zypper in NetworkManager</screen>
</step>
<step>
<para>
Remove <command>wicked</command> from the system:
</para>
<screen>&prompt.root;zypper rm wicked-service</screen>
</step>
<step>
<para>
Enable the &nm; service:
</para>
<screen>&prompt.root;systemctl enable NetworkManager</screen>
</step>
<step>
<para>
If needed, configure the service according to your needs.
</para>
</step>
<step>
<para>
Close the <command>transactonal-update</command> shell:
</para>
<screen>&prompt.root;exit</screen>
</step>
<step>
<para>
Reboot your system to switch to the new snapshot.
</para>
</step>
</procedure>
</sect1>

<sect1 xml:id="sec-upgrade-cancel-slemicro">
<title>Reverting the migration process</title>

Expand All @@ -201,5 +212,4 @@
<xref linkend="sec-rollback-procedure"/>.
</para>
</sect1>

</chapter>

0 comments on commit e2861e0

Please sign in to comment.