X-Git-Url: https://gerrit.opnfv.org/gerrit/gitweb?p=escalator.git;a=blobdiff_plain;f=docs%2Fdesign%2F2A1-Appendix.rst;fp=docs%2FA1-Appendix.rst;h=80fe44772871b19c32f508e78896e1bf43749156;hp=85f0717d62b0656dee7adec4b7db6c5be388faa1;hb=61a851845546300cc2f5ee9f3dd6761c9ecd093e;hpb=0fdf3b89887dfb7a9ea303f58c5e06c348889aa0

diff --git a/docs/A1-Appendix.rst b/docs/design/2A1-Appendix.rst
similarity index 97%
rename from docs/A1-Appendix.rst
rename to docs/design/2A1-Appendix.rst
index 85f0717..80fe447 100644
--- a/docs/A1-Appendix.rst
+++ b/docs/design/2A1-Appendix.rst
@@ -1,8 +1,9 @@
+========
 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
@@ -15,7 +16,7 @@ continuity of the vNFs.
 #. 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?