CN114374698A - Ingress-based automatic NodePort pool switching system - Google Patents
Ingress-based automatic NodePort pool switching system Download PDFInfo
- Publication number
- CN114374698A CN114374698A CN202210279758.8A CN202210279758A CN114374698A CN 114374698 A CN114374698 A CN 114374698A CN 202210279758 A CN202210279758 A CN 202210279758A CN 114374698 A CN114374698 A CN 114374698A
- Authority
- CN
- China
- Prior art keywords
- pod
- ingress
- module
- access
- service
- 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
- 238000012544 monitoring process Methods 0.000 claims abstract description 21
- 238000000034 method Methods 0.000 claims abstract description 8
- 238000006243 chemical reaction Methods 0.000 claims description 11
- 230000001360 synchronised effect Effects 0.000 claims description 9
- 238000004891 communication Methods 0.000 claims description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 2
- 241000287196 Asthenes Species 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1036—Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45591—Monitoring or debugging support
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an Ingress-based automatic NodePort pool switching system, which comprises an external access module, an Ingress rule module, an Ingress control module, a monitoring module and a rear-end service module, wherein the rear-end service module is used for providing a Pod, the external access module is used for submitting an access application, the Ingress rule module is used for recording an access rule, the Ingress control module forwards the access application to a corresponding Pod according to the access rule, the monitoring module is used for monitoring the Pod operation state of the rear-end service module, and the access rule in the Ingress rule module is automatically updated according to the operation state of the Pod; the system can process a large number of Pod service access problems in the container cloud, and enables a user to access the most appropriate Pod by automatically changing the binding relationship between the Ids of the NodePort and the Pod.
Description
Technical Field
The present disclosure relates generally to the field of container clouds, and more particularly to an Ingress-based automatic nodoport pool switching system.
Background
The container cloud is a very popular service framework at present, can provide lightweight and easy-to-transfer service, and the Pod is a collection of a plurality of containers, and for safety, the Pod service is not directly exposed to an external network, and meanwhile, the id of the Pod can be changed all the time due to frequent creation and logout, and the Pod service is often accessed in a reverse proxy manner, while Ingress is an efficient reverse proxy manner, and when Ingress is used, an effective switching system is needed to switch the accessed Pod, so that the access efficiency is improved, and the stability of the system is guaranteed;
now, many switching systems have been developed, and through a lot of search and reference, it is found that the existing authorization systems, such as the systems disclosed in publication nos. KR100950744B1, KR101828424B1, CN111181968B and KR101454678B1, use a listener configured to monitor whether the configuration file corresponding to the Pod changes; setting an initial trigger variable for triggering Pod and executing synchronous operation of the configuration file; the monitor synchronizes the monitoring result of the configuration file to the APIServer; and the label selector built in the Kubelet component does not wait for whether the synchronization operation between the configuration file of the last version of the current configuration file and the Pod is completed or not, and injects the current configuration file into the Pod to complete the synchronization operation between the Pod and the current configuration file and restore the initial trigger variable. However, in the system, the access efficiency of the system needs to be improved in order to optimize specific Pod handover.
Disclosure of Invention
The invention aims to provide an Ingress-based automatic NodePort pool switching system,
the invention adopts the following technical scheme:
an Ingress-based automatic NodePort pool switching system comprises an external access module, an Ingress rule module, an Ingress control module, a monitoring module and a back-end service module, wherein the external access module is used for providing a NodePort port for a user to access the system, the back-end service module is used for providing a Pod for service, the Ingress rule module is used for recording the binding relationship between an access domain name and the Id of the Pod, the monitoring module is used for monitoring the Id change of the Pod, and the Ingress control module is used for realizing the flow forwarding from the NodePort to the Pod according to the binding relationship between the access domain name and the Id of the Pod;
a user submits an access application containing an access domain name through the NodePort port, one or one access domain name corresponds to one Pod service, one Pod service comprises a plurality of pods running at different nodes, and the Ingress control module selects one Pod for switching;
the Ingress control module calculates the viscosity index of the j-th Pod service accessed by the user through the i-th NodePort port according to the historical access data
：
Wherein,
indicating the number of times the user selects the jth Pod service,
indicating the number of times the user selects the i < th > NodePort port for access,
representing the number of times that the user accesses the jth Pod service through the ith NodePort port;
the Ingress control module calculates the candidate indexes of all the Pods in the jth Pod service
：
Wherein,
in order to be the first conversion factor,
in order to be the second conversion coefficient,
the function is a network communication cost estimation function for estimating the network delay cost from the ith NodePort port to the kth Pod in the jth Pod service,
represents the load capacity of the node where the kth Pod of the jth Pod service is located,
representing the number of times that the user obtains a service by accessing a kth Pod in a jth Pod service;
the Ingress control module selects a to-be-selected index
The largest Pod is used as the object of flow forwarding;
further, the monitoring module monitors a new Pod created in the node and a cancelled old Pod and obtains an update event, and the Ingress control module matches the update event to obtain three types of synchronization tasks: the Ingress rule module updates binding data of Id of the Pod according to the synchronous task;
furthermore, the Ingress control module generates link data of Id of a user, namely NodePort, Pod and Pod, when the user accesses the network, and the Ingress control module obtains historical access data according to the link data statistics and stores the historical access data in a database;
further, the first conversion coefficient
The calculation formula of (2) is as follows:
wherein,
the average load of all nodes in the whole system in a fixed time,
the time average value from each NodePort port to all nodes is obtained;
further, the second conversion coefficient
The calculation formula of (2) is as follows:
wherein,
for intermediate times, for all of the whole system
The median value over a fixed time.
The beneficial effects obtained by the invention are as follows:
the system adopts the Ingress frame to carry out anti-proxy, can solve the problem that the Id of the Pod changes due to drift, can also easily deal with the problem of creating a new Pod, and selects the most appropriate Pod for flow forwarding according to the historical access data of the user and the running state of the Pod in each node under the current state when the Pod accessed by the user is switched, so that the access efficiency is improved, and the stability of the system is ensured.
For a better understanding of the features and technical content of the present invention, reference should be made to the following detailed description of the invention and accompanying drawings, which are provided for purposes of illustration and description only and are not intended to limit the invention.
Drawings
FIG. 1 is a schematic view of the overall structural framework of the present invention;
FIG. 2 is a schematic diagram illustrating an Ingress rule change flow according to the present invention;
FIG. 3 is a diagram illustrating readable data in an update time pool according to the present invention;
FIG. 4 is a schematic diagram of a rule package according to the present invention;
FIG. 5 is a schematic diagram of chain data accessed by a user according to the present invention.
Detailed Description
The following is a description of embodiments of the present invention with reference to specific embodiments, and those skilled in the art will understand the advantages and effects of the present invention from the disclosure of the present specification. The invention is capable of other and different embodiments and its several details are capable of modification in various other respects, all without departing from the spirit and scope of the present invention. The drawings of the present invention are for illustrative purposes only and are not intended to be drawn to scale. The following embodiments will further explain the related art of the present invention in detail, but the disclosure is not intended to limit the scope of the present invention.
The first embodiment.
The embodiment provides an Ingress-based automatic node port pool switching system, which, with reference to fig. 1, includes an external access module, an Ingress rule module, an Ingress control module, a monitoring module, and a back-end service module, where the external access module is configured to provide a node port for a user to access the system, the back-end service module is configured to provide a Pod for service, the Ingress rule module is configured to record a binding relationship between an access domain name and an Id of the Pod, the monitoring module is configured to monitor Id change of the Pod, and the Ingress control module is configured to implement traffic forwarding from the node port to the Pod according to the binding relationship between the access domain name and the Id of the Pod;
a user submits an access application containing an access domain name through the NodePort port, one or one access domain name corresponds to one Pod service, one Pod service comprises a plurality of pods running at different nodes, and the Ingress control module selects one Pod for switching;
the Ingress control module calculates the viscosity index of the j-th Pod service accessed by the user through the i-th NodePort port according to the historical access data
：
Wherein,
indicating the number of times the user selects the jth Pod service,
indicating the number of times the user selects the i < th > NodePort port for access,
representing the number of times that the user accesses the jth Pod service through the ith NodePort port;
the Ingress control module calculates the candidate indexes of all the Pods in the jth Pod service
：
Wherein,
in order to be the first conversion factor,
in order to be the second conversion coefficient,
the function is a network communication cost estimation function for estimating the network delay cost from the ith NodePort port to the kth Pod in the jth Pod service,
represents the load capacity of the node where the kth Pod of the jth Pod service is located,
representing the number of times that the user obtains a service by accessing a kth Pod in a jth Pod service;
the Ingress control module selects a to-be-selected index
The largest Pod is used as the object of flow forwarding;
the monitoring module monitors a new Pod created in a node and a cancelled old Pod and obtains an update event, and the Ingress control module matches the update event to obtain three types of synchronous tasks: the Ingress rule module updates binding data of Id of the Pod according to the synchronous task;
the Ingress control module generates link data of Id of a user, namely NodePort-Pod, when the user accesses the network every time, and the Ingress control module obtains historical access data according to the link data statistics and stores the historical access data in a database;
the first conversion coefficient
The calculation formula of (2) is as follows:
wherein,
the average load of all nodes in the whole system in a fixed time,
the time average value from each NodePort port to all nodes is obtained;
the second conversion coefficient
The calculation formula of (2) is as follows:
wherein,
for intermediate times, for all of the whole system
The median value over a fixed time.
Example two.
The embodiment includes the whole content of the first embodiment, and provides an Ingress-based automatic nodoport pool switching system, which includes an external access module, an Ingress rule module, an Ingress control module, a monitoring module, and a back-end service module, where the back-end service module is configured to provide a Pod, the external access module is configured to submit an access application, the Ingress rule module is configured to record an access rule, the Ingress control module forwards the access application to a corresponding Pod according to the access rule, the monitoring module is configured to monitor a Pod operation state of the back-end service module, and the access rule in the Ingress rule module is automatically updated according to the operation state of the Pod;
the access rule binds an access domain name and the Id of the Pod, a user submits an access application in the external access module in a mode of inputting the domain name, and the Ingress control module acquires the Id of the Pod corresponding to the domain name and then forwards the access flow to the corresponding Pod;
with reference to fig. 2, since a node where a Pod works in a container cloud changes, and an Id of the Pod also changes, the monitoring module monitors the change of the Id of the Pod in real time, and feeds back the change information to the Ingress rule module, and the Ingress rule module updates the Id of the access domain name and the bound Pod according to the change information, and the specific process includes the following steps:
s1, the monitoring module establishes monitoring connection in each main node;
s2, the monitoring module sets a trigger thread, and when a logout Pod or a creation Pod appears on the master node, the event is written into an update event pool;
s3, the control process reads the update event from the update event pool, and when the update event is read, a synchronization task is added into the synchronization queue;
s4, the task processing thread acquires the synchronous task from the synchronous queue periodically;
s5, the task processing thread judges whether the synchronous task is reloaded, if yes, the step is jumped to S6, and if not, the step is jumped to S7;
s6, the Ingress rule module reloads and switches the recorded access rules;
s7, the Ingress rule module binds the access domain name and the Id of the new Pod again, constructs POST data and uploads the POST data to the pairing reading unit;
s8, the Ingress control module acquires corresponding Id information of Pod in the paired reading unit when receiving the access application;
in the process, a control process, a task processing thread, an update event pool and a synchronous queue all belong to the Ingress control module;
in step S2, the triggering thread corresponding to each master node records the number of Pod running on the master node and the Id of the corresponding Pod, and when the Pod decreases in number due to logout or increases in number due to creation, the triggering thread starts a query unit, and the query unit compares the Id of the existing Pod with the Id of the recorded Pod to find the logged Pod or the created Pod, and then writes the event into an update pool, and updates the Id of the recorded Pod at the same time, where it is noted that the update event includes only two types of events, namely logout Pod and creation Pod;
with reference to fig. 3, the update event pool is provided with a pairing unit, the pairing module performs content scanning on a previous logout Pod event and a subsequent created Pod event, when the function descriptions of the pods in the events are consistent, the two events are paired to form readable data, for the logout Pod event, a pairing time is set, when a pairable created Pod event does not occur within the pairing time, the logout Pod event is separately formed into readable data, for the created Pod event, when there is no previous logout Pod event in the update event pool, the created Pod event is directly and separately formed into readable data;
when the control process in step S3 reads the update events in the update event pool, only the three types of readable data can be read;
in step S5, the paired synchronization task corresponding to the logout Pod event and the creation Pod event and the synchronization task corresponding to the individual logout Pod event need to be reloaded, and the synchronization task corresponding to the individual creation Pod event does not need to be reloaded;
with reference to fig. 4, the Ingress rule module includes a plurality of rule packages, each rule package records one or more access domain names pointing to the same service name and ids of a plurality of bound Pod, the ids of the pods in the same rule package are ids of pods distributed in different nodes but providing the same service, and the rule packages with similar types are integrated into a cluster;
the Ingress control module switches and selects an Id of a Pod from Ids of a plurality of pods in a corresponding rule packet according to NodePort submitted with an access application and IP information of a user to forward the flow;
with reference to fig. 5, when accessing Pod services, a user can submit an access application through different nodoports, and access different Pod services, and select one Pod of the Pod services for final access, where each access generates link data of Id of the user, nodoport-Pod, and the Ingress control module obtains historical access data according to the link data statistics, and selects an Id of a proper Pod for the next access of the user according to the historical access record data;
for the same user, the historical access data comprises:
the Ingress control module calculates the viscosity index of the j-th Pod service accessed by the user through the i-th NodePort port according to the historical access data
：
The Ingress control module obtains the load capacity of a node where a kth Pod of a jth Pod service is located, and uses the load capacity
Showing that the Ingress control module calculates the index to be selected of each Pod
：
Wherein,
in order to be the first conversion factor,
for the second conversion factor, the specific value is obtained by actual testing,
the function is a network communication cost estimation function and is used for estimating the network delay cost from the ith NodePort port to the kth Pod in the jth Pod service;
the Ingress control module selects a to-be-selected index
The largest Pod is used as the object of flow forwarding;
the second conversion coefficient
The acquisition method comprises the following steps:
testing the time from each NodePort port to all nodes and obtaining the average value as
Then, then
Comprises the following steps:
wherein,
intermediate times, as in the whole systemIs provided with
A median value over a fixed time;
the first conversion coefficient
The calculation formula of (2) is as follows:
wherein,
the average load of all nodes in the whole system in a fixed time is obtained.
The disclosure is only a preferred embodiment of the invention, and is not intended to limit the scope of the invention, so that all equivalent technical changes made by using the contents of the specification and the drawings are included in the scope of the invention, and further, the elements thereof can be updated as the technology develops.
Claims (5)
1. An Ingress-based automatic NodePort pool switching system is characterized by comprising an external access module, an Ingress rule module, an Ingress control module, a monitoring module and a back-end service module, wherein the external access module is used for providing a NodePort port for a user to access the system, the back-end service module is used for providing a Pod for service, the Ingress rule module is used for recording the binding relationship between an access domain name and the Id of the Pod, the monitoring module is used for monitoring the Id change of the Pod, and the Ingress control module is used for realizing the flow forwarding from the NodePort to the Pod according to the binding relationship between the access domain name and the Id of the Pod;
a user submits an access application containing an access domain name through the NodePort port, one access domain name corresponds to one Pod service, one Pod service comprises a plurality of pods running at different nodes, and the Ingress control module selects one Pod for switching;
the Ingress control module calculates the viscosity index of the j-th Pod service accessed by the user through the i-th NodePort port according to the historical access data
：
Wherein,
indicating the number of times the user selects the jth Pod service,
indicating the number of times the user selects the i < th > NodePort port for access,
representing the number of times that the user accesses the jth Pod service through the ith NodePort port;
the Ingress control module calculates the candidate indexes of all the Pods in the jth Pod service
：
Wherein,
in order to be the first conversion factor,
in order to be the second conversion coefficient,
the function is a network communication cost estimation function for estimating the network delay cost from the ith NodePort port to the kth Pod in the jth Pod service,
represents the load capacity of the node where the kth Pod of the jth Pod service is located,
representing the number of times that the user obtains a service by accessing a kth Pod in a jth Pod service;
the Ingress control module selects a to-be-selected index
The largest one Pod is the subject of traffic forwarding.
2. The system as claimed in claim 1, wherein the monitoring module monitors a new Pod created in a node and a revoked old Pod and obtains an update event, and the Ingress control module matches the update event to obtain three types of synchronization tasks: and the Ingress rule module updates binding data of the Id of the Pod according to the synchronous task.
3. The system as claimed in claim 2, wherein the Ingress control module generates a link data of Id of user-nodoport-Pod at each access of the user, and the Ingress control module obtains historical access data according to the link data statistics and stores the historical access data in the database.
4. The method as claimed in claim 3, wherein the Ingress-based automatic NodePort pool switchingSystem characterized in that said first conversion coefficient
The calculation formula of (2) is as follows:
wherein,
the average load of all nodes in the whole system in a fixed time,
the time average of each nodoport port to all nodes.
5. The Ingress-based automatic NodePort pool switching system as claimed in claim 4, wherein said second conversion factor
The calculation formula of (2) is as follows:
wherein,
for intermediate times, for all of the whole system
The median value over a fixed time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210279758.8A CN114374698B (en) | 2022-03-22 | 2022-03-22 | Ingress-based automatic NodePort pool switching system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210279758.8A CN114374698B (en) | 2022-03-22 | 2022-03-22 | Ingress-based automatic NodePort pool switching system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114374698A true CN114374698A (en) | 2022-04-19 |
| CN114374698B CN114374698B (en) | 2022-05-17 |
Family
ID=81145822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210279758.8A Active CN114374698B (en) | 2022-03-22 | 2022-03-22 | Ingress-based automatic NodePort pool switching system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114374698B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20160101127A (en) * | 2014-02-24 | 2016-08-24 | 인텔 아이피 코포레이션 | Measurement gap patterns |
| CN109558446A (en) * | 2018-12-13 | 2019-04-02 | 杭州数梦工场科技有限公司 | Job request method, apparatus, electronic equipment and storage medium |
| CN110300130A (en) * | 2018-03-21 | 2019-10-01 | 中移(苏州)软件技术有限公司 | A kind of resource regulating method, device, electronic equipment and storage medium |
| CN111181968A (en) * | 2019-12-30 | 2020-05-19 | 北京金山云网络技术有限公司 | Cross-block chain communication method and device, cross-chain service system and cross-chain transaction system |
| CN112491717A (en) * | 2019-09-12 | 2021-03-12 | 华为技术有限公司 | Service routing method and device |
| CN113055220A (en) * | 2019-12-26 | 2021-06-29 | 瞻博网络公司 | Scalable and robust network management for cloud-based NAT environments |
| WO2021205212A1 (en) * | 2020-04-08 | 2021-10-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Traffic controller for cloud native deployment |
-
2022
- 2022-03-22 CN CN202210279758.8A patent/CN114374698B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20160101127A (en) * | 2014-02-24 | 2016-08-24 | 인텔 아이피 코포레이션 | Measurement gap patterns |
| CN110300130A (en) * | 2018-03-21 | 2019-10-01 | 中移(苏州)软件技术有限公司 | A kind of resource regulating method, device, electronic equipment and storage medium |
| CN109558446A (en) * | 2018-12-13 | 2019-04-02 | 杭州数梦工场科技有限公司 | Job request method, apparatus, electronic equipment and storage medium |
| CN112491717A (en) * | 2019-09-12 | 2021-03-12 | 华为技术有限公司 | Service routing method and device |
| CN113055220A (en) * | 2019-12-26 | 2021-06-29 | 瞻博网络公司 | Scalable and robust network management for cloud-based NAT environments |
| CN111181968A (en) * | 2019-12-30 | 2020-05-19 | 北京金山云网络技术有限公司 | Cross-block chain communication method and device, cross-chain service system and cross-chain transaction system |
| WO2021205212A1 (en) * | 2020-04-08 | 2021-10-14 | Telefonaktiebolaget Lm Ericsson (Publ) | Traffic controller for cloud native deployment |
Non-Patent Citations (1)
| Title |
|---|
| 李翔: "在私有Kubernetes集群中实现服务的负载均衡", 《电子技术与软件工程》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114374698B (en) | 2022-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR100256016B1 (en) | Scheduling of real-time i/o in the presence of replication in a client-server environment | |
| CN107517228B (en) | Dynamic acceleration method and device in content distribution network | |
| US5937042A (en) | Method and system for rehome optimization | |
| CN107888666A (en) | A kind of cross-region data-storage system and method for data synchronization and device | |
| US20030018688A1 (en) | Method and apparatus to facilitate accessing data in network management protocol tables | |
| EP2227016A1 (en) | A content buffering, querying method and point-to-point media transmitting system | |
| CN103607418B (en) | Large-scale data segmenting system based on cloud service data characteristics and dividing method | |
| CN103078906A (en) | Document transparent moving method | |
| CN108920552A (en) | A kind of distributed index method towards multi-source high amount of traffic | |
| CN102890714A (en) | Method and device for indexing data | |
| CN111966289A (en) | Partition optimization method and system based on Kafka cluster | |
| CN106021585A (en) | Traffic incident video access method and system based on time-space characteristics | |
| CN105450964B (en) | Method, system and management node for cloud storage of video data | |
| US7899906B2 (en) | Multi-layered measurement model for data collection and method for data collection using same | |
| CN108063832B (en) | Cloud storage system and storage method thereof | |
| WO2023040259A1 (en) | Resource alarm analysis method and apparatus, electronic device, and storage medium | |
| CN114374698B (en) | Ingress-based automatic NodePort pool switching system | |
| US6381237B1 (en) | Trail explorer and method for exploring trails in a communication network | |
| AU5946800A (en) | Summary building block, and system and method for managing networks | |
| KR101592860B1 (en) | Distributed storage system using Internet of Things Device and operating method thereof | |
| CN116132698A (en) | Content recording method, playing method, CDN system and storage medium | |
| CN115374101A (en) | Rail transit station level data management system | |
| CN106991129B (en) | Real-time database system based on SOA (service oriented architecture) framework power dispatching system and implementation method | |
| CN117591039B (en) | Distributed storage method, system, equipment and medium | |
| CN108646137A (en) | A kind of line node positioning system and method |
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 |