From c7632ae31654c96aac34fc863e874c1fdbc9a0ef Mon Sep 17 00:00:00 2001 From: Pedro Ielpi Date: Mon, 21 Oct 2024 12:50:19 +0200 Subject: [PATCH 1/2] M #-: Add clarification on opennebula-migration-community pkg Signed-off-by: Pedro Ielpi --- .../upgrades/upgrading_single.rst | 18 +++++++++++++++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git a/source/intro_release_notes/upgrades/upgrading_single.rst b/source/intro_release_notes/upgrades/upgrading_single.rst index 8a931230bf..09fa0974b1 100644 --- a/source/intro_release_notes/upgrades/upgrading_single.rst +++ b/source/intro_release_notes/upgrades/upgrading_single.rst @@ -81,20 +81,32 @@ RHEL Community Edition -------------------------------------------------------------------------------- -There is an additional step if you are upgrading OpenNebula CE. After you get the `opennebula-migration-community package `__, you need to install it in the OpenNebula Front-end. +If upgrading OpenNebula CE, you will need to install the ``opennebula-migration-community`` package on your Front-end. -RHEL +If you are upgrading to the *latest* version, you will need to download the package from the `Get Migration Packages `__ page. + +If you are upgrading to any prior version (such as upgrading from 6.6 to 6.8), then the migration package is already included in the OpenNebula repositories. + +To install the migration package: + +On RHEL: .. prompt:: bash $ auto $ rpm -i opennebula-migration-community*.rpm -Debian/Ubuntu +On Debian/Ubuntu: .. prompt:: bash $ auto $ dpkg -i opennebula-migration-community*.deb +.. note:: + + Before downloading the migration package, it's a good idea to double-check the URL in your software repository file. Ensure that the URL includes the software major and minor version (in ``.`` format), but not the exact release. + + For example, for OpenNebula version 6.8, the file should point to https://downloads.opennebula.io/repo/6.8 and not https://downloads.opennebula.io/repo/6.8.0. The first case will include migration packages for 6.8.*, whereas the second case will exclude minor versions such as 6.8.0.1. + Step 7. Update Configuration Files ================================================================================ From 8b494d0d453f7931e8a24b91fff6b810999a6eed Mon Sep 17 00:00:00 2001 From: Pedro Ielpi Date: Mon, 21 Oct 2024 13:15:48 +0200 Subject: [PATCH 2/2] M #-: Correct note on repo URLs Signed-off-by: Pedro Ielpi --- source/intro_release_notes/upgrades/upgrading_single.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/intro_release_notes/upgrades/upgrading_single.rst b/source/intro_release_notes/upgrades/upgrading_single.rst index 09fa0974b1..d229352ad0 100644 --- a/source/intro_release_notes/upgrades/upgrading_single.rst +++ b/source/intro_release_notes/upgrades/upgrading_single.rst @@ -105,7 +105,7 @@ On Debian/Ubuntu: Before downloading the migration package, it's a good idea to double-check the URL in your software repository file. Ensure that the URL includes the software major and minor version (in ``.`` format), but not the exact release. - For example, for OpenNebula version 6.8, the file should point to https://downloads.opennebula.io/repo/6.8 and not https://downloads.opennebula.io/repo/6.8.0. The first case will include migration packages for 6.8.*, whereas the second case will exclude minor versions such as 6.8.0.1. + For example, for OpenNebula version 6.8, the file should point to ``https://downloads.opennebula.io/repo/6.8`` and not ``https://downloads.opennebula.io/repo/6.8.0``. The first case will include migration packages for 6.8.*, whereas the second case will exclude minor versions such as 6.8.0.1. Step 7. Update Configuration Files ================================================================================