CN115473766B - Vip implementation method and system based on distributed gateway - Google Patents
Vip implementation method and system based on distributed gateway Download PDFInfo
- Publication number
- CN115473766B CN115473766B CN202211004332.8A CN202211004332A CN115473766B CN 115473766 B CN115473766 B CN 115473766B CN 202211004332 A CN202211004332 A CN 202211004332A CN 115473766 B CN115473766 B CN 115473766B
- Authority
- CN
- China
- Prior art keywords
- vip
- pod
- virtual machine
- entity
- crd
- 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
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000012544 monitoring process Methods 0.000 claims abstract description 23
- 238000001514 detection method Methods 0.000 claims description 28
- 238000012217 deletion Methods 0.000 claims description 21
- 230000037430 deletion Effects 0.000 claims description 21
- 230000008859 change Effects 0.000 claims description 14
- 238000006243 chemical reaction Methods 0.000 abstract description 3
- 230000005540 biological transmission Effects 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000002372 labelling Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0811—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking connectivity
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a vip realization method and a vip realization system based on a distributed gateway, which relate to the technical field of data exchange networks in data transmission; based on the distributed gateway virtual machine architecture of kubernetes cluster, a vip controller entity, vip CRD resources and vip agent entity pod are newly added, wherein the vip controller entity is used for monitoring the creation, updating and deleting of the vip CRD resources, and simultaneously executing the creation and deleting of the vip agent entity pod, the issuing of a corresponding flow table of a virtual machine on a network conversion entity and the like; the vip CRD resource defines basic information of the virtual machine to use vip; the vip agent entity exists in the cluster node where the virtual machine is located in a pod form and is responsible for monitoring the service condition of vip of the virtual machine and updating vip CRD resources.
Description
Technical Field
The invention discloses a method and a system, relates to the technical field of data exchange networks in data transmission, and particularly relates to a vip implementation method and a vip implementation system based on a distributed gateway.
Background
Existing edge gateway technologies typically include both centralized and distributed. In a centralized gateway scene, the gateway is usually located at a certain physical node, three layers of traffic in the north-south direction and the east-west direction of all node virtual machines pass through the centralized gateway, and the gateway converts the internal address and the external address of the virtual machines so as to forward the traffic.
In the distributed gateway scene, the nodes have a master-slave role, the gateway is positioned on each physical node, the gateway address of the internal interface of the virtual machine is positioned on the gateway of the master node, the gateway is responsible for converting the source address and the mapping address of the virtual machine, the flow of the virtual machine of the master node is forwarded through the gateway on the master node, and the flow of the virtual machine on the slave node is forwarded from the gateway entity of the slave node after replacing the gateway address and mac in the data message through the network control flow table.
In a service production environment, a distributed gateway mode is generally adopted to improve network utilization rate and reduce fault probability. However, in the existing distributed gateway scenario, the following problems exist: when vip is used for a plurality of virtual machines, because vip is randomly bound to a certain virtual machine, vip can drift to other virtual machines when the state of the virtual machine changes, such as vip drift from a master node to a slave node virtual machine, and the like. The traffic of the virtual machine realizes address conversion by binding the ovs flow table on the physical node, so that the outside of the virtual machine cannot perceive the drift of vip, and the corresponding network control flow table cannot be updated on the network switching entity of the physical node, so that vip cannot be used in the distributed gateway scene.
Disclosure of Invention
Aiming at the situation that the virtual machine cannot use the vip due to vip drifting in a distributed gateway scene, the invention provides a vip realization method and a vip realization system based on the distributed gateway, which ensure that the virtual machine uses the vip.
The specific scheme provided by the invention is as follows:
the invention provides a vip realizing method based on a distributed gateway, which is based on a distributed gateway virtual machine architecture of kubernetes clusters, creates vip CRD resources of a virtual machine, and configures the corresponding vip CRD resources for use when the virtual machine uses vip;
deploying pod of the vip agent entity to a cluster node where the virtual machine is located;
monitoring the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executing the creation and deletion of the pod of the vip agent entity, and executing corresponding operation;
monitoring the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the vip controller entity monitors the vip CRD resource change, updates a corresponding network control flow table on a physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
Further, in the vip implementation method based on the distributed gateway, the vip controller entity is utilized to monitor creation of the vip CRD resource, and corresponding operations are executed, including:
all information defined in the vip CRD resource, including virtual machine vip information,
inquiring cluster nodes where virtual machines pod are located in kubernetes clusters,
creating a pod of the vip agent entity on the cluster node, injecting virtual machine vip information in the pod of the vip agent entity,
and bridging the pod of the vip agent entity on a network switching entity of the cluster node, and issuing a rule of a network control flow table to the pod of the vip agent entity to enable the pod of the vip agent entity to be communicated with a virtual machine pod of the cluster node.
Further, in the vip implementation method based on the distributed gateway, the step of monitoring deletion of the vip CRD resource by using a vip controller entity, and executing corresponding operations includes:
inquiring all information defined by the current vip CRD resource, obtaining cluster node information,
deleting the pod of the vip agent entity corresponding to the cluster node,
deleting the network control flow table information corresponding to the pod of the vip agent entity in the network switching entity on the cluster node,
and deleting the network control flow table information containing vip in the network switching entity on the cluster node where the currently bound vip virtual machine is located.
Further, in the vip implementation method based on the distributed gateway, the monitoring, by the vip controller entity, the change of the vip CRD resource, and executing the corresponding operation, include:
acquiring updated vip CRD resource information, comparing the updated vip CRD resource information with original vip CRD resource information, acquiring cluster node information before and after updating,
deleting the pod of the vip agent entity before updating, and recreating the pod of the vip agent entity after updating.
Further, in the vip implementation method based on a distributed gateway, the monitoring the service condition of the vip of the virtual machine through the pod includes:
and performing connectivity detection on the virtual machine vip by utilizing the pod at a certain time interval, comparing the result of each connectivity detection with the result of the last connectivity detection, and updating cluster node information of the pod of the vip agent entity, where the connectivity detection is successful, into vip CRD resources.
The invention also provides a vip realizing system based on the distributed gateway, which comprises a control module and a proxy module,
the control module creates vip CRD resources of the virtual machine based on the distributed gateway virtual machine architecture of the kubernetes cluster, and configures the corresponding vip CRD resources for use when the virtual machine uses vip;
the agent module deploys the pod of the vip agent entity to the cluster node where the virtual machine is located;
the control module monitors the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executes the creation and deletion of the pod of the vip agent entity and executes corresponding operation;
the agent module monitors the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the proxy module monitors the change of the vip CRD resource through the vip controller entity, updates the corresponding network control flow table on the physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
Further, in the vip implementation system based on the distributed gateway, the control module monitors creation of the vip CRD resource by using a vip controller entity, and performs corresponding operations, including:
all information defined in the vip CRD resource, including virtual machine vip information,
inquiring cluster nodes where virtual machines pod are located in kubernetes clusters,
creating a pod of the vip agent entity on the cluster node, injecting virtual machine vip information in the pod of the vip agent entity,
and bridging the pod of the vip agent entity on a network switching entity of the cluster node, and issuing a rule of a network control flow table to the pod of the vip agent entity to enable the pod of the vip agent entity to be communicated with a virtual machine pod of the cluster node.
Further, in the vip implementation system based on the distributed gateway, the control module monitors deletion of the vip CRD resource by using a vip controller entity, and performs corresponding operations, including:
inquiring all information defined by the current vip CRD resource, obtaining cluster node information,
deleting the pod of the vip agent entity corresponding to the cluster node,
deleting the network control flow table information corresponding to the pod of the vip agent entity in the network switching entity on the cluster node,
and deleting the network control flow table information containing vip in the network switching entity on the cluster node where the currently bound vip virtual machine is located.
Further, in the vip implementation system based on the distributed gateway, the control module monitors the change of the vip CRD resource by using a vip controller entity, and performs corresponding operations, including:
acquiring updated vip CRD resource information, comparing the updated vip CRD resource information with original vip CRD resource information, acquiring cluster node information before and after updating,
deleting the pod of the vip agent entity before updating, and recreating the pod of the vip agent entity after updating.
Further, in the vip implementation system based on the distributed gateway, the agent module monitors the service condition of the vip of the virtual machine through the pod, and the vip implementation system includes:
and performing connectivity detection on the virtual machine vip by utilizing the pod at a certain time interval, comparing the result of each connectivity detection with the result of the last connectivity detection, and updating cluster node information of the pod of the vip agent entity, where the connectivity detection is successful, into vip CRD resources.
The invention has the advantages that:
the invention provides a vip realization method based on a distributed gateway, which solves the problem that a virtual machine vip in the existing distributed gateway scene cannot forward three-layer traffic in the north-south direction and the east-west direction by using a distributed gateway only by using a centralized gateway, and realizes the function of forwarding the three-layer traffic in the north-south direction and the east-west direction by using the distributed gateway by using the virtual machine vip;
the monitoring of the vip drifting condition in the virtual machine is realized, and when the vip drifts, the corresponding network control flow tables on the front and back physical machines of the virtual machine where the vip is positioned are automatically updated, so that the vip is ensured to be in an accessible state all the time;
the prior virtual machine is not required to be changed, and the virtual machine is not invaded;
and the created vip CRD resource and the like are loosely coupled with the whole system, so that the expansion and maintenance are easy.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a prior art schematic diagram of a distributed edge gateway virtual machine vip usage scenario. In the figure, ethX is used to represent the name of the network card in the physical machine or the virtual machine, which is a common labeling manner.
Fig. 2 is a schematic diagram of a virtual machine vip usage scenario of a distributed edge gateway in the method of the present invention.
Fig. 3 is a schematic flow chart of newly created vip CRD resource according to the method of the present invention.
Figure 4 is a schematic diagram of the system workflow when vip drift occurs under the method of the present invention.
Detailed Description
The present invention will be further described with reference to the accompanying drawings and specific examples, which are not intended to be limiting, so that those skilled in the art will better understand the invention and practice it.
The invention relates to the noun:
vip, virtual ip, is mainly used for switching between different services. In an efficient active-standby environment. The host service may use a VIP for access in addition to its own IP. At the time of service provision, only VIP is exposed. If the primary service is abnormal, the VIP can be quickly associated with the backup service. Thus, the service user can obtain stable service by using VIP without perception.
The vip controller entity refers to a newly added controller for monitoring vip CRD resource change in the k8s environment, and corresponding operation is executed when the resource change is monitored. For example, when a new vip CRD resource is detected, the vip controller entity performs a new corresponding flow table creation operation, and has structural and functional similarities with existing controllers such as the Deployment in k8 s.
The vip agent entity exists in k8s in a pod form and is used for executing functions such as virtual machine vip binding relation detection and the like, and is created/deleted along with the creation/deletion of vip CRD resources.
The vip CRD resource, wherein CRD is an abbreviation of CustomResourceDefinition, is one of Kubernetes and aims at the secondary development capability of the custom resource to expand the Kubernetes API, and through the CRD, new resource types can be added into the Kubernetes API without modifying the Kubernetes source code to create the custom API server. The vip CRD resource is a resource type which is self-defined in kubernetes and related to vip functions and is used for realizing the vip related functions.
The pod is the smallest unit that can be created and managed in kubernetes, is the smallest resource object model created or deployed by a user in the resource object model, and is also the resource object for running the containerized application on kubernetes, and general services run in kubernetes in the form of a pod.
The invention provides a vip realizing method based on a distributed gateway, which is based on a distributed gateway virtual machine architecture of kubernetes clusters, creates vip CRD resources of a virtual machine, and configures the corresponding vip CRD resources for use when the virtual machine uses vip;
deploying pod of the vip agent entity to a cluster node where the virtual machine is located;
monitoring the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executing the creation and deletion of the pod of the vip agent entity, and executing corresponding operation;
monitoring the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the vip controller entity monitors the vip CRD resource change, updates a corresponding network control flow table on a physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
The method is based on a distributed gateway virtual machine architecture of kubernetes clusters, and a vip controller entity, vip CRD resources and vip agent entity pod are newly added, wherein the vip controller entity is used for monitoring the creation, updating and deletion of the vip CRD resources, simultaneously executing the creation and deletion of the vip agent entity pod, issuing a corresponding flow table of a virtual machine on a network conversion entity and the like; the vip CRD resource defines basic information of the virtual machine to use vip; the vip agent entity exists in the cluster node where the virtual machine is located in a pod form and is responsible for monitoring the service condition of vip of the virtual machine and updating vip CRD resources.
In specific applications, in some embodiments of the method of the present invention, reference may be made to fig. 2, in which eth and ethX are used to represent names of network cards in physical machines or virtual machines, which are commonly used as labeling methods.
The method comprises the steps of adding a vip controller entity, vip CRD resources and a pod of a vip agent entity on an existing distributed gateway virtual machine architecture, and monitoring the vip service condition of a virtual machine, wherein the vip controller entity is used for monitoring the creation, update and deletion of the vip CRD resources and simultaneously executing corresponding operations, the CRD is used as a resource type in a kubernetes cluster, and the expansion of kubernetesapi can be realized through a custom CRD form, so that a custom function is realized. Wherein the vip CRD resource may define basic information including ip of vip used by the virtual machine, internet address of the virtual machine, mac address of the virtual machine, name, namespace, etc. in yaml. When the virtual machine uses the vip, the configuration of the vip CRD file is completed according to the information items defined in the vip CRD resource.
Further, in the vip implementation method based on the distributed gateway, the vip controller entity is utilized to monitor creation of the vip CRD resource, and corresponding operations are executed, which specifically include:
step 11: all information defined in the vip CRD resource is acquired, including virtual machine vip information, and Internalip information is read,
step 12: inquiring etcd of kubernetes cluster, determining cluster node where virtual machine pod is located according to the internip information obtained in step 1,
step 13: creating a pod of the vip agent entity on the cluster node in a DaemonSet mode, injecting virtual machine vip information in the pod of the vip agent entity,
step 14: and bridging the pod of the vip agent entity on a network switching entity of the cluster node, and issuing a rule of a network control flow table to the pod of the vip agent entity, so that the pod of the vip agent entity can be communicated with a virtual machine pod of the cluster node, and real-time return information of the pod of the vip agent entity can be monitored.
Further, in the vip implementation method based on the distributed gateway, the vip controller entity is used for monitoring deletion of the vip CRD resource, and corresponding operations are executed, and the method specifically includes:
step 21: inquiring all information defined by the current vip CRD resource, including state information, obtaining cluster node information of the vip agent entity pod,
step 22: deleting the pod of the vip agent entity corresponding to the cluster node,
step 23: deleting the network control flow table information corresponding to the pod of the vip agent entity in the network switching entity on the cluster node,
step 24: and deleting the network control flow table information containing vip in the network switching entity on the cluster node where the currently bound vip virtual machine is located.
Further, in the vip implementation method based on the distributed gateway, the vip controller entity is used for monitoring the change of the vip CRD resource, and executing corresponding operations, wherein updating may include manually modifying the vip CRD resource and automatically modifying the vip CRD state when the virtual machine vip is drifting, and the method specifically includes:
step 31: acquiring updated vip CRD resource information, comparing the updated vip CRD resource information with original vip CRD resource information, such as vip address change, virtual machine ip address change, vip drift and the like, acquiring cluster node information before and after updating,
step 32: and deleting the pod of the vip agent entity before updating according to the cluster node and the updated vip CRD resource item obtained in the step 31, and recreating the pod of the vip agent entity after updating.
Further, in the vip implementation method based on the distributed gateway, the vip agent entity exists in the cluster node where the virtual machine is located in a pod form, and has the same life cycle as the vip CRD resource, and when the pod of the vip agent entity is started, the pod workflow is as follows:
step 41: the vip detection program in the pod is automatically started, connectivity detection is carried out on the vip of the virtual machine, and the detection result is recorded;
step 42: only the pod associated with the virtual machine bound with the vip can detect success, the vip agent entity pod updates the cluster node information of the detection success into the vip CRD resource, other detection failure nodes pod are not fed back, and at the moment, the vip controller entity monitors the CRD resource change and executes corresponding operation;
step 43: and then, the pod detects connectivity of the virtual machine vip at a certain time interval, and compares each time with the last result, for example, when the vip in the virtual machine drifts, the vip agent entity pod detection result on the physical machine of the virtual machine bound by the vip is changed from non-through to on, at this time, the pod changes the vip binding relation in the vip CRD resource into a new cluster node, at this time, the vip controller entity monitors the CRD resource change, performs corresponding operations, for example, the vip controller entity acquires the cluster node where the updated vip is located, judges the master-slave role of the cluster node, and sends out a network control flow table containing vip information on the network switching entity of the cluster node, so that the north-south and east-west three-layer traffic of the vip of the virtual machine can be forwarded through the network switching entity.
The invention also provides a vip realizing system based on the distributed gateway, which comprises a control module and a proxy module,
the control module creates vip CRD resources of the virtual machine based on the distributed gateway virtual machine architecture of the kubernetes cluster, and configures the corresponding vip CRD resources for use when the virtual machine uses vip;
the agent module deploys the pod of the vip agent entity to the cluster node where the virtual machine is located;
the control module monitors the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executes the creation and deletion of the pod of the vip agent entity and executes corresponding operation;
the agent module monitors the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the proxy module monitors the change of the vip CRD resource through the vip controller entity, updates the corresponding network control flow table on the physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
The content of information interaction and execution process between the modules in the system is based on the same concept as the method embodiment of the present invention, and specific content can be referred to the description in the method embodiment of the present invention, which is not repeated here.
Similarly, the system solves the problem that the virtual machine vip in the existing distributed gateway scene cannot use the distributed gateway and can only use the centralized gateway to forward the three-layer traffic in the north-south direction and the east-west direction, and realizes the function of forwarding the three-layer traffic in the north-south direction and the east-west direction by using the distributed gateway by the virtual machine vip;
the monitoring of the vip drifting condition in the virtual machine is realized, and when the vip drifts, the corresponding network control flow tables on the front and back physical machines of the virtual machine where the vip is positioned are automatically updated, so that the vip is ensured to be in an accessible state all the time;
the prior virtual machine is not required to be changed, and the virtual machine is not invaded;
and the created vip CRD resource and the like are loosely coupled with the whole system, so that the expansion and maintenance are easy.
It should be noted that not all the steps and modules in the above processes and the system structures are necessary, and some steps or modules may be omitted according to actual needs. The execution sequence of the steps is not fixed and can be adjusted as required. The system structure described in the above embodiments may be a physical structure or a logical structure, that is, some modules may be implemented by the same physical entity, or some modules may be implemented by multiple physical entities, or may be implemented jointly by some components in multiple independent devices.
The above-described embodiments are merely preferred embodiments for fully explaining the present invention, and the scope of the present invention is not limited thereto. Equivalent substitutions and modifications will occur to those skilled in the art based on the present invention, and are intended to be within the scope of the present invention. The protection scope of the invention is subject to the claims.
Claims (10)
1. A vip realizing method based on a distributed gateway is characterized in that a vip CRD resource of a virtual machine is created based on a distributed gateway virtual machine architecture of kubernetes clusters, and the vip CRD resource is configured correspondingly for use when the virtual machine uses vip;
deploying pod of the vip agent entity to a cluster node where the virtual machine is located;
monitoring the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executing the creation and deletion of the pod of the vip agent entity, and executing corresponding operation;
monitoring the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the vip controller entity monitors the vip CRD resource update, updates a corresponding network control flow table on a physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
2. The vip implementation method based on the distributed gateway according to claim 1, wherein the monitoring the creation of the vip CRD resource by the vip controller entity, performing corresponding operations, includes:
all information defined in the vip CRD resource, including virtual machine vip information,
inquiring cluster nodes where virtual machines pod are located in kubernetes clusters,
creating a pod of the vip agent entity on the cluster node, injecting virtual machine vip information in the pod of the vip agent entity,
and bridging the pod of the vip agent entity on a network switching entity of the cluster node, and issuing a rule of a network control flow table to the pod of the vip agent entity to enable the pod of the vip agent entity to be communicated with a virtual machine pod of the cluster node.
3. The vip realizing method based on the distributed gateway according to claim 1, wherein the monitoring the deletion of the vip CRD resource by the vip controller entity, performing the corresponding operation includes:
inquiring all information defined by the current vip CRD resource, obtaining cluster node information,
deleting the pod of the vip agent entity corresponding to the cluster node,
deleting the network control flow table information corresponding to the pod of the vip agent entity in the network switching entity on the cluster node,
and deleting the network control flow table information containing vip in the network switching entity on the cluster node where the currently bound vip virtual machine is located.
4. The vip realizing method based on the distributed gateway according to claim 1, wherein the step of using the vip controller entity to monitor the update of the vip CRD resource, and performing the corresponding operation comprises:
acquiring updated vip CRD resource information, comparing the updated vip CRD resource information with original vip CRD resource information, acquiring cluster node information before and after updating,
deleting the pod of the vip agent entity before updating, and recreating the pod of the vip agent entity after updating.
5. The vip implementation method based on the distributed gateway according to claim 1, wherein the monitoring the service condition of the virtual machine vip through the pod comprises:
and performing connectivity detection on the virtual machine vip by utilizing the pod at a certain time interval, comparing the result of each connectivity detection with the result of the last connectivity detection, and updating cluster node information of the pod of the vip agent entity with successful connectivity detection into vip CRD resources.
6. A vip realizing system based on a distributed gateway is characterized by comprising a control module and a proxy module,
the control module creates vip CRD resources of the virtual machine based on the distributed gateway virtual machine architecture of the kubernetes cluster, and configures the corresponding vip CRD resources for use when the virtual machine uses vip;
the agent module deploys the pod of the vip agent entity to the cluster node where the virtual machine is located;
the control module monitors the creation, updating and deletion of the vip CRD resource by utilizing a vip controller entity, executes the creation and deletion of the pod of the vip agent entity and executes corresponding operation;
the agent module monitors the service condition of the virtual machine vip through the pod: performing connectivity detection on the virtual machine vip by using the pod, wherein only the pod associated with the virtual machine binding the vip is successfully detected, and the pod updates cluster node information of the virtual machine binding the vip into vip CRD resources;
the proxy module monitors the change of the vip CRD resource through the vip controller entity, updates the corresponding network control flow table on the physical machine of the virtual machine binding the vip, and ensures that the vip is always in an access state.
7. The vip realizing system based on the distributed gateway of claim 6, wherein the control module monitors creation of the vip CRD resource by a vip controller entity, performs corresponding operations, including:
all information defined in the vip CRD resource, including virtual machine vip information,
inquiring cluster nodes where virtual machines pod are located in kubernetes clusters,
creating a pod of the vip agent entity on the cluster node, injecting virtual machine vip information in the pod of the vip agent entity,
and bridging the pod of the vip agent entity on a network switching entity of the cluster node, and issuing a rule of a network control flow table to the pod of the vip agent entity to enable the pod of the vip agent entity to be communicated with a virtual machine pod of the cluster node.
8. The vip realizing system based on the distributed gateway of claim 6, wherein the control module monitors deletion of the vip CRD resource by a vip controller entity, performs corresponding operations, including:
inquiring all information defined by the current vip CRD resource, obtaining cluster node information,
deleting the pod of the vip agent entity corresponding to the cluster node,
deleting the network control flow table information corresponding to the pod of the vip agent entity in the network switching entity on the cluster node,
and deleting the network control flow table information containing vip in the network switching entity on the cluster node where the currently bound vip virtual machine is located.
9. The vip realizing system based on the distributed gateway of claim 6, wherein the control module monitors updating of the vip CRD resource by a vip controller entity, and performs corresponding operations comprising:
acquiring updated vip CRD resource information, comparing the updated vip CRD resource information with original vip CRD resource information, acquiring cluster node information before and after updating,
deleting the pod of the vip agent entity before updating, and recreating the pod of the vip agent entity after updating.
10. The vip realizing system based on the distributed gateway as claimed in claim 6, wherein the proxy module monitors the service condition of the virtual machine vip through the pod, comprising: and performing connectivity detection on the virtual machine vip by utilizing the pod at a certain time interval, comparing the result of each connectivity detection with the result of the last connectivity detection, and updating cluster node information of the pod of the vip agent entity with successful connectivity detection into vip CRD resources.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211004332.8A CN115473766B (en) | 2022-08-22 | 2022-08-22 | Vip implementation method and system based on distributed gateway |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202211004332.8A CN115473766B (en) | 2022-08-22 | 2022-08-22 | Vip implementation method and system based on distributed gateway |
Publications (2)
Publication Number | Publication Date |
---|---|
CN115473766A CN115473766A (en) | 2022-12-13 |
CN115473766B true CN115473766B (en) | 2024-01-26 |
Family
ID=84366468
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202211004332.8A Active CN115473766B (en) | 2022-08-22 | 2022-08-22 | Vip implementation method and system based on distributed gateway |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN115473766B (en) |
Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102710814A (en) * | 2012-06-21 | 2012-10-03 | 奇智软件(北京)有限公司 | Method and device for controlling Internet protocol (IP) address of virtual machine |
CN103812704A (en) * | 2014-02-25 | 2014-05-21 | 国云科技股份有限公司 | Public network IP (Internet Protocol) dynamic management method for virtual machine |
CN104243427A (en) * | 2013-06-19 | 2014-12-24 | 日电(中国)有限公司 | Virtual machine online migration method and data package transmission method and device |
CN104301445A (en) * | 2013-07-15 | 2015-01-21 | 北京邮电大学 | Mobile Internet data transmission method and system |
CN104702476A (en) * | 2013-12-05 | 2015-06-10 | 华为技术有限公司 | Distributed gateway, message processing method and message processing device based on distributed gateway |
CA2910654A1 (en) * | 2014-11-10 | 2016-05-10 | Investel Capital Corporation | System and method for migrating a voice over data call between distinct data networks, and a voice over data call intermediating system and method therefor |
CN105592139A (en) * | 2015-10-28 | 2016-05-18 | 杭州华三通信技术有限公司 | HA implementation method and device of distributed file system management platform |
CN105812340A (en) * | 2014-12-31 | 2016-07-27 | 杭州华三通信技术有限公司 | Access method and device for virtual network to extranet |
CN106487695A (en) * | 2015-08-25 | 2017-03-08 | 华为技术有限公司 | A kind of data transmission method, virtual network managing device and data transmission system |
CN107147533A (en) * | 2017-05-31 | 2017-09-08 | 郑州云海信息技术有限公司 | A kind of flow table configuration distributing method and system based on SDN frameworks |
CN107947961A (en) * | 2017-10-17 | 2018-04-20 | 上海数讯信息技术有限公司 | Kubernetes Network Management System and method based on SDN |
CN109067827A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on Kubernetes and OpenStack container cloud platform multi-tenant construction method, medium, equipment |
CN109067828A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on the more cluster construction methods of Kubernetes and OpenStack container cloud platform, medium, equipment |
CN109446178A (en) * | 2018-11-13 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of Hadoop object storage high availability method, system, device and readable storage medium storing program for executing |
CN110198329A (en) * | 2018-03-26 | 2019-09-03 | 腾讯科技(深圳)有限公司 | Database deployment method, device and system, electronic equipment and readable medium |
CN111163189A (en) * | 2020-01-07 | 2020-05-15 | 上海道客网络科技有限公司 | IP monitoring and recycling system and method based on network name space management and control |
CN111314098A (en) * | 2018-12-11 | 2020-06-19 | 杭州海康威视系统技术有限公司 | Method and device for realizing VIP address drift in HA system |
CN111612466A (en) * | 2020-01-17 | 2020-09-01 | 厦门潭宏信息科技有限公司 | Consensus and resource transmission method, device and storage medium |
CN111698164A (en) * | 2020-06-11 | 2020-09-22 | 北京金山云网络技术有限公司 | Network routing method and device of virtual machine and management server |
CN111736944A (en) * | 2019-03-25 | 2020-10-02 | 北京奇虎科技有限公司 | Docker container positioning method and device based on Kubernetes |
CN112422683A (en) * | 2020-11-19 | 2021-02-26 | 浪潮云信息技术股份公司 | API gateway service high-availability implementation method under K8S environment |
CN112583655A (en) * | 2020-11-02 | 2021-03-30 | 北京迈格威科技有限公司 | Data transmission method and device, electronic equipment and readable storage medium |
CN112820366A (en) * | 2020-12-23 | 2021-05-18 | 京东方科技集团股份有限公司 | Data processing method, device, system, equipment and storage medium |
CN112910939A (en) * | 2019-12-03 | 2021-06-04 | 华为技术有限公司 | Data processing method and related device |
CN113572831A (en) * | 2021-07-21 | 2021-10-29 | 重庆星环人工智能科技研究院有限公司 | Communication method between Kubernetes clusters, computer equipment and medium |
CN114465895A (en) * | 2022-03-03 | 2022-05-10 | 上海微盟企业发展有限公司 | Request distribution method, device, equipment and storage medium based on micro service |
CN114500523A (en) * | 2021-11-29 | 2022-05-13 | 上海浦东发展银行股份有限公司 | Fixed IP application release method based on container cloud platform |
CN114640678A (en) * | 2022-03-14 | 2022-06-17 | 明阳产业技术研究院(沈阳)有限公司 | Pod management method, device and medium based on SR-IOV |
CN114780489A (en) * | 2022-06-17 | 2022-07-22 | 苏州思萃工业互联网技术研究所有限公司 | Method and device for realizing distributed block storage bottom layer GC |
CN114924839A (en) * | 2022-05-30 | 2022-08-19 | 苏州思萃工业互联网技术研究所有限公司 | Method and device for realizing designated migration of kubernets cluster pod |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9898317B2 (en) * | 2012-06-06 | 2018-02-20 | Juniper Networks, Inc. | Physical path determination for virtual network packet flows |
CN103731353B (en) * | 2013-12-26 | 2017-07-14 | 华为技术有限公司 | The physical address acquisition methods of virtual machine |
US10931478B2 (en) * | 2014-10-14 | 2021-02-23 | Mido Holdings Ltd. | System and method for distributed flow state P2P setup in virtual networks |
-
2022
- 2022-08-22 CN CN202211004332.8A patent/CN115473766B/en active Active
Patent Citations (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102710814A (en) * | 2012-06-21 | 2012-10-03 | 奇智软件(北京)有限公司 | Method and device for controlling Internet protocol (IP) address of virtual machine |
CN104243427A (en) * | 2013-06-19 | 2014-12-24 | 日电(中国)有限公司 | Virtual machine online migration method and data package transmission method and device |
CN104301445A (en) * | 2013-07-15 | 2015-01-21 | 北京邮电大学 | Mobile Internet data transmission method and system |
CN104702476A (en) * | 2013-12-05 | 2015-06-10 | 华为技术有限公司 | Distributed gateway, message processing method and message processing device based on distributed gateway |
CN103812704A (en) * | 2014-02-25 | 2014-05-21 | 国云科技股份有限公司 | Public network IP (Internet Protocol) dynamic management method for virtual machine |
CA2910654A1 (en) * | 2014-11-10 | 2016-05-10 | Investel Capital Corporation | System and method for migrating a voice over data call between distinct data networks, and a voice over data call intermediating system and method therefor |
CN105812340A (en) * | 2014-12-31 | 2016-07-27 | 杭州华三通信技术有限公司 | Access method and device for virtual network to extranet |
CN106487695A (en) * | 2015-08-25 | 2017-03-08 | 华为技术有限公司 | A kind of data transmission method, virtual network managing device and data transmission system |
CN105592139A (en) * | 2015-10-28 | 2016-05-18 | 杭州华三通信技术有限公司 | HA implementation method and device of distributed file system management platform |
CN107147533A (en) * | 2017-05-31 | 2017-09-08 | 郑州云海信息技术有限公司 | A kind of flow table configuration distributing method and system based on SDN frameworks |
CN107947961A (en) * | 2017-10-17 | 2018-04-20 | 上海数讯信息技术有限公司 | Kubernetes Network Management System and method based on SDN |
CN110198329A (en) * | 2018-03-26 | 2019-09-03 | 腾讯科技(深圳)有限公司 | Database deployment method, device and system, electronic equipment and readable medium |
CN109067827A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on Kubernetes and OpenStack container cloud platform multi-tenant construction method, medium, equipment |
CN109067828A (en) * | 2018-06-22 | 2018-12-21 | 杭州才云科技有限公司 | Based on the more cluster construction methods of Kubernetes and OpenStack container cloud platform, medium, equipment |
CN109446178A (en) * | 2018-11-13 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of Hadoop object storage high availability method, system, device and readable storage medium storing program for executing |
CN111314098A (en) * | 2018-12-11 | 2020-06-19 | 杭州海康威视系统技术有限公司 | Method and device for realizing VIP address drift in HA system |
CN111736944A (en) * | 2019-03-25 | 2020-10-02 | 北京奇虎科技有限公司 | Docker container positioning method and device based on Kubernetes |
CN112910939A (en) * | 2019-12-03 | 2021-06-04 | 华为技术有限公司 | Data processing method and related device |
CN111163189A (en) * | 2020-01-07 | 2020-05-15 | 上海道客网络科技有限公司 | IP monitoring and recycling system and method based on network name space management and control |
CN111612466A (en) * | 2020-01-17 | 2020-09-01 | 厦门潭宏信息科技有限公司 | Consensus and resource transmission method, device and storage medium |
CN111698164A (en) * | 2020-06-11 | 2020-09-22 | 北京金山云网络技术有限公司 | Network routing method and device of virtual machine and management server |
CN112583655A (en) * | 2020-11-02 | 2021-03-30 | 北京迈格威科技有限公司 | Data transmission method and device, electronic equipment and readable storage medium |
CN112422683A (en) * | 2020-11-19 | 2021-02-26 | 浪潮云信息技术股份公司 | API gateway service high-availability implementation method under K8S environment |
CN112820366A (en) * | 2020-12-23 | 2021-05-18 | 京东方科技集团股份有限公司 | Data processing method, device, system, equipment and storage medium |
CN113572831A (en) * | 2021-07-21 | 2021-10-29 | 重庆星环人工智能科技研究院有限公司 | Communication method between Kubernetes clusters, computer equipment and medium |
CN114500523A (en) * | 2021-11-29 | 2022-05-13 | 上海浦东发展银行股份有限公司 | Fixed IP application release method based on container cloud platform |
CN114465895A (en) * | 2022-03-03 | 2022-05-10 | 上海微盟企业发展有限公司 | Request distribution method, device, equipment and storage medium based on micro service |
CN114640678A (en) * | 2022-03-14 | 2022-06-17 | 明阳产业技术研究院(沈阳)有限公司 | Pod management method, device and medium based on SR-IOV |
CN114924839A (en) * | 2022-05-30 | 2022-08-19 | 苏州思萃工业互联网技术研究所有限公司 | Method and device for realizing designated migration of kubernets cluster pod |
CN114780489A (en) * | 2022-06-17 | 2022-07-22 | 苏州思萃工业互联网技术研究所有限公司 | Method and device for realizing distributed block storage bottom layer GC |
Non-Patent Citations (3)
Title |
---|
Gatewaying the Wireless Sensor Networks;Wenlong Yue;《2013 IEEE 9th International Conference on Mobile Ad-hoc and Sensor Networks》;全文 * |
天然气分布式能源站蓄冷方案研究及应用;王学勤;江婷;徐静静;邓亚男;胡永锋;;华电技术(第11期);全文 * |
边界网关协议分布式设计与实现;游建平;《保密科学技术》;全文 * |
Also Published As
Publication number | Publication date |
---|---|
CN115473766A (en) | 2022-12-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN106331098B (en) | Server cluster system | |
CN100426751C (en) | Method for ensuring accordant configuration information in cluster system | |
CN104935672A (en) | High available realizing method and equipment of load balancing service | |
CN111984274B (en) | Method and device for automatically deploying ETCD cluster by one key | |
CN107203617B (en) | The online migratory system of mysql and method based on MHA | |
JP2008210412A (en) | Method of controlling remotely accessible resource in multi-node distributed data processing system | |
CN112003728B (en) | Kubernetes cluster-based application master and standby implementation method and device | |
CN112698992B (en) | Disaster recovery management method and related device for cloud cluster | |
CN109684131B (en) | Dynamic reconstruction method of hybrid structure network fault-tolerant system based on table driving | |
CN111966467B (en) | Method and device for disaster recovery based on kubernetes container platform | |
CN109446170A (en) | A kind of profile data synchronous method and equipment | |
CN103036934A (en) | Wide area network clustered deployment system and method based on mirror image | |
CN104023061A (en) | High availability cluster scheme of OSS (Open Storage service) for LUSTRE | |
CN117130730A (en) | Metadata management method for federal Kubernetes cluster | |
CN102487332B (en) | Fault processing method, apparatus thereof and system thereof | |
CN113835834A (en) | K8S container cluster-based computing node capacity expansion method and system | |
CN115473766B (en) | Vip implementation method and system based on distributed gateway | |
CN116095145B (en) | Data control method and system of VPC cluster | |
CN115048190B (en) | Virtual machine snapshot management method, system and computer readable medium | |
CN114124803B (en) | Device management method and device, electronic device and storage medium | |
CN101420327A (en) | Method for avoiding routing oscillation in smooth restarting process and smooth restarting equipment | |
CN110399254A (en) | A kind of server CMC dual-locomotive heat activating method, system, terminal and storage medium | |
CN112491633B (en) | Fault recovery method, system and related components of multi-node cluster | |
CN114036129A (en) | Database switching method for reducing data loss | |
CN115550371B (en) | Pod scheduling method and system based on Kubernetes and cloud platform |
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 |