Method, device and equipment for generating service grid configuration XDS based on DPU and medium

By creating a discovery server in the DPU service mesh and processing push requests, the problem of node-level configuration updates is solved, and Istio's flexibility and functional expansion is achieved to adapt to a variety of deployment scenarios.

CN118921403APending Publication Date: 2024-11-08YUSUR TECH CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411113206.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-14
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the DPU service mesh, the management node cannot obtain node-level service mesh configuration updates, resulting in the agent being unable to synchronize the configuration of all sidecar identities.

Method used

By creating and starting a discovery server, using asynchronous coroutines to process push requests, initializing push context, traversing configurations, determining target resources, and generating cluster configurations based on DPU node enumeration types, realizing node-level proxy filter content updates.

Benefits of technology

It solves the problem that DPU identity cannot obtain node-level XDS, and increases the flexibility and functional expansion of Istio to adapt to various deployment scenarios and needs.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118921403A_ABST
    Figure CN118921403A_ABST
Patent Text Reader

Abstract

The invention provides a method, device and equipment for generating a service grid configuration XDS based on a DPU and a medium, and the method comprises the steps: creating and starting a discovery server, and updating the XDS for self-defined resources of a service grid through an asynchronous coroutine; processing the self-defined resources from a push pipeline, and executing anti-shake and push requests in an independent thread; pushing processing is carried out based on the pushing request, pushing configuration updating is carried out through configuration aggregation service, the pushing configuration updating comprises initialization of a pushing context, and the pushing context is used for traversing configuration in the pushing request; determining a target resource from the configuration in the push request; if the target resource is of a newly added DPU node enumeration type, triggering content update of a proxy filter at a node level; and generating cluster configuration of the XDS according to the DPU node enumeration type and the proxy filter of the node level. The method and the device are used for solving the problem that the existing DPU identity cannot acquire the node-level XDS.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of network communication technology, and in particular to a method, apparatus, device and medium for generating a service grid configuration XDS based on a DPU. Background Art

[0002] In traditional service grids, Envoy proxy is configured by setting different node types to meet specific deployment requirements and scenarios. In the existing technology of DPU service grid, the management node sends the required service grid configuration according to the identity of the proxy. In the service grid of DPU, Envoy proxy is deployed in a centralized form, that is, a node has only one envoy located in soc. The adapter receives the request of the data plane network proxy (soc envoy) of the grid on DPU, and requests the management node to obtain all service grid configurations at the node level, and sends them to soc envoy after aggregation. The adapter uses the identity of soc envoy to establish a long link with the management node. The identity of soc envoy is in the form of sidecar (the default setting of the node type). Therefore, the service grid configuration of the management node in push mode sends the service grid configuration of the sidecar type according to the identity of soc envoy, which will cause soc envoy to not receive the update of the service grid configuration of all sidecar identities of this node.

[0003] Therefore, there is no applicable node type for DPU node-level proxy management, so a method is needed to synchronize the service mesh configuration of all sidecar identities on the node for the DPU scenario. Summary of the invention

[0004] The embodiment of the present application provides a method for configuring XDS based on DPU-generated service grid, so as to solve the problem that the existing DPU identity cannot obtain node-level XDS.

[0005] In a first aspect, an embodiment of the present application provides a method for generating a service grid configuration XDS based on a DPU, including:

[0006] Create and start the discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines;

[0007] Process the custom resource from the push pipeline and perform deshaking and push requests in separate threads;

[0008] The discovery server performs push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request;

[0009] Determine a target resource from the configuration in the push request;

[0010] If the target resource is a resource of a proxy filter and the identity is of the default type, then the proxy filter content update of the distinguished namespace is triggered; if the target resource is of a newly added DPU node enumeration type, then the node-level proxy filter content update is triggered;

[0011] A cluster configuration of the XDS is generated according to the DPU node enumeration type and the node-level proxy filter.

[0012] In a possible implementation, the method further includes:

[0013] Push the push request to the push queue, the push coroutine obtains the push request from the push queue, and pushes the push request to the push channel;

[0014] Obtain a push request from the push channel, and perform a push action of the XDS according to the push request; or,

[0015] When a client in a streaming connection makes an active request, the pull request is obtained from the pull queue, and a push action of the XDS is performed according to the pull request.

[0016] In a possible implementation manner, when the target resource is a newly added DPU enumeration type, the scope of the proxy filter is determined according to the content update of the node-level proxy filter.

[0017] In a possible implementation manner, the XDSs are different and the corresponding XDS resource generators are different.

[0018] In a possible implementation, the configuration in the push request includes at least one resource, and the at least one resource includes a target resource.

