Skip to content

Commit bdacf06

Browse files
committed
M #-: Remove get migration form reference
1 parent 98b8d9a commit bdacf06

File tree

3 files changed

+0
-16
lines changed

3 files changed

+0
-16
lines changed

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 & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +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::
12-
13-
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>`__.
14-
1511
Previous Steps
1612
==============
1713

source/intro_release_notes/upgrades/upgrading_single.rst

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

77
If you are upgrading from a 6.0.x installation you only need to follow a reduced set of steps. If you are running a 5.12.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>`__.
12-
139
.. _upgrade_60:
1410

1511
Upgrading from 6.0.x
@@ -177,8 +173,6 @@ CentOS/RHEL
177173
Community Edition
178174
------------------
179175

180-
There is an additoinal step if you are upgrading OpenNebula CE. After you get the `opennebula-migration-community package <https://opennebula.io/get-migration>`__, you need to install it in the OpenNebula Front-end.
181-
182176
CentOS/RHEL
183177
~~~~~~~~~~~
184178

@@ -311,10 +305,6 @@ If you don't want to use the new feature, comment these out in order to get rid
311305
Step 8. Upgrade the Database Version
312306
================================================================================
313307

314-
.. important::
315-
316-
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>`__.
317-
318308
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 ``oned.conf``.
319309

320310
Step 9. Check DB Consistency

0 commit comments

Comments
 (0)