WO2023197874A1 - Procédé et appareil d'accès à une application, dispositif et support - Google Patents

Procédé et appareil d'accès à une application, dispositif et support Download PDF

Info

Publication number
WO2023197874A1
WO2023197874A1 PCT/CN2023/084815 CN2023084815W WO2023197874A1 WO 2023197874 A1 WO2023197874 A1 WO 2023197874A1 CN 2023084815 W CN2023084815 W CN 2023084815W WO 2023197874 A1 WO2023197874 A1 WO 2023197874A1
Authority
WO
WIPO (PCT)
Prior art keywords
pod
information
endpoint
request
preset
Prior art date
Application number
PCT/CN2023/084815
Other languages
English (en)
Chinese (zh)
Inventor
黄吉旺
吴栋
王玉东
Original Assignee
苏州浪潮智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 苏州浪潮智能科技有限公司 filed Critical 苏州浪潮智能科技有限公司
Publication of WO2023197874A1 publication Critical patent/WO2023197874A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare

Definitions

  • This application relates to the technical field of application access, and in particular to an application access method, device, equipment and medium.
  • master-slave mechanism is represented by one of the replicas acting as the master replica to respond to requests for the application, and the remaining replicas running as slave replicas.
  • master replica When the master replica is abnormal, one of the slave replicas becomes the master replica to take over the traffic.
  • This mechanism can ensure atomicity and avoid data processing inconsistencies that may be caused by multiple copies responding to requests at the same time.
  • the technical implementation plan of master-slave is generally to develop or integrate an election mechanism in the source code. By continuously running the election process, the master copy role of a certain copy is maintained. The master copy responds to the request.
  • the purpose of this application is to provide an application access method, device, equipment and medium that can reduce the complexity of application development and improve the response performance of application access.
  • the specific plan is as follows:
  • Some embodiments of the present application disclose an application access method, applied to a preset admission controller, including:
  • the platform creates or updates endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • the pod information corresponding to each pod ip in the pod ip list it also includes:
  • the service information is the information of the service corresponding to the endpoint;
  • the step of querying the pod information corresponding to each pod ip in the pod ip list is triggered.
  • a main pod is determined from all pods of the target application based on all pod information and preset policies, including:
  • the pod with the earliest creation time is determined from all pods of the target application as the main pod.
  • a main pod is determined from all pods of the target application based on all pod information and preset policies, including:
  • the pod with the latest creation time is determined from all pods of the target application as the main pod.
  • the k8s platform before parsing the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, it also includes:
  • Some embodiments of the present application also disclose an application access device, applied to a preset admission controller, including:
  • the request parsing module is used to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information;
  • the list acquisition module is used to obtain the pod ip list corresponding to the target application from the request parsing information
  • Information query module used to query the pod information corresponding to each pod ip in the pod ip list
  • the main pod determination module is used to determine a main pod from all pods of the target application based on all pod information and preset policies;
  • the information update module is used to replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create or update endpoints based on the replacement request information to forward all access traffic of the target application. to the main pod.
  • the endpoint name acquisition module is used to obtain the endpoint name from the request parsing information
  • the service information query module is used to query service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint;
  • the master-slave label judgment module is used to determine whether there is a preset master-slave label in the service information; if there is a preset master-slave label and the value of the preset master-slave label is the first preset value, the information query module is triggered to execute the query pod Steps for pod information corresponding to each pod ip in the ip list.
  • Some embodiments of the present application also disclose an electronic device, including a processor and a memory; wherein,
  • Memory used to hold computer programs
  • the processor is used to execute the computer program to implement the aforementioned application access method.
  • Some embodiments of the present application also disclose a computer non-volatile readable storage medium for storing a computer program, wherein when the computer program is executed by a processor, the aforementioned application access method is implemented.
  • this application first parses the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtains the pod ip list corresponding to the target application from the request parsing information, and queries each pod ip in the pod ip list. Corresponding pod information, then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information. This allows the k8s platform to create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • this application uses the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtains the request parsing information, and determines a main pod based on the request parsing information and the preset policy. Use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all the access traffic of the target application to the main pod, avoiding complex and difficult-to-maintain problems.
  • the election mechanism and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • Figure 1 is a flow chart of an application access method disclosed in some embodiments of the present application.
  • Figure 2 is a schematic diagram of a specific application access solution provided by some embodiments of the present application.
  • Figure 3 is a schematic structural diagram of an application access device disclosed in some embodiments of the present application.
  • Figure 4 is a structural diagram of an electronic device disclosed in some embodiments of the present application.
  • Figure 5 is a schematic structural diagram of a computer non-volatile readable storage medium provided by some embodiments of the present application.
  • kubernetes a common open source container orchestration architecture for container cloud platforms, which can realize automatic scheduling, expansion, fault recovery, etc. of containers, referred to as k8s.
  • kube-apiserver k8s’ external service API (Application Programming Interface, application programming interface). All resource-related operations in k8s need to be implemented by calling the kube-apiserver related interface.
  • Workload The deployment form of application components on k8s, including deployment (stateless load)/statefulset (stateful load)/job (task)/cronjob (timed task)/daemonset (daemon process) and other forms. Each workload can manage 1 or more pods.
  • Pod The smallest management unit of k8s, consisting of one or more containers. These containers share namespaces such as processes and networks.
  • Service An object resource designed by k8s to satisfy requests for workloads. It matches pods under the workload through labelselector and provides load balancing capabilities to forward traffic to different pods.
  • endpoint a set of pod IPs and ports. When the service is created, the pod corresponding to the workload is selected based on the labelselector of the service. Access to the service will be loaded to a certain pod IP and port on the endpoint through load balancing.
  • the master-slave technical implementation plan is generally to develop or integrate an election mechanism in the source code.
  • the master copy role of a certain copy is maintained.
  • the master copy responds to the request.
  • a new primary copy is re-elected from the backup copy.
  • the secondary copy needs to forward the traffic to the primary copy to avoid No need to manipulate data from copies.
  • This solution not only has complex technical principles and is difficult to maintain, but also has response performance problems caused by the slave replica forwarding traffic to the master replica again.
  • this application discloses an application access solution that can reduce the complexity of application development and improve the response performance of application access.
  • an application access method which is applied to a preset admission controller, including:
  • Step S11 Parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information.
  • the request information includes the pod IPs of all pods of the target application found by the k8s platform, and the endpoint name of the endpoint to be created or updated.
  • some embodiments of this application obtain the endpoint initiated by the k8s platform based on the admission webhook mechanism (a type of admission control plug-in that can be used to intercept all requests sent to APISERVER, and can modify the request or reject the request) Create request or endpoint update request.
  • the admission webhook mechanism a type of admission control plug-in that can be used to intercept all requests sent to APISERVER, and can modify the request or reject the request
  • Containerized applications are deployed on k8s clusters in the form of workloads, and each workload can run one or more instances (pods) at the same time.
  • K8s provides a service mechanism to access workloads. Each service has a corresponding access address outside the cluster or within the cluster, and provides a load balancing function to achieve load access to multiple pods. After each service is created, k8s will create an endpoint resource with the same name in real time. This resource contains all pod IPs and ports to be loaded by the service. Access to the service will be loaded to a certain pod IP and port on the endpoint through load balancing. superior.
  • k8s provides an admission webhook mechanism, which allows calling a custom admission controller to perform verification and modification actions during the resource creation process.
  • some embodiments of this application are based on k8s's service and endpoint resource management and combine with webhook Mechanism, develop a master-slave high-availability admission controller, obtain a preset admission controller, and deploy the preset admission controller on the container platform in advance and register it in the k8s platform.
  • k8s creates an endpoint, it calls the default admission controller and passes the endpoint creation request to the default admission controller.
  • Step S12 Obtain the pod IP list corresponding to the target application from the request resolution information.
  • some embodiments of this application can also obtain the endpoint name from the request parsing information; query the service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint; determine whether there is a preset master-slave tag in the service information; If there is a preset master-slave label and the value of the preset master-slave label is the first preset value, the step of querying the pod information corresponding to each pod ip in the pod ip list is triggered. If there is no default master-slave tag, or there is a default master-slave tag and the value of the default master-slave tag is the second default value, no processing is performed.
  • the endpoint name is the service name, so you can query based on the endpoint name. service information.
  • application developers create services for their applications, they can add a label to the service, that is, a default master-slave label, based on whether there is a requirement for master-slave high availability.
  • Step S13 Query the pod information corresponding to each pod ip in the pod ip list.
  • pod information can include creation time, name, etc.
  • Step S14 Determine a main pod from all pods of the target application based on all pod information and preset policies.
  • the pod with the earliest creation time can be determined from all pods of the target application based on all pod information and preset policies as the main pod. It is understandable that the earliest pods created are more stable.
  • the pod with the latest creation time can be determined from all pods of the target application as the main pod based on all pod information and preset policies. It is understandable that the latest pod created is the pod created based on the latest application to facilitate the provision of updated application services.
  • all pods can be sorted according to their creation time, and the main pod is determined based on the sorting results.
  • the main pod can also be determined through other strategies.
  • Step S15 Replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create or update endpoints based on the replacement request information to forward all access traffic of the target application to the main pod. superior.
  • the request information can be a global variable, so that the preset admission controller can directly modify the request information.
  • the k8s platform when it detects that the pod of the target application has changed, it initiates an endpoint update request; when any pod in the target application becomes abnormal, is deleted, or a new pod is added, it is determined that the pod of the target application has changed. That is to say, some embodiments of this application call the preset admission controller during the process of creating an endpoint for a service, query the associated pod information based on all pod IPs in the current endpoint creation request, and select all pods from all pods according to the preset policy.
  • Filter a master pod in the pod, and use the pod ip of the pod to replace the pod ip list in the request information, so that the request traffic through the service is only forwarded to the pod, and the pod will respond to the request as the master copy.
  • k8s will automatically trigger an endpoint update request in real time. It will also call the preset admission controller through the admission webhook mechanism and select the new pod as the main pod again based on the same logic when creating the endpoint.
  • a service creates or updates an endpoint
  • a certain pod IP is selected as the pod IP in the endpoint according to the preset policy, that is, a pod is selected as the backend of the service load, thereby forwarding traffic directly to the pod.
  • the master-slave high-availability access mechanism of multi-copy applications is realized.
  • the application can focus on the business logic of the application itself, avoiding performance problems caused by forwarding traffic to the slave replicas, and developing and deploying it once. It can be used by all applications in the cluster that require it.
  • the overall solution is simple, flexible, and easy to expand. There is a new pod selection strategy that can directly modify the controller processing logic, and it has good reusability and scalability.
  • FIG. 2 is a schematic diagram of a specific application access solution disclosed in some embodiments of the present application.
  • the client initiates a request to create a service, adds a master-slave processing label to the service, and sets the labelselector of the service to the label of the application.
  • k8s receives the request, creates a service, and queries all pods corresponding to the application based on labelselector, obtains the pod ip list, determines the request information, initiates an endpoint creation request based on the request information, and calls the registered admission controller (preset accurate Admission controller), when a pod exception, deletion, or addition is detected, an endpoint update request is automatically initiated based on the current request information.
  • the registered admission controller preset accurate Admission controller
  • the business processing logic of the preset admission controller is: parse the endpoint creation or update request, and obtain the request Parse the information; obtain the endpoint name, pod ip list, etc. from the request parsing information; query the service information based on the endpoint name; determine whether the service has a master-slave label. If the label exists and the value is true, it means that the service requires master-slave access, then Carry out subsequent processing logic. If the tag does not exist, it means that the service does not require master-slave access, and the execution will not continue and will be completed directly.
  • Subsequent processing logic includes: querying all pod information based on the pod ip list, sorting by creation time from early to late, and obtaining the first pod ip; replacing the ip list in the original request information with the filtered pod ip so that k8 can update based on Create or update the endpoint with the request information.
  • some embodiments of this application first parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtain the pod ip list corresponding to the target application from the request parsing information, and query each pod ip list in the pod ip list.
  • pod information corresponding to each pod ip then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement Request information so that the k8s platform can create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • some embodiments of this application use the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtain the request parsing information, and determine an endpoint based on the request parsing information and the preset policy.
  • the main pod use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all access traffic of the target application to the main pod, avoiding complexity and The election mechanism that is not easy to maintain and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • an application access device which is applied to a preset admission controller, including:
  • the request parsing module 11 is used to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information;
  • the list acquisition module 12 is used to obtain the pod ip list corresponding to the target application from the request parsing information
  • Information query module 13 used to query the pod information corresponding to each pod ip in the pod ip list;
  • the main pod determination module 14 is used to determine a main pod from all pods of the target application based on all pod information and preset policies;
  • Information update module 15 used to replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement request information, so that the k8s platform can create endpoints or updates based on the replacement request information to evenly distribute the access traffic of the target application. Forwarded to the main pod.
  • some embodiments of this application first parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information to obtain the request parsing information, and then obtain the pod ip list corresponding to the target application from the request parsing information, and query each pod ip list in the pod ip list.
  • pod information corresponding to each pod ip then determine a main pod from all pods of the target application based on all pod information and preset policies, and finally replace the pod ip list in the request information with the pod ip of the main pod to obtain the replacement Request information so that the k8s platform can create or update endpoints based on the replaced request information to forward all access traffic of the target application to the main pod.
  • some embodiments of this application use the preset admission controller to parse the endpoint creation request or endpoint update request initiated by the k8s platform based on the request information, obtain the request parsing information, and determine an endpoint based on the request parsing information and the preset policy.
  • Main pod use the pod ip of the main pod to replace the pod ip list in the request information.
  • the endpoint created or updated by the k8s platform based on the request information can forward all access traffic of the target application to the main pod, avoiding complexity and
  • the election mechanism that is not easy to maintain and the performance issues caused by forwarding traffic from replicas can reduce the complexity of application development and improve the response performance of application access.
  • the application access device further includes: an endpoint name acquisition module, configured to obtain the endpoint name from the request parsing information.
  • application access devices also include:
  • the service information query module is used to query service information based on the endpoint name; where the service information is the information of the service corresponding to the endpoint;
  • the master-slave tag judgment module is used to judge whether there is a preset master-slave tag in the service information; if there is a preset master-slave tag and the value of the preset master-slave tag is the first preset value, the information query module 13 is triggered to execute the query.
  • Each pod ip list Steps for pod information corresponding to pod ip. If there is no default master-slave tag, or there is a default master-slave tag and the value of the default master-slave tag is the second default value, no processing is performed.
  • the main pod determination module 14 is specifically configured to determine the pod with the earliest creation time from all pods of the target application based on all pod information and preset policies as the main pod.
  • the main pod determination module 14 is specifically configured to determine the pod with the latest creation time from all pods of the target application based on all pod information and preset policies as the main pod.
  • the application access device also includes a request acquisition module, which is used to obtain the endpoint creation request or endpoint update request initiated by the k8s platform based on the admission webhook mechanism.
  • some embodiments of the present application disclose an electronic device 20, which includes a processor 21 and a memory 22; the memory 22 is used to save the computer program; the processor 21 is used to execute the computer program.
  • the aforementioned implementation Example public application access methods.
  • the memory 22, as a carrier for resource storage may be a read-only memory, a random access memory, a magnetic disk or an optical disk, etc., and the storage method may be short-term storage or permanent storage.
  • the electronic device 20 also includes a power supply 23, a communication interface 24, an input and output interface 25 and a communication bus 26; the power supply 23 is used to provide operating voltage for each hardware device on the electronic device 20; the communication interface 24 can provide the electronic device 20 with working voltage.
  • a data transmission channel with external devices and the communication protocol it follows is any communication protocol that can be applied to the technical solution of this application, which is not specifically limited here; the input and output interface 25 is used to obtain external input data or To output data to the outside world, the specific interface type can be selected according to specific application needs, and is not specifically limited here.
  • some embodiments of the present application also disclose a computer non-volatile readable storage medium for storing computer programs.
  • the computer non-volatile readable storage medium 5 stores computer programs. 51, wherein the computer program 51 implements the application access method disclosed in the foregoing embodiments when executed by the processor.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically programmable ROM
  • EEPly erasable programmable ROM registers, hard disks, removable disks, CD-ROM, or any other form of storage media known in the technical field.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Sont divulgués dans la présente demande un procédé et un appareil d'accès à une application, ainsi qu'un dispositif et un support qui sont appliqués dans le domaine technique de l'accès aux applications. Le procédé consiste : à analyser une demande de création de terminal ou une demande de mise à jour de terminal qui est initiée par une plate-forme k8s sur la base d'informations de demande, de façon à obtenir des informations d'analyse de demande ; à acquérir, à partir des informations d'analyse de demande, une liste IP de modules correspondant à une application cible ; à interroger des informations de module correspondant à chaque IP de module dans la liste IP de modules ; sur la base de tous les éléments d'informations de module et d'une politique prédéfinie, à déterminer un module maître à partir de tous les modules de l'application cible ; et à remplacer la liste IP de modules dans les informations de demande par un module IP du module maître, de façon à obtenir des informations de demande qui ont été soumises à un remplacement, de telle sorte que la plateforme k8s crée ou mette à jour un terminal sur la base des informations de demande qui ont été soumises à un remplacement, de façon à transférer tout le trafic d'accès de l'application cible au module maître. De cette manière, la complexité du développement d'une application peut être réduite et la performance de la réponse de l'accès à l'application peut également être améliorée.
