Skip to content

Commit 0db2b1b

Browse files
MilsteinMilstein
committed
centos to RedHat/Rocky/AlmaLinux
1 parent 153c37d commit 0db2b1b

File tree

10 files changed

+105
-68
lines changed

10 files changed

+105
-68
lines changed

‎docs/openstack/create-and-connect-to-the-VM/images.md

Lines changed: 16 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -19,17 +19,22 @@ Navigate to *Project -> Compute -> Images*.
1919
NERC provides a set of default images that can be used as source while launching
2020
an instance:
2121

22-
| Name |
23-
|---------------------------------------|
24-
| centos-7-x86_64 |
25-
| centos-8-x86_64 |
26-
| debian-10-x86_64 |
27-
| fedora-36-x86_64 |
28-
| rocky-8-x86_64 |
29-
| ubuntu-18.04-x86_64 |
30-
| ubuntu-20.04-x86_64 |
31-
| ubuntu-22.04-x86_64 |
32-
| MS-Windows-2022 |
22+
+--------------------------------------+---------------------+
23+
| ID | Name |
24+
+--------------------------------------+---------------------+
25+
| a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 |
26+
| cfecb5d4-599c-4ffd-9baf-9cbe35424f97 | almalinux-8-x86_64 |
27+
| 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 |
28+
| 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 |
29+
| 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 |
30+
| 74a33f77-fc42-4dd1-a5a2-55fb18fc50cc | rocky-8-x86_64 |
31+
| d7d41e5f-58f4-4ba6-9280-7fef9ac49060 | rocky-9-x86_64 |
32+
| 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 |
33+
| 8c87cf6f-32f9-4a4b-91a5-0d734b7c9770 | ubuntu-20.04-x86_64 |
34+
| da314c41-19bf-486a-b8da-39ca51fd17de | ubuntu-22.04-x86_64 |
35+
+--------------------------------------+---------------------+
36+
37+
3338

3439
## How to create and upload own custom images?
3540

‎docs/openstack/create-and-connect-to-the-VM/ssh-to-the-VM.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,12 +33,18 @@ In our example, the IP is `199.94.60.66`.
3333
Default usernames for all the base images are:
3434

3535
- **all Ubuntu images**: ubuntu
36-
- **all CentOS images**: centos
36+
- **all AlmaLinux images**: almalinux
3737
- **all Rocky Linux images**: rocky
3838
- **all Fedora images**: fedora
3939
- **all Debian images**: debian
4040
- **all RHEL images**: cloud-user
4141

42+
!!! warning "Removed Centos Images"
43+
If you still have VMs running with deleted **CentOS** images, you need to use
44+
the following default username for your CentOS images: `centos`.
45+
46+
- **all CentOS images**: centos
47+
4248
Our example VM was launched with the **ubuntu-22.04-x86_64** base image, the
4349
user we need is 'ubuntu'.
4450

‎docs/openstack/create-and-connect-to-the-VM/using-vpn/openvpn/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -135,10 +135,10 @@ OpenVPN is available through the package management system on most Linux distrib
135135
sudo apt-get install openvpn
136136
```
137137

138-
**On RedHat/CentOS:**
138+
**On RedHat/Rocky/AlmaLinux:**
139139

140140
```sh
141-
sudo yum install openvpn
141+
sudo dnf install openvpn
142142
```
143143

144144
Then, to run OpenVPN using the client profile:

‎docs/openstack/create-and-connect-to-the-VM/using-vpn/sshuttle/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,10 +74,10 @@ sshuttle is available through the package management system on most Linux distri
7474
sudo apt-get install sshuttle
7575
```
7676

77-
**On RedHat/CentOS:**
77+
**On RedHat/Rocky/AlmaLinux:**
7878

7979
```sh
80-
sudo yum install sshuttle
80+
sudo dnf install sshuttle
8181
```
8282

8383
It is also possible to install into a **virtualenv** as *a non-root user*.

