summaryrefslogtreecommitdiffstats
path: root/doc/A1-Appendix.rst
diff options
context:
space:
mode:
Diffstat (limited to 'doc/A1-Appendix.rst')
-rw-r--r--doc/A1-Appendix.rst23
1 files changed, 13 insertions, 10 deletions
diff --git a/doc/A1-Appendix.rst b/doc/A1-Appendix.rst
index dcacccf..85f0717 100644
--- a/doc/A1-Appendix.rst
+++ b/doc/A1-Appendix.rst
@@ -11,12 +11,14 @@ continuity of the vNFs.
**Software modules in the computing nodes**
#. Host OS patch
- ==[MT] As SW module, we should list the host OS and maybe ====its
- drivers as well. From upgrade perspective do we limit host OS
- upgrades to patches only?==
+
#. Hypervisor, such as KVM, QEMU, XEN, libvirt
#. Openstack agent in computing nodes (like Nova agent, Ceilometer
agent...)
+
+.. <MT> As SW module, we should list the host OS and maybe its
+ drivers as well. From upgrade perspective do we limit host OS
+ upgrades to patches only?
**Software modules in network nodes**
@@ -37,10 +39,11 @@ of each software module - from the following aspects:
- what should be backed up before the upgrade,
- the duration of restoration time if the upgrade fails
-| These values provided come from internal testing and based on some
- assumptions, they may vary depending on the deployment techniques.
- Please feel free to add if you find more efficient values during your
- testing.
-| https://wiki.opnfv.org/_media/upgrade_analysis_v0.5.xlsx
-| Note that no redundancy of the software modules is considered in the
- table.
+These values provided come from internal testing and based on some
+assumptions, they may vary depending on the deployment techniques.
+Please feel free to add if you find more efficient values during your
+testing.
+
+https://wiki.opnfv.org/_media/upgrade_analysis_v0.5.xlsx
+
+Note that no redundancy of the software modules is considered in the table.