Skip to content

Commit 6abd34d

Browse files
authored
Merge pull request #126 from sej7278/els2esu
Added migration instructions from ELS to ESU
2 parents afe9fea + 183ad95 commit 6abd34d

File tree

1 file changed

+84
-38
lines changed
  • docs/enterprise-support-for-almalinux

1 file changed

+84
-38
lines changed

docs/enterprise-support-for-almalinux/README.md

Lines changed: 84 additions & 38 deletions
Original file line numberDiff line numberDiff line change
@@ -144,44 +144,6 @@ Then you will have to run `tuxctl` like this:
144144

145145
:::
146146

147-
### SaaS usage
148-
149-
If you are using ESU with our SaaS license in AWS, then the instructions are slightly different. You should login to your instance and run the following as root (use of `--fips` is optional depending on your needs):
150-
151-
```text
152-
# dnf -y install https://repo.tuxcare.com/tuxcare/tuxcare-release-latest-9.2.$(uname -i).rpm
153-
154-
# tuxctl --saas --fips
155-
```
156-
157-
If you want to reclaim a license when you terminate an instance, you should first run:
158-
159-
```text
160-
# tuxctl --delete
161-
162-
De-registration successful
163-
```
164-
165-
Then you can use that license to register another instance.
166-
167-
If you want to check if you've already registered an instance, you can run the following to display your token:
168-
169-
```text
170-
# tuxctl --validate
171-
172-
Server is registered with token EXTENDED_SECURITY_UPDATES-SERVER-xxxxx
173-
```
174-
175-
If the instance has no license installed, it will return:
176-
177-
```text
178-
Server is not registered
179-
```
180-
181-
:::warning
182-
We can provide a systemd unit file and instructions, should you want to incorporate installing tuxcare-release and registering using tuxctl into your AMI, so that when you spin-up an instance its ready to receive patches, simply email [[email protected]]([email protected])
183-
:::
184-
185147
### Enabling FIPS 140-3 mode
186148

187149
First please ensure you have installed the `tuxcare-release` package as described above. If you haven't already registered your ESU license using `tuxctl` the next step will also do that for you.
@@ -267,6 +229,90 @@ Then run the following:
267229
# dnf upgrade
268230
```
269231

232+
### Migrating from CentOS
233+
234+
This guide contains steps on how to upgrade from CentOS 7 or Stream 8 [ELS](https://tuxcare.com/endless-lifecycle-support/centos-stream-8-eol-support/) to AlmaLinux 9.2 [ESU](https://tuxcare.com/fips-for-almalinux/).
235+
236+
You will require an ESU license key from [https://tuxcare.com/buy/almalinux/](https://tuxcare.com/buy/almalinux/) or talk to your Account Manager about our ELS-to-ESU migration bundle offer.
237+
238+
:::warning
239+
Ensure that you have a non-root user who can SSH and elevate privileges to root using su/sudo as this process will disable root SSH login. FIPS mode will also disable non-RSA SSH keys. Console access is recommended.
240+
:::
241+
242+
Choose **one** of the migrations below (1a or 1b) based on your CentOS ELS version. Once you have migrated to AlmaLinux 8, the instructions for getting to 9.2 and enabling ESU/FIPS are the same.
243+
244+
**1A. Migrate CentOS 7.9 ELS to AlmaLinux 8.10**
245+
246+
```text
247+
# update then disable els
248+
yum -y update
249+
dnf config-manager --set-disabled centos7*
250+
251+
# install elevate 7to8
252+
yum install -y http://repo.almalinux.org/elevate/elevate-release-latest-el7.noarch.rpm
253+
yum install -y leapp-upgrade leapp-data-almalinux
254+
leapp preupgrade
255+
leapp answer --section remove_pam_pkcs11_module_check.confirm=True
256+
leapp upgrade
257+
reboot
258+
```
259+
260+
You will now be running AlmaLinux 8.10 and can skip ahead to step 2.
261+
262+
**1B. Migrate CentOS Stream 8 ELS to AlmaLinux 8.10**
263+
264+
```text
265+
# update then disable els
266+
dnf -y upgrade
267+
dnf config-manager --set-disabled centos8stream-els
268+
269+
# install almalinux-deploy
270+
curl -O https://raw.githubusercontent.com/AlmaLinux/almalinux-deploy/master/almalinux-deploy.sh
271+
bash almalinux-deploy.sh -d
272+
reboot
273+
```
274+
275+
**2. Upgrade AlmaLinux 8.10 to 9.2**
276+
277+
```text
278+
# clean up
279+
sed -i '/^exclude=.*/d' /etc/yum.conf /etc/dnf/dnf.conf
280+
dnf -y remove *leapp* elevate-release els-define
281+
rm -rf /lib/modules/3.10*
282+
283+
# disable root ssh in a portable way
284+
echo PermitRootLogin no | sudo tee -a /etc/ssh/sshd_config
285+
sed -i 's/^PermitRootLogin.*/PermitRootLogin no/' /etc/ssh/sshd_config
286+
287+
# install elevate 8to9
288+
dnf -y install https://repo.almalinux.org/elevate/elevate-release-latest-el8.noarch.rpm
289+
dnf -y install leapp-upgrade leapp-data-almalinux
290+
291+
# upgrade specifically to 9.2
292+
export LEAPP_DISABLE_NET_NAMING_SCHEMES=1
293+
leapp preupgrade --target=9.2
294+
leapp upgrade --target=9.2
295+
reboot
296+
```
297+
298+
**3. Enable AlmaLinux 9.2 ESU repositories and FIPS mode**
299+
300+
```text
301+
# clean up
302+
sed -i '/^exclude=.*/d' /etc/yum.conf /etc/dnf/dnf.conf
303+
dnf -y remove *leapp* elevate-release kernel-*.el8*
304+
305+
# enable esu+fips
306+
dnf -y install https://repo.tuxcare.com/tuxcare/tuxcare-release-latest-9.2.$(uname -i).rpm
307+
tuxctl --fips --license-key ESU-xxxxxxxxxxxxxxx
308+
dnf -y install kernel-5.14.0-284.11*
309+
dnf -y upgrade
310+
fips-mode-setup --enable
311+
reboot
312+
```
313+
314+
See also [Enabling FIPS 140-3 mode](#enabling-fips-140-3-mode)
315+
270316
## **Essential and Enhanced Support**
271317

272318
### 1. Introduction

0 commit comments

Comments
 (0)