From 81eeba7607f9453ef18ba0917024fe0476cc9178 Mon Sep 17 00:00:00 2001 From: Jie Hu Date: Thu, 17 Sep 2015 19:43:22 +0800 Subject: JIRA ESCALATOR-3 Change-Id: I6044ea74eca6ad6337cbc19f35cbfb437f8d1386 Signed-off-by: Jie Hu --- doc/A1-Appendix.rst | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 doc/A1-Appendix.rst (limited to 'doc/A1-Appendix.rst') diff --git a/doc/A1-Appendix.rst b/doc/A1-Appendix.rst new file mode 100644 index 0000000..dcacccf --- /dev/null +++ b/doc/A1-Appendix.rst @@ -0,0 +1,46 @@ +Appendix +-------- + +A.1 Impact Analysis +~~~~~~~~~~~~~~~~~~~ + +Upgrading the different software modules may cause different impact on +the availability of the infrastructure resources and even on the service +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...) + +**Software modules in network nodes** + +#. Neutron L2/L3 agent +#. OVS, SR-IOV Driver + +**Software modules storage nodes** + +#. Ceph + +The table below analyses such an impact - considering a single instance +of each software module - from the following aspects: + +- the function which will be lost during upgrade, +- the duration of the loss of this specific function, +- if this causes the loss of the vNF function, +- if it causes incompatibility in the different parts of the software, +- 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. -- cgit 1.2.3-korg