CN117792709A - Load balancing method and device supporting intercommunication of physical network and virtual network - Google Patents

Load balancing method and device supporting intercommunication of physical network and virtual network Download PDF

Info

Publication number
CN117792709A
CN117792709A CN202311709518.8A CN202311709518A CN117792709A CN 117792709 A CN117792709 A CN 117792709A CN 202311709518 A CN202311709518 A CN 202311709518A CN 117792709 A CN117792709 A CN 117792709A
Authority
CN
China
Prior art keywords
elb
data
xgw
request
underlay
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.)
Pending
Application number
CN202311709518.8A
Other languages
Chinese (zh)
Inventor
李宙洲
鲍文澜
杨广泽
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tianyi Cloud Technology Co Ltd
Original Assignee
Tianyi Cloud Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tianyi Cloud Technology Co Ltd filed Critical Tianyi Cloud Technology Co Ltd
Priority to CN202311709518.8A priority Critical patent/CN117792709A/en
Publication of CN117792709A publication Critical patent/CN117792709A/en
Pending legal-status Critical Current

Links

Abstract

The invention relates to a load balancing method and a device supporting intercommunication of a physical network and a virtual network, which belong to the field of cloud computing, a user initiates a resource instance creation request, the resource instance creation request is sent to a resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data surface identifiable data and sends the data surface identifiable data to a forwarding logic unit; the forwarding logic unit executes a load balancing strategy on a traffic transfer scene between the physical network and the virtual network according to the identifiable data of the data plane. According to the invention, the original network architecture is not required to be modified, the load balancing is used for opening the Underlay and Overlay networks, the intercommunication between the virtual network and the physical network in the cloud is realized, the intercommunication is realized based on the load balancing, the Underlay address and the port are not required to be exposed outwards, the security of Underlay resources is improved, the intercommunication is realized based on the load balancing, and the network architecture difference of the back-end service entity is shielded.

Description