[0019] In a possible implementation manner, the at least one resource includes at least one of the following: a proxy configuration, a proxy filter, a virtual service, a service entry, or a routing rule.

[0020] In a possible implementation, before starting the discovery server, a DPU node enumeration type is added.

[0021] In a second aspect, an embodiment of the present application provides a device for generating a service grid configuration XDS based on a DPU, including:

[0022] Create a module to create and start a discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines;

[0023] A processing module, used to process the custom resource from the push pipeline and execute anti-shake and push requests in independent threads;

[0024] A configuration module, used for the discovery server to perform push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request;

[0025] A determination module, used to determine the target resource from the configuration in the push request;

[0026] An update module, configured to trigger a content update of a proxy filter that distinguishes namespaces if the target resource is a resource of a proxy filter and the identity is of a default type; and trigger a content update of a proxy filter at a node level if the target resource is a newly added DPU enumeration type;

[0027] A generation module is used to generate a cluster configuration of the XDS according to the newly added DPU enumeration type and the node-level proxy filter.

[0028] In a possible implementation, the device further includes a push module, which is used to:

[0029] Push the push request to the push queue, the push coroutine obtains the push request from the push queue, and pushes the push request to the push channel;

[0030] Obtain a push request from the push channel, and perform a push action of the XDS according to the push request; or,

[0031] When a client in a streaming connection makes an active request, the pull request is obtained from the pull queue, and a push action of the XDS is performed according to the pull request.

[0032] In a possible implementation manner, when the target resource is a newly added DPU enumeration type, the scope of the proxy filter is determined according to the content update of the node-level proxy filter.

[0033] In a possible implementation manner, the XDSs are different and the corresponding XDS resource generators are different.

[0034] In a possible implementation, the configuration in the push request includes at least one resource, and the at least one resource includes a target resource.

[0035] In a possible implementation manner, the at least one resource includes at least one of the following: a proxy configuration, a proxy filter, a virtual service, a service entry, or a routing rule.

[0036] In a possible implementation, the device further includes an adding module, configured to add a DPU node enumeration type before starting the discovery server.

[0037] In a third aspect, an embodiment of the present application further provides an electronic device, the electronic device comprising:

[0038] at least one processor;

[0039] and a memory communicatively coupled to the at least one processor;

[0040] Among them, the memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the electronic device to execute a method corresponding to any embodiment in the first aspect of the embodiments of the present application.

[0041] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, in which computer-readable storage medium is stored computer execution instructions, which, when executed by a processor, are used to implement any method of the first aspect of the embodiment of the present application.

[0042] In a fifth aspect, the present disclosure further provides a computer program product, which includes computer execution instructions, and the computer execution instructions are used to implement the method when executed by a processor.

[0043] In summary, the method shown in the embodiment of the present application is used to solve the problem that the existing DPU identity cannot obtain the node-level XDS. By adding new node types for DPU scenarios or requirements to Istio, adding new DPU nodes can bring greater flexibility, functional expansion and ecosystem enrichment to Istio, so that it can better adapt to various deployment scenarios and requirements. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0045] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0046] Figure 1 A schematic diagram of a method flow for configuring XDS based on DPU generation of a service grid provided in an embodiment of the present application;

[0047] Figure 2A schematic diagram of a device for configuring XDS based on DPU generation of a service grid provided in an embodiment of the present application;

[0048] Figure 3 A schematic diagram of an electronic device that generates a service grid configuration XDS based on a DPU provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments are only examples of devices and methods consistent with some aspects of the embodiments of the present application as detailed in the appended claims.

[0050] The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. The following will describe the embodiments of the present application in conjunction with the accompanying drawings.

[0051] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0052] DPU: Data Processing Unit, as a dedicated hardware accelerator, is a new generation of data-centric computing processors that integrates complete data center functions into a single chip. Together with CPU and GPU, it constitutes the three pillars of new computing. By using specially designed hardware accelerators to quickly process data packets entering the DPU, processing delays can be reduced and processing throughput can be improved.

[0053] K8S: Its full name is kubernetes, and K8S is its abbreviation, with the word "8" replacing the eight characters of "ubernete". It is a container-based cluster management platform, which can also be called an open source container orchestration platform, used to automate the deployment, expansion and management of containerized applications. It provides a flexible and scalable way to manage containerized applications, and provides a range of features to simplify application deployment, scheduling, self-healing and expansion.

[0054] Pod: An abbreviation for Point of Delivery, Kubernetes encapsulates one or more containers into a high-level structure called a pod. Any container in the same pod will share the same namespace and local network. Containers can easily communicate with other containers in the same container, just as if they were on the same machine while maintaining a certain degree of isolation.

