Skip to content

Commit be7358f

Browse files
committed
Update upgrade guides
1 parent 3ceca54 commit be7358f

File tree

9 files changed

+138
-2
lines changed

9 files changed

+138
-2
lines changed

source/intro_release_notes/upgrades/upgrade_38.rst

+17
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
2727

2828
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
2929

30+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
31+
32+
.. prompt:: text $ auto
33+
34+
$ onevnet list -x > networks.txt
35+
$ onehost list -x > hosts.txt
36+
$ onevm list -x > vms.txt
37+
38+
The list of valid network drivers in 5.0 Wizard are:
39+
40+
* ``802.1Q``
41+
* ``dummy``
42+
* ``ebtables``
43+
* ``fw``
44+
* ``ovswitch``
45+
* ``vxlan``
46+
3047
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
3148

3249
.. code::

source/intro_release_notes/upgrades/upgrade_40.rst

+17
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
2727

2828
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
2929

30+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
31+
32+
.. prompt:: text $ auto
33+
34+
$ onevnet list -x > networks.txt
35+
$ onehost list -x > hosts.txt
36+
$ onevm list -x > vms.txt
37+
38+
The list of valid network drivers in 5.0 Wizard are:
39+
40+
* ``802.1Q``
41+
* ``dummy``
42+
* ``ebtables``
43+
* ``fw``
44+
* ``ovswitch``
45+
* ``vxlan``
46+
3047
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
3148

3249
.. code::

source/intro_release_notes/upgrades/upgrade_410.rst

+17
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
4242

4343
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
4444

45+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
46+
47+
.. prompt:: text $ auto
48+
49+
$ onevnet list -x > networks.txt
50+
$ onehost list -x > hosts.txt
51+
$ onevm list -x > vms.txt
52+
53+
The list of valid network drivers in 5.0 Wizard are:
54+
55+
* ``802.1Q``
56+
* ``dummy``
57+
* ``ebtables``
58+
* ``fw``
59+
* ``ovswitch``
60+
* ``vxlan``
61+
4562
Stop OpenNebula and any other related services you may have running: OneFlow, EC2, and Sunstone. Use preferably the system tools, like `systemctl` or `service` as `root` in order to stop the services.
4663

4764
Backup

source/intro_release_notes/upgrades/upgrade_412.rst

+17
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
5757

5858
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
5959

60+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
61+
62+
.. prompt:: text $ auto
63+
64+
$ onevnet list -x > networks.txt
65+
$ onehost list -x > hosts.txt
66+
$ onevm list -x > vms.txt
67+
68+
The list of valid network drivers in 5.0 Wizard are:
69+
70+
* ``802.1Q``
71+
* ``dummy``
72+
* ``ebtables``
73+
* ``fw``
74+
* ``ovswitch``
75+
* ``vxlan``
76+
6077
Stop OpenNebula and any other related services you may have running: OneFlow, EC2, and Sunstone. Use preferably the system tools, like `systemctl` or `service` as `root` in order to stop the services.
6178

6279
Backup

source/intro_release_notes/upgrades/upgrade_414.rst

+2-2
Original file line numberDiff line numberDiff line change
@@ -58,9 +58,9 @@ Preparation
5858

5959
Before proceeding, make sure you don't have any VMs in a transient state (prolog, migr, epil, save). Wait until these VMs get to a final state (runn, suspended, stopped, done). Check the :ref:`Managing Virtual Machines guide <vm_guide_2>` for more information on the VM life-cycle.
6060

61-
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather that in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
61+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
6262

63-
.. code::
63+
.. prompt:: text $ auto
6464

6565
$ onevnet list -x > networks.txt
6666
$ onehost list -x > hosts.txt

source/intro_release_notes/upgrades/upgrade_42.rst

+17
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
2222

2323
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
2424

25+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
26+
27+
.. prompt:: text $ auto
28+
29+
$ onevnet list -x > networks.txt
30+
$ onehost list -x > hosts.txt
31+
$ onevm list -x > vms.txt
32+
33+
The list of valid network drivers in 5.0 Wizard are:
34+
35+
* ``802.1Q``
36+
* ``dummy``
37+
* ``ebtables``
38+
* ``fw``
39+
* ``ovswitch``
40+
* ``vxlan``
41+
2542
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
2643

2744
.. code::

source/intro_release_notes/upgrades/upgrade_44.rst

+17
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
1414

1515
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
1616

17+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
18+
19+
.. prompt:: text $ auto
20+
21+
$ onevnet list -x > networks.txt
22+
$ onehost list -x > hosts.txt
23+
$ onevm list -x > vms.txt
24+
25+
The list of valid network drivers in 5.0 Wizard are:
26+
27+
* ``802.1Q``
28+
* ``dummy``
29+
* ``ebtables``
30+
* ``fw``
31+
* ``ovswitch``
32+
* ``vxlan``
33+
1734
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
1835

1936
.. code::

source/intro_release_notes/upgrades/upgrade_46.rst

+17
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
4242

4343
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
4444

45+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
46+
47+
.. prompt:: text $ auto
48+
49+
$ onevnet list -x > networks.txt
50+
$ onehost list -x > hosts.txt
51+
$ onevm list -x > vms.txt
52+
53+
The list of valid network drivers in 5.0 Wizard are:
54+
55+
* ``802.1Q``
56+
* ``dummy``
57+
* ``ebtables``
58+
* ``fw``
59+
* ``ovswitch``
60+
* ``vxlan``
61+
4562
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
4663

4764
.. code::

source/intro_release_notes/upgrades/upgrade_48.rst

+17
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,23 @@ Before proceeding, make sure you don't have any VMs in a transient state (prolog
4343

4444
.. warning:: In 4.14 the ``FAILED`` state dissapears. You need to delete all the VMs in this state **before** the new version is installed.
4545

46+
The network drivers in OpenNebula 5.0 are located in the Virtual Network, rather than in the host. The upgrade process may ask you questions about your existing VMs, Virtual Networks and hosts, and as such it is wise to have the following information saved beforehand, since in the upgrade process OpenNebula will be stopped.
47+
48+
.. prompt:: text $ auto
49+
50+
$ onevnet list -x > networks.txt
51+
$ onehost list -x > hosts.txt
52+
$ onevm list -x > vms.txt
53+
54+
The list of valid network drivers in 5.0 Wizard are:
55+
56+
* ``802.1Q``
57+
* ``dummy``
58+
* ``ebtables``
59+
* ``fw``
60+
* ``ovswitch``
61+
* ``vxlan``
62+
4663
Stop OpenNebula and any other related services you may have running: EC2, OCCI, and Sunstone. As ``oneadmin``, in the front-end:
4764

4865
.. code::

0 commit comments

Comments
 (0)