Load balancing method and device supporting intercommunication of physical network and virtual network
Technical Field
The invention belongs to the field of private cloud and cloud computing, and particularly relates to a load balancing method and device supporting intercommunication of a physical network and a virtual network.
Background
With the rapid growth of internet traffic and data, various businesses need to continuously improve service capability. On one hand, the configuration of a single server can be optimized, but the hardware configuration is limited and the cost is high; on the other hand, cluster network technology may be used, with multiple low-profile servers providing services at the same time, which has become IT-compliant with high availability and high economy. In the cluster construction process, the most important technology is LB (Load Balance) load balancing technology, and the LB receives the service request first and distributes the request to a plurality of background service servers according to the forwarding strategy.
In the prior art, by determining the configuration parameters of the target access service, the configuration parameters comprise an Overlay network address; determining an Underlay network address from a preset Underlay network address resource pool, and forming a mapping relation between the Overlay network address and the Underlay network address; performing access policy configuration processing on the target access service based on the mapping relation, and determining a target access policy; the target access policy is used for realizing target access service through the Overlay network and the Underlay network. In this way, the Overlay network address is mapped to the Underlay network address, so that the Overlay network and the Underlay network can be flexibly accessed to each other, and the convenience and safety of access service are improved.
However, the prior art generally carries out transformation of the original underway network architecture when realizing, realizes intercommunication based on a load equalizer, and needs to expose the underway address and the port to the outside, so that the safety of underway resources is not high.
Disclosure of Invention
In view of the above shortcomings of the prior art, an object of the present invention is to provide a load balancing method and apparatus supporting interworking of a physical network and a virtual network.
According to a first aspect of the present invention, the present invention claims a load balancing method for supporting interworking between a physical network and a virtual network, comprising:
the user initiates a resource instance creation request, the resource instance creation request is sent to a resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data surface identifiable data and sends the data surface identifiable data to a forwarding logic unit;
the forwarding logic unit executes a load balancing strategy on a traffic transfer scene between the physical network and the virtual network according to the identifiable data of the data plane.
Further, the user initiates a resource instance creation request, the resource instance creation request is sent to the resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data face identifiable data and sends the data face identifiable data to the forwarding logic unit, and the method specifically comprises the following steps:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
elb-server comprises an api request processing unit which is responsible for processing requests from users to create lb related resources and managing the addresses of underway;
elb-manager is elb data reading unit responsible for providing data reading for elb-controller;
elb-controller translates the user's request data into data recognizable by the data plane, configuring the data plane forwarding rules.
Further, the forwarding logic unit executes a load balancing policy on a traffic transfer scenario between the physical network and the virtual network according to the identifiable data of the data plane, and specifically includes:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
xgw or Xgw has Mapping tables including VNI and underway mappings;
xgw or Xgw are components that forward the relevant traffic of the load balancer;
underway is a service associated with a physical network;
overlay is a service associated with a virtual network.
Further, the user initiates a resource instance creation request, the resource instance creation request is sent to the resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data face identifiable data and sends the data face identifiable data to the forwarding logic unit, and the method further comprises the steps of:
the user initiates a back-end request for creating the Underlay, sends the request to elb-server, elb-server to analyze the request and then confirms that the Underlay address of the request is valid, and sends notify notification to elb-manager and elb-controller;
elb-manager receives the discovery request from elb-server and reads the discovery back end details of the request from the database, and stores the discovery back end details in the local memory;
elb-controller, after receiving the notification sent by elb-server to create the underlayback end host, reads the underlayback end details of the request from elb-manager, translates the underlayback end details into Xgw or Xgw7 recognizable configuration, and sends the configuration to the forwarding logic unit.
Further, the forwarding logic unit executes a load balancing policy on a traffic delivery scenario between the physical network and the virtual network according to the identifiable data of the data plane, and further includes:
when the traffic transfer scene is from a physical network to a virtual network, storing a mapping relation from the underwlay to the Overlay for the traffic from the underwlay to the Overlay Xgw or Xgw, completing VXLAN encapsulation at Xgw or Xgw7, and forwarding the traffic to an Overlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain a destination IP, the Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is sealed in the Vxlan encapsulation, and then the VNI is forwarded to a back-end host;
when the traffic transfer scene is from a virtual network to a physical network, storing a mapping relation from an Overlay to an Underlay for the traffic from the Overlay to the Underlay Xgw or Xgw, and completing VXLAN decapsulation and forwarding the traffic to an Underlay back-end host at Xgw or Xgw 7;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, searching Mapping table for corresponding underwlay address according to the analyzed VNI, stripping Vxlan header, translating inner layer source IP into a preset underwlay IP, forwarding, and forwarding to underwlay back-end host.
According to a second aspect of the present invention, the present invention claims a load balancing apparatus supporting interworking of a physical network and a virtual network, comprising:
the user terminal initiates a resource instance creation request and sends the resource instance creation request to the resource management control unit;
the resource management control unit receives the resource instance creation request, analyzes the source instance creation request, translates the source instance creation request into data which can be identified by the data plane and transmits the data to the forwarding logic unit;
and the forwarding logic unit is used for receiving the data face identifiable data and executing a load balancing strategy on a traffic transmission scene between the physical network and the virtual network according to the data face identifiable data.
Further, the device further comprises:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
elb-server comprises an api request processing unit which is responsible for processing requests from users to create lb related resources and managing the addresses of underway;
elb-manager is elb data reading unit responsible for providing data reading for elb-controller;
elb-controller translates the user's request data into data recognizable by the data plane, configuring the data plane forwarding rules.
Further, the device further comprises:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
xgw or Xgw has Mapping tables including VNI and underway mappings;
xgw or Xgw are components that forward the relevant traffic of the load balancer;
underway is a service associated with a physical network;
overlay is a service associated with a virtual network.
Further, the device further comprises:
the user initiates a back-end request for creating the Underlay, sends the request to elb-server, elb-server to analyze the request and then confirms that the Underlay address of the request is valid, and sends notify notification to elb-manager and elb-controller;
elb-manager receives the discovery request from elb-server and reads the discovery back end details of the request from the database, and stores the discovery back end details in the local memory;
elb-controller, after receiving the notification sent by elb-server to create the underlayback end host, reads the underlayback end details of the request from elb-manager, translates the underlayback end details into Xgw or Xgw7 recognizable configuration, and sends the configuration to the forwarding logic unit.
Further, the device further comprises:
when the traffic transfer scene is from a physical network to a virtual network, storing a mapping relation from the underwlay to the Overlay for the traffic from the underwlay to the Overlay Xgw or Xgw, completing VXLAN encapsulation at Xgw or Xgw7, and forwarding the traffic to an Overlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain a destination IP, the Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is sealed in the Vxlan encapsulation, and then the VNI is forwarded to a back-end host;
when the traffic transfer scene is from a virtual network to a physical network, storing a mapping relation from an Overlay to an Underlay for the traffic from the Overlay to the Underlay Xgw or Xgw, and completing VXLAN decapsulation and forwarding the traffic to an Underlay back-end host at Xgw or Xgw 7;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, searching Mapping table for corresponding underwlay address according to the analyzed VNI, stripping Vxlan header, translating inner layer source IP into a preset underwlay IP, forwarding, and forwarding to underwlay back-end host.
The invention has the following beneficial effects:
according to the invention, the original underway network architecture is not required to be modified, the underway network and the Overlay network are opened by using load balancing, the intercommunication between the virtual network and the physical network in the cloud is realized, the intercommunication is realized based on the load balancing, the underway address and the port are not required to be exposed outwards, the safety of underway resources is improved, the intercommunication is realized based on the load balancing, and the network architecture difference of the back-end service entity is shielded.
Drawings
The drawings are only for purposes of illustrating particular embodiments and are not to be construed as limiting the invention, like reference numerals being used to refer to like parts throughout the several views. It is apparent that the drawings in the following description are only some of the embodiments described in the embodiments of the present invention, and that other drawings may be obtained from these drawings by those of ordinary skill in the art.
FIG. 1 is a workflow diagram of a load balancing method supporting interworking of a physical network and a virtual network in accordance with an embodiment of the present invention;
fig. 2 is a data flow diagram of a load balancing method supporting interworking between a physical network and a virtual network according to an embodiment of the present invention;
fig. 3 is a structural module supporting load balancing for interworking between a physical network and a virtual network according to an embodiment of the present invention.
Detailed Description
In order to make the technical solutions of the embodiments of the present invention better understood by those skilled in the art, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments. It should be understood that the description is only illustrative and is not intended to limit the scope of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, shall fall within the scope of the invention.
In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
In the description of the present invention, it should be noted that unless explicitly stated and limited otherwise, the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc. indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, are merely for convenience in describing the present invention and simplifying the description, and do not indicate or imply that the devices or elements referred to must have a specific orientation, be configured and operated in a specific orientation, and thus should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The terms "mounted," "connected," "coupled," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the above terms in the present invention will be understood in specific cases by those of ordinary skill in the art.
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the invention. Rather, they are merely examples of methods and systems that are consistent with aspects of the invention as detailed in the accompanying claims.
According to a first embodiment of the present invention, referring to fig. 1, the present invention claims a load balancing method for supporting interworking between a physical network and a virtual network, which is characterized by comprising:
the user initiates a resource instance creation request, the resource instance creation request is sent to a resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data surface identifiable data and sends the data surface identifiable data to a forwarding logic unit;
the forwarding logic unit executes a load balancing strategy on a traffic transfer scene between the physical network and the virtual network according to the identifiable data of the data plane.
Further, the user initiates a resource instance creation request, the resource instance creation request is sent to the resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data face identifiable data and sends the data face identifiable data to the forwarding logic unit, and the method specifically comprises the following steps:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
elb-server comprises an api request processing unit which is responsible for processing requests from users to create lb related resources and managing the addresses of underway;
elb-manager is elb data reading unit responsible for providing data reading for elb-controller;
elb-controller translates the user's request data into data recognizable by the data plane, configuring the data plane forwarding rules.
In this embodiment, the load balancer in the cloud implements a management module for the Underlay address, so as to ensure intercommunication between the virtual network and the physical network in the cloud. The underway may serve as either a front end (VIP) or a back end to the outside.
And a load balancing back end of an Underlay type is newly added, so that the service network difference of the back end is shielded. Whether the Underray or the Overlay back-end, the Underray or the Overlay back-end can be freely added through the back-end without paying attention to network implementation details.
The Mapping Table is utilized to realize the Mapping of the VNI and the underway address, and the conversion problem of the Overlay and underway networks in the original load balancing scene is solved.
Further, the forwarding logic unit executes a load balancing policy on a traffic transfer scenario between the physical network and the virtual network according to the identifiable data of the data plane, and specifically includes:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
xgw or Xgw has Mapping tables including VNI and underway mappings;
xgw or Xgw are components that forward the relevant traffic of the load balancer;
underway is a service associated with a physical network;
overlay is a service associated with a virtual network.
Further, referring to fig. 2, the resource management Control unit is a Control Plane, the forwarding logic unit is a Data Plane, the user initiates a resource instance creation request, the resource instance creation request is sent to the resource management Control unit, the resource management Control unit parses the source instance creation request, translates the source instance creation request into Data face identifiable Data and sends the Data face identifiable Data to the forwarding logic unit, and the method further includes:
the user initiates a back-end request for creating the Underlay, sends the request to elb-server, elb-server to analyze the request and then confirms that the Underlay address of the request is valid, and sends notify notification to elb-manager and elb-controller;
elb-manager receives the discovery request from elb-server and reads the discovery back end details of the request from the database, and stores the discovery back end details in the local memory;
elb-controller, after receiving the notification sent by elb-server to create the underlayback end host, reads the underlayback end details of the request from elb-manager, translates the underlayback end details into Xgw or Xgw7 recognizable configuration, and sends the configuration to the forwarding logic unit.
Wherein in this embodiment, the underway address effectively refers to the underway address having been within an underly CIDR created in advance by elb-server; for example, an Underlay address field, such as 10.10.10.0/24, then 10.10.10.10/24 is valid for that address field.
The specific contents of the Notify are: backend id+version.
Xgw or Xgw is identified as underway IP+port, translating A to B using specific transformation rules.
Further, the forwarding logic unit executes a load balancing policy on a traffic delivery scenario between the physical network and the virtual network according to the identifiable data of the data plane, and further includes:
when the traffic transfer scene is from a physical network to a virtual network, storing a mapping relation from the underwlay to the Overlay for the traffic from the underwlay to the Overlay Xgw or Xgw, completing VXLAN encapsulation at Xgw or Xgw7, and forwarding the traffic to an Overlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain a destination IP, the Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is sealed in the Vxlan encapsulation, and then the VNI is forwarded to a back-end host;
when the traffic transfer scene is from a virtual network to a physical network, storing a mapping relation from an Overlay to an Underlay for the traffic from the Overlay to the Underlay Xgw or Xgw, and completing VXLAN decapsulation and forwarding the traffic to an Underlay back-end host at Xgw or Xgw 7;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, searching Mapping table for corresponding underwlay address according to the analyzed VNI, stripping Vxlan header, translating inner layer source IP into a preset underwlay IP, forwarding, and forwarding to underwlay back-end host.
In this embodiment, the Mapping table includes a correspondence between an underlay ip and a vxlan vni;
VNI refers to Vxlan encapsulation and decapsulation, which is to add/remove Vxlan headers to the header of a message.
Traffic delivery relies on vxlan encapsulation and decapsulation.
According to a second embodiment of the present invention, the present invention claims a load balancing apparatus supporting interworking of a physical network and a virtual network, comprising:
the user terminal initiates a resource instance creation request and sends the resource instance creation request to the resource management control unit;
the resource management control unit receives the resource instance creation request, analyzes the source instance creation request, translates the source instance creation request into data which can be identified by the data plane and transmits the data to the forwarding logic unit;
and the forwarding logic unit is used for receiving the data face identifiable data and executing a load balancing strategy on a traffic transmission scene between the physical network and the virtual network according to the data face identifiable data.
Further, the device further comprises:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
elb-server comprises an api request processing unit which is responsible for processing requests from users to create lb related resources and managing the addresses of underway;
elb-manager is elb data reading unit responsible for providing data reading for elb-controller;
elb-controller translates the user's request data into data recognizable by the data plane, configuring the data plane forwarding rules.
Further, the device further comprises:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
xgw or Xgw has Mapping tables including VNI and underway mappings;
xgw or Xgw are components that forward the relevant traffic of the load balancer;
underway is a service associated with a physical network;
overlay is a service associated with a virtual network.
Further, the device further comprises:
the user initiates a back-end request for creating the Underlay, sends the request to elb-server, elb-server to analyze the request and then confirms that the Underlay address of the request is valid, and sends notify notification to elb-manager and elb-controller;
elb-manager receives the discovery request from elb-server and reads the discovery back end details of the request from the database, and stores the discovery back end details in the local memory;
elb-controller, after receiving the notification sent by elb-server to create the underlayback end host, reads the underlayback end details of the request from elb-manager, translates the underlayback end details into Xgw or Xgw7 recognizable configuration, and sends the configuration to the forwarding logic unit.
Further, the device further comprises:
when the traffic transfer scene is from a physical network to a virtual network, storing a mapping relation from the underwlay to the Overlay for the traffic from the underwlay to the Overlay Xgw or Xgw, completing VXLAN encapsulation at Xgw or Xgw7, and forwarding the traffic to an Overlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain a destination IP, the Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is sealed in the Vxlan encapsulation, and then the VNI is forwarded to a back-end host;
when the traffic transfer scene is from a virtual network to a physical network, storing a mapping relation from an Overlay to an Underlay for the traffic from the Overlay to the Underlay Xgw or Xgw, and completing VXLAN decapsulation and forwarding the traffic to an Underlay back-end host at Xgw or Xgw 7;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, searching Mapping table for corresponding underwlay address according to the analyzed VNI, stripping Vxlan header, translating inner layer source IP into a preset underwlay IP, forwarding, and forwarding to underwlay back-end host.
While the applicant has described and illustrated the embodiments of the present invention in detail with reference to the drawings, it should be understood by those skilled in the art that the above embodiments are only preferred embodiments of the present invention, and the detailed description is only for the purpose of helping the reader to better understand the spirit of the present invention, and not to limit the scope of the present invention, but any improvements or modifications based on the spirit of the present invention should fall within the scope of the present invention.
Finally, it should be noted that the above embodiments are merely for illustrating the technical solution of the embodiments of the present invention, and are not limiting. Although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the embodiments of the invention, and any changes and substitutions that would be apparent to one skilled in the art are intended to be included within the scope of the present invention.

