Skip to content

Commit 6efcd77

Browse files
authored
M #-: Remove reference to migrator package in 6.8 (#3020)
Signed-off-by: Pedro Ielpi <pielpi@opennebula.io>
1 parent 2e20a5f commit 6efcd77

3 files changed

Lines changed: 0 additions & 13 deletions

File tree

source/intro_release_notes/upgrades/overview.rst

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,6 @@ Overview
66

77
Keeping your OpenNebula up-to-date is very important, as you will receive the latest functionality and, more importantly, the latest security patches. It is possible to upgrade to the latest OpenNebula release from earlier versions.
88

9-
If you are using the Enterprise Edition you can upgrade from previous OpenNebula versions. If you are using the Community Edition you can only upgrade from the previous stable release if you are using your cloud for non-commercial purposes and you `need to request the migrator package <https://opennebula.io/get-migration>`__.
10-
119
Hypervisor Compatibility
1210
================================================================================
1311

source/intro_release_notes/upgrades/start_here.rst

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,6 @@ This guide describes the upgrade procedure for systems that are already running
88

99
Read the :ref:`Compatibility Guide <compatibility>` and `Release Notes <http://opennebula.org/software/release/>`_ to know what's new in OpenNebula |version|.
1010

11-
.. important:: Users of the Community Edition of OpenNebula can upgrade to the latest version only if they are running a non-commercial deployment, but they will need to upgrade first to the previous stable version. In order to access the latest migrator package, a request needs to be submitted through this `online form <https://opennebula.io/get-migration>`__.
12-
13-
1411
Previous Steps
1512
================================================================================
1613

source/intro_release_notes/upgrades/upgrading_single.rst

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,6 @@ Upgrading Single Front-end Deployments
66

77
If you are upgrading from a 6.8.x installation you only need to follow a reduced set of steps. If you are running a 6.6.x version or older, please check :ref:`these set of steps <upgrading_from_previous_extended_steps>` (some additional ones may apply, please review them at the end of the section).
88

9-
.. important::
10-
11-
Users of the Community Edition of OpenNebula can upgrade from the previous stable version if they are running a non-commercial OpenNebula cloud. In order to access the migrator package a request needs to be made through this `online form <https://opennebula.io/get-migration>`__. In order to use these non-commercial migrators to upgrade to the latest CE release (OpenNebula 6.6), you will need to upgrade your existing OpenNebula environment first to CE Patch Release 6.6.0.1
12-
13-
.. important:: If you haven't done so, please enable the :ref:`OpenNebula and needed 3rd party repositories <setup_opennebula_repos>` before attempting the upgrade process. If you want to use Docker related functionality of OpenNebula and/or OpenNebula Edge Clusters provisioning you'll need to follow :ref:`this for RedHat <install_docker_deps_rh>` or :ref:`this for Debian <install_docker_deps_deb>` distributions.
14-
159
.. _upgrade_68:
1610

1711
Upgrading from 6.8.x
@@ -305,8 +299,6 @@ If you don't want to use the new feature, comment these out in order to get rid
305299
Step 8. Upgrade the Database Version
306300
================================================================================
307301

308-
.. important:: Users of the Community Edition of OpenNebula can upgrade from the previous stable version if they are running a non-commercial OpenNebula cloud. In order to access the migrator package a request needs to be made through this `online form <https://opennebula.io/get-migration>`__.
309-
310302
Make sure at this point that OpenNebula is not running. If you installed from packages, the service may have been started automatically. Simply run the ``onedb upgrade -v`` command. The connection parameters are automatically retrieved from ``/etc/one/oned.conf``.
311303

312304
Step 9. Check DB Consistency

0 commit comments

Comments
 (0)