diff --git a/content/software/installation_process/manual_installation/front_end_installation.md b/content/software/installation_process/manual_installation/front_end_installation.md index 0cea8714..ba2b6ec9 100644 --- a/content/software/installation_process/manual_installation/front_end_installation.md +++ b/content/software/installation_process/manual_installation/front_end_installation.md @@ -29,23 +29,34 @@ Follow the [OpenNebula Repositories]({{% relref "opennebula_repository_configura Not all OpenNebula dependencies are in base distribution repositories. On selected platforms below you need to enable third party repositories by running the following commands under privileged user (`root`): -**AlmaLinux 8,9** +### EPEL repository -```default -yum -y install epel-release +**AlmaLinux 8 and 9** + +```bash +dnf -y install epel-release ``` **RHEL 8** -```default +```bash rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` **RHEL 9** -```default +```bash rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` +### CRB repository + +**AlmaLinux/RHEL 8 and 9** + + +```bash +crb enable +``` + @@ -84,7 +95,7 @@ Install all OpenNebula Front-end components by executing the following commands ### AlmaLinux / RHEL ```bash -yum -y install opennebula opennebula-fireedge opennebula-gate opennebula-flow +dnf -y install opennebula opennebula-fireedge opennebula-gate opennebula-flow ``` ### Debian / Ubuntu @@ -214,7 +225,7 @@ Since 5.12, the OpenNebula comes with an integrated SSH agent as the `opennebula You are ready to **start** all OpenNebula services with the following command (NOTE: you might want to remove the services from the command arguments if you skipped their configuration steps above): -```default +```bash systemctl start opennebula opennebula-fireedge opennebula-gate opennebula-flow ``` @@ -223,7 +234,7 @@ Make sure all required [network ports]({{% relref "front_end_installation#fronte Other OpenNebula services might be started as a dependency but you don’t need to care about them unless they need to be explicitly restarted or stopped. To start these **services automatically on server boot**, it’s necessary to enable them by the following command: -```default +```bash systemctl enable opennebula opennebula-fireedge opennebula-gate opennebula-flow ``` @@ -237,8 +248,8 @@ After OpenNebula is started for the first time, you should check that the comman In the Front-end, run the following command as `oneadmin` system user and find a similar output: -```default -$ oneuser show +```bash +oneuser show USER 0 INFORMATION ID : 0 NAME : oneadmin @@ -255,8 +266,8 @@ RESOURCE USAGE & QUOTAS If you get an error message then the OpenNebula Daemon could not be started properly: -```default -$ oneuser show +```bash +oneuser show Failed to open TCP connection to localhost:2633 (Connection refused - connect(2) for "localhost" port 2633) ``` diff --git a/content/software/installation_process/manual_installation/kvm_node_installation.md b/content/software/installation_process/manual_installation/kvm_node_installation.md index 4478eeb7..3fbe4fba 100644 --- a/content/software/installation_process/manual_installation/kvm_node_installation.md +++ b/content/software/installation_process/manual_installation/kvm_node_installation.md @@ -38,35 +38,33 @@ Refer to [OpenNebula Repositories]({{% relref "opennebula_repository_configurati ### Installing on AlmaLinux/RHEL -#### Repository EPEL +Besides AlmaLinux and RHEL 8/9, OpenNebula depends on packages available in other distribution repositories. Execute one of the commands below, distinguished by the Host platform, under privileged user (`root`) to configure access to [EPEL](https://fedoraproject.org/wiki/EPEL) (Extra Packages for Enterprise Linux) repository: -OpenNebula depends on packages which aren’t in the base distribution repositories. Execute one of the commands below (distinguished by the Host platform) to configure access to additional [EPEL](https://fedoraproject.org/wiki/EPEL) (Extra Packages for Enterprise Linux) repository: +**AlmaLinux 8,9** -**AlmaLinux** - -```default -# yum -y install epel-release +```bash +dnf -y install epel-release ``` **RHEL 8** -```default -# rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +```bash +rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm ``` **RHEL 9** -```default -# rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +```bash +rpm -ivh https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` #### Install OpenNebula KVM Node Package Execute the following commands to install the OpenNebula KVM Node package and restart libvirt to use the OpenNebula-provided configuration file: -```default -# yum -y install opennebula-node-kvm -# systemctl restart libvirtd +```bash +dnf -y install opennebula-node-kvm +systemctl restart libvirtd ``` For further configuration, check the specific [guide]({{% relref "kvm_driver#kvmg" %}}). @@ -75,10 +73,10 @@ For further configuration, check the specific [guide]({{% relref "kvm_driver#kvm Execute the following commands to install the OpenNebula KVM Node package and restart libvirt to use the OpenNebula-provided configuration file: -```default -# apt-get update -# apt-get -y install opennebula-node-kvm -# systemctl restart libvirtd +```bash +apt-get update +apt-get -y install opennebula-node-kvm +systemctl restart libvirtd ``` For further configuration check the specific [guide]({{% relref "kvm_driver#kvmg" %}}). @@ -94,7 +92,7 @@ If you are performing an upgrade skip this and the next steps and go back to the Depending on the type of OpenNebula deployment, the SELinux can block some operations initiated by the OpenNebula Front-end, which results in a failure of the particular operation. It’s **not recommended to disable** the SELinux on production environments, as it degrades the security of your server, but to investigate and work around each individual problem based on the [SELinux User’s and Administrator’s Guide](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/selinux_users_and_administrators_guide/). The administrator might disable the SELinux to temporarily work around the problem or on non-production deployments by changing the following line in `/etc/selinux/config`: -```default +```bash SELINUX=disabled ``` @@ -106,19 +104,18 @@ Depending on your OpenNebula deployment type, the following may be required on y * package `util-linux` newer than 2.23.2-51 installed * SELinux boolean `virt_use_nfs` enabled (with datastores on NFS): -```default -# setsebool -P virt_use_nfs on +```bash +setsebool -P virt_use_nfs on ``` ### Disable AppArmor on Ubuntu/Debian Depending on the type of OpenNebula deployment, the AppArmor can block some operations initiated by the OpenNebula Front-end, which results in a failure of the particular operation. It’s **not recommended to disable** the apparmor on production environments, as it degrades the security of your server, but to investigate and work around each individual problem. A good starting point is [AppArmor HowToUse Guide](https://wiki.debian.org/AppArmor/HowToUse/). The administrator might disable the AppArmor to temporarily work around the problem or on non-production deployments the steps for disabling it can be found [here](https://wiki.debian.org/AppArmor/HowToUse#Disable_AppArmor). -{{< alert title="Note" color="success" >}} -Depending on your OpenNebula deployment type, the following lines might be required at `/etc/apparmor.d/abstractions/libvirt-qemu` profile:{{< /alert >}} +Depending on your OpenNebula deployment type, the following lines might be required at `/etc/apparmor.d/abstractions/libvirt-qemu` profile: -```default -# /var/lib/one/datastores/** rwk, +```bash +/var/lib/one/datastores/** rwk, ``` @@ -155,14 +152,14 @@ If [default SSH configuration]({{% relref "advanced_ssh_usage#node-ssh-config" % Make sure you are logged in on your Front-end and run the commands as `oneadmin`, e.g., by typing: -```default -# su - oneadmin +```bash +su - oneadmin ``` Create the `known_hosts` file by running following command with all the node names including the Front-end as parameters: -```default -$ ssh-keyscan ... >> /var/lib/one/.ssh/known_hosts +```bash +ssh-keyscan ... >> /var/lib/one/.ssh/known_hosts ``` ### B. Distribute Authentication Configuration @@ -171,37 +168,37 @@ To enable passwordless login on your infrastructure, you must copy authenticatio Make sure you are logged in on your Front-end and run the commands as `oneadmin`, e.g., by typing: -```default -# su - oneadmin +```bash +su - oneadmin ``` Enable passwordless logins by executing the following command for each of your nodes. For example: -```default -$ ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub -$ ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub -$ ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub +```bash +ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub +ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub +ssh-copy-id -i /var/lib/one/.ssh/id_rsa.pub ``` If the list of host SSH public keys was created in the previous section, distribute the `known_hosts` file to each of your nodes. For example: -```default -$ scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ -$ scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ -$ scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ +```bash +scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ +scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ +scp -p /var/lib/one/.ssh/known_hosts :/var/lib/one/.ssh/ ``` -#### Without SSH Authentication Agent (Optional) +#### (Optional) Without SSH Authentication Agent {{< alert title="Warning" color="warning" >}} **Not Recommended**. If you don’t use integrated SSH authentication agent service (which is initially enabled) on the Front-end, you’ll have to distribute also `oneadmin`’s private SSH key on your hypervisor nodes to allow connections among nodes and from nodes to Front-end. For security reasons, it’s recommended to use SSH authentication agent service and **avoid this step**. If you need to distribute `oneadmin`’s private SSH key on your nodes, proceed with steps above and continue with following extra commands for all your nodes. For example: -```default -$ scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ -$ scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ -$ scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ +```bash +scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ +scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ +scp -p /var/lib/one/.ssh/id_rsa :/var/lib/one/.ssh/ ```{{< /alert >}} ### C. Validate Connections @@ -215,40 +212,40 @@ You should verify that none of these connections (under user `oneadmin`) fail an For example, execute on the Front-end: -```default +```bash # from Front-end to Front-end itself -$ ssh -$ exit +ssh +exit # from Front-end to node, back to Front-end and to other nodes -$ ssh -$ ssh -$ exit -$ ssh -$ exit -$ ssh -$ exit -$ exit +ssh +ssh +exit +ssh +exit +ssh +exit +exit # from Front-end to node, back to Front-end and to other nodes -$ ssh -$ ssh -$ exit -$ ssh -$ exit -$ ssh -$ exit -$ exit +ssh +ssh +exit +ssh +exit +ssh +exit +exit # from Front-end to nodes and back to Front-end and other nodes -$ ssh -$ ssh -$ exit -$ ssh -$ exit -$ ssh -$ exit -$ exit +ssh +ssh +exit +ssh +exit +ssh +exit +exit ``` @@ -266,15 +263,15 @@ There are various models for virtual networks, check the [Open Cloud Networking] You may want to use the simplest network model that corresponds to the [bridged]({{% relref "bridged#bridged" %}}) driver. For this driver, you will need to set up a Linux bridge and include a physical device in the bridge. Later on, when defining the network in OpenNebula, you will specify the name of this bridge and OpenNebula will know that it should connect the VM to this bridge, thus giving it connectivity with the physical network device connected to the bridge. For example, a typical Host with two physical networks, one for public IP addresses (attached to an `eth0` NIC for example) and the other for private virtual LANs (NIC `eth1` for example) should have two bridges: -```default -# ip link show type bridge +```bash +ip link show type bridge 4: br0: ... 5: br1: ... -# ip link show master br0 +ip link show master br0 2: eth0: ... -# ip link show master br1 +ip link show master br1 3: eth1: ... ``` @@ -318,16 +315,16 @@ Finally, return back to the **Hosts** list, and check that the Host has switched To add a node to the cloud, run this command as `oneadmin` in the Front-end (replace `` with your node hostname): -```default -$ onehost create -i kvm -v kvm +```bash +onehost create -i kvm -v kvm -$ onehost list +onehost list ID NAME CLUSTER RVM ALLOCATED_CPU ALLOCATED_MEM STAT 1 localhost default 0 - - init # After some time (up to 1 minute) -$ onehost list +onehost list ID NAME CLUSTER RVM ALLOCATED_CPU ALLOCATED_MEM STAT 0 node01 default 0 0 / 400 (0%) 0K / 7.7G (0%) on ``` diff --git a/content/software/installation_process/manual_installation/opennebula_repository_configuration.md b/content/software/installation_process/manual_installation/opennebula_repository_configuration.md index ed420db8..d7878949 100644 --- a/content/software/installation_process/manual_installation/opennebula_repository_configuration.md +++ b/content/software/installation_process/manual_installation/opennebula_repository_configuration.md @@ -29,21 +29,19 @@ OpenNebula Systems provides an OpenNebula Enterprise Edition to customers with a {{< alert title="Important" color="success" >}} You should have received the customer access token (username and password) to access these repositories. You have to substitute the appearance of `` with your customer specific token in all instructions below.{{< /alert >}} -### AlmaLinux/RHEL +Some AlmaLinux and RHEL 8/9 dependencies are not available in the default repositories. You need to enable additional repositories. To do this, execute the following as the `root` user: -In **rhel9** and **AlmaLinux9** some dependencies cannot be found in the default repositories. Some extra repositories need to be enabled. To do this, execute the following as the root user: - -```default -repo=$(yum repolist --disabled | grep -i -e powertools -e crb | awk '{print $1}' | head -1) -yum config-manager --set-enabled $repo && yum makecache +```bash +crb enable ``` +Check [Add Third Party Repositories]({{% relref "front_end_installation/#step-2-add-third-party-repositories" %}}) for more details. To add the OpenNebula enterprise repository, execute the following as user `root`: -**RHEL 8, 9** +### RHEL 8 and 9 -```default -# cat << "EOT" > /etc/yum.repos.d/opennebula.repo +```bash +cat << "EOT" > /etc/dnf.repos.d/opennebula.repo [opennebula] name=OpenNebula Enterprise Edition baseurl=https://@enterprise.opennebula.io/repo/{{< release >}}/RedHat/$releasever/$basearch @@ -52,13 +50,13 @@ gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 EOT -# yum makecache +dnf makecache ``` -**AlmaLinux 8, 9** +### AlmaLinux 8 and 9 -```default -# cat << "EOT" > /etc/yum.repos.d/opennebula.repo +```bash +cat << "EOT" > /etc/dnf.repos.d/opennebula.repo [opennebula] name=OpenNebula Enterprise Edition baseurl=https://@enterprise.opennebula.io/repo/{{< release >}}/AlmaLinux/$releasever/$basearch @@ -67,7 +65,7 @@ gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 EOT -# yum makecache +dnf makecache ``` ### Debian/Ubuntu @@ -75,9 +73,9 @@ EOT {{< alert title="Note" color="success" >}} If the commands below fail, ensure you have `gnupg`, `wget` and `apt-transport-https` packages installed and retry. E.g., -```default -# apt-get update -# apt-get -y install gnupg wget apt-transport-https +```bash +apt-get update +apt-get -y install gnupg wget apt-transport-https ```{{< /alert >}} First, add the repository signing GPG key on the Front-end by executing as user `root`: @@ -85,55 +83,55 @@ First, add the repository signing GPG key on the Front-end by executing as user {{< alert title="Note" color="success" >}} It might be necessary to create /etc/apt/keyrings directory in Debian 11 because it does not exist by default: -```default -# mkdir -p /etc/apt/keyrings +```bash +mkdir -p /etc/apt/keyrings ```{{< /alert >}} -```default -# wget -q -O- https://downloads.opennebula.io/repo/repo2.key | gpg --dearmor --yes --output /etc/apt/keyrings/opennebula.gpg +```bash +wget -q -O- https://downloads.opennebula.io/repo/repo2.key | gpg --dearmor --yes --output /etc/apt/keyrings/opennebula.gpg ``` and then continue with repository configuration: **Debian 11** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Debian/11 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Debian/11 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Debian 12** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Debian/12 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Debian/12 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Ubuntu 22.04** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Ubuntu 24.04** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Ubuntu/24.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/{{< release >}}/Ubuntu/24.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` {{< alert title="Note" color="success" >}} You can point to a specific 6.6.x version by changing the occurrence of shorter version 6.6 in any of the above commands to the particular full 3 components version number (X.Y.Z). For instance, to point to version 6.6.1 on Ubuntu 22.04, use the following command:{{< /alert >}} -> ```default -> # echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/6.6.1/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -> # apt-get update +> ```bash +> echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://@enterprise.opennebula.io/repo/6.6.1/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +> apt-get update > ``` In Debian and Ubuntu it’s possible (and recommended) to store a customer token in a separate file to the repository configuration. If you choose to store the repository credentials separately, you need to avoid using the `@` part in the repository definitions above. You should create a new file `/etc/apt/auth.conf.d/opennebula.conf` with the following structure and replace the `` and `` parts with the customer credentials you have received: -```default +```bash machine enterprise.opennebula.io login password @@ -145,21 +143,19 @@ password The community edition of OpenNebula offers the full functionality of the Cloud Management Platform. You can configure the community repositories as follows: -### AlmaLinux/RHEL - -In **rhel9** and **AlmaLinux9** some dependencies cannot be found in the default repositories. Some extra repositories need to be enabled. To do this, execute the following as the root user: +Some AlmaLinux and RHEL 8/9 dependencies are not available in the default repositories. You need to enable additional repositories. To do this, execute the following as the `root` user: -```default -repo=$(yum repolist --disabled | grep -i -e powertools -e crb | awk '{print $1}' | head -1) -yum config-manager --set-enabled $repo && yum makecache +```bash +crb enable ``` +Check [Add Third Party Repositories]({{% relref "front_end_installation/#step-2-add-third-party-repositories" %}}) for more details. To add OpenNebula repository, execute the following as user `root`: -**RHEL 8, 9** +### RHEL 8 and 9 -```default -# cat << "EOT" > /etc/yum.repos.d/opennebula.repo +```bash +cat << "EOT" > /etc/dnf.repos.d/opennebula.repo [opennebula] name=OpenNebula Community Edition baseurl=https://downloads.opennebula.io/repo/{{< release >}}/RedHat/$releasever/$basearch @@ -168,13 +164,13 @@ gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 EOT -# yum makecache +dnf makecache ``` -**AlmaLinux 8, 9** +### AlmaLinux 8 and 9 -```default -# cat << "EOT" > /etc/yum.repos.d/opennebula.repo +```bash +cat << "EOT" > /etc/dnf.repos.d/opennebula.repo [opennebula] name=OpenNebula Community Edition baseurl=https://downloads.opennebula.io/repo/{{< release >}}/AlmaLinux/$releasever/$basearch @@ -183,7 +179,7 @@ gpgkey=https://downloads.opennebula.io/repo/repo2.key gpgcheck=1 repo_gpgcheck=1 EOT -# yum makecache +dnf makecache ``` ### Debian/Ubuntu @@ -191,41 +187,41 @@ EOT {{< alert title="Note" color="success" >}} If the commands below fail, ensure you have `gnupg`, `wget` and `apt-transport-https` packages installed and retry. E.g.,{{< /alert >}} -```default -# apt-get update -# apt-get -y install gnupg wget apt-transport-https +```bash +apt-get update +apt-get -y install gnupg wget apt-transport-https ``` First, add the repository signing GPG key on the Front-end by executing as user `root`: -```default -# wget -q -O- https://downloads.opennebula.io/repo/repo2.key | gpg --dearmor --yes --output /etc/apt/keyrings/opennebula.gpg +```bash +wget -q -O- https://downloads.opennebula.io/repo/repo2.key | gpg --dearmor --yes --output /etc/apt/keyrings/opennebula.gpg ``` **Debian 11** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Debian/11 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Debian/11 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Debian 12** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Debian/12 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Debian/12 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Ubuntu 22.04** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Ubuntu/22.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` **Ubuntu 24.04** -```default -# echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Ubuntu/24.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list -# apt-get update +```bash +echo "deb [signed-by=/etc/apt/keyrings/opennebula.gpg] https://downloads.opennebula.io/repo/{{< release >}}/Ubuntu/24.04 stable opennebula" > /etc/apt/sources.list.d/opennebula.list +apt-get update ``` diff --git a/content/software/upgrade_process/upgrade_guide/upgrading_single.md b/content/software/upgrade_process/upgrade_guide/upgrading_single.md index 74c32925..961fc46b 100644 --- a/content/software/upgrade_process/upgrade_guide/upgrading_single.md +++ b/content/software/upgrade_process/upgrade_guide/upgrading_single.md @@ -43,7 +43,7 @@ Upgrade the OpenNebula software using the package manager of your OS. Refer to t For example, in CentOS/RHEL simply execute: ```bash -yum upgrade opennebula +dnf upgrade opennebula ``` For Debian/Ubuntu use: @@ -60,7 +60,7 @@ Upgrade the OpenNebula node KVM or LXC packages, using the package manager of yo For example, in a rpm-based Linux distribution simply execute: ```bash -yum upgrade opennebula-node-kvm +dnf upgrade opennebula-node-kvm ``` For deb-based distros use: @@ -140,6 +140,9 @@ onedb backup In order to be able to retrieve the packages for the latest version, you need to update the OpenNebula packages repository. The instructions for doing this are detailed [here]({{% relref "opennebula_repository_configuration#repositories" %}}). +{{< alert title="Important" color="danger" >}} +Ensure that the required third-party repositories for your OS are enabled as described in [Add Third Party Repositories]({{% relref "front_end_installation/#step-2-add-third-party-repositories" %}}){{< /alert >}} + ### Step 6. Upgrade to the New Version {{< alert title="Important" color="success" >}} @@ -152,10 +155,10 @@ apt-get update apt-get install --only-upgrade opennebula opennebula-gate opennebula-flow opennebula-fireedge opennebula-migration python3-pyone ``` -RHEL +RHEL/AlmaLinux ```bash -yum upgrade opennebula opennebula-gate opennebula-flow opennebula-fireedge opennebula-migration python3-pyone +dnf upgrade opennebula* ``` ### Step 7. Update Configuration Files @@ -300,7 +303,7 @@ apt-get install --only-upgrade opennebula-node- RHEL ```bash -yum upgrade opennebula-node- +dnf upgrade opennebula-node- ``` {{< alert title="Note" color="success" >}}