Claims (10)

1. A load balancing method supporting interworking between a physical network and a virtual network, comprising:
a user initiates a resource instance creation request, the resource instance creation request is sent to a resource management control unit, the resource management control unit analyzes the source instance creation request, translates the source instance creation request into data face identifiable data and sends the data face identifiable data to a forwarding logic unit;
and the forwarding logic unit executes a load balancing strategy on a traffic transfer scene between the physical network and the virtual network according to the identifiable data of the data plane.
2. The load balancing method for supporting interworking between a physical network and a virtual network according to claim 1, wherein the user initiates a resource instance creation request, and sends the resource instance creation request to a resource management control unit, and the resource management control unit parses the source instance creation request, translates the source instance creation request into data-plane identifiable data, and issues the data-plane identifiable data to a forwarding logic unit, and specifically comprises:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
the elb-server comprises an api request processing unit which is responsible for processing a request from a user for creating lb related resources and managing an address of the Underlay;
the elb-manager is a elb data reading unit and is responsible for providing data reading for the elb-controller;
the elb-controller translates the request data of the user into data identifiable by the data plane, and configures the forwarding rule of the data plane.
3. The load balancing method for supporting interworking between a physical network and a virtual network according to claim 1, wherein the forwarding logic unit executes a load balancing policy on a traffic delivery scenario between the physical network and the virtual network according to the data plane identifiable data, and specifically comprises:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
the Xgw or Xgw7 is provided with Mapping tables, including the Mapping of the VNI and the underway;
the Xgw or Xgw is a component for forwarding the relevant traffic of the load balancer;
the underway is a service associated with a physical network;
the Overlay is a service associated with a virtual network.
4. The method for balancing load supporting interworking between a physical network and a virtual network according to claim 2, wherein the user initiates a resource instance creation request, and sends the resource instance creation request to a resource management control unit, and the resource management control unit parses the source instance creation request, translates the source instance creation request into data-plane identifiable data, and issues the data-plane identifiable data to a forwarding logic unit, and further comprising:
a user initiates a back-end request for creating an Underlay, the request is sent to a elb-server, the elb-server confirms that an Underlay address of the request is effective after analyzing the request, and a notify notification is sent to the elb-manager and the elb-controller;
the elb-manager receives the discovery Underlay back-end host notify sent by the elb-server, reads Underlay back-end details of the request from a database, and stores the details in a local memory;
and the elb-controller reads the detail of the Underray back end of the request from the elb-manager after receiving the notification of creating the Underray back end host sent by the elb-server, translates the detail into Xgw or Xgw7 identifiable configuration and sends the configuration to a forwarding logic unit.
5. A method for load balancing supporting interworking between a physical network and a virtual network according to claim 3, wherein the forwarding logic unit performs a load balancing policy on traffic delivery scenarios between a physical network and a virtual network according to the data plane identifiable data, and further comprising:
when the traffic transfer scenario is from a physical network to a virtual network, for the traffic from the Underlay to the Overlay, the Xgw or Xgw7 stores the mapping relationship from the Underlay to the Overlay, and the VXLAN encapsulation is completed at the Xgw or Xgw7, and the traffic is forwarded to the Overlay back-end host;
the traffic entering the Xgw or Xgw7 is identified by the Xgw or Xgw7 and analyzed to obtain a destination IP, a Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is encapsulated therein, and then the VNI is forwarded to a back-end host;
when the traffic transfer scenario is from a virtual network to a physical network, for the traffic from Overlay to Underlay, the Xgw or Xgw7 stores the mapping relationship from Overlay to Underlay, and the VXLAN decapsulation is completed at Xgw or Xgw7, and the traffic is forwarded to the Underlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, find the corresponding underway address by searching Mapping table for the analyzed VNI, and translate the inner layer source IP into a preset underway IP for forwarding after Vxlan header is stripped, and forward to the underway back-end host.
6. A load balancing apparatus supporting interworking of a physical network and a virtual network, comprising:
the method comprises the steps that a user terminal initiates a resource instance creation request and sends the resource instance creation request to a resource management control unit;
the resource management control unit receives the resource instance creation request, analyzes the source instance creation request, translates the source instance creation request into data surface identifiable data and transmits the data surface identifiable data to the forwarding logic unit;
and the forwarding logic unit is used for receiving the data face identifiable data and executing a load balancing strategy on a traffic transmission scene between the physical network and the virtual network according to the data face identifiable data.
7. The load balancing apparatus supporting interworking of a physical network and a virtual network of claim 6, further comprising:
the resource management control unit comprises a elb-server, an elb-manager and an elb-controller;
the elb-server comprises an api request processing unit which is responsible for processing a request from a user for creating lb related resources and managing an address of the Underlay;
the elb-manager is a elb data reading unit and is responsible for providing data reading for the elb-controller;
the elb-controller translates the request data of the user into data identifiable by the data plane, and configures the forwarding rule of the data plane.
8. The load balancing apparatus supporting interworking of a physical network and a virtual network of claim 6, further comprising:
the forwarding logic unit includes Xgw or Xgw7, underlay, overlay;
the Xgw or Xgw7 is provided with Mapping tables, including the Mapping of the VNI and the underway;
the Xgw or Xgw is a component for forwarding the relevant traffic of the load balancer;
the underway is a service associated with a physical network;
the Overlay is a service associated with a virtual network.
9. The load balancing apparatus supporting interworking of a physical network and a virtual network of claim 7, further comprising:
a user initiates a back-end request for creating an Underlay, the request is sent to a elb-server, the elb-server confirms that an Underlay address of the request is effective after analyzing the request, and a notify notification is sent to the elb-manager and the elb-controller;
the elb-manager receives the discovery Underlay back-end host notify sent by the elb-server, reads Underlay back-end details of the request from a database, and stores the details in a local memory;
and the elb-controller reads the detail of the Underray back end of the request from the elb-manager after receiving the notification of creating the Underray back end host sent by the elb-server, translates the detail into Xgw or Xgw7 identifiable configuration and sends the configuration to a forwarding logic unit.
10. The load balancing apparatus supporting interworking of a physical network and a virtual network of claim 8, further comprising:
when the traffic transfer scenario is from a physical network to a virtual network, for the traffic from the Underlay to the Overlay, the Xgw or Xgw7 stores the mapping relationship from the Underlay to the Overlay, and the VXLAN encapsulation is completed at the Xgw or Xgw7, and the traffic is forwarded to the Overlay back-end host;
the traffic entering the Xgw or Xgw7 is identified by the Xgw or Xgw7 and analyzed to obtain a destination IP, a Mapping table is searched for the analyzed IP to find a corresponding VNI, the message is subjected to Vxlan encapsulation, the VNI is encapsulated therein, and then the VNI is forwarded to a back-end host;
when the traffic transfer scenario is from a virtual network to a physical network, for the traffic from Overlay to Underlay, the Xgw or Xgw7 stores the mapping relationship from Overlay to Underlay, and the VXLAN decapsulation is completed at Xgw or Xgw7, and the traffic is forwarded to the Underlay back-end host;
the traffic entering Xgw or Xgw7 is identified by Xgw or Xgw7 and analyzed to obtain VNI in Vxlan message, find the corresponding underway address by searching Mapping table for the analyzed VNI, and translate the inner layer source IP into a preset underway IP for forwarding after Vxlan header is stripped, and forward to the underway back-end host.
CN202311709518.8A 2023-12-13 2023-12-13 Load balancing method and device supporting intercommunication of physical network and virtual network Pending CN117792709A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311709518.8A CN117792709A (en) 2023-12-13 2023-12-13 Load balancing method and device supporting intercommunication of physical network and virtual network

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311709518.8A CN117792709A (en) 2023-12-13 2023-12-13 Load balancing method and device supporting intercommunication of physical network and virtual network

