diff --git a/DC-quickstart-smt b/DC-quickstart-smt new file mode 100644 index 0000000..246aa9a --- /dev/null +++ b/DC-quickstart-smt @@ -0,0 +1,12 @@ +# +# DC file for SUSE Liberty Linux with SMT +# +MAIN="art-quickstart-smt.xml" +ROOTID="art-quickstart-smt" + +PROFCONDITION="suse-product" +#PROFCONDITION="suse-product;beta" +#PROFCONDITION="community-project" + +STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" +FALLBACK_STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2021-ns" diff --git a/xml/art-quickstart-smt.xml b/xml/art-quickstart-smt.xml new file mode 100644 index 0000000..9f75d58 --- /dev/null +++ b/xml/art-quickstart-smt.xml @@ -0,0 +1,244 @@ + + + + %entities; +]> + +
+ + + Registering &rhla; &productnumber; or CentOS Linux &productnumber; with ⪪ + &productname; + &productnameshort; + + + + + This guide describes how to use &productname; to update &rhel; &productnumber; + or CentOS Linux &productnumber;. + + + + + https://github.com/SUSE/doc-liberty/issues/new + documentation,issue + 7 + tahliar + + https://github.com/SUSE/doc-liberty/edit/maintenance/SLL7/xml/ + no + + + +
+ Introduction + + &productname; is a technology and support solution for mixed Linux environments. + With a &productname; subscription, you can register and receive updates for + &rhel;, CentOS Linux, and &sles;. An optional &ha; extension is also available. + + + + CentOS Stream is not supported. + + + + You can register &rhla; &productnumber; or CentOS Linux &productnumber; with one of the + following tools: + + + + + &smtool; (⪪) on &sle; 12 + + + + + &rmtool; (&rmt;) on &sle; 15 + + + + + &suma; + + + + + This guide describes how to register with ⪪ on &sle; 12. ⪪ is a proxy system for the + &scc;. The ⪪ server is registered with the &scc;, and other systems in the network are + registered with the ⪪ server and receive packages from it directly. + + + Procedure overview + + + . Make sure you have everything + required for the following procedures. + + + + + . This server must be installed on + &sles; 12. You can skip this step if you already have an ⪪ server in + your network. + + + + + . You can skip this step if + &productname; is already enabled and mirrored on your ⪪ server. + + + + + . + + + + + + <emphasis>&productname;</emphasis> and <emphasis>&sles; with Expanded Support</emphasis> + + &productname; now provides what used to be covered by + the &sles; with Expanded Support subscription. Some + components might still use the Expanded Support name + during the transition period. + + + + Related information + + + + &smtool; Guide + + + + + + Registering &rhla; 7 or CentOS Linux 7 with RMT + + + + + + Registering &rhla; 8 or CentOS Linux 8 with RMT + + + + + + Registering &rhla; 9 with RMT + + + + + + &suma; Client Configuration Guide: Registering &sliberty; Clients + + + +
+ +
+ Requirements + + + + You have a &productname; subscription. + + + + + You have a &scc; account. + + + + + The systems you want to register are up to date. &productname; only + supports the latest minor release of each &rhla; or CentOS Linux version. + + + + + &sles; (&slsa;) 12 is installed and running in the same network as the + systems you want to register. You can use the &productname; subscription to + register &slsa;. To install &slsa; 12, see + + &instquick;. + + + + + &sles; has enough storage available for repository mirroring. + Downloaded packages are stored in /srv/www/htdocs/repo. + The amount of storage required depends on the number of repositories you mirror. + We recommend at least 1.5 times the total size of all enabled repositories. + Be aware that these repositories will grow substantially over time. + + + +
+ + + + + + + +
+ Troubleshooting + + + Mirroring completes with errors + + + If some packages could not be downloaded because of timeouts, rerun the + smt-mirror command until all packages are downloaded. + + + + + Cannot access the &productname; repository + + + The repodata directory on the ⪪ server will not + be available until all of the packages for that repository are downloaded. + If some packages could not be downloaded to the ⪪ server because of + timeouts during the first mirroring, rerun the smt-mirror + command until all packages are downloaded. + + + + + yum update fails because of package conflicts + + + If sles_es-release-server conflicts with existing packages, + try the following workaround: + +&prompt.root;rm -r /usr/share/redhat-release + + On CentOS, this removes the symbolic link between + redhat-release and centos-release. + + + + Make sure you run this command without a / + after redhat-release. + + + + + +
+ +
diff --git a/xml/art-quickstart.xml b/xml/art-quickstart.xml index dd786a6..e1a85fc 100644 --- a/xml/art-quickstart.xml +++ b/xml/art-quickstart.xml @@ -15,7 +15,7 @@ xmlns:xlink="http://www.w3.org/1999/xlink"> - Registering &rhla; &productnumber; or CentOS Linux &productnumber; + Registering &rhla; &productnumber; or CentOS Linux &productnumber; with &rmt; &productname; &productnameshort; @@ -51,20 +51,33 @@ - To register &rhla; &productnumber; or CentOS Linux &productnumber;, use &suse;'s - &smtool; (⪪) for &sle; 12. ⪪ is a proxy system for the &scc;. The ⪪ - server is registered with the &scc;, and other systems in the network are - registered with the ⪪ server and receive packages from it directly. + You can register &rhla; &productnumber; or CentOS Linux &productnumber; with one of the + following tools: - - - The &rmtool; (&rmt;) for &sle; 15 does not support &rhla;/CentOS &productnumber; registration. - - + + + + &smtool; (⪪) on &sle; 12 + + + + + &rmtool; (&rmt;) on &sle; 15 + + + + + &suma; + + + - Registering &rhla; or CentOS Linux with ⪪ involves the following steps: + This guide describes how to register with &rmt; on &sle; 15. &rmt; is a proxy system for the + &scc;. The &rmt; server is registered with the &scc;, and other systems in the network are + registered with the &rmt; server and receive packages from it directly. + Procedure overview . Make sure you have everything @@ -73,20 +86,20 @@ - . This server must be installed on - &sles; 12. You can skip this step if you already have an ⪪ server in + . This server must be installed on + &sles; 15. You can skip this step if you already have an &rmt; server in your network. - . You can skip this step if - &productname; is already enabled and mirrored on your ⪪ server. + . You can skip this step if + &productname; is already enabled and mirrored on your &rmt; server. - . + . @@ -104,22 +117,34 @@ Related information - - &smtool; Guide + + &rmtguide; + + + + + + Registering &rhla; 7 or CentOS Linux 7 with SMT - Registering &rhla; 8 or CentOS Linux 8 + Registering &rhla; 8 or CentOS Linux 8 with RMT - Registering &rhla; 9 + Registering &rhla; 9 with RMT + + + + &suma; Client Configuration Guide: Registering &sliberty; Clients + + @@ -144,10 +169,10 @@ - &sles; (&slsa;) 12 is installed and running in the same network as the + &sles; (&slsa;) 15 is installed and running in the same network as the systems you want to register. You can use the &productname; subscription to - register &slsa;. To install &slsa; 12, see - + register &slsa;. To install &slsa; 15, see + &instquick;. @@ -163,56 +188,91 @@ - + - + - +
Troubleshooting - - Mirroring completes with errors - - - If some packages could not be downloaded because of timeouts, rerun the - smt-mirror command until all packages are downloaded. - - - - - Cannot access the &productname; repository - - - The repodata directory on the ⪪ server will not - be available until all of the packages for that repository are downloaded. - If some packages could not be downloaded to the ⪪ server because of - timeouts during the first mirroring, rerun the smt-mirror - command until all packages are downloaded. - - - - - yum update fails because of package conflicts - - - If sles_es-release-server conflicts with existing packages, - try the following workaround: - -&prompt.root;rm -r /usr/share/redhat-release - - On CentOS, this removes the symbolic link between - redhat-release and centos-release. - - + + nginx.service is inactive after installing the + rmt-server package + - Make sure you run this command without a / - after redhat-release. + Continue the procedure to configure &rmt; in &yast;. This often resolves + the issue. If that fails, Apache might be installed on your server, and + must be disabled. Apache conflicts with NGINX because both web servers + listen on port 80. - - - + + + + &productname; doesn't appear in rmt-cli products list + after rmt-cli sync + + + Check your network. If the network is down, rmt-cli sync fails without + showing an error. + + + + + Mirroring completes with errors + + + If some packages could not be downloaded because of timeouts, rerun the + rmt-cli mirror command until all packages are downloaded. + + + + + Setup script cannot access the &productname; repository + + + The repodata directory on the &rmt; server will not + be available until all of the packages for that repository are downloaded. + If some packages could not be downloaded to the &rmt; server because of timeouts + during the first mirroring, rerun the rmt-cli mirror + command until all packages are downloaded. + + + + + Setup script cannot install SUSEConnect because of + package dependencies + + + &productname; only supports the latest minor release of &rhla; or CentOS Linux. + If your system is running the latest version and SUSEConnect + still has package dependency issues, try the following workaround: + + + + + Edit the rmt-client-setup-res script to add + --skip-broken to the following line: + +$DNF install SUSEConnect librepo --skip-broken + + + + Run the script and accept any proposed package changes. + SUSEConnect will be skipped. + + + + + Run the script a second time. The package changes from the first attempt + can sometimes resolve the package dependency issues, allowing the second + attempt to successfully install SUSEConnect. + + + + +
diff --git a/xml/configure-rmt-server.xml b/xml/configure-rmt-server.xml new file mode 100644 index 0000000..0eabee6 --- /dev/null +++ b/xml/configure-rmt-server.xml @@ -0,0 +1,136 @@ + + + %entities; +]> + +
+ Configuring the &rmt; server + + + + + + + no + + + + + Use this procedure to configure the &rmtool; (&rmt;) on &sles; 15. + + + Requirements + + + &sles; 15 is installed and up to date. + + + + + You have a &scc; account and organization credentials. + + + + + + Configuring the &rmt; server + + + Install &rmt; on &sles; 15: + +&prompt.root;zypper in rmt-server + + + + Start the rmt module in &yast;: + +&prompt.root;yast2 rmt + + + + Enter your Organization Credentials, then select + Next. + + + + To find your organization credentials, log in to the + &scc;, select your + organization from My Organizations, and click + Proxies. Your organization's Mirroring + credentials are in the top right corner. + + + + + + Enter Database Credentials for a new MariaDB database user, + then select Next. The new user is created. + + + + + If a password for the &mariadb; root user is already set, enter the password + when prompted, then select OK. + + + If no password is set for the &mariadb; root user, enter and confirm a new + password when prompted, then select OK. + + + + + Enter a Common Name for the SSL certificates. The common + name is usually the FQDN of the server. + + + + + If the server has other domain names or IP addresses, enter these as + Alternative common names. Select Add + to add new names. When all common names are entered, select Next. + + + + + If prompted, enter and confirm a password for the CA private key, then select + OK. + + + + + Activate the check box Open Ports for HTTP and HTTPS in Firewall, + then select Next. + + + + + &yast; displays the &rmt; Service Status. + Select Next. + + + + + Review the Configuration Summary, then select + Finish to close &yast;. + + + + + &yast; enables and starts all &rmt; &systemd; services and timers. + + + More information + + + + &rmt; installation and configuration + + + +
diff --git a/xml/mirror-repositories-with-rmt.xml b/xml/mirror-repositories-with-rmt.xml new file mode 100644 index 0000000..d3ebb9a --- /dev/null +++ b/xml/mirror-repositories-with-rmt.xml @@ -0,0 +1,114 @@ + + + %entities; +]> + +
+ Mirroring &productname; repositories with &rmt; + + + + no + + + + + Use this procedure to mirror the &productname; repositories for &rhel; &productnumber; + and CentOS Linux &productnumber;. + + + Requirements + + + + + + + + The &rmt; server has enough storage available for repository mirroring. + + + + + Your organization credentials appear correctly in /etc/rmt.conf. + + + + + You have a &productname; subscription activated in the &scc;. + + + + + + Mirroring &productname; repositories with &rmt; + + + On the &rmt; server, update the available product and repository metadata: + +&prompt.root;rmt-cli sync + + Synchronization is also performed automatically by + rmt-server-sync.timer. You can check the status and + the next scheduled synchronization time with the following command: + +&prompt.root;systemctl status rmt-server-sync.timer + + + + Enable &productname; using the product ID 1251: + +&prompt.root;rmt-cli product enable 1251 + + This enables all of the default repositories associated with the product. + + + + + If your subscription includes the &ha; extension, enable the extension using + the product ID 1252: + +&prompt.root;rmt-cli product enable 1252 + + + To check whether the &ha; extension is available, run this command: + rmt-cli products list --all --name="Liberty" --version=&productnumber; + + + + + + If you also need the Source or Debug + repositories, find and enable them with the following commands: + +&prompt.root;rmt-cli repo list --all | grep RES- +&prompt.root;rmt-cli repo enable REPO_ID + + + + Start package mirroring for the enabled repositories: + +&prompt.root;rmt-cli mirror + + Packages are downloaded to the &rmt; server once per day by + rmt-server-mirror.timer. You can check the status + and the next scheduled download time with the following command: + +&prompt.root;systemctl status rmt-server-mirror.timer + + + + More information + + + + Mirroring repositories on the &rmt; server + + + +
diff --git a/xml/register-with-rmt.xml b/xml/register-with-rmt.xml new file mode 100644 index 0000000..5ba5f0c --- /dev/null +++ b/xml/register-with-rmt.xml @@ -0,0 +1,227 @@ + + + %entities; +]> + +
+ Registering &rhla; or CentOS Linux with &rmt; + + + + + no + + + + + Use this procedure to register &rhel; &productnumber; or CentOS Linux &productnumber; + with the &rmt; server. + + + + CentOS Stream is not supported. + + + + Requirements + + + + + + + + + + + + + The &rmt; server is running rmt-server version 2.10 or later. + + + + + The system you want to register can access the &rmt; server. + + + + + The system you want to register is running the latest minor release of &rhla; &productnumber; + or CentOS Linux &productnumber;. + + + + + You have a &productname; subscription activated in the &scc;. + + + + + You have removed the system from any &rh; subscription services it was + registered to. + + + + + Registering &rhla; or CentOS Linux with &rmt; + + + + + Save the following script as rmt-client-setup-res: + +#! /bin/sh + +SUSECONNECT=/usr/bin/SUSEConnect +RPM=/usr/bin/rpm +CURL=/usr/bin/curl +YUM=/usr/bin/yum +YUM_CONFIG_MGR=/usr/bin/yum-config-manager + +TEMPFILE="/etc/pki/ca-trust/source/anchors/rmt.crt" +UPDATE_CA_TRUST=/usr/bin/update-ca-trust +RPM_GPG_KEY_LOCATION="/etc/pki/rpm-gpg" + +PARAMS=$@ +REGURL="" +RMTNAME="" +REGURL=$1 + +CERTURL=`echo "$REGURL" | awk -F/ '{print "https://" $3 "/rmt.crt"}'` +$CURL --tlsv1.2 --silent --insecure --connect-timeout 10 --output $TEMPFILE $CERTURL +$UPDATE_CA_TRUST enable +$UPDATE_CA_TRUST extract + +SLL_version=7 +SLL_name="RES"; +SLL_release_package="sles_es-release-server" + +echo "Importing repomd.xml.key" +$CURL --silent --show-error --insecure ${REGURL}/repo/SUSE/Updates/${SLL_name}/${SLL_version}/x86_64/update/repodata/repomd.xml.key --output repomd.xml.key +$RPM --import repomd.xml.key + +echo "Disabling all repositories" +$YUM_CONFIG_MGR --disable \* > /dev/null + +if [ -f /usr/share/redhat-release ] | [ -h /usr/share/redhat-release ]; then + rm -f /usr/share/redhat-release; +fi + +$YUM_CONFIG_MGR --add-repo ${REGURL}/repo/SUSE/Updates/${SLL_name}/${SLL_version}/x86_64/update +$YUM_CONFIG_MGR --enable *suse.* > /dev/null + +$YUM install sles_es-release-server suseconnect-ng librepo +$YUM update yum + +$CURL --silent --show-error --insecure $REGURL/tools/rmt-client-setup --output rmt-client-setup +echo "Running rmt-client-setup $PARAMS" +sh rmt-client-setup $PARAMS + + + + Run the rmt-client-setup-res script with + the URL of the &rmt; server as a parameter: + +&prompt.root;sh rmt-client-setup-res https://RMT_SERVER + + The script installs &suseconnect; and its dependencies, + then downloads and runs the rmt-client-setup script, + which performs the following tasks: + + + + + Downloads all keys from + http://RMT_SERVER/repo/keys. + + + + + Imports the keys with gpg --import and + rpm --import. + + + + + Downloads the CA certificate from + https://RMT_SERVER/rmt.crt. + + + + + Imports the CA certificate to the trust store. + + + + + Uses &suseconnect; to register the system with the + &rmt; server. Registering the system using &suseconnect; + adds and enables all default repositories. + + + + + You should see Successfully registered system. + + + + + Verify the installed product: + +&prompt.root;&suseconnect; --status-text + + You should see the following output: + + +Installed Products: +------------------------------------------ + + SLES Expanded Support platform release file + (RES/&productnumber;/x86_64) + + Registered + +------------------------------------------ + + + + + Verify the available repositories: + +&prompt.root;dnf repolist + + You should see RES-&productnumber;-Updates. + + + + + If your subscription includes the &ha; extension, activate it with the + following command: + +&prompt.root;&suseconnect; -p RES-HA/&productnumber;/x86_64 + + + To check whether the extension is available, run the + &suseconnect; --list-extensions command. + + + + + + Run the update command to make sure there are no errors: + +&prompt.root;dnf update + + + + You can now update your system from repositories provided by &productname;. + +
diff --git a/xml/register-rhel-with-smt.xml b/xml/register-with-smt.xml similarity index 100% rename from xml/register-rhel-with-smt.xml rename to xml/register-with-smt.xml