From f260553e9f26a7e96d5bf20a0350e25ce409a956 Mon Sep 17 00:00:00 2001 From: ligc Date: Mon, 3 Aug 2015 02:51:06 -0400 Subject: [PATCH] fix a heading issue in high_available_management_node.rst --- source/advanced/hamn/high_available_management_node.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/advanced/hamn/high_available_management_node.rst b/source/advanced/hamn/high_available_management_node.rst index e6577dfd0..33359eaf5 100644 --- a/source/advanced/hamn/high_available_management_node.rst +++ b/source/advanced/hamn/high_available_management_node.rst @@ -55,9 +55,9 @@ The configuration for the high availability applications is usually complex, it The automatic failover brings in several high availability applications, after the initial configuration is done, additional maintenance effort will be needed. For example, taking care of the high availability applications during cluster update, the updates for the high availability applications themselves, trouble shooting any problems with the high availability applications. A simple question may be able to help you to decide: could you get technical support if some of the high availability applications run into problems? All software has bugs ... -********************* +===================== Configuration Options -********************* +===================== The combinations of data synchronization mechanism and manual/automatic failover indicates different HAMN configuration options, the table below list all the combinations (the bold numbers are the combinations xCAT has documented and tested):