CN114301919A - Kubernetes-based ICE (Internet encryption and encryption Equipment) frame improvement method - Google Patents
Kubernetes-based ICE (Internet encryption and encryption Equipment) frame improvement method Download PDFInfo
- Publication number
- CN114301919A CN114301919A CN202111655705.3A CN202111655705A CN114301919A CN 114301919 A CN114301919 A CN 114301919A CN 202111655705 A CN202111655705 A CN 202111655705A CN 114301919 A CN114301919 A CN 114301919A
- Authority
- CN
- China
- Prior art keywords
- ice
- zeroc
- address
- monitoring
- client
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000006872 improvement Effects 0.000 title claims abstract description 24
- 238000012544 monitoring process Methods 0.000 claims abstract description 73
- 238000004590 computer program Methods 0.000 claims description 5
- 238000013459 approach Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 5
- 238000012986 modification Methods 0.000 description 5
- 230000004048 modification Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides an ICE (Internet of things) framework improvement method based on Kubernetes, wherein the method comprises the following steps: removing a registration center of a Zeroc ICE server; starting a first monitoring thread; monitoring a registration center; when the service node IP changes, acquiring a first IP address and updating the first IP address into a local cache of the client; the client uses all IP addresses to load balance to the Zeroc ICE service end node through a direct proxy approach provided by Zeroc ICE. The problem that Zeroc ICE and Kubernets are incompatible in the prior art is solved, in a Kubernets cluster, load balancing of a Zeroc ICE client side accessing a server side fails, and the technical problem that a node IP cannot be updated to a client side cache in time when a server side node changes is solved.
Description
Technical Field
The invention relates to the field of artificial intelligence, in particular to an ICE (Internet of things) framework improvement method based on Kubernetes.
Background
Zeroc ICE is a TCP protocol-based rpc (remote Procedure call) framework, mainly solving the problem of remote invocation of distributed services. Zeroc ICE contains a registry program (responsible for storing service end IP corresponding to service), Node nodes (corresponding to physical servers), and data transmission protocols (including data format specifications and communication protocols). The Zeroc ICE has the characteristic that one service node corresponds to one server, and when the Zeroc ICE service node is expanded, the server needs to be added, so that the cost is increased. And when the nodes are expanded, servers need to be manually appointed for the Zeroc ICE service, and the expansion operation is complicated. While deployment in kubernets may solve the above problem, Zeroc ICE services are not fully compatible with kubernets.
However, in the process of implementing the technical scheme of the invention of the embodiment of the present application, it is found that the above technology has at least the following technical problems:
the problem that Zeroc ICE and Kubernets are incompatible exists, in a Kubernets cluster, load balance of a Zeroc ICE client side accessing a server side fails, and when a server side node changes, a node IP cannot be updated into a client side cache timely.
Disclosure of Invention
The embodiment of the application provides an ICE framework improvement method based on Kubernetes, and solves the technical problems that in the prior art, Zeroc ICE and Kubernetes are incompatible, in a Kubernetes cluster, load balance failure occurs when a Zeroc ICE client accesses a server, and when a server node is changed, a node IP cannot be updated to a client cache in time. The method achieves the technical effects that improvement is made on the basis of a Zeroc ICE framework, the Zeroc ICE framework can be deployed in a Kubernetes container cluster, the problem that Zeroc ICE and Kubernetes are incompatible is solved, load balancing failure of a client calling Zeroc ICE service in the Kubernetes is avoided, and the node IP is updated to the client cache in time when a service end node changes.
In view of the above problems, the embodiments of the present application provide an ICE framework improvement method based on Kubernetes.
In a first aspect, an embodiment of the present application provides an ICE framework improving method based on Kubernetes, where the method includes: removing a registration center of a Zeroc ICE server; starting a first monitoring thread at a client; monitoring the registration center according to the first monitoring thread; when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address; and the client uses all IP addresses corresponding to the service nodes in the local cache and performs load balancing on the Zeroc ICE service end node through a direct proxy mode provided by Zeroc ICE.
On the other hand, an embodiment of the present application provides an ICE framework improving system based on Kubernetes, where the system includes: the first execution unit is used for removing a registration center of a Zeroc ICE server; the second execution unit is used for starting a first monitoring thread at the client; the first monitoring unit is used for monitoring the registration center according to the first monitoring thread; a first obtaining unit, configured to obtain a first IP address when a service node IP of the registry changes, and update the first IP address to a local cache of the client, where the first IP address is a new IP address; and the third execution unit is used for the client to use all IP addresses corresponding to the service nodes in the local cache and balance the load to the Zeroc ICE service node in a direct proxy mode provided by Zeroc ICE.
In a third aspect, the present invention provides a Kubernetes-based ICE framework improvement system, comprising a memory, a processor and a computer program stored on the memory and operable on the processor, wherein the processor implements the steps of the method of the first aspect when executing the program.
One or more technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:
the registration center without a Zeroc ICE server is adopted; starting a first monitoring thread at a client; monitoring the registration center according to the first monitoring thread; when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address; the client uses all IP addresses corresponding to the service nodes in the local cache, and the technical scheme that the load is balanced to the Zeroc ICE service end node in a direct proxy mode provided by the Zeroc ICE is provided.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
Fig. 1 is a schematic flow chart of an ICE framework improvement method based on Kubernetes according to an embodiment of the present application;
fig. 2 is a schematic diagram of accessing the Zeroc ICE server from within a kubernets cluster according to an ICE framework improvement method based on kubernets in the embodiment of the present application;
fig. 3 is a schematic diagram illustrating that the Zeroc ICE server is accessed from outside the kubernets cluster based on the kubernets ICE framework improvement method in the embodiment of the present application;
FIG. 4 is a schematic structural diagram of an ICE framework improvement system based on Kubernetes according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an exemplary electronic device according to an embodiment of the present application.
Description of reference numerals: the device comprises a first execution unit 11, a second execution unit 12, a first monitoring unit 13, a first obtaining unit 14, a third execution unit 15, an electronic device 300, a memory 301, a processor 302, a communication interface 303, and a bus architecture 304.
Detailed Description
The embodiment of the application provides an ICE framework improvement method based on Kubernetes, and solves the technical problems that in the prior art, Zeroc ICE and Kubernetes are incompatible, in a Kubernetes cluster, load balance failure occurs when a Zeroc ICE client accesses a server, and when a server node is changed, a node IP cannot be updated to a client cache in time. The method achieves the technical effects that improvement is made on the basis of a Zeroc ICE framework, the Zeroc ICE framework can be deployed in a Kubernetes container cluster, the problem that Zeroc ICE and Kubernetes are incompatible is solved, load balancing failure of a client calling Zeroc ICE service in the Kubernetes is avoided, and the node IP is updated to the client cache in time when a service end node changes.
Summary of the application
The Zeroc ICE has the characteristic that one service node corresponds to one server, and when the Zeroc ICE service node is expanded, the server needs to be added, so that the cost is increased. And when the nodes are expanded, servers need to be manually appointed for the Zeroc ICE service, and the expansion operation is complicated. While deployment in kubernets may solve the above problem, Zeroc ICE services are not fully compatible with kubernets. The problem that Zeroc ICE and Kubernets are incompatible exists in the prior art, and in a Kubernets cluster, the technical problems that Zeroc ICE client-side access server-side load balance fails and a node IP cannot be updated into a client-side cache timely when a server-side node changes exist.
In view of the above technical problems, the technical solution provided by the present application has the following general idea:
the embodiment of the application provides an ICE (internal Integrated Circuit) frame improvement method based on Kubernetes, which comprises the following steps: removing a registration center of a Zeroc ICE server; starting a first monitoring thread at a client; monitoring the registration center according to the first monitoring thread; when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address; and the client uses all IP addresses corresponding to the service nodes in the local cache and performs load balancing on the Zeroc ICE service end node through a direct proxy mode provided by Zeroc ICE.
Having thus described the general principles of the present application, various non-limiting embodiments thereof will now be described in detail with reference to the accompanying drawings.
Example one
As shown in fig. 1, an embodiment of the present application provides an ICE framework improving method based on Kubernetes, where the method includes:
s100: removing a registration center of a Zeroc ICE server;
further, after removing the registration center of the Zeroc ICE server, step S100 includes:
s110: initiated by Icebox, registers the service into the registry of kubernets.
In particular, Zeroc ICE is a TCP protocol-based rpc (remote Procedure call) framework, mainly solving the problem of distributed service remote invocation. Zeroc ICE contains a registry program (responsible for storing service end IP corresponding to service), Node nodes (corresponding to physical servers), and data transmission protocols (including data format specifications and communication protocols).
Kubernetes is an open source platform for automatic deployment, capacity expansion and operation and maintenance of container clusters. Through Kubernetes, you can respond to user demands quickly and effectively; deploy your application quickly and expecting; expand your application very quickly; seamlessly docking new application functions; the resources are saved, and the use of hardware resources is optimized. And transforming a Zeroc ICE server, removing a registration center of the Zeroc ICE, starting in an Icebox mode, and automatically registering the service into the registration center of Kubernetes. Instead of using a registration center with zerocICE itself, using a registration center with Kubernetes itself can solve the problem of incompatibility between Zeroc ICE and Kubernetes.
S200: starting a first monitoring thread at a client;
s300: monitoring the registration center according to the first monitoring thread;
specifically, the client may be an ICE client, and a thread, that is, the first listening thread, is started at the client, and a change of a kubernets registry may be listened through the first listening thread from inside or outside of a kubernets cluster. And a foundation is laid for the thread to automatically acquire a new IP address.
S400: when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address;
specifically, in order to solve the problem that the node IP cannot be updated into the client cache in time when the service node changes, when the service node IP of the kubernets registry changes, the first monitoring thread may automatically acquire a new IP address, that is, the first IP address, and update the new IP address into the client local cache. To give an example without limitation: when monitoring a change of a kubernets registry through the first monitoring thread from outside a kubernets cluster, the first monitoring thread may acquire the first IP address through a node port (port accessible by an external machine).
The first IP address includes but is not limited to Pod IP, there are three IP addresses in Kubernetes cluster, Node IP: the IP address of the Node, i.e. the IP address of the physical network card. Pod IP: the IP address of the Pod, i.e., the IP address of the docker container, is a virtual IP address. Cluster IP: the IP address of Service, this is the virtual IP address. And the monitoring thread automatically acquires a new IP address and updates the new IP address into the client local cache, so that the timeliness of updating the node IP into the client cache can be improved.
S500: and the client uses all IP addresses corresponding to the service nodes in the local cache and performs load balancing on the Zeroc ICE service end node through a direct proxy mode provided by Zeroc ICE.
In particular, Load Balance (Load Balance) is an application of Cluster technology (Cluster). Load balancing may spread work tasks across multiple processing units, thereby increasing concurrent processing capabilities. There are two ways for connecting the client to the ICE service, which are direct connection and indirect connection, where the direct connection is directly connected through the name (or IP) of the machine where the service is located, the port, and the corresponding service name. The client uses all IP addresses corresponding to the services in the cache to load balance the service end node through a direct proxy mode provided by Zeroc ICE. The direct proxy approach includes, but is not limited to, the stringToProxy approach. The technical effect of solving the problem of load balancing failure of a Zeroc ICE client side in a Kubernetes cluster when accessing a server side is achieved.
Further, as shown in fig. 2, the monitoring the registry according to the first monitoring thread, and step S300 includes:
s310: and according to the first monitoring thread, accessing the Zeroc ICE service end from a Kubernets cluster to monitor the registration center.
Further, according to the first monitoring thread, accessing the Zeroc ICE service end from a kubernets cluster to monitor the registration center according to the first monitoring thread, where step S310 includes:
s311: obtaining a first Kubernetes cluster, wherein the first Kubernetes cluster comprises a first Zeroc ICE server;
s312: and monitoring the registration center through the first monitoring thread in the first Zeroc ICE server.
Specifically, the first listening thread is a thread for listening opened at an ICE client, and when the registration center is listened by accessing the Zeroc ICE server from a kubernets cluster according to the first listening thread, a first kubernets cluster is obtained, where the first kubernets cluster includes but is not limited to the first Zeroc ICE server.
Further, as shown in fig. 3, the monitoring the registry according to the first monitoring thread, and step S300 includes:
s320: and according to the first monitoring thread, accessing the Zeroc ICE service end from outside the Kubernets cluster to monitor the registration center.
Further, according to the first monitoring thread, accessing the Zeroc ICE server from outside the kubernets cluster to monitor the registration center, where step S320 includes:
s321: obtaining a second Kubernetes cluster, wherein the second Kubernetes cluster comprises a first Zeroc ICE server;
s322: and monitoring the registration center through the first monitoring thread in the first Zeroc ICE server.
Specifically, the first monitoring thread is a thread for monitoring opened at an ICE client, and when the registration center is monitored by accessing the Zeroc ICE server from outside the kubernets cluster according to the first monitoring thread, the second kubernets cluster is obtained, where the second kubernets cluster includes the first Zeroc ICE server. And monitoring the registration center based on the first monitoring thread in the first Zeroc ICE server.
To sum up, the ICE frame improvement method based on Kubernetes provided by the embodiment of the present application has the following technical effects:
1. the registration center without a Zeroc ICE server is adopted; starting a first monitoring thread at a client; monitoring the registration center according to the first monitoring thread; when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address; the client uses all IP addresses corresponding to the service nodes in the local cache, and the technical scheme that the load is balanced to the Zeroc ICE service end node in a direct proxy mode provided by the Zeroc ICE is provided.
Example two
Based on the same inventive concept as the Kubernetes-based ICE framework improvement method in the foregoing embodiment, as shown in fig. 4, an embodiment of the present application provides a Kubernetes-based ICE framework improvement system, where the system includes:
a first execution unit 11, where the first execution unit 11 is configured to remove a registration center of a Zeroc ICE server;
a second execution unit 12, where the second execution unit 12 is configured to start a first listening thread at a client;
the first monitoring unit 13, where the first monitoring unit 13 is configured to monitor the registry according to the first monitoring thread;
a first obtaining unit 14, where the first obtaining unit 14 is configured to obtain a first IP address when a service node IP of the registry changes, and update the first IP address to a local cache of the client, where the first IP address is a new IP address;
a third execution unit 15, where the third execution unit 15 is configured to load balance, by using all IP addresses corresponding to service nodes in the local cache, the load on the Zeroc ICE service end node in a direct proxy manner provided by Zeroc ICE.
Further, the system comprises:
a first registration unit, which is used for starting up in an Icebox mode and registering the service into a registration center of Kubernets.
Further, the system comprises:
and the second monitoring unit is used for accessing the Zeroc ICE service end from a Kubernets cluster to monitor the registration center according to the first monitoring thread.
Further, the system comprises:
a second obtaining unit, configured to obtain a first kubernets cluster, where the first kubernets cluster includes a first Zeroc ICE server;
a third monitoring unit, configured to monitor the registry through the first monitoring thread in the first Zeroc ICE server.
Further, the system comprises:
and the fourth monitoring unit is used for monitoring the registration center by accessing the Zeroc ICE server from outside the Kubernets cluster according to the first monitoring thread.
Further, the system comprises:
a third obtaining unit, configured to obtain a second kubernets cluster, where the second kubernets cluster includes a first Zeroc ICE server;
a fifth monitoring unit, configured to monitor the registry through the first monitoring thread in the first Zeroc ICE server.
Exemplary electronic device
The electronic device of the embodiment of the present application is described below with reference to fig. 5.
Based on the same inventive concept as the Kubernetes-based ICE framework improvement method in the foregoing embodiment, an embodiment of the present application further provides a Kubernetes-based ICE framework improvement system, including: a processor coupled to a memory, the memory for storing a program that, when executed by the processor, causes a system to perform the method of any of the first aspects.
The electronic device 300 includes: processor 302, communication interface 303, memory 301. Optionally, the electronic device 300 may also include a bus architecture 304. Wherein, the communication interface 303, the processor 302 and the memory 301 may be connected to each other through a bus architecture 304; the bus architecture 304 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus architecture 304 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.
The communication interface 303 may be any device, such as a transceiver, for communicating with other devices or communication networks, such as an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), a wired access network, and the like.
The memory 301 may be, but is not limited to, a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, an electrically erasable Programmable read-only memory (EEPROM), a compact disk read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor through a bus architecture 304. The memory may also be integral to the processor.
The memory 301 is used for storing computer-executable instructions for executing the present application, and is controlled by the processor 302 to execute. The processor 302 is configured to execute the computer-executable instructions stored in the memory 301, so as to implement the Kubernetes-based ICE framework improvement method provided by the above-described embodiment of the present application.
Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application program codes, which are not specifically limited in the embodiments of the present application.
The embodiment of the application provides an ICE (internal Integrated Circuit) framework improvement method based on Kubernetes, wherein the method comprises the following steps: removing a registration center of a Zeroc ICE server; starting a first monitoring thread at a client; monitoring the registration center according to the first monitoring thread; when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address; and the client uses all IP addresses corresponding to the service nodes in the local cache and performs load balancing on the Zeroc ICE service end node through a direct proxy mode provided by Zeroc ICE.
Those of ordinary skill in the art will understand that: the various numbers of the first, second, etc. mentioned in this application are only used for the convenience of description and are not used to limit the scope of the embodiments of this application, nor to indicate the order of precedence. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one" means one or more. At least two means two or more. "at least one," "any," or similar expressions refer to any combination of these items, including any combination of singular or plural items. For example, at least one (one ) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device including one or more available media integrated servers, data centers, and the like. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
The various illustrative logical units and circuits described in this application may be implemented or operated upon by design of a general purpose processor, a digital signal processor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other similar configuration.
The steps of a method or algorithm described in the embodiments herein may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software cells may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. For example, a storage medium may be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may be disposed in a terminal. In the alternative, the processor and the storage medium may reside in different components within the terminal. These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although the present application has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the application. Accordingly, the specification and figures are merely exemplary of the present application as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the present application and its equivalent technology, it is intended that the present application include such modifications and variations.
Claims (8)
1. A Kubernetes-based ICE framework improvement method is characterized by comprising the following steps:
removing a registration center of a Zeroc ICE server;
starting a first monitoring thread at a client;
monitoring the registration center according to the first monitoring thread;
when the service node IP of the registration center changes, acquiring a first IP address, and updating the first IP address to a local cache of the client, wherein the first IP address is a new IP address;
and the client uses all IP addresses corresponding to the service nodes in the local cache and performs load balancing on the Zeroc ICE service end node through a direct proxy mode provided by Zeroc ICE.
2. The method of claim 1, wherein after removing the registration center of Zeroc ICE service, further comprising:
initiated by Icebox, registers the service into the registry of kubernets.
3. The method of claim 1, wherein said listening for the registry according to the first listening thread comprises:
and according to the first monitoring thread, accessing the Zeroc ICE service end from a Kubernets cluster to monitor the registration center.
4. The method of claim 3, wherein said accessing the Zeroc ICE server from within a Kubernets cluster to listen to the registry according to the first listening thread comprises:
obtaining a first Kubernetes cluster, wherein the first Kubernetes cluster comprises a first Zeroc ICE server;
and monitoring the registration center through the first monitoring thread in the first Zeroc ICE server.
5. The method of claim 1, wherein said listening for the registry according to the first listening thread comprises:
and according to the first monitoring thread, accessing the Zeroc ICE service end from outside the Kubernets cluster to monitor the registration center.
6. The method of claim 5, wherein accessing the Zeroc ICE server from outside a Kubernets cluster to listen to the registry according to the first listening thread comprises:
obtaining a second Kubernetes cluster, wherein the second Kubernetes cluster comprises a first Zeroc ICE server;
and monitoring the registration center through the first monitoring thread in the first Zeroc ICE server.
7. A Kubernetes-based ICE framework retrofit system, the system comprising:
the first execution unit is used for removing a registration center of a Zeroc ICE server;
the second execution unit is used for starting a first monitoring thread at the client;
the first monitoring unit is used for monitoring the registration center according to the first monitoring thread;
a first obtaining unit, configured to obtain a first IP address when a service node IP of the registry changes, and update the first IP address to a local cache of the client, where the first IP address is a new IP address;
and the third execution unit is used for the client to use all IP addresses corresponding to the service nodes in the local cache and balance the load to the Zeroc ICE service node in a direct proxy mode provided by Zeroc ICE.
8. A Kubernetes-based ICE framework improvement system comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method of any one of claims 1 to 6 are implemented when the program is executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111655705.3A CN114301919B (en) | 2021-12-30 | 2021-12-30 | ICE frame improvement method based on Kubernetes |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111655705.3A CN114301919B (en) | 2021-12-30 | 2021-12-30 | ICE frame improvement method based on Kubernetes |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114301919A true CN114301919A (en) | 2022-04-08 |
| CN114301919B CN114301919B (en) | 2024-04-05 |
Family
ID=80972743
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111655705.3A Active CN114301919B (en) | 2021-12-30 | 2021-12-30 | ICE frame improvement method based on Kubernetes |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114301919B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713226A (en) * | 2015-11-12 | 2017-05-24 | 卓望数码技术（深圳）有限公司 | Remote procedure call processing method used for distributed system and remote procedure call processing system thereof |
| CN111010304A (en) * | 2019-12-23 | 2020-04-14 | 浪潮云信息技术有限公司 | Method for integrating Dubbo service and Kubernetes system |
| CN111752807A (en) * | 2020-07-01 | 2020-10-09 | 浪潮云信息技术股份公司 | Resource monitoring method based on Kubernetes |
| WO2020237797A1 (en) * | 2019-05-31 | 2020-12-03 | 烽火通信科技股份有限公司 | Dynamic configuration management method and system in microservice framework |
| WO2020251828A1 (en) * | 2019-06-12 | 2020-12-17 | Cisco Technology, Inc. | Systems and methods providing a multi-cloud microservices gateway using a sidecar proxy |
| CN113094074A (en) * | 2021-05-07 | 2021-07-09 | 聚好看科技股份有限公司 | Service cluster updating method and device |
-
2021
- 2021-12-30 CN CN202111655705.3A patent/CN114301919B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106713226A (en) * | 2015-11-12 | 2017-05-24 | 卓望数码技术（深圳）有限公司 | Remote procedure call processing method used for distributed system and remote procedure call processing system thereof |
| WO2020237797A1 (en) * | 2019-05-31 | 2020-12-03 | 烽火通信科技股份有限公司 | Dynamic configuration management method and system in microservice framework |
| WO2020251828A1 (en) * | 2019-06-12 | 2020-12-17 | Cisco Technology, Inc. | Systems and methods providing a multi-cloud microservices gateway using a sidecar proxy |
| CN111010304A (en) * | 2019-12-23 | 2020-04-14 | 浪潮云信息技术有限公司 | Method for integrating Dubbo service and Kubernetes system |
| CN111752807A (en) * | 2020-07-01 | 2020-10-09 | 浪潮云信息技术股份公司 | Resource monitoring method based on Kubernetes |
| CN113094074A (en) * | 2021-05-07 | 2021-07-09 | 聚好看科技股份有限公司 | Service cluster updating method and device |
Non-Patent Citations (1)
| Title |
|---|
| 龙界非;江果;王朝;王洪鹏;: "电子战系统中分布式数据同步技术", 电子信息对抗技术, 15 May 2019 (2019-05-15) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114301919B (en) | 2024-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11388228B2 (en) | Methods, systems and computer readable media for self-replicating cluster appliances | |
| JP7014887B2 (en) | PDU type setting method, UE policy setting method, and related entities | |
| US7269721B2 (en) | Method, system, and apparatus for booting with remote configuration data | |
| US7225356B2 (en) | System for managing operational failure occurrences in processing devices | |
| CN110365748B (en) | Service data processing method and device, storage medium and electronic device | |
| US9161239B2 (en) | Network access point management | |
| US20170163479A1 (en) | Method, Device and System of Renewing Terminal Configuration In a Memcached System | |
| CN110557357B (en) | Remote procedure call protocol self-adaption method, related device and server | |
| WO2016184175A1 (en) | Database processing method and apparatus | |
| US20040230670A1 (en) | Method and system for representing, configuring and deploying distributed applications | |
| US20170163478A1 (en) | Method,electronic device and system for updating client configuration in key-value pair database | |
| CN112565334B (en) | Access method and device of Internet of things equipment and MQTT gateway | |
| US7966394B1 (en) | Information model registry and brokering in virtualized environments | |
| CN112333017A (en) | Service configuration method, device, equipment and storage medium | |
| US9705978B1 (en) | Dependency graph management | |
| CN116800825A (en) | Calling method, device, equipment and medium based on micro-service splitting | |
| US20240147578A1 (en) | Wireless communication service over an edge data network (edn) between a user equipment (ue) and an application server (as) | |
| CN113079098B (en) | Method, device, equipment and computer readable medium for updating route | |
| CN110795205B (en) | System and method for providing cloud service based on software container | |
| CN110851166A (en) | User-unaware application program updating method and device and computer equipment | |
| CN114301919B (en) | ICE frame improvement method based on Kubernetes | |
| CN114338763B (en) | Micro-service calling method, micro-service calling device, server and computer readable storage medium | |
| CN112711466B (en) | Hanging affair inspection method and device, electronic equipment and storage medium | |
| CN106790666A (en) | Load balancing mesh architecture and its build operation method | |
| CN112671871B (en) | Mirror image distribution method and device, terminal equipment and storage medium |
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 |