PCT/CN2023/084815 2022-04-11 2023-03-29 Procédé et appareil d'accès à une application, dispositif et support WO2023197874A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210371384.2A CN114448895B (zh) 2022-04-11 2022-04-11 一种应用访问方法、装置、设备及介质
CN202210371384.2 2022-04-11

Publications (1)

Publication Number Publication Date
WO2023197874A1 true WO2023197874A1 (fr) 2023-10-19

Family

ID=81360394

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/084815 WO2023197874A1 (fr) 2022-04-11 2023-03-29 Procédé et appareil d'accès à une application, dispositif et support

Country Status (2)

Country Link
CN (1) CN114448895B (fr)
WO (1) WO2023197874A1 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114448895B (zh) * 2022-04-11 2022-06-17 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质
CN115277652B (zh) * 2022-06-29 2024-03-22 北京百度网讯科技有限公司 基于推理服务的流媒体处理方法、装置、电子设备
CN116033010A (zh) * 2023-02-16 2023-04-28 北京有竹居网络技术有限公司 远程访问方法、装置、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112153143A (zh) * 2020-09-24 2020-12-29 新浪网技术(中国)有限公司 Kubernetes集群的流量调度方法、装置及电子设备
WO2021063339A1 (fr) * 2019-09-30 2021-04-08 星环信息科技(上海)股份有限公司 Procédé, appareil, dispositif de planification de ressources en grappe et support de stockage
US20210328858A1 (en) * 2020-04-16 2021-10-21 Ribbon Communications Operating Company, Inc. Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system
CN114124948A (zh) * 2021-09-19 2022-03-01 济南浪潮数据技术有限公司 一种云端组件高可用的方法、装置、设备及可读介质
CN114448895A (zh) * 2022-04-11 2022-05-06 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113741923A (zh) * 2020-05-27 2021-12-03 华为技术有限公司 一种应用更新方法、装置、设备及介质
CN111901157B (zh) * 2020-07-10 2023-01-10 苏州浪潮智能科技有限公司 一种基于k8s的服务部署方法、装置、设备、介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021063339A1 (fr) * 2019-09-30 2021-04-08 星环信息科技(上海)股份有限公司 Procédé, appareil, dispositif de planification de ressources en grappe et support de stockage
US20210328858A1 (en) * 2020-04-16 2021-10-21 Ribbon Communications Operating Company, Inc. Communications methods and apparatus for migrating a network interface and/or ip address from one pod to another pod in a kubernetes system
CN112153143A (zh) * 2020-09-24 2020-12-29 新浪网技术(中国)有限公司 Kubernetes集群的流量调度方法、装置及电子设备
CN114124948A (zh) * 2021-09-19 2022-03-01 济南浪潮数据技术有限公司 一种云端组件高可用的方法、装置、设备及可读介质
CN114448895A (zh) * 2022-04-11 2022-05-06 苏州浪潮智能科技有限公司 一种应用访问方法、装置、设备及介质