‎docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -292,10 +292,10 @@ sudo apt update
292292
sudo apt-get install wireguard resolvconf -y
293293
```
294294

295-
**On RedHat/CentOS:**
295+
**On RedHat/Rocky/AlmaLinux:**
296296

297297
```sh
298-
sudo yum install wireguard
298+
sudo dnf install wireguard
299299
```
300300

301301
Then, to run WireGuard using the client profile:

‎docs/openstack/data-transfer/data-transfer-from-to-vm.md

Lines changed: 17 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -93,10 +93,10 @@ various sources.
9393

9494
!!! tip "Helpful Tip"
9595
We use '~' in the examples. The tilde '~' is a Unix short-hand that means
96-
"my home directory". So if user `centos` uses `~/` this is the same as typing
97-
out the full path to centos user's home directory (easier to remember than
98-
`/home/centos/`). You can, of course, specify other paths (ex. –
99-
`/user/centos/output/files.zip`) Also, we use `.` in the examples to specify
96+
"my home directory". So if user `almalinux` uses `~/` this is the same as typing
97+
out the full path to almalinux user's home directory (easier to remember than
98+
`/home/almalinux/`). You can, of course, specify other paths (ex. –
99+
`/user/almalinux/output/files.zip`) Also, we use `.` in the examples to specify
100100
the current directory path from where the command is issued. This can be
101101
replaced with the actual path.
102102

@@ -115,7 +115,7 @@ is issued or you can specify the actual path instead of `.`.
115115

116116
For e.g.
117117

118-
scp -i ~/.ssh/your_pem_key_file.pem centos@199.94.60.219:~/myfile.zip /my_local_directory/
118+
scp -i ~/.ssh/your_pem_key_file.pem almalinux@199.94.60.219:~/myfile.zip /my_local_directory/
119119

120120
**ii. Copying Files From Another Computer to the NERC VM:**
121121

@@ -131,7 +131,7 @@ for `my home directory`)
131131

132132
For e.g.
133133

134-
scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip centos@199.94.60.219:~/myfile.zip
134+
scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip almalinux@199.94.60.219:~/myfile.zip
135135

136136
!!! info "Important Note"
137137
While it’s probably best to compress all the files you intend to transfer into
@@ -140,7 +140,7 @@ For e.g.
140140

141141
For e.g.
142142

143-
scp -i ~/.ssh/your_pem_key_file.pem -r centos@<Floating_IP>:~/mydata/ ./destination_directory/
143+
scp -i ~/.ssh/your_pem_key_file.pem -r almalinux@<Floating_IP>:~/mydata/ ./destination_directory/
144144

145145
This copies all the files from `~/mydata/` on the cluster to the current
146146
directory (i.e. `.`) on the computer you issued the command from. Here we can
@@ -269,7 +269,7 @@ Edit the config file's content on the path location described by
269269
[nerc]
270270
type = sftp
271271
host = 199.94.60.219
272-
user = centos
272+
user = almalinux
273273
port =
274274
pass =
275275
key_file = C:\Users\YourName\.ssh\rshiny_bentley
@@ -424,12 +424,15 @@ as shown below:
424424

425425
!!! info "Default User name based on OS"
426426
- **all Ubuntu images**: ubuntu
427-
- **all CentOS images**: centos
427+
- **all AlmaLinux images**: almalinux
428428
- **all Rocky Linux images**: rocky
429429
- **all Fedora images**: fedora
430430
- **all Debian images**: debian
431431
- **all RHEL images**: cloud-user
432432

433+
If you still have VMs running with deleted **CentOS** images, you need to
434+
use the following default username for your CentOS images: `centos`.
435+
433436
**"Password"**: "`<Leave blank as you using SSH key>`"
434437

435438
- Change Authentication Options
@@ -495,7 +498,7 @@ for more information.
495498

496499
!!! info "Default User name based on OS"
497500
- **all Ubuntu images**: ubuntu
498-
- **all CentOS images**: centos
501+
- **all AlmaLinux images**: almalinux
499502
- **all Rocky Linux images**: rocky
500503
- **all Fedora images**: fedora
501504
- **all Debian images**: debian
@@ -558,12 +561,15 @@ for more information.
558561

559562
!!! info "Default User name based on OS"
560563
- **all Ubuntu images**: ubuntu
561-
- **all CentOS images**: centos
564+
- **all AlmaLinux images**: almalinux
562565
- **all Rocky Linux images**: rocky
563566
- **all Fedora images**: fedora
564567
- **all Debian images**: debian
565568
- **all RHEL images**: cloud-user
566569

570+
If you still have VMs running with deleted **CentOS** images, you need to
571+
use the following default username for your CentOS images: `centos`.
572+
567573
**"Key file"**: "Browse and choose the appropriate SSH Private Key from you
568574
local machine that has corresponding Public Key attached to your VM"
569575

‎docs/openstack/openstack-cli/launch-a-VM-using-openstack-CLI.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -34,8 +34,8 @@ Get the flavor list using below openstack command:
3434
Get the image name and its ID,
3535

3636
```sh
37-
openstack image list | grep centos
38-
| 41eafa05-c264-4840-8c17-746e6a388c2d | centos-7-x86_64 | active |
37+
openstack image list | grep almalinux-9
38+
| 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 | active |
3939
```
4040

4141
Get Private Virtual network details, which will be attached to the VM:
@@ -125,7 +125,7 @@ Example:
125125

126126
```sh
127127
openstack server create --flavor cpu-su.2 \
128-
--image centos-7-x86_64 \
128+
--image almalinux-8-x86_64 \
129129
--nic net-id=8ee63932-464b-4999-af7e-949190d8fe93 \
130130
--security-group default \
131131
--key-name cloud_key \

