CN109688219B - Unified management method of network load balancer suitable for multi-cloud management - Google Patents
Unified management method of network load balancer suitable for multi-cloud management Download PDFInfo
- Publication number
- CN109688219B CN109688219B CN201811585160.1A CN201811585160A CN109688219B CN 109688219 B CN109688219 B CN 109688219B CN 201811585160 A CN201811585160 A CN 201811585160A CN 109688219 B CN109688219 B CN 109688219B
- Authority
- CN
- China
- Prior art keywords
- load balancer
- forwarding
- network load
- layer
- unified management
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a unified management method of a network load balancer, which is suitable for multi-cloud management. The method of the invention comprises the following steps: s10, defining a network load balancer unified management API, and adapting to a cloud platform needing to be accessed; s20, the unified management platform acquires the basic information of the network load balancer and classifies the basic information according to the forwarding mode; s30, the unified management platform obtains the differentiated high-level configuration of the network load balancer to form a visual complete topological diagram. The invention can classify the network load balancer of the access cloud platform uniformly according to four-layer and seven-layer forwarding protocols; and the structure of each load balancer is shown to the user by means of a topological graph.
Description
Technical Field
The invention relates to the technical field of cloud computing, in particular to a unified management method of a network load balancer, which is suitable for multi-cloud management.
Background
At present, each big cloud platform provides network load balancing service. With the development of the technology and the purpose of guaranteeing the compatibility of old users, two network load balances exist in most cloud platforms; one is traditional, and is simply forwarded based on four-layer protocols of IP and ports; the other is an application type, which can not only forward based on a four-layer protocol, but also increase the forwarding of a seven-layer protocol based on content rules.
Two types of network load balancing provided by a single cloud platform are completely separated and independently managed, and two different sets of APIs exist, so that user experience is poor. In practice the application type contains the functionality of the conventional type. Due to lack of industrial standards, the existing multi-cloud management platform basically does not take over network load balancing service; unified management of the multi-cloud network load balancer cannot be achieved.
Disclosure of Invention
The invention solves the technical problem of providing a unified management method of a network load balancer, which is suitable for multi-cloud management; and unified management of the cloud platform on the network load balancer is realized.
The technical scheme for solving the technical problems is as follows:
the method comprises the following steps:
s10, defining a network load balancer unified management API, and adapting to a cloud platform needing to be accessed;
s20, the unified management platform acquires the basic information of the network load balancer and classifies the basic information according to the forwarding mode;
s30, the unified management platform obtains the differentiated high-level configuration of the network load balancer to form a visual complete topological diagram.
The network load balancing API comprises a load balancer instance, a listener, a back-end server, a seven-layer forwarding strategy and high-level configuration.
The definition method specifically comprises the following steps:
example load balancer: instance name, network type, and network configuration;
a listener: an external monitoring port, an external monitoring protocol and an internal forwarding port; in the snooping protocol, the four-layer protocol is: TCP/UDP; the seven-layer protocol is: HTTP/HTTPS;
a back-end server: self-defining a back-end server group and a back-end server;
seven-layer forwarding strategy: listener ID, forwarding domain name, forwarding URL;
high-level configuration: configuration object ID, scheduling policy, health check information, session maintenance information.
The step S20 specifically includes:
the unified management platform acquires the basic information of the network load balancer by using a defined unified API and stores the basic information in a database;
and the unified management platform defines a list interface of the query load balancer and classifies the query result.
The basic information includes the load balancer instance, the associated listener and the seven-layer forwarding policy of the listener.
The information returned by the query load balancer list interface comprises: load balancer instance ID, load balancer instance name, monitor port, and forwarding mode; the forwarding mode is determined according to whether the real-time query has a seven-layer forwarding strategy.
The step S30 specifically includes:
generating a backbone topological graph according to the basic information of the network load balancer;
and generating a complete topological graph according to the high-level configuration information of the three objects of the listener, the back-end server group and the seven-layer forwarding rule.
The high-level configuration information comprises a scheduling strategy of load balance, health check configuration information and session maintenance configuration of a seven-layer monitoring protocol; the scheduling policy includes polling, minimum number of connections.
By adopting the unified management method of the network load balancer, the network load balancer accessed to the cloud platform can be uniformly classified according to four-layer and seven-layer forwarding protocols; the structure of each load balancer is displayed to a user in a topological graph mode, and the difference of the configuration of each platform can be reflected in the topology; the unified management of the network load balancer is realized, and the user experience of managing the network load balancer is improved.
Drawings
The invention is further described below with reference to the accompanying drawings:
FIG. 1 is a flow chart of the present invention;
fig. 2 is a topology diagram of the network load balancer of the present invention.
Detailed Description
Fig. 1 is a flowchart illustrating a unified management method for a network load balancer according to an embodiment of the present invention; the method comprises the following steps:
s10: and defining a unified management API of the network load balancer, and adapting to the cloud platform needing to be accessed.
The network load balancing API mainly comprises the following steps: load balancer instances, listeners, backend servers, seven-layer forwarding policies, and advanced configurations. The specific definition method is as follows:
example load balancer: instance name, network type, and network configuration;
a listener: an external monitoring port, an external monitoring protocol (four layers: TCP/UDP; seven layers: HTTP/HTTPS), and an internal forwarding port;
a back-end server: self-defining a back-end server group and a back-end server;
seven-layer forwarding strategy: listener ID, forwarding domain name, forwarding URL;
high-level configuration: configuration object ID, scheduling policy, health check information, session maintenance information. The high-level configuration is the largest difference among cloud platforms, the same configuration content can act on a listener, a back-end server group or a forwarding strategy, and therefore unified processing is carried out by using configuration object IDs when an API is defined.
When the cloud platform is adapted, because a part of the cloud platform can independently manage the traditional API and the data, the traditional API and the application API/the enhanced API and the data, the adaptation of the cloud platform needs to be carried out in two parts, a version field is used for distinguishing when the unified management platform is called, and the version value is 'platform type + V1/V2 and the like'.
S20: and the unified management platform acquires the basic information of the network load balancer and classifies the basic information according to the forwarding mode.
In order to shield the classification and naming difference of different platforms to respective load balancer products, the load balancer products are classified in a uniform forwarding mode, and the specific steps are as follows:
s21: and the unified management platform acquires the basic information of the network load balancer by using the defined unified API and stores the basic information in a database.
The basic information includes: load balancer instances, associated listeners, and seven-layer forwarding policies for listeners.
S22: the unified management platform defines a query load balancer list interface.
In this embodiment, querying the load balancer list interface return information mainly includes: load balancer instance ID, load balancer instance name, listening port, forwarding mode (four layers/seven layers). The forwarding mode is determined according to whether the real-time query has a seven-layer forwarding strategy, and is not simply determined according to a monitoring protocol.
For example, the load balancer a monitors a TCP port 3300, and the TCP protocol belongs to four layers, and only supports IP address and port forwarding according to a backend server, so the forwarding manner is defined as four layers;
the load balancer B monitors an HTTP port 80, the HTTP protocol belongs to seven layers, and if no forwarding rule is set, the HTTP protocol is forwarded to a back-end server or is forwarded according to the IP address and the port of the back-end server, so that the forwarding mode is defined as four layers;
the load balancer C monitors the HTTP port 8080, and configures the forwarding rule 1 as a.test.com to be forwarded to the server 1, and the forwarding rule 2 as b.test.com to be forwarded to the server 2, where the forwarding mode has specific service content, and thus the forwarding mode is defined as seven layers.
By adopting the method, the classification of each platform can be unified, and the confusion caused by the use of different platforms by a user is avoided.
S30: the unified management platform obtains the differentiated high-level configuration of the network load balancer to form a visual complete topological graph.
In this embodiment, in order to enable a user to manage the load balancers more intuitively and avoid the problem of management confusion caused by differentiation of each cloud platform, a visual management topological graph is generated according to each network load balancer.
Fig. 2 is a complete topology diagram of a network load balancer in one embodiment.
The steps of generating the topological graph are as follows:
s31: adding back-end server information related to the listener on the basis of data acquisition of S21 and generating a backbone structure of the topological graph;
in this embodiment, the solid line part of fig. 2 is a backbone structure of a network load balancer. In order to unify load balancers that do not support custom backend server groups, a default backend server group is added to such products in the backbone structure.
S32: acquiring advanced configuration information of three objects of a listener, a back-end server group and a seven-layer forwarding rule to generate a complete topological graph;
in this embodiment, the dotted line portion of fig. 2 is high-level configuration information for a network load balancer.
The high-level configuration information mainly comprises: scheduling policies for load balancing, such as round robin, minimum number of connections; health check configuration information; session maintenance configuration for the seven-layer listening protocol. Objects of the information acting in different cloud platforms are different and can be a listener, a back-end server group or a seven-layer forwarding rule, so that platform differences can be clearly seen through a topological graph, and management is facilitated.
Claims (2)
1. A unified management method of a network load balancer suitable for multi-cloud management is characterized by comprising the following steps: the network load balancers accessed to the cloud platform are classified in a four-layer and seven-layer forwarding mode, the structure of each load balancer is displayed to a user in a topological graph mode, and the difference of the configuration of each platform is reflected in the topological graph; the method specifically comprises the following steps:
s10, defining a network load balancer unified management API, and adapting to a cloud platform needing to be accessed; the network load balancing unified management API comprises a load balancer instance, a listener, a back-end server, seven layers of forwarding strategies and high-level configuration; the specific definition method is as follows:
example load balancer: instance name, network type, and network configuration;
a listener: an external monitoring port, an external monitoring protocol and an internal forwarding port;
a back-end server: self-defining a back-end server group and a back-end server;
seven-layer forwarding strategy: listener ID, forwarding domain name, forwarding URL;
high-level configuration: configuring object ID, scheduling strategy, health examination information and conversation maintenance information;
s20, the unified management platform obtains the basic information of the network load balancer, and classifies the basic information according to the forwarding mode in a unified way, specifically:
the unified management platform acquires the basic information of the network load balancer by using a defined unified management API and stores the basic information in a database; the basic information comprises a load balancer instance, a related listener and a seven-layer forwarding strategy of the listener;
the unified management platform defines a list interface of the query load balancer and classifies the query result; the information returned by the query load balancer list interface comprises: load balancer instance ID, load balancer instance name, monitor port, and forwarding mode; the forwarding mode is determined according to whether the real-time query has a seven-layer forwarding strategy;
if the load balancer monitors the TCP port 3300, the TCP protocol belongs to a four-layer protocol, and only supports the IP address and port forwarding according to the back-end server, the forwarding mode is defined as a four-layer protocol;
if the HTTP port 80 of the load balancer is monitored, the HTTP protocol belongs to seven layers, and if the HTTP protocol is forwarded to the back-end server or is forwarded according to the IP address and the port of the back-end server under the condition that the forwarding rule is not set, the forwarding mode is defined as a four-layer protocol;
if the load balancer monitors the HTTP port 8080 and is configured with a forwarding rule, and the forwarding mode has specific service content, the forwarding mode is defined as a seven-layer protocol;
s30, the unified management platform acquires the differentiated advanced configuration of the network load balancer to form a visual complete topological graph, the solid line part is a backbone structure of the network load balancer, and the dotted line part is the advanced configuration information of the network load balancer:
generating a backbone topological graph according to the basic information of the network load balancer;
generating a complete topological graph according to the advanced configuration information of the three objects of the listener, the back-end server group and the seven-layer forwarding rule;
the high-level configuration information comprises a scheduling strategy of load balance, health check configuration information and session maintenance configuration of a seven-layer monitoring protocol; objects in which these high-level configuration information acts in different cloud platforms relate to listeners, backend server groups, or seven-layer forwarding rules.
2. The method for uniformly managing the network load balancer applicable to the multi-cloud management according to claim 1, wherein: the scheduling policy includes polling, minimum number of connections.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811585160.1A CN109688219B (en) | 2018-12-24 | 2018-12-24 | Unified management method of network load balancer suitable for multi-cloud management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811585160.1A CN109688219B (en) | 2018-12-24 | 2018-12-24 | Unified management method of network load balancer suitable for multi-cloud management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109688219A CN109688219A (en) | 2019-04-26 |
| CN109688219B true CN109688219B (en) | 2021-12-21 |
Family
ID=66188212
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811585160.1A Active CN109688219B (en) | 2018-12-24 | 2018-12-24 | Unified management method of network load balancer suitable for multi-cloud management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109688219B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104135542A (en) * | 2014-08-19 | 2014-11-05 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous load balancing management system and method in cloud computing environment |
| CN105282191A (en) * | 2014-06-20 | 2016-01-27 | 中国电信股份有限公司 | Load balancing system, controller and method |
| CN105357275A (en) * | 2015-10-12 | 2016-02-24 | 江西掌中无限网络科技股份有限公司 | Intelligent aggregation interface method and system |
| CN108200018A (en) * | 2017-12-20 | 2018-06-22 | 北京百度网讯科技有限公司 | Flow forwarding method and equipment, computer equipment and readable medium in cloud computing |
| CN108390766A (en) * | 2017-10-25 | 2018-08-10 | 国云科技股份有限公司 | A kind of service register and discovery method suitable for micro services |
| CN108989430A (en) * | 2018-07-19 | 2018-12-11 | 北京百度网讯科技有限公司 | Load-balancing method, device and storage medium |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7590989B2 (en) * | 2005-07-08 | 2009-09-15 | Microsoft Corporation | Load balancer management |
| US9069617B2 (en) * | 2011-09-27 | 2015-06-30 | Oracle International Corporation | System and method for intelligent GUI navigation and property sheets in a traffic director environment |
| CN108234208A (en) * | 2017-12-29 | 2018-06-29 | 三盟科技股份有限公司 | The visualization load balancing dispositions method and system of resource management based on business |
-
2018
- 2018-12-24 CN CN201811585160.1A patent/CN109688219B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105282191A (en) * | 2014-06-20 | 2016-01-27 | 中国电信股份有限公司 | Load balancing system, controller and method |
| CN104135542A (en) * | 2014-08-19 | 2014-11-05 | 浪潮(北京)电子信息产业有限公司 | Heterogeneous load balancing management system and method in cloud computing environment |
| CN105357275A (en) * | 2015-10-12 | 2016-02-24 | 江西掌中无限网络科技股份有限公司 | Intelligent aggregation interface method and system |
| CN108390766A (en) * | 2017-10-25 | 2018-08-10 | 国云科技股份有限公司 | A kind of service register and discovery method suitable for micro services |
| CN108200018A (en) * | 2017-12-20 | 2018-06-22 | 北京百度网讯科技有限公司 | Flow forwarding method and equipment, computer equipment and readable medium in cloud computing |
| CN108989430A (en) * | 2018-07-19 | 2018-12-11 | 北京百度网讯科技有限公司 | Load-balancing method, device and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109688219A (en) | 2019-04-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20230359479A1 (en) | Architecture of networks with middleboxes | |
| US9507932B2 (en) | Policy enforcement in a topology abstraction system | |
| CN111541796B (en) | CDN access flow scheduling method, device, communication system and storage medium | |
| US9647943B2 (en) | Method for providing tiered load balancing for a hosted voice-over internet protocol (VoIP) private branch exchange (PBX) | |
| CN104364761B (en) | For the system and method for the converting flow in cluster network | |
| CN103119907B (en) | It is provided for the system and method for the smart group of access control | |
| CN104380693B (en) | System and method for dynamic routing in the cluster | |
| US11102066B1 (en) | Server-based service configuration system and approach | |
| CN104365058B (en) | For the system and method in multinuclear and group system high speed caching SNMP data | |
| CN104620539B (en) | System and method for supporting SNMP requests by cluster | |
| US20130046883A1 (en) | End-to-End Content Delivery Network Incorporating Independently Operated Transparent Caches and Proxy Caches | |
| US9294411B2 (en) | Application aware network virtualization | |
| CN108989430B (en) | Load balancing method, device and storage medium | |
| CN104767690B (en) | A kind of flow scheduling device and method | |
| US20130091584A1 (en) | Distributed System and Method for Tracking and Blocking Malicious Internet Hosts | |
| Gregori et al. | Sensing the Internet through crowdsourcing | |
| Hesselman et al. | Increasing DNS security and stability through a control plane for top-level domain operators | |
| CN108259372A (en) | A kind of multi-link load balance system and method | |
| CN103401799A (en) | Method and device for realizing load balance | |
| CN109688219B (en) | Unified management method of network load balancer suitable for multi-cloud management | |
| Kumar et al. | Enhancing security management at software-defined exchange points | |
| CN106534396A (en) | Domain name analysis method and analysis system with multiple forwarding servers | |
| CN103905324A (en) | Dispatching and distributing method and system based on message five-element set | |
| CN102469110A (en) | Load balancing method applied to cluster system | |
| AU2018204247A1 (en) | Architecture of networks with middleboxes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |