path: root/docs/userguide/Deployment_Guideline.rst
diff options
Diffstat (limited to 'docs/userguide/Deployment_Guideline.rst')
1 files changed, 13 insertions, 14 deletions
diff --git a/docs/userguide/Deployment_Guideline.rst b/docs/userguide/Deployment_Guideline.rst
index d6a8cf3..7d3b018 100644
--- a/docs/userguide/Deployment_Guideline.rst
+++ b/docs/userguide/Deployment_Guideline.rst
@@ -27,7 +27,7 @@ sure to react in its best way when facing failure.
The following picture shows the the architecture of HA deployment based on the
framework from ETSI NFV ISG.
-.. figure:: Overview.jpg
+.. figure:: Overview.png
:alt: Architecture for HA Deployment
:figclass: align-center
@@ -70,7 +70,7 @@ of failure to the VIM, and congress provides proper recovery procedure. In such
the compute nodes are not recovered by the cluster scheme, but recovered under the
supervision of VIM.
-.. figure:: topology_control_compute.jpg
+.. figure:: topology_control_compute.png
:alt: HA Deployment Topology of Control Nodes and Compute Nodes
:figclass: align-center
@@ -88,7 +88,7 @@ compute nodes.
On thing to be notify is that all hosts in the NFV system should have at least two NICs
that are bonded via LACP.
-.. figure:: topology_control_compute_network.jpg
+.. figure:: topology_control_compute_network.png
:alt: HA Deployment Topology of Control Nodes and Compute Nodes and Network Nodes
:figclass: align-center
@@ -125,7 +125,7 @@ such as Pacemaker, is recommended to use to provide the following metrics.
Figure 4 shows the details of HA schemes for Openstack controller nodes with Pacemaker.
-.. figure:: HA_control.jpg
+.. figure:: HA_control.png
:alt: HA Deployment of Openstack Control Nodes based on Pacemaker
:figclass: align-center
@@ -248,7 +248,7 @@ such scheme should coordinate with the VM HA scheme, so that when both the host
VM detect the failure, they should know who should take responsibility for the evacuation.
-.. figure:: HA_Hypervisor.jpg
+.. figure:: HA_Hypervisor.png
:alt: HA Deployment of Host OS and Hypervisor
:figclass: align-center
@@ -278,7 +278,7 @@ rely on VMs to provide redundancy. However, for stateful VNFs, there should be d
between the active VM and standby VM. In this case, fault for the active VM can also be
copied to the standby VM, leading to failure of the new active VM.
-.. figure:: images/HA_VM.jpg
+.. figure:: HA_VM.png
:alt: VM Active/Standby Deployment
:figclass: align-center
@@ -310,7 +310,7 @@ affinity/inaffinity deployment support. example about watchdog
Figure 7 gives an example for the VNF HA scheme.
-.. figure:: HA_VNF.jpg
+.. figure:: HA_VNF.png
:alt: HA Deployment of VNFs
:figclass: align-center
@@ -331,6 +331,12 @@ Deployment Framework
Figure 8 shows an overall architecture for the HA deployment of ARNO.
+.. figure:: HA_ARNO.png
+ :alt: HA Deployment of OPNFV ARNO release
+ :figclass: align-center
+ Fig 8. HA Deployment of OPNFV ARNO release
For OPNFV Arno release, HA deployment of Openstack Control Node (Openstack Juno) and ODL
controller (ODL Helium) is supported. Both deployment tools (fuel and forman)support
such HA deployment.
@@ -351,13 +357,6 @@ Controller hardware:
* dead disk
* full disk
-Figure 9 gives an example for the VNF HA scheme.
-.. figure:: HA_ARNO.jpg
- :alt: HA Deployment of OPNFV ARNO release
- :figclass: align-center
- Fig 9. HA Deployment of OPNFV ARNO release
HA test result for ARNO