‎docs/openstack/openstack-cli/openstack-CLI.md

Lines changed: 14 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -106,18 +106,20 @@ following command lists all the images available to your project:
106106

107107
```sh
108108
openstack image list
109-
+--------------------------------------+---------------------+--------+
110-
| ID | Name | Status |
111-
+--------------------------------------+---------------------+--------+
112-
| a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 | active |
113-
| 41eafa05-c264-4840-8c17-746e6a388c2d | centos-7-x86_64 | active |
114-
| 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 | active |
115-
| 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 | active |
116-
| cf1be3e5-b6f6-466e-bac4-abe7587921a8 | rocky-8-x86_64 | active |
117-
| 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 | active |
118-
| 126a1c8a-1802-434f-bee3-c3b6c8def513 | ubuntu-20.04-x86_64 | active |
119-
| 8183fe83-1403-412c-8ef8-5608a5e09166 | ubuntu-22.04-x86_64 | active |
120-
+--------------------------------------+---------------------+--------+
109+
+--------------------------------------+---------------------+--------+
110+
| ID | Name | Status |
111+
+--------------------------------------+---------------------+--------+
112+
| a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 | active |
113+
| cfecb5d4-599c-4ffd-9baf-9cbe35424f97 | almalinux-8-x86_64 | active |
114+
| 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 | active |
115+
| 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 | active |
116+
| 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 | active |
117+
| 74a33f77-fc42-4dd1-a5a2-55fb18fc50cc | rocky-8-x86_64 | active |
118+
| d7d41e5f-58f4-4ba6-9280-7fef9ac49060 | rocky-9-x86_64 | active |
119+
| 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 | active |
120+
| 8c87cf6f-32f9-4a4b-91a5-0d734b7c9770 | ubuntu-20.04-x86_64 | active |
121+
| da314c41-19bf-486a-b8da-39ca51fd17de | ubuntu-22.04-x86_64 | active |
122+
+--------------------------------------+---------------------+--------+
121123
```
122124

123125
If you have launched some instances already, the following command shows a list

‎docs/openstack/persistent-storage/mount-the-object-storage.md

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -546,9 +546,9 @@ Access your virtual machine using SSH. Update the packages on your system and in
546546
sudo apt update && sudo apt upgrade
547547
sudo apt install s3fs
548548

549-
!!! tip "For CentOS"
550-
The **CentOS** repositiories do not have `s3fs`. Therefore, you will need to
551-
compile it yourself.
549+
!!! tip "For RedHat/Rocky/AlmaLinux"
550+
The **RedHat/Rocky/AlmaLinux** repositiories do not have `s3fs`. Therefore,
551+
you will need to compile it yourself.
552552

