lbaas.rst line chart showing confusion in github
1. What is the problem? Browsing the lbaas.rst file on github, the line chart appears confusion. 2. What is the solution to the problem? update lbaas.rst format. Change-Id: Ia1e890cc1ffb1daa33038c69d235b671efa14986 Signed-off-by: zhang xiaohan <zhangxiaohan@szzt.com.cn> Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
This commit is contained in:
parent
c3e4a072bb
commit
03e593be24
@ -35,14 +35,14 @@ Octavia, we plan to deploy LBaaS as follows. ::
|
||||
+---------------------------+
|
||||
Central Region
|
||||
|
||||
+----------------------------+ +-----------------------------+
|
||||
| +----------------+ | | +----------------+ |
|
||||
| | LBaaS Octavia | | | | LBaaS Octavia | |
|
||||
| +----------------+ | | +----------------+ |
|
||||
| +------+ +---------------+ | | +-------+ +---------------+ |
|
||||
| | Nova | | Local Neutron | | | | Nova | | Local Neutron | |
|
||||
| +------+ +---------------+ | | +-------+ +---------------+ |
|
||||
+----------------------------+ +-----------------------------+
|
||||
+----------------------------+ +-----------------------------+
|
||||
| +----------------+ | | +----------------+ |
|
||||
| | LBaaS Octavia | | | | LBaaS Octavia | |
|
||||
| +----------------+ | | +----------------+ |
|
||||
| +------+ +---------------+ | | +-------+ +---------------+ |
|
||||
| | Nova | | Local Neutron | | | | Nova | | Local Neutron | |
|
||||
| +------+ +---------------+ | | +-------+ +---------------+ |
|
||||
+----------------------------+ +-----------------------------+
|
||||
Region One Region Two
|
||||
|
||||
As demonstrated in the figure above, for each region where a local neutron
|
||||
@ -96,25 +96,26 @@ LBaaS members in multiple regions
|
||||
|
||||
1. members in the same subnet yet locating in different regions
|
||||
---------------------------------------------------------------
|
||||
As shown below. ::
|
||||
|
||||
+-------------------------------+ +-----------------------+
|
||||
| +---------------------------+ | | |
|
||||
| | Amphora | | | |
|
||||
| | | | | |
|
||||
| | +-------+ +---------+ | | | |
|
||||
| +--+ mgmt +--+ subnet1 +---+ | | |
|
||||
| +-------+ +---------+ | | |
|
||||
| | | |
|
||||
| +--------------------------+ | | +-------------------+ |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | member1 | | member2 | | | | | | member3 | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| +--------------------------+ | | +-------------------+ |
|
||||
| network1(subnet1) | | network1(subnet1) |
|
||||
+-------------------------------+ +-----------------------+
|
||||
+-------------------------------+ +-----------------------+
|
||||
| +---------------------------+ | | |
|
||||
| | Amphora | | | |
|
||||
| | | | | |
|
||||
| | +-------+ +---------+ | | | |
|
||||
| +--+ mgmt +--+ subnet1 +---+ | | |
|
||||
| +-------+ +---------+ | | |
|
||||
| | | |
|
||||
| +--------------------------+ | | +-------------------+ |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | member1 | | member2 | | | | | | member3 | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| +--------------------------+ | | +-------------------+ |
|
||||
| network1(subnet1) | | network1(subnet1) |
|
||||
+-------------------------------+ +-----------------------+
|
||||
Region One Region Two
|
||||
Fig. 1. The scenario of balancing load across instances of one subnet which
|
||||
reside in different regions.
|
||||
Fig. 1. The scenario of balancing load across instances of one subnet which
|
||||
reside in different regions.
|
||||
|
||||
As shown in Fig. 1, suppose that a load balancer is created in Region one,
|
||||
and hence a listener, a pool, and two members in subnet1. When adding an
|
||||
@ -126,27 +127,28 @@ a pool.
|
||||
|
||||
2. members residing in different subnets and regions
|
||||
----------------------------------------------------
|
||||
As shown below. ::
|
||||
|
||||
+---------------------------------------+ +-----------------------+
|
||||
| +-----------------------------------+ | | |
|
||||
| | Amphora | | | |
|
||||
| | | | | |
|
||||
| | +---------+ +------+ +---------+ | | | |
|
||||
| +-+ subnet2 +--+ mgmt +-+ subnet1 +-+ | | |
|
||||
| +---------+ +------+ +---------+ | | |
|
||||
| | | |
|
||||
| +----------------------------------+ | | +-------------------+ |
|
||||
| | | | | | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | member1 | | member2 | | | | | | member3 | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | | | | | |
|
||||
| +----------------------------------+ | | +-------------------+ |
|
||||
| network1(subnet1) | | network2(subnet2) |
|
||||
+---------------------------------------+ +-----------------------+
|
||||
+---------------------------------------+ +-----------------------+
|
||||
| +-----------------------------------+ | | |
|
||||
| | Amphora | | | |
|
||||
| | | | | |
|
||||
| | +---------+ +------+ +---------+ | | | |
|
||||
| +-+ subnet2 +--+ mgmt +-+ subnet1 +-+ | | |
|
||||
| +---------+ +------+ +---------+ | | |
|
||||
| | | |
|
||||
| +----------------------------------+ | | +-------------------+ |
|
||||
| | | | | | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | member1 | | member2 | | | | | | member3 | | |
|
||||
| | +---------+ +---------+ | | | | +---------+ | |
|
||||
| | | | | | | |
|
||||
| +----------------------------------+ | | +-------------------+ |
|
||||
| network1(subnet1) | | network2(subnet2) |
|
||||
+---------------------------------------+ +-----------------------+
|
||||
Region One Region Two
|
||||
Fig. 2. The scenario of balancing load across instances of different subnets
|
||||
which reside in different regions as well.
|
||||
Fig. 2. The scenario of balancing load across instances of different subnets
|
||||
which reside in different regions as well.
|
||||
|
||||
As show in Fig. 2, supposing that a load balancer is created in region one, as
|
||||
well as a listener, a pool, and two members in subnet1. When adding an instance
|
||||
|
Loading…
x
Reference in New Issue
Block a user