Publications (1)

Publication Number Publication Date
CN117792709A true CN117792709A (en) 2024-03-29

Family

ID=90384528

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311709518.8A Pending CN117792709A (en) 2023-12-13 2023-12-13 Load balancing method and device supporting intercommunication of physical network and virtual network

Country Status (1)

Country Link
CN (1) CN117792709A (en)

Similar Documents

Publication Publication Date Title
US9825911B1 (en) Security policy check based on communication establishment handshake packet
CN112965824B (en) Message forwarding method and device, storage medium and electronic equipment
CN110166570B (en) Service session management method and device, and electronic device
EP2901630B1 (en) Method operating in a fixed access network and user equipments
CN112040030B (en) Message transmission method and device, computer equipment and storage medium
US20150350154A1 (en) Using Distributed Network Elements to Send Authoritative DNS Responses
CN102281180A (en) Virtual network interface card (NIC) communication device applied in mutual communication of terminals in different local area networks
WO2021057348A1 (en) Server security defense method and system, communication device, and storage medium
US11025738B2 (en) Systems and methods for determining a destination location for transmission of packetized data in a network system based on an application server attribute
WO2017096888A1 (en) Method and device for implementing domain name system
US11871309B2 (en) Methods, systems, and computer readable media for network function discovery using preferred-locality information
US11496599B1 (en) Efficient flow management utilizing control packets
CN107580079A (en) A kind of message transmitting method and device
WO2020181735A1 (en) Method for providing network address translation (nat) service and controller
CN104995610A (en) Intra-platform networking
CN112583655B (en) Data transmission method and device, electronic equipment and readable storage medium
CN114025009A (en) Method, system, proxy server and device for forwarding request
JP2024511907A (en) Network function registration method, discovery method, equipment, device and medium
CN111600929B (en) Transmission line detection method, routing strategy generation method and proxy server
CN103442096B (en) NAT method based on mobile Internet and system
CN114785733B (en) Method for realizing session tracing in cross-VPC network flow forwarding
CN117792709A (en) Load balancing method and device supporting intercommunication of physical network and virtual network
US10637777B2 (en) Address converting device, information processing system, and method of providing service
US20200196135A1 (en) Enhanced connectivity in dual-mode networks for single-mode nodes
CN115442328B (en) Network address conversion method, device, gateway, medium and equipment

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