553553
First, using your local computer, visit the following website (it contains
554554
the releases of `s3fs`): [https://github.com/s3fs-fuse/s3fs-fuse/releases/latest](https://github.com/s3fs-fuse/s3fs-fuse/releases/latest).
@@ -566,11 +566,15 @@ Access your virtual machine using SSH. Update the packages on your system and in
566566

567567
Update your packages:
568568

569-
sudo yum update
569+
sudo dnf update -y
570570

571571
Install the prerequisites including fuse, the *C++ compiler* and make:
572572

573-
sudo yum install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip
573+
sudo dnf config-manager --set-enabled crb
574+
575+
sudo dnf install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip
576+
577+
# OR, sudo dnf --enablerepo=crb install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip
574578

575579
Now, use `wget` to download the source code. Replace https://github.com/s3fs-fuse/s3fs-fuse/archive/refs/tags/v1.94.zip with the link to the source code you found previously:
576580

@@ -675,8 +679,8 @@ of the option `noauto`.
675679

676680
- `/usr/bin/s3fs` is the location of your `s3fs` binary. If you installed
677681
it using `apt` on Debian or Ubuntu, you do not have to change anything here.
678-
If you are using a self-compiled version of `s3fs` created on CentOS as explained
679-
above, that location is `/usr/local/bin/s3fs`.
682+
If you are using a self-compiled version of `s3fs` created on RedHat/Rocky/AlmaLinux
683+
as explained above, that location is `/usr/local/bin/s3fs`.
680684

681685
- `/home/ubuntu/.passwd-s3fs` is the location of the file which contains
682686
the key pair used for mounting the "bucket1" repository as we named it in previous

‎docs/other-tools/kubernetes/kind.md

Lines changed: 31 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
We will need 1 VM to create a single node kubernetes cluster using `kind`.
66
We are using following setting for this purpose:
77

8-
- 1 Linux machine, `centos-7-x86_64`, `cpu-su.2` flavor with 2vCPU, 8GB RAM,
8+
- 1 Linux machine, `almalinux-9-x86_64`, `cpu-su.2` flavor with 2vCPU, 8GB RAM,
99
20GB storage - also [assign Floating IP](../../openstack/create-and-connect-to-the-VM/assign-a-floating-IP.md)
1010
to this VM.
1111

@@ -23,26 +23,38 @@ We are using following setting for this purpose:
2323
hostnamectl set-hostname kind
2424
```
2525

26-
## Install docker on CentOS7
26+
## Install docker on AlmaLinux
2727

28-
Run the below command on the CentOS7 VM:
28+
Run the below command on the AlmaLinux VM:
2929

3030
- SSH into **kind** machine
3131

3232
- Switch to root user: `sudo su`
3333

3434
- Execute the below command to initialize the cluster:
3535

36+
Please remove `container-tools` module that includes stable versions of podman,
37+
buildah, skopeo, runc, conmon, etc as well as dependencies and will be removed
38+
with the module. If this module is not removed then it will conflict with Docker.
39+
Red Hat does recommend Podman on RHEL 8.
40+
3641
```sh
37-
yum -y install epel-release; yum -y install docker; systemctl enable --now docker;
42+
dnf module remove container-tools
43+
44+
dnf update -y
45+
46+
dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo
47+
48+
dnf install docker-ce docker-ce-cli containerd.io docker-compose-plugin
49+
50+
systemctl start docker
51+
systemctl enable --now docker
3852
systemctl status docker
39-
```
4053
41-
```sh
42-
docker version
54+
docker -v
4355
```
4456

45-
## Install kubectl on CentOS7
57+
## Install kubectl on AlmaLinux
4658

4759
```sh
4860
curl -LO "https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl"
@@ -67,7 +79,7 @@ mv ./kind /usr/bin
6779
```sh
6880
which kind
6981
70-
/usr/bin/kind
82+
/bin/kind
7183
```
7284

7385
```sh
@@ -82,17 +94,18 @@ kind v0.11.1 go1.16.4 linux/amd64
8294
kind create cluster --name k8s-kind-cluster1
8395
8496
Creating cluster "k8s-kind-cluster1" ...
85-
✓ Ensuring node image (kindest/node:v1.21.1) 🖼
86-
✓ Preparing nodes 📦
87-
✓ Writing configuration 📜
88-
✓ Starting control-plane 🕹️
89-
✓ Installing CNI 🔌
90-
✓ Installing StorageClass 💾
97+
✓ Ensuring node image (kindest/node:v1.21.1) 🖼
98+
✓ Preparing nodes 📦
99+
✓ Writing configuration 📜
100+
✓ Starting control-plane 🕹️
101+
✓ Installing CNI 🔌
102+
✓ Installing StorageClass 💾
91103
Set kubectl context to "kind-k8s-kind-cluster1"
92104
You can now use your cluster with:
93105
94106
kubectl cluster-info --context kind-k8s-kind-cluster1
95-
Thanks for using kind! 😊
107+
108+
Have a nice day! 👋
96109
```
97110

98111
- Get the cluster details:
@@ -102,6 +115,7 @@ kind v0.11.1 go1.16.4 linux/amd64
102115
103116
Kubernetes control plane is running at https://127.0.0.1:38646
104117
CoreDNS is running at https://127.0.0.1:38646/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
118+
105119
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
106120
```
107121

@@ -116,7 +130,7 @@ kind v0.11.1 go1.16.4 linux/amd64
116130
kubectl get nodes
117131
118132
NAME STATUS ROLES AGE VERSION
119-
k8s-kind-cluster1-control-plane Ready control-plane,master 5m26s v1.26.1
133+
k8s-kind-cluster1-control-plane Ready control-plane,master 5m26s v1.21.1
120134
```
121135

122136
## Deleting a Cluster

0 commit comments

Comments
 (0)