diff --git a/docs/openstack/create-and-connect-to-the-VM/images.md b/docs/openstack/create-and-connect-to-the-VM/images.md index 59da8072..3122088f 100644 --- a/docs/openstack/create-and-connect-to-the-VM/images.md +++ b/docs/openstack/create-and-connect-to-the-VM/images.md @@ -19,17 +19,18 @@ Navigate to *Project -> Compute -> Images*. NERC provides a set of default images that can be used as source while launching an instance: -| Name | -|---------------------------------------| -| centos-7-x86_64 | -| centos-8-x86_64 | -| debian-10-x86_64 | -| fedora-36-x86_64 | -| rocky-8-x86_64 | -| ubuntu-18.04-x86_64 | -| ubuntu-20.04-x86_64 | -| ubuntu-22.04-x86_64 | -| MS-Windows-2022 | +| ID | Name | +| -------------------------------------- | -------------------- | +| a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 | +| cfecb5d4-599c-4ffd-9baf-9cbe35424f97 | almalinux-8-x86_64 | +| 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 | +| 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 | +| 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 | +| 74a33f77-fc42-4dd1-a5a2-55fb18fc50cc | rocky-8-x86_64 | +| d7d41e5f-58f4-4ba6-9280-7fef9ac49060 | rocky-9-x86_64 | +| 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 | +| 8c87cf6f-32f9-4a4b-91a5-0d734b7c9770 | ubuntu-20.04-x86_64 | +| da314c41-19bf-486a-b8da-39ca51fd17de | ubuntu-22.04-x86_64 | ## How to create and upload own custom images? diff --git a/docs/openstack/create-and-connect-to-the-VM/ssh-to-the-VM.md b/docs/openstack/create-and-connect-to-the-VM/ssh-to-the-VM.md index 990fe4f0..535cd201 100644 --- a/docs/openstack/create-and-connect-to-the-VM/ssh-to-the-VM.md +++ b/docs/openstack/create-and-connect-to-the-VM/ssh-to-the-VM.md @@ -33,12 +33,18 @@ In our example, the IP is `199.94.60.66`. Default usernames for all the base images are: - **all Ubuntu images**: ubuntu -- **all CentOS images**: centos +- **all AlmaLinux images**: almalinux - **all Rocky Linux images**: rocky - **all Fedora images**: fedora - **all Debian images**: debian - **all RHEL images**: cloud-user +!!! warning "Removed Centos Images" + If you still have VMs running with deleted **CentOS** images, you need to use + the following default username for your CentOS images: `centos`. + + - **all CentOS images**: centos + Our example VM was launched with the **ubuntu-22.04-x86_64** base image, the user we need is 'ubuntu'. diff --git a/docs/openstack/create-and-connect-to-the-VM/using-vpn/openvpn/index.md b/docs/openstack/create-and-connect-to-the-VM/using-vpn/openvpn/index.md index e89f0eef..1502e86d 100644 --- a/docs/openstack/create-and-connect-to-the-VM/using-vpn/openvpn/index.md +++ b/docs/openstack/create-and-connect-to-the-VM/using-vpn/openvpn/index.md @@ -135,10 +135,10 @@ OpenVPN is available through the package management system on most Linux distrib sudo apt-get install openvpn ``` -**On RedHat/CentOS:** +**On RedHat/Rocky/AlmaLinux:** ```sh -sudo yum install openvpn +sudo dnf install openvpn ``` Then, to run OpenVPN using the client profile: diff --git a/docs/openstack/create-and-connect-to-the-VM/using-vpn/sshuttle/index.md b/docs/openstack/create-and-connect-to-the-VM/using-vpn/sshuttle/index.md index 38a4daa3..c84a9058 100644 --- a/docs/openstack/create-and-connect-to-the-VM/using-vpn/sshuttle/index.md +++ b/docs/openstack/create-and-connect-to-the-VM/using-vpn/sshuttle/index.md @@ -74,10 +74,10 @@ sshuttle is available through the package management system on most Linux distri sudo apt-get install sshuttle ``` -**On RedHat/CentOS:** +**On RedHat/Rocky/AlmaLinux:** ```sh -sudo yum install sshuttle +sudo dnf install sshuttle ``` It is also possible to install into a **virtualenv** as *a non-root user*. diff --git a/docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md b/docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md index e584050b..c8a3c17a 100644 --- a/docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md +++ b/docs/openstack/create-and-connect-to-the-VM/using-vpn/wireguard/index.md @@ -292,10 +292,10 @@ sudo apt update sudo apt-get install wireguard resolvconf -y ``` -**On RedHat/CentOS:** +**On RedHat/Rocky/AlmaLinux:** ```sh -sudo yum install wireguard +sudo dnf install wireguard ``` Then, to run WireGuard using the client profile: diff --git a/docs/openstack/data-transfer/data-transfer-from-to-vm.md b/docs/openstack/data-transfer/data-transfer-from-to-vm.md index de403a71..8b2dc928 100644 --- a/docs/openstack/data-transfer/data-transfer-from-to-vm.md +++ b/docs/openstack/data-transfer/data-transfer-from-to-vm.md @@ -93,10 +93,10 @@ various sources. !!! tip "Helpful Tip" We use '~' in the examples. The tilde '~' is a Unix short-hand that means - "my home directory". So if user `centos` uses `~/` this is the same as typing - out the full path to centos user's home directory (easier to remember than - `/home/centos/`). You can, of course, specify other paths (ex. – - `/user/centos/output/files.zip`) Also, we use `.` in the examples to specify + "my home directory". So if user `almalinux` uses `~/` this is the same as typing + out the full path to almalinux user's home directory (easier to remember than + `/home/almalinux/`). You can, of course, specify other paths (ex. – + `/user/almalinux/output/files.zip`) Also, we use `.` in the examples to specify the current directory path from where the command is issued. This can be replaced with the actual path. @@ -115,7 +115,7 @@ is issued or you can specify the actual path instead of `.`. For e.g. - scp -i ~/.ssh/your_pem_key_file.pem centos@199.94.60.219:~/myfile.zip /my_local_directory/ + scp -i ~/.ssh/your_pem_key_file.pem almalinux@199.94.60.219:~/myfile.zip /my_local_directory/ **ii. Copying Files From Another Computer to the NERC VM:** @@ -131,7 +131,7 @@ for `my home directory`) For e.g. - scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip centos@199.94.60.219:~/myfile.zip + scp -i ~/.ssh/your_pem_key_file.pem ./myfile.zip almalinux@199.94.60.219:~/myfile.zip !!! info "Important Note" While it’s probably best to compress all the files you intend to transfer into @@ -140,7 +140,7 @@ For e.g. For e.g. - scp -i ~/.ssh/your_pem_key_file.pem -r centos@:~/mydata/ ./destination_directory/ + scp -i ~/.ssh/your_pem_key_file.pem -r almalinux@:~/mydata/ ./destination_directory/ This copies all the files from `~/mydata/` on the cluster to the current directory (i.e. `.`) on the computer you issued the command from. Here we can @@ -269,10 +269,10 @@ Edit the config file's content on the path location described by [nerc] type = sftp host = 199.94.60.219 - user = centos + user = almalinux port = pass = - key_file = C:\Users\YourName\.ssh\rshiny_bentley + key_file = C:\Users\YourName\.ssh\cloud.key shell_type = unix More about the config for **SFTP** can be [found here](https://rclone.org/sftp/). @@ -424,12 +424,15 @@ as shown below: !!! info "Default User name based on OS" - **all Ubuntu images**: ubuntu - - **all CentOS images**: centos + - **all AlmaLinux images**: almalinux - **all Rocky Linux images**: rocky - **all Fedora images**: fedora - **all Debian images**: debian - **all RHEL images**: cloud-user + If you still have VMs running with deleted **CentOS** images, you need to + use the following default username for your CentOS images: `centos`. + **"Password"**: "``" - Change Authentication Options @@ -495,7 +498,7 @@ for more information. !!! info "Default User name based on OS" - **all Ubuntu images**: ubuntu - - **all CentOS images**: centos + - **all AlmaLinux images**: almalinux - **all Rocky Linux images**: rocky - **all Fedora images**: fedora - **all Debian images**: debian @@ -558,12 +561,15 @@ for more information. !!! info "Default User name based on OS" - **all Ubuntu images**: ubuntu - - **all CentOS images**: centos + - **all AlmaLinux images**: almalinux - **all Rocky Linux images**: rocky - **all Fedora images**: fedora - **all Debian images**: debian - **all RHEL images**: cloud-user + If you still have VMs running with deleted **CentOS** images, you need to + use the following default username for your CentOS images: `centos`. + **"Key file"**: "Browse and choose the appropriate SSH Private Key from you local machine that has corresponding Public Key attached to your VM" diff --git a/docs/openstack/openstack-cli/launch-a-VM-using-openstack-CLI.md b/docs/openstack/openstack-cli/launch-a-VM-using-openstack-CLI.md index 25dfecc6..68974878 100644 --- a/docs/openstack/openstack-cli/launch-a-VM-using-openstack-CLI.md +++ b/docs/openstack/openstack-cli/launch-a-VM-using-openstack-CLI.md @@ -34,8 +34,8 @@ Get the flavor list using below openstack command: Get the image name and its ID, ```sh - openstack image list | grep centos - | 41eafa05-c264-4840-8c17-746e6a388c2d | centos-7-x86_64 | active | + openstack image list | grep almalinux-9 + | 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 | active | ``` Get Private Virtual network details, which will be attached to the VM: @@ -125,7 +125,7 @@ Example: ```sh openstack server create --flavor cpu-su.2 \ - --image centos-7-x86_64 \ + --image almalinux-8-x86_64 \ --nic net-id=8ee63932-464b-4999-af7e-949190d8fe93 \ --security-group default \ --key-name cloud_key \ diff --git a/docs/openstack/openstack-cli/openstack-CLI.md b/docs/openstack/openstack-cli/openstack-CLI.md index 0458be5e..b3c2b74d 100644 --- a/docs/openstack/openstack-cli/openstack-CLI.md +++ b/docs/openstack/openstack-cli/openstack-CLI.md @@ -106,18 +106,20 @@ following command lists all the images available to your project: ```sh openstack image list - +--------------------------------------+---------------------+--------+ - | ID | Name | Status | - +--------------------------------------+---------------------+--------+ - | a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 | active | - | 41eafa05-c264-4840-8c17-746e6a388c2d | centos-7-x86_64 | active | - | 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 | active | - | 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 | active | - | cf1be3e5-b6f6-466e-bac4-abe7587921a8 | rocky-8-x86_64 | active | - | 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 | active | - | 126a1c8a-1802-434f-bee3-c3b6c8def513 | ubuntu-20.04-x86_64 | active | - | 8183fe83-1403-412c-8ef8-5608a5e09166 | ubuntu-22.04-x86_64 | active | - +--------------------------------------+---------------------+--------+ ++--------------------------------------+---------------------+--------+ +| ID | Name | Status | ++--------------------------------------+---------------------+--------+ +| a9b48e65-0cf9-413a-8215-81439cd63966 | MS-Windows-2022 | active | +| cfecb5d4-599c-4ffd-9baf-9cbe35424f97 | almalinux-8-x86_64 | active | +| 263f045e-86c6-4344-b2de-aa475dbfa910 | almalinux-9-x86_64 | active | +| 41fa5991-89d5-45ae-8268-b22224c772b2 | debian-10-x86_64 | active | +| 99194159-fcd1-4281-b3e1-15956c275692 | fedora-36-x86_64 | active | +| 74a33f77-fc42-4dd1-a5a2-55fb18fc50cc | rocky-8-x86_64 | active | +| d7d41e5f-58f4-4ba6-9280-7fef9ac49060 | rocky-9-x86_64 | active | +| 75a40234-702b-4ab7-9d83-f436b05827c9 | ubuntu-18.04-x86_64 | active | +| 8c87cf6f-32f9-4a4b-91a5-0d734b7c9770 | ubuntu-20.04-x86_64 | active | +| da314c41-19bf-486a-b8da-39ca51fd17de | ubuntu-22.04-x86_64 | active | ++--------------------------------------+---------------------+--------+ ``` If you have launched some instances already, the following command shows a list diff --git a/docs/openstack/persistent-storage/mount-the-object-storage.md b/docs/openstack/persistent-storage/mount-the-object-storage.md index a92a8c38..3cc6ca61 100644 --- a/docs/openstack/persistent-storage/mount-the-object-storage.md +++ b/docs/openstack/persistent-storage/mount-the-object-storage.md @@ -546,9 +546,9 @@ Access your virtual machine using SSH. Update the packages on your system and in sudo apt update && sudo apt upgrade sudo apt install s3fs -!!! tip "For CentOS" - The **CentOS** repositiories do not have `s3fs`. Therefore, you will need to - compile it yourself. +!!! tip "For RedHat/Rocky/AlmaLinux" + The **RedHat/Rocky/AlmaLinux** repositiories do not have `s3fs`. Therefore, + you will need to compile it yourself. First, using your local computer, visit the following website (it contains 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 Update your packages: - sudo yum update + sudo dnf update -y Install the prerequisites including fuse, the *C++ compiler* and make: - sudo yum install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip + sudo dnf config-manager --set-enabled crb + + sudo dnf install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip + + # OR, sudo dnf --enablerepo=crb install automake fuse fuse-devel gcc-c++ git libcurl-devel libxml2-devel make openssl-devel wget unzip 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: @@ -675,8 +679,8 @@ of the option `noauto`. - `/usr/bin/s3fs` is the location of your `s3fs` binary. If you installed it using `apt` on Debian or Ubuntu, you do not have to change anything here. - If you are using a self-compiled version of `s3fs` created on CentOS as explained - above, that location is `/usr/local/bin/s3fs`. + If you are using a self-compiled version of `s3fs` created on RedHat/Rocky/AlmaLinux + as explained above, that location is `/usr/local/bin/s3fs`. - `/home/ubuntu/.passwd-s3fs` is the location of the file which contains the key pair used for mounting the "bucket1" repository as we named it in previous diff --git a/docs/other-tools/kubernetes/kind.md b/docs/other-tools/kubernetes/kind.md index 7453426f..606fbba3 100644 --- a/docs/other-tools/kubernetes/kind.md +++ b/docs/other-tools/kubernetes/kind.md @@ -5,7 +5,7 @@ We will need 1 VM to create a single node kubernetes cluster using `kind`. We are using following setting for this purpose: -- 1 Linux machine, `centos-7-x86_64`, `cpu-su.2` flavor with 2vCPU, 8GB RAM, +- 1 Linux machine, `almalinux-9-x86_64`, `cpu-su.2` flavor with 2vCPU, 8GB RAM, 20GB storage - also [assign Floating IP](../../openstack/create-and-connect-to-the-VM/assign-a-floating-IP.md) to this VM. @@ -23,9 +23,9 @@ We are using following setting for this purpose: hostnamectl set-hostname kind ``` -## Install docker on CentOS7 +## Install docker on AlmaLinux -Run the below command on the CentOS7 VM: +Run the below command on the AlmaLinux VM: - SSH into **kind** machine @@ -33,16 +33,28 @@ Run the below command on the CentOS7 VM: - Execute the below command to initialize the cluster: + Please remove `container-tools` module that includes stable versions of podman, + buildah, skopeo, runc, conmon, etc as well as dependencies and will be removed + with the module. If this module is not removed then it will conflict with Docker. + Red Hat does recommend Podman on RHEL 8. + ```sh - yum -y install epel-release; yum -y install docker; systemctl enable --now docker; + dnf module remove container-tools + + dnf update -y + + dnf config-manager --add-repo=https://download.docker.com/linux/centos/docker-ce.repo + + dnf install docker-ce docker-ce-cli containerd.io docker-compose-plugin + + systemctl start docker + systemctl enable --now docker systemctl status docker - ``` - ```sh - docker version + docker -v ``` -## Install kubectl on CentOS7 +## Install kubectl on AlmaLinux ```sh 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 ```sh which kind -/usr/bin/kind +/bin/kind ``` ```sh @@ -92,7 +104,8 @@ kind v0.11.1 go1.16.4 linux/amd64 You can now use your cluster with: kubectl cluster-info --context kind-k8s-kind-cluster1 - Thanks for using kind! 😊 + + Have a nice day! πŸ‘‹ ``` - Get the cluster details: @@ -102,6 +115,7 @@ kind v0.11.1 go1.16.4 linux/amd64 Kubernetes control plane is running at https://127.0.0.1:38646 CoreDNS is running at https://127.0.0.1:38646/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy + To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. ``` @@ -116,7 +130,7 @@ kind v0.11.1 go1.16.4 linux/amd64 kubectl get nodes NAME STATUS ROLES AGE VERSION - k8s-kind-cluster1-control-plane Ready control-plane,master 5m26s v1.26.1 + k8s-kind-cluster1-control-plane Ready control-plane,master 5m26s v1.21.1 ``` ## Deleting a Cluster