Browse Prior Art Database

Type & Priority based two level load balance Disclosure Number: IPCOM000215231D
Publication Date: 2012-Feb-22
Document File: 7 page(s) / 111K

Publishing Venue

The Prior Art Database


Type and Priority Based Two Level Load Balance module is one core part of our Networking Automation Test Management System, it uses test task type and priority to do two level load balance between physical testbeds. each physical testbed is virtualized as a server and can be access via IP address. Those physical testbed servers are greedy self help servers, they can fetch test task (match phy testbed server's type and execution priority) from test task database by itself. this is quite different with other load balance system. since each phy testbed server's execution priority can be set by controllor dynamically, so via thus load balance module, system can execute user test task as faster as possible and make sure each test task will take appropriate precedence over the other test task. no test task will be ignored

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 42% of the total text.

Page 01 of 7

Type & Priority based two level load balance

1. what we try to solved

To develop this system, because, now we encounter the following problems:

1) Problem 1: Now we have no system can control load balance between physical networking testbeds, it always causes some physical testbeds are very busy, whereas, the other physical testbeds are idle, thus result at a very low use efficiency of physical testbed.

2) Problem 2: we need a system to provide test task priority control. To make sure that high priority test task can take the precedence of other test task, and can be executed much faster. Whereas, make sure no low priority test task will be ignored.

3) Problem 3: each physical testbed may be composed of more than one physical switch, to connect and control each physical switch is too complicated and too boring. we have to virtualize each physical testbed into a server. and make physical testbed accession is as simple as possible. and make the system easy to maintain.

2. our innovations

1) Two level load balance

This is a two level load balance system. First level is testbed suite, the second is priority level, whereas, priority level is under dynamical controlled.

Two level load balance will highly improve physical testbed's use efficiency and make sure each test task will take the right precedence over the other test task, and keep the whole system as simple as possible.

2) Greedy self help system

There isn't any central controllor used to assign test task, test task is fetched and executed by each physical testbed. If there are test task available, each physical testbed will fetch and execute test task when it is idle. Each physical testbed is an active participant not passive receiver.

This will simplify system design, and improve the use efficiency and robust of the system. System doesn't need to care about any complicated test task assignment and maintain any complicated communication between controllor and physical testbed.

3. System topology

As shown in Figure1. To achieve two level load balance, system is divided into three level, they are User Level, Database & Controllor Level


Page 02 of 7

and Physical Testbed Level. Their functions are listed as following.

1) User Level. User level is used to accept user's test task input. User can decide each test task's testbed suite type and priority. After test tasks are assigned, they are stored in the database and in queue status.

2) Database & Controllor Level. Database is used to store test task and all physical testbed information. Controllor is used to dynamically control each physical testbed's execution priority. In fact, assign testbed's execution priority is controllor's secondary function, controllor's main function is used to do physical health check and acts as a centralize test report generator.

3) Physical testbed. Each physical testbed will fetch test task from database according to its testbed suite type and execution priority. Each physical testbed

will strictly...