Also Published As

Publication number Publication date
CN114448895A (zh) 2022-05-06
CN114448895B (zh) 2022-06-17

Similar Documents

Publication Publication Date Title
US10630779B2 (en) System and method for using VoIP session continuity information using logical scalable units
US10523545B2 (en) System and method for managing VoIP session continuity information using logical scalable units
WO2023197874A1 (fr) Procédé et appareil d'accès à une application, dispositif et support
US11157304B2 (en) System for peering container clusters running on different container orchestration systems
US7779010B2 (en) Repartitioning live data
US10713071B2 (en) Method and apparatus for network function virtualization
US9489443B1 (en) Scheduling of splits and moves of database partitions
US11991094B2 (en) Metadata driven static determination of controller availability
EP3583765B1 (fr) Abstraction de point d'extrémité pour communication de service à service
CN109525590B (zh) 数据包的传输方法及装置
EP3065379A1 (fr) Système et procédé de poursuite de session volte utilisant des unités logiques échelonnables
US20240089352A1 (en) Udp message distribution method, udp message distribution apparatus, electronic device and computer readable storage medium
CN111818188B (zh) 一种Kubernetes集群的负载均衡可用性提升方法和装置
US11366648B2 (en) Compiling monoglot function compositions into a single entity
CN112583740B (zh) 网络通信方法及装置
US20210377718A1 (en) Pattern affinity for discovery
US20240259473A1 (en) Distributed serverless rule consequence evaluation for a containerized rules engine
US11768704B2 (en) Increase assignment effectiveness of kubernetes pods by reducing repetitive pod mis-scheduling
WO2024193269A1 (fr) Procédé et appareil d'accès à une base de données, et support de stockage lisible par ordinateur
US11924031B2 (en) Highly scalable container network interface operation to reduce startup overhead of functions
US20240028358A1 (en) A general network policy for namespaces
US11108641B2 (en) Automatic switching fabric role determination system
US11665167B2 (en) Dynamically deployed limited access interface to computational resources
WO2021072967A1 (fr) Procédé et dispositif de gestion d'informations de configuration
US20200252336A1 (en) Switching fabric configuration and management system

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23787520

Country of ref document: EP

Kind code of ref document: A1