[0055] Service Mesh: Service Mesh is a network infrastructure layer used to manage and control communication between services in a microservice architecture. It solves complex network communication, security, observability, and traffic management issues in a microservice architecture. Service Mesh provides a transparent and standardized approach to make communication between microservices more reliable and manageable.

[0056] Istio: is an open source service mesh platform for managing and controlling the communication between services in a microservice architecture. Service mesh is an architectural pattern for dealing with the complexity of network communication, security, observability, and traffic management between different microservices in an application. In the embodiments of this application, we refer to it as the management node of the service mesh.

[0057] XdS: XdS is part of the Istio service mesh. It is a system for configuring and managing network proxies (Envoy). It represents a variety of different configuration and discovery services, such as CDS (Cluster Discovery Service), EDS (Endpoint Discovery Service), RDS (Route Discovery Service), etc. These services work together to ensure the correct configuration and dynamic update of the Envoy proxy.

[0058] CDS: (Cluster Discovery Service) CDS is used to define and configure the cluster of Envoy proxies. It can specify the cluster of backend services and define load balancing policies, connection pool sizes, etc.

[0059] EDS: (Endpoint Discovery Service) EDS is used to configure the endpoints of the Envoy proxy, that is, the specific instances of the backend services. It provides information about each service instance so that Envoy can route requests to the correct instance.

[0060] RDS: (Route Discovery Service) RDS is used to configure Envoy's routing rules. Through RDS, you can define how requests should be routed to different services and versions to implement functions such as traffic management and A / B testing.

[0061] SDS: (Secret Discovery Service) SDS is used to configure the security certificates and keys of the Envoy proxy to ensure the confidentiality and integrity of communications.

[0062] In the management node Istio, NodeType is a configuration option that specifies how the Envoy proxy is deployed. NodeType can be set to three different values:

[0063] sidecar: is the default setting for NodeType. In sidecar mode, the Envoy proxy is deployed as a sidecar container with each application container. Each application container will have a corresponding Envoy sidecar container that is responsible for handling inbound and outbound traffic for the application and implementing the various features provided by Istio, such as traffic management, policy enforcement, monitoring, and security.

[0064] ingress: When NodeType is set to ingress, the Envoy proxy is deployed as an ingress proxy to manage inbound traffic for applications. This deployment method is suitable for directing traffic to the edge of the service in the Istio mesh, usually to direct external traffic into the cluster controlled by Istio.

[0065] router: When NodeType is set to router, the Envoy proxy will only be used for traffic forwarding and will not be directly associated with the application container. This deployment method is suitable for using the Envoy proxy as a standalone router, such as outside the Kubernetes cluster or at other network levels.

[0066] However, there is no applicable nodetype for Istio, the DPU node-level proxy. Therefore, Istio is developed for the DPU scenario to obtain an applicable nodetype.

[0067] Figure 1A method for configuring XDS based on DPU generation of service grid is provided in an embodiment of the present application. Figure 1 The method includes steps S101 to S106. Each step is described in detail as follows.

[0068] S101. Create and start a discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines.

[0069] In a possible implementation, before starting the discovery server, a DPU node enumeration type is added.

[0070] In the embodiment of the present application, a discovery server (discoveryServer) is created and started through the management node (Istio) of the service grid. Before starting the discovery server, the DPU node enumeration type is added through the management node of the service grid. After starting the server, the custom resource CRD of the discovered service grid is updated through an asynchronous coroutine.

[0071] S102: Process the custom resource from the push pipeline, and execute anti-shake and push request in an independent thread.

[0072] In an embodiment of the present application, Istio processes events from the push pipeline, that is, it processes custom resource CRDs. Istio performs anti-shake and push requests in separate threads to ensure that at least the minimum quiet time (minQuiet) has passed before processing the event, and at most the maximum delay time (maxDelay) has passed between receiving the event and processing the event. Anti-shake prevents a large number of high-concurrency envoy agents from triggering update configuration requests during the minimum quiet time, causing an impact on Istio. When it is less than the quiet time, no update processing is performed.

[0073] S103, the discovery server performs push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request;

[0074] In a possible implementation, the configuration in the push request includes at least one resource, and the at least one resource includes a target resource.

[0075] In a possible implementation manner, the at least one resource includes at least one of the following: a proxy configuration, a proxy filter, a virtual service, a service entry, or a routing rule.

[0076] It can be understood that in the embodiment of the present application, the discovery server pushes configuration updates based on the push request through the configuration aggregation service (ADS). In the process of pushing the configuration update, it includes initializing the push configuration context (initPushContext), that is, the push configuration context includes creating / updating a global push context (PushContext). The above push context needs to traverse the update configuration (pushReq.ConfigsUpdated) in the push request. The configuration in the push request includes at least one of the following resources: proxy configuration (ProxyConfig), proxy filter (EnvoyFilter), virtual service (VirtualService), service entry (ServiceEntry) or routing rule (DestinationRule).

[0077] S104: Determine the target resource from the configuration in the push request.

[0078] At least one of the following resources is determined in the configuration in the push request: a proxy configuration (ProxyConfig), a proxy filter (EnvoyFilter), a virtual service (VirtualService), a service entry (ServiceEntry), or a routing rule (DestinationRule), that is, the determined resource is a target resource.

[0079] S105. If the target resource is a resource of a proxy filter and the identity is of a default type, then a proxy filter content update that differentiates the namespace is initiated; if the target resource is of a newly added DPU node enumeration type, then a node-level proxy filter content update is triggered.

[0080] Exemplarily, if the resource is a resource of an Envoy filter and the identity is a sidecar, the proxy filter content update for distinguishing namespaces is triggered. If the identity is a newly added DPU, the content update of the node-level proxy filter (envoyFiltersByNode) is triggered. This embodiment of the application does not limit this.

[0081] In a possible implementation, the method further includes:

[0082] Push the push request to the push queue, the push coroutine obtains the push request from the push queue, and pushes the push request to the push channel;

[0083] Obtain a push request from the push channel, and perform a push action of the XDS according to the push request; or,

[0084] When a client in a streaming connection makes an active request, the pull request is obtained from the pull queue, and a push action of the XDS is performed according to the pull request.

[0085] It can be understood that the control component (controllers) of the discovery server pushes the push request information to the push queue (pushQueue). The discovery server sends a push goroutine (sendPushes goroutine), which obtains the push request information from the push queue and pushes the push request information to the push channel (push channel). The streaming server of the aggregated resources in the discovery server sends an XDS push action in the push queue, obtains the push request from the push pipeline, and performs an XDS push action based on the push request; or, when a client makes an active request for the streaming connection, a request is taken from the pull queue and an XDS push action is performed based on the request.

[0086] In a possible implementation manner, the XDSs are different and the corresponding XDS resource generators are different.

[0087] In a possible implementation manner, when the target resource is a newly added DPU enumeration type, the scope of the proxy filter is determined according to the content update of the node-level proxy filter.

[0088] Exemplarily, CDS triggers CDS resource generator, which determines the scope of the proxy based on the proxy information. If it is a newly added DPU, the scope of the proxy filter is determined based on the content update of the proxy filter that distinguishes the node level. EDS triggers EDS resource generator, which determines the scope of the proxy based on the proxy information. If it is a newly added DPU, the scope of the proxy filter is determined based on the content update of the proxy filter that distinguishes the node level.

[0089] S106: Generate a cluster configuration of the XDS according to the DPU node enumeration type and the node-level proxy filter.

[0090] The method shown in the embodiment of the present application is used to solve the problem that the existing DPU identity cannot obtain the node-level XDS. By adding new node types for DPU scenarios or requirements to Istio, adding new DPU nodes can bring greater flexibility, functional expansion and ecosystem enrichment to Istio, so that it can better adapt to various deployment scenarios and requirements.

[0091] Figure 2 An embodiment of the present application provides a device for generating a service grid configuration XDS based on a DPU, including:

[0092] A creation module 201 is used to create and start a discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines;

[0093] A processing module 202, configured to process the custom resource from the push pipeline and execute anti-shake and push requests in an independent thread;

[0094] Configuration module 203, used for the discovery server to perform push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request;

[0095] A determination module 204, configured to determine a target resource from the configuration in the push request;

[0096] An update module 205, configured to trigger a proxy filter content update for distinguishing namespaces if the target resource is a resource of a proxy filter and the identity is of a default type; and trigger a node-level proxy filter content update if the target resource is a newly added DPU enumeration type;

[0097] The generating module 206 is configured to generate the cluster configuration of the XDS according to the newly added DPU enumeration type and the node-level proxy filter.

[0098] In a possible implementation, the device further includes a push module 207, which is used to:

[0099] The push request is pushed to the push queue, the push coroutine obtains the push request from the push queue, and pushes the push request to the push channel; the push request is obtained from the push channel, and the push action of the XDS is performed according to the push request; or, when the client in the streaming connection makes an active request, the pull request is obtained from the pull queue, and the push action of the XDS is performed according to the pull request.

[0100] In a possible implementation manner, when the target resource is a newly added DPU enumeration type, the scope of the proxy filter is determined according to the content update of the node-level proxy filter.

[0101] In a possible implementation manner, the XDSs are different and the corresponding XDS resource generators are different.

[0102] In a possible implementation, the configuration in the push request includes at least one resource, and the at least one resource includes a target resource.

[0103] In a possible implementation manner, the at least one resource includes at least one of the following: a proxy configuration, a proxy filter, a virtual service, a service entry, or a routing rule.

[0104] In a possible implementation, the device further includes an adding module 208, which is used to add a DPU node enumeration type before starting the discovery server.

[0105] The above device is used to realize Figure 1 Any of the embodiment methods shown.

[0106] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 3 As shown, the electronic device 300 includes: a memory 310 and a processor 320 .

[0107] The memory 310 stores a computer program that can be executed by at least one processor 320. The computer program is executed by at least one processor 320 to enable the electronic device to implement the method provided in any of the above embodiments.

[0108] The memory 310 and the processor 320 may be connected via a bus 330 .

[0109] The relevant instructions can be understood by referring to the relevant descriptions and effects corresponding to the method embodiments, which will not be repeated here.

[0110] An embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and the computer program is executed by a processor to implement the following Figure 1 The method of any corresponding embodiment.

[0111] Among them, the computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0112] An embodiment of the present application provides a computer program product, which includes computer-executable instructions, which are used to implement the following when the computer-executable instructions are executed by a processor: Figure 1 The method of any corresponding embodiment.

[0113] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0114] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the disclosure disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope of the present application is indicated by the claims.

[0115] It should be understood that the present application is not limited to the exact construction that has been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof.

Claims

1. A method for generating a service grid configuration XDS based on a DPU, characterized in that: include: Create and start the discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines; Process the custom resource from the push pipeline and perform deshaking and push requests in separate threads; The discovery server performs push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request; Determine a target resource from the configuration in the push request; If the target resource is a resource of a proxy filter and the identity is of the default type, then the proxy filter content update of the distinguished namespace is triggered; if the target resource is of a newly added DPU node enumeration type, then the node-level proxy filter content update is triggered; A cluster configuration of the XDS is generated according to the DPU node enumeration type and the node-level proxy filter.

2. The method according to claim 1, characterized in that The method further comprises: Push the push request to the push queue, the push coroutine obtains the push request from the push queue, and pushes the push request to the push channel; Obtain a push request from the push channel, and perform a push action of the XDS according to the push request; or, When a client in a streaming connection makes an active request, the pull request is obtained from the pull queue, and a push action of the XDS is performed according to the pull request.

3. The method according to claim 2, characterized in that include: In the case where the target resource is a newly added DPU enumeration type, the scope of the proxy filter is determined according to the content update of the node-level proxy filter.

4. The method according to any one of claims 1 to 3, characterized in that: include: The XDSs are different, and the corresponding XDS resource generators are different.

5. The method according to any one of claims 1 to 4, characterized in that: The configuration in the push request includes at least one resource, and the at least one resource includes a target resource.

6. The method according to claim 5, characterized in that The at least one resource includes at least one of the following: a proxy configuration, a proxy filter, a virtual service, a service entry, or a routing rule.

7. The method according to any one of claims 1 to 5, characterized in that: The method further includes: before starting the discovery server, adding a DPU node enumeration type.

8. A device for generating a service grid configuration XDS based on a DPU, characterized in that: include: Create a module to create and start a discovery server, and update XDS for custom resources of the service grid through asynchronous coroutines; A processing module, used to process the custom resource from the push pipeline and execute anti-shake and push requests in independent threads; A configuration module, used for the discovery server to perform push processing based on the push request, the push processing performs push configuration update through the configuration aggregation service, the push configuration update includes initializing a push context, and the push context is used to traverse the configuration in the push request; A determination module, used to determine the target resource from the configuration in the push request; An update module, configured to trigger a content update of a proxy filter that distinguishes namespaces if the target resource is a resource of a proxy filter and the identity is of a default type; and trigger a content update of a proxy filter at a node level if the target resource is a newly added DPU enumeration type; A generation module is used to generate a cluster configuration of the XDS according to the newly added DPU enumeration type and the node-level proxy filter.

9. An electronic device, characterized in that: include: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the electronic device to perform the method as claimed in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

11. A computer program product comprising computer executable instructions, characterized in that: The computer-executable instructions are used to implement the method according to any one of claims 1 to 7 when executed by a processor.

Citation Information

Cited By

  • Communication configuration method and device based on DPU centralized service grid, and medium

    CN120223742A