CN115185611A - Method, device, system and equipment for dynamic loading of service grid proxy configuration - Google Patents
Method, device, system and equipment for dynamic loading of service grid proxy configuration Download PDFInfo
- Publication number
- CN115185611A CN115185611A CN202210899901.3A CN202210899901A CN115185611A CN 115185611 A CN115185611 A CN 115185611A CN 202210899901 A CN202210899901 A CN 202210899901A CN 115185611 A CN115185611 A CN 115185611A
- Authority
- CN
- China
- Prior art keywords
- workload
- service grid
- feature
- information
- agent
- 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.)
- Pending
Links
Images
Classifications
-
- 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/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- 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/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- 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/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a method, a device, a system and equipment for dynamic loading of service grid proxy configuration. The method, the device and the equipment realize the characteristic source required to be perceived by the workload in the self-defined service grid by configuring the dynamic loading description information of the agent at the control surface of the service grid, can dynamically acquire the resource characteristic information of the node where the workload is located according to the characteristic source required to be perceived by the workload when the service grid agent configuration is loaded, generate the configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, load the configuration information into the service grid agent configuration corresponding to the workload, and dynamically update the service grid agent configuration into the service grid agent configuration corresponding to the workload, thereby realizing the dynamic loading function of the service grid agent configuration based on the resource characteristic perception.
Description
Technical Field
The present application relates to computer technologies, and in particular, to a method, an apparatus, a system, and a device for dynamic loading of service grid proxy configuration.
Background
A Service Mesh refers to a configurable infrastructure layer for microservice application management that may provide a range of functions such as Service discovery, load balancing, encryption, authentication, authorization, fuse mode support, and others. For example, to ensure the functions of the service grid, the control plane generally issues configuration data to each service grid agent through service grid agent configuration, so that the service grid can correctly agent service traffic, thereby implementing service interworking and service management.
The current service grid agent configuration supports two loading modes, one mode is that related technical personnel manually configure global static service grid agent configuration on a control surface; the other is to manually configure the service grid agent corresponding workload by means of configuration comments before the machine/workload container group where the service grid agent is located is started. In any of the above loading methods, static service grid proxy configuration can only be loaded when the machine is started, and dynamic loading of service grid proxy configuration cannot be realized.
Disclosure of Invention
The application provides a method, a device, a system and equipment for dynamic loading of service grid agent configuration, which are used for solving the problem that the dynamic loading of the service grid agent configuration cannot be realized.
In one aspect, the present application provides a method for dynamically loading a service grid proxy configuration, including:
determining a feature source required to be sensed by a workload in a service grid according to the configured agent dynamic loading description information;
acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be perceived by the workload;
generating configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loading the configuration information into service grid agent configuration corresponding to the workload;
and dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
In another aspect, the present application provides a device for dynamically loading service grid proxy configuration, including:
the characteristic source determining module is used for determining a characteristic source required to be sensed by a workload in a service grid according to the configured agent dynamic loading description information;
the characteristic acquisition module is used for acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be perceived by the workload;
a dynamic loading module, configured to generate configuration information corresponding to the resource feature information according to the resource feature information of the node where the workload is located, and load the configuration information into a service grid agent configuration corresponding to the workload;
and the dynamic updating module is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
In another aspect, the present application provides a system for dynamic loading of service grid agent configuration, where the service grid includes a control plane layer, a data plane layer, and a function application layer, where the function application layer runs a workload, the data plane layer runs a service grid agent corresponding to the workload, the workload and the corresponding service grid agent have a bidirectional communication link therebetween, and different service grid agents have a bidirectional communication link therebetween;
the system comprises: the system comprises a configuration module and a characteristic source determining module which are positioned on a control surface layer, and a characteristic obtaining module, a dynamic loading module and a dynamic updating module which are positioned on a data surface layer;
the configuration module is used for configuring agent dynamic loading description information, and the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid;
the characteristic source determining module is used for determining a characteristic source required to be sensed by a workload in a service grid according to the configured agent dynamic loading description information;
the characteristic acquisition module is used for acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be perceived by the workload;
the dynamic loading module is used for generating configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loading the configuration information into service grid agent configuration corresponding to the workload;
and the dynamic updating module is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
In another aspect, the present application provides an electronic device comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer execution instructions;
the processor executes the computer-executable instructions stored in the memory to implement the method for dynamically loading the service grid agent configuration.
In another aspect, the present application provides a computer-readable storage medium, in which computer-executable instructions are stored, and when executed by a processor, the computer-executable instructions are used to implement the method for dynamically loading service grid proxy configuration described above.
In another aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method for dynamic loading of service grid proxy configuration as described above.
According to the method, the device, the system and the equipment for dynamically loading the service grid proxy configuration, description information is dynamically loaded through the configuration proxy, the characteristic source required to be perceived by a working load in a service grid is customized, the resource characteristic information of the node where the working load is located can be dynamically obtained according to the characteristic source required to be perceived by the working load, the configuration information corresponding to the resource characteristic information is generated according to the resource characteristic information of the node where the working load is located, the configuration information is loaded into the service grid proxy configuration corresponding to the working load, the service grid proxy configuration is dynamically updated into the service grid proxy configuration corresponding to the working load, and the dynamic loading function of the service grid proxy configuration based on the resource characteristic perception is achieved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram of a services grid provided herein;
FIG. 2 is a flowchart of a method for dynamic loading of a service grid proxy configuration according to an exemplary embodiment of the present application;
fig. 3 is a framework diagram for acquiring resource feature information of a node according to an exemplary embodiment of the present application;
FIG. 4 is a block diagram of a dynamic loading of a service grid proxy configuration provided by an exemplary embodiment of the present application;
FIG. 5 is a flowchart of a method for dynamic loading of a service grid proxy configuration according to another exemplary embodiment of the present application;
FIG. 6 is a schematic structural diagram of an apparatus for dynamically loading a service grid proxy configuration according to an exemplary embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an example embodiment of the present application.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terms referred to in the present application are explained first:
serving the grid: refers to a configurable infrastructure layer for microservice application management, which is commonly used to describe the services (e.g., microservices) that make up an application and the interactions between the various services. A service grid is generally composed of a control plane and a data plane. The control plane is a group of services running in a dedicated namespace, and the services are used for completing some control management functions, such as aggregating telemetry data, providing an Application Programming Interface (API for short) facing a user, providing control data for a data plane, and the like; and the data plane is made up of a series of transparent proxies running alongside each service instance.
Serving the grid agent: the method is used for forwarding the request to be sent to or sent by the service grid, and the request corresponding to each micro-service in the service grid passes through the service grid proxy.
Service grid agent configuration: the service grid agent configuration refers to configuration data issued by a control surface to each service grid agent in order to enable a service grid to correctly agent service flow and realize service intercommunication and service management.
Illustratively, fig. 1 is a schematic diagram of a service grid provided herein. As shown in FIG. 1, the service grid 100 is primarily used to facilitate secure and reliable communications between multiple microservices, which refers to the breaking up of applications into multiple smaller services or instances that are distributed across different clusters/machines.
As shown in FIG. 1, the microservice includes an application service instance A and an application service instance B, which form the functional application layer of the service grid 100. In one embodiment, application service instances A and B run in the form of containers/processes on a machine/workload container group (machine/Pod). Illustratively, application service instance a may be a commodity inquiry service and application service instance B may be a commodity ordering service.
As shown in FIG. 1, application service instance A and service grid proxy (sidecar) 103 coexist in machine/workload container set 114, and application service instance B and service grid proxy 105 coexist in machine/workload container 116. Service grid agents 103 and 105 form the data plane (data plane) of service grid 100. Where the service grid proxies 103 and 105 are run in the form of containers/ processes 104, 106, respectively, and two-way communication is possible between the service grid proxy 103 and the application service instance a and between the service grid proxy 105 and the application service instance B. In addition, there may be two-way communication between the serving grid agent 103 and the serving grid agent 105.
Illustratively, all traffic for application service instance A is routed through the services grid proxy 103 to the appropriate destination and all network traffic for application service instance B is routed through the services grid proxy 105 to the appropriate destination. It should be noted that the network traffic mentioned herein includes, but is not limited to, forms of hypertext Transfer Protocol (HTTP), representational State Transfer (REST), remote Procedure Call (RPC, such as RPC), remote Dictionary service (Redis), and the like.
Illustratively, the functionality of the extended data plane may be implemented by writing custom filters (filters) for agents (Envoy) in service grid 100, which may be configured to allow the service grid to properly proxy service traffic, service interworking, and service governance. The serving grid agent 103 and the serving grid agent 105 may be configured to perform at least one of the following functions: service discovery (service discovery), health checking (health checking), routing (Routing), load Balancing (Load Balancing), authentication and authorization (authentication and authorization), and observability (observability).
As shown in FIG. 1, the services grid 100 also includes a control plane layer. Where the control plane layer may be a group of services running in a dedicated namespace, the services are hosted by the hosting control plane component 101 at the machine/workload container group 102. As shown in fig. 1, the hosted control plane component 101 is in two-way communication with the mesh agent 103 and the mesh agent 105. The managed control plane component 101 is configured to perform some control management functions. For example, the hosted control plane component 101 receives telemetry data transmitted by the serving grid agent 103 and the serving grid agent 105, which may be further aggregated. These services, hosting the control plane component 101, may also provide user-oriented Application Program Interfaces (APIs) to more easily manipulate network behavior, as well as provide configuration data to the service grid agents 103 and 105, and the like.
The current service grid agent configuration supports two loading modes, one mode is that related technical personnel manually configure global static service grid agent configuration on a control surface; the other is to manually configure the service grid agent corresponding workload by means of configuration comments before the machine/workload container group where the service grid agent is located is started. In any of the above loading methods, the static service grid agent configuration can only be loaded when the machine is started, and the dynamic loading of the service grid agent configuration cannot be realized.
The application provides a method for dynamically loading service grid proxy configuration, which is used for realizing the dynamic loading of the service grid proxy configuration in the service grid. The execution main body of the method for dynamically loading the service grid proxy configuration provided by the application may be an electronic device for implementing the loading of the service grid proxy configuration in the service grid, where the electronic device may be a server, such as one or more servers, a server cluster, a cloud computing platform, and the like, or the electronic device may also be a terminal device, such as a desktop computer, a portable computer, a tablet computer, an account computer, and the like.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
FIG. 2 is a flowchart of a method for dynamic loading of a service grid proxy configuration according to an exemplary embodiment of the present application. As shown in fig. 2, the method comprises the following specific steps:
step S201, according to the configured agent dynamic loading description information, determining the feature source required to be sensed by the workload in the service grid.
The agent dynamic loading description information is information configured by a user, and the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid. Workload refers to applications running in the service grid, corresponding to application service instances, each workload having a corresponding service grid agent.
The feature source required to be perceived by the workload is a feature source which a user expects to perceive the workload in the process of loading the configuration of the service grid agent corresponding to the workload, and is used for indicating that resource feature information of a node where the workload is required to be acquired is derived from resources of the node, such as a CPU, a memory, a network device, an operating system kernel, a storage device, a Peripheral Component Interconnect (PCI) device, and the like.
In this embodiment, the feature sources required to be perceived by different workloads may be different, and specifically, the features may be configured and adjusted by a user (which may be a technician related to operation and maintenance personnel, a user, a manager, and the like of a service grid) according to the actual application scenario and function of the workload.
For example, if the user compares instruction sets supported by the CPU concerning the node where the workload C is located, the user may configure the feature source corresponding to the workload C to include the CPU feature, and specifically may include the CPUID instruction and the like.
For example, if the user is interested in the kernel version of the operating system of workload D and wants to run workload D on a specified kernel version, the user may configure the source of the feature corresponding to workload D to include the kernel feature of the operating system, specifically, the kernel version information of the operating system.
Step S202, according to the feature source required to be sensed by the workload, resource feature information of the node where the workload is located is obtained.
After determining the feature source required to be perceived by the workload in the service grid, according to the feature source required to be perceived by each workload, resource feature information of the feature source corresponding to the workload of the node where each workload is located is obtained.
For example, for the workload C, if the feature source corresponding to the workload C indicates that the resource feature information of the node where the workload C is located is derived from the CPU, the memory, the network device, and the operating system kernel, the CPU feature, the memory feature, the network feature, and the operating system kernel feature of the node where the workload C is located are obtained.
For example, for the workload D, if the feature source corresponding to the workload C indicates that the resource feature information of the node where the workload D is located is derived from a CPU, a memory, and a PCI device, the CPU feature, the memory feature, and the PCI device feature of the node where the workload D is located are obtained.
In addition, the resource feature information of each feature source specifically includes which information, and may be configured uniformly in the system according to a specific application scenario, which is not limited specifically here.
Step S203, according to the resource characteristic information of the node where the workload is located, generating configuration information corresponding to the resource characteristic information, and loading the configuration information into service grid agent configuration corresponding to the workload.
After the resource characteristic information of the node where the workload is located is obtained, corresponding configuration information is generated according to each item of resource characteristic information of the node where the workload is located, each item of resource characteristic information of the node where the workload is located is loaded into service grid agent configuration corresponding to the workload, and therefore the obtained resource characteristic information is dynamically loaded into the service grid agent configuration.
Step S204, the service grid agent configuration is dynamically updated to the service grid agent corresponding to the workload.
After configuration information corresponding to resource characteristic information of a node where a workload is located is loaded into service grid agent configuration corresponding to the workload, the service grid agent configuration is dynamically updated into a service grid agent corresponding to the workload, and dynamic loading configuration of the service grid agent configuration is achieved.
In this embodiment, the description information is dynamically loaded by the configuration agent, the feature source required to be perceived by the workload in the service grid is customized, the resource feature information of the node where the workload is located can be dynamically obtained according to the feature source required to be perceived by the workload, the configuration information corresponding to the resource feature information is generated according to the resource feature information of the node where the workload is located, the configuration information is loaded into the service grid agent configuration corresponding to the workload, the service grid agent configuration is dynamically updated into the service grid agent configuration corresponding to the workload, and the dynamic loading function of the service grid agent configuration based on the resource feature perception is realized.
In an optional embodiment, a user may dynamically load description information at a control plane configuration agent of a service grid, where the agent dynamic loading description information defines a feature source required to be sensed by at least one workload in the service grid, so that the user may define, by himself, the agent dynamic loading description information required by the service grid agent to specify a feature source range required by dynamic loading of the service grid agent configuration, thereby providing a feature source range for automatically sensing and acquiring resource feature information required by dynamic loading of each service grid agent configuration, avoiding loading of unnecessary feature information, and thus improving flexibility and efficiency of a dynamic loading method for service grid agent configuration.
Illustratively, taking a certain cloud native Application built based on a micro-service framework kubernets as an example, for a workload of a certain micro-service in the cloud native Application, agent dynamic loading description information may be defined in a manner of a declarative Application Programming Interface (API), so as to customize agent dynamic loading description information of each workload with a user.
For example, taking as an example that the data plane cluster of the service grid may be a kubernets cluster, a user may define the following agents to dynamically load description information in the manner of a cloud native declarative API:
for example, if the feature source range corresponding to the customized workload "myworkload" includes all preset feature sources, the following contents may be replaced in the agent dynamic loading description information:
scope:// custom feature Source Range
All// including all sources of features predetermined
In addition, in other embodiments, the user may also be implemented by using an existing method for configuring one or more configuration information corresponding to the workload at the control plane, which is not described herein again.
In an alternative embodiment, the resource feature information of all feature sources of the nodes in the service grid may be obtained according to the set feature source, and the resource feature information of all feature sources of the nodes in the service grid may be stored in the feature storage library in a serialized manner.
Optionally, the set feature source comprises at least one built-in feature. Illustratively, the preset built-in source characteristics may include at least one of:
CPU characteristics, memory characteristics, network characteristics, operating system kernel characteristics, storage characteristics, peripheral component interconnect device characteristics.
Illustratively, the CPU features may include the model of the CPU, extended instruction set supported, and the like.
Illustratively, the memory characteristics may include whether the input memory management unit is supported by the host hardware platform, whether the output memory management unit is supported by the host hardware platform, whether the input memory management unit is enabled in the kernel of the host operating system, whether the output memory management unit is enabled in the kernel of the host operating system, and the like.
Illustratively, the network characteristics may include: whether a Network Interface Card (NIC) with a specific function exists or not. The specific function may be set and adjusted according to an actual application scenario, which is not specifically limited herein.
Operating system kernel features may include, for example: kernel versions of the host operating system, etc. Operating systems of different kernel versions may respond to some specific workload dependencies.
Illustratively, the storage features may include: whether there are specific storage characteristics, such as memory type, physical media type, fast access speed, slow access speed, large capacity, etc. The specific storage characteristics may be set and adjusted according to the needs of the actual application scenario, and are not specifically limited herein.
Illustratively, the peripheral component interconnect device characteristics may include the presence or absence of a compatible PCT device or the like.
By setting various and comprehensive built-in characteristics, a user can define agent dynamic loading description information corresponding to a workload based on the set built-in characteristics to realize flexible configuration of a characteristic source range of resource characteristic information required by dynamic loading of each service grid agent configuration, so that the resource characteristic information of a user-defined characteristic source can be obtained for different workloads, the flexibility of a service grid agent configuration dynamic loading method is improved, and unnecessary characteristic information loading can be avoided.
With the evolution of the subsequent technology, the hardware resources that can be selected by the node may change, and the source of the resource characteristic information of the node may also change. Optionally, the set feature sources may further include a custom feature, and a user may customize one or more custom feature sources, called as a custom feature, and customize a way and a result of obtaining the custom feature, so as to support extension of the feature sources and improve flexibility and extensibility of the dynamic loading method for service grid agent configuration.
Illustratively, as shown in fig. 3, the present embodiment provides an engine 30 for acquiring the feature information of the analysis node, which includes a built-in feature engine 31 and a custom feature engine 32. The built-in feature engine 31 may include the following different engines according to different feature sources:
the CPU feature engine 311 is primarily used to determine the CPUID instruction of the CPU functionality, including model and support for instruction set extensions, so that all CPU features that can be obtained from the CPUID information include: the model of the CPU, the extended instruction set supported by the CPU, etc.
The memory characteristics engine 312 is mainly used to detect whether specific memory characteristics exist on a node, including detecting whether an input memory management unit/an output memory management unit is supported by a host hardware platform, detecting whether the input memory management unit/the output memory management unit is enabled in a kernel of a host operating system, and the like.
The network feature engine 313 is mainly used to detect whether specific network features exist on the node, including detecting whether a Network Interface Card (NIC) with a specific function exists, and the like.
The kernel characterization engine 314 is primarily used to detect kernel versions of the underlying host operating system in response to some specific workload dependencies.
The storage characteristics engine 315 is mainly used to detect whether specific storage characteristics exist on a node, and includes: whether or not there are specific storage characteristics such as memory type, physical media type, fast access speed, slow access speed, large capacity, and the like.
The PCI device feature engine 316 is primarily used to detect the presence of compatible PCI hardware devices, and the like.
The custom feature engine 32 is used for the user to customize the used feature source and the way and result of obtaining the feature, and detects the resource feature information of the customized feature source according to the way and result of obtaining the feature by the user.
By acquiring the resource characteristic information of all the characteristic sources of the nodes in the service grid in real time or periodically and updating the resource characteristic information of all the characteristic sources of the nodes in the service grid to the characteristic repository in a serialized manner, when the dynamic loading of the service grid agent configuration is realized, the resource characteristic information of the characteristic sources required to be sensed by the workload of the node where the workload is located can be inquired (dynamically sensed) from the characteristic repository, the acquisition efficiency of the resource characteristic information is improved, and the dynamic loading efficiency of the service grid agent configuration is improved.
Optionally, after acquiring the resource feature information of all feature sources of the nodes in the service grid, performing aggregation analysis on the resource feature information of all feature sources of the nodes in the service grid to obtain aggregation analysis data; and serializing and storing the aggregation analysis data into the feature repository to improve the retrieval efficiency of the feature repository, so that the dynamic loading efficiency of the service grid agent configuration is improved.
For example, the resource feature information of all feature sources of the nodes in the service grid is subjected to aggregation analysis, and may be stored in the feature repository in a serialized manner after resource features are classified, sorted and the like according to the feature sources. In addition, a method for performing aggregation analysis on data in the database to accelerate the retrieval efficiency of the database may also be used, and details are not repeated here.
Further, in step S202, the resource characteristic information of the node where the workload is located is obtained according to the characteristic source that the workload needs to perceive, which may specifically be implemented by the following method:
and periodically querying the feature repository according to the feature source required to be perceived by the workload to acquire the resource feature information of the feature source required to be perceived by the workload of the node where the workload is located.
By periodically querying the feature repository, the latest resource feature information of the feature sources corresponding to the workload can be dynamically sensed, and dynamic loading of service grid agent configuration is realized based on the latest resource feature information of the feature sources corresponding to the workload.
FIG. 4 is a block diagram of a dynamic loading of a service grid proxy configuration provided by an exemplary embodiment of the present application. As shown in FIG. 4, the services grid control plane 401 is a collection of services grid control plane components in a hosting mode provided by the present embodiment. A managed schema represents that the components of the service grids run on separate server runtimes, rather than in a cluster of data planes. Cloud vendors tend to support service grid capabilities in this hosting mode to reduce the operation and maintenance complexity and cost for users. The service grid hosting control plane 401 is responsible for managing and configuring the service grid data plane clusters under the service grid data plane 405, as well as the workloads 406 running therein and their service grid agents 407.
Correspondingly, the service mesh data plane 405 includes a logical partition of a plurality of service mesh data plane clusters, and is managed by the service mesh hosting control plane 401 in a unified manner. For example, the service mesh data plane cluster may be a kubernets cluster, including a plurality of nodes 415, and the like.
FIG. 5 is a flowchart of a method for dynamic loading of a service grid proxy configuration according to another exemplary embodiment of the present application. Based on the framework shown in fig. 4, as shown in fig. 5, the method comprises the following specific steps:
step S501, the configuration agent dynamically loads description information.
In this step, the user may configure a proxy dynamic loading description information 402 at the control plane 401 of the services grid.
The dynamic loading description information of the agent defines the feature source required to be sensed by at least one workload in the service grid, so that a user can define the dynamic loading description information of the agent required by the service grid agent by himself to specify the feature source range required by the dynamic loading service grid agent configuration, thereby providing the feature source range for automatically sensing and acquiring the resource feature information required by the dynamic loading of each service grid agent configuration, avoiding the loading of unnecessary feature information, and improving the flexibility and efficiency of the dynamic loading method of the service grid agent configuration.
Illustratively, a user may define an agent to dynamically load description information in the manner of a cloud-native declarative API.
Step S502, according to the configured agent dynamic loading description information, determining the feature source required to be sensed by the workload in the service grid.
In this embodiment, different workloads may correspond to different feature sources, and specifically, a user (which may be a technician related to operation and maintenance personnel, a user, a manager, and the like of a service grid) may configure and adjust the workload according to an actual application scenario and function of the workload.
In this step, the workload selector 403 may analyze the agent dynamic loading description information configured by the user, determine the effective range of the agent dynamic loading description, that is, which workloads the agent dynamic loading description acts on, and determine the feature sources required to be sensed by the workloads.
Illustratively, taking as an example that the data plane cluster of the service grid may be a kubernets cluster, a user may define the following proxy dynamic loading description information in the manner of a cloud native declarative API:
based on the agent dynamic loading description information, the fact that the agent dynamic loading description information acts on the workload named as myworkload can be determined by analyzing the part of ' workload selector ', and the feature source required to be perceived by the workload named as myworkload ' can be determined by analyzing the part of ' scope ', and the feature source comprises the following steps: CPU features, memory features, and network features.
Step S503, according to the set characteristic source, acquiring resource characteristic information of all characteristic sources of the nodes in the service grid.
In this embodiment, the resource feature information of all feature sources of the nodes in the service grid may also be obtained in real time according to the set feature source.
Resource profile information for all profile sources of nodes 415 in the service grid may be obtained, illustratively, by a built-in profile engine 31 and a custom profile engine 32 for obtaining profile information for analysis nodes as shown in FIG. 3.
Step S504, resource feature information of all feature sources of the nodes in the service grid is stored in a feature storage library in a serialized mode.
After resource feature information of all feature sources of the node 415 in the service grid is obtained, the obtained resource feature information may be further subjected to aggregation analysis by the feature information aggregator 412 and stored in the feature storage library 404 in a serialized manner.
Step S505, periodically querying the feature repository according to the feature source required to be perceived by the workload, so as to obtain resource feature information of the feature source required to be perceived by the workload of the node where the workload is located.
In this embodiment, there is one corresponding service grid agent for each workload. In this step, the feature repository 404 is periodically queried by the data plane feature extractor 410, and resource feature information of the feature source required to be perceived by the workload is acquired according to the feature source required to be perceived by the workload.
Step S506, according to the resource characteristic information of the node where the workload is located, configuration information corresponding to the resource characteristic information is generated, and the configuration information is loaded to service grid agent configuration corresponding to the workload.
In this step, the dynamic loader 411 generates configuration information corresponding to the resource feature information according to the resource feature information of the node where the workload 406 is located, and loads the configuration information into the service grid agent configuration 409 corresponding to the workload.
Illustratively, if the node at which the workload resides supports the AVX-512 instruction set, allowing dynamic configuration of private key providers, then the workload-corresponding service grid agent configuration may be dynamically adjusted to contain the following configuration information:
in addition, if the node at which the workload resides does not support the AVX-512 instruction set, then the workload-to-service grid agent configuration may be dynamically updated to include the following default configurations:
tls_certificates:
certificate _ chain { ' filename '/path/cert. Pem ' }// certificate storage path
private _ key { ' filename ': path/key.pem ' }// private key storage path
Step S507, the service grid agent configuration is dynamically updated to the service grid agent corresponding to the workload.
In this step, service grid agent configuration 409 is dynamically updated to service grid agent 407 corresponding to workload 406 by configuration updater 408, thereby implementing the dynamic loading function of service grid agent configuration.
The embodiment provides a specific implementation manner for acquiring resource characteristic information, the resource characteristic information of a node is acquired through a built-in characteristic engine and a custom characteristic engine, and is stored in a characteristic repository in a serialized manner after aggregation analysis, and when service grid agent configuration is dynamically loaded, the service grid agent configuration can sense the resource characteristic information of a corresponding characteristic source of the node where a workload is located based on the characteristic repository. The embodiment provides a dynamic loading mechanism for realizing user-defined service grid agent configuration based on node feature awareness, wherein a user can define dynamic loading description required by a service grid agent, specify a required feature source range, and support a dynamic loader to acquire resource feature information of a corresponding feature source of a node where a workload is located and load the resource feature information into grid agent configuration, so that a dynamic loading function of the service grid agent configuration is realized.
The system is based on a service grid shown in figure 1, the service grid comprises a control layer, a data layer and a function application layer, the function application layer runs a work load, the data layer runs a service grid agent corresponding to the work load, a two-way communication link is arranged between the work load and the corresponding service grid agent, and two-way communication links are arranged between different service grid agents.
The system comprises: the device comprises a configuration module and a characteristic source determining module which are positioned on a control surface layer, and a characteristic obtaining module, a dynamic loading module and a dynamic updating module which are positioned on a data surface layer.
The configuration module is used for configuring agent dynamic loading description information, and the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid.
The characteristic source determining module is used for determining the characteristic source required to be sensed by the workload in the service grid according to the configured agent dynamic loading description information.
The characteristic obtaining module is used for obtaining resource characteristic information of a node where the workload is located according to the characteristic source required to be sensed by the workload.
And the dynamic loading module is used for generating configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loading the configuration information into service grid agent configuration corresponding to the workload.
And the dynamic updating module is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
Illustratively, the system may configure the proxy dynamic loading description information 402 through a configuration module of the control layer based on the system framework shown in fig. 4, and use the workload selector 403 shown in fig. 4 as a feature source determination module to determine the feature source required to be perceived by the workload in the service grid according to the configured proxy dynamic loading description information. The feature acquirer 410 shown in fig. 4 is used as a feature acquiring module to acquire resource feature information of a node where a workload is located according to a feature source required to be sensed by the workload. The dynamic loader 411 shown in fig. 4 is used as a dynamic loading module, and generates configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loads the configuration information into the service grid agent configuration corresponding to the workload. The serving grid agent configuration 409 is updated by a dynamic update module.
In addition, the system may further include a feature engine (including the built-in feature engine 31 and/or the custom feature engine 32 shown in FIG. 4) and a feature information aggregator (such as the feature information aggregator 410 shown in FIG. 4).
The feature engine is used for acquiring resource feature information of all feature sources of the nodes in the service grid according to the set feature sources before acquiring the resource feature information of the nodes where the workload is located according to the feature sources required to be sensed by the workload.
The feature information aggregator is used for serializing and storing resource feature information of all feature sources of the nodes in the service grid into the feature storage library.
Optionally, the feature information aggregator is further configured to aggregate and analyze the resource feature information of all feature sources of the nodes in the service grid to obtain aggregated and analyzed data; the aggregate analysis data is stored in a feature store (e.g., feature store 404 shown in fig. 4) in a serialized manner.
Fig. 6 is a schematic structural diagram of an apparatus for dynamically loading a service grid agent configuration according to an exemplary embodiment of the present application, where the apparatus provided in this embodiment is applied to the above-mentioned electronic device for implementing loading of a service grid agent configuration in a service grid, and as shown in fig. 6, an apparatus 60 for dynamically loading a service grid agent configuration includes: a feature source determination module 61, a feature acquisition module 62, a dynamic loading module 63, and a dynamic update module 64.
Specifically, the characteristic source determining module 61 is configured to determine a characteristic source required to be perceived by a workload in the service grid according to the configured agent dynamic loading description information.
The characteristic obtaining module 62 is configured to obtain resource characteristic information of a node where the workload is located according to a characteristic source that the workload needs to perceive.
The dynamic loading module 63 is configured to generate configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and load the configuration information into service grid agent configuration corresponding to the workload.
The dynamic update module 64 is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
The apparatus provided in this embodiment may be specifically configured to execute the scheme provided in the method embodiment corresponding to fig. 2, and specific functions and technical effects that can be achieved are not described herein again.
In an alternative embodiment, the apparatus 60 for dynamically loading service grid agent configuration further comprises: a feature engine and a feature information aggregator.
And the characteristic engine is used for acquiring the resource characteristic information of all the characteristic sources of the nodes in the service grid according to the set characteristic source before acquiring the resource characteristic information of the node where the workload is located according to the characteristic source required to be sensed by the workload.
And the characteristic information aggregator is used for storing the resource characteristic information of all the characteristic sources of the nodes in the service grid into the characteristic storage library in a serialized mode.
In an optional embodiment, in enabling serialization of resource feature information for all feature sources of nodes in a services grid into a feature repository, the feature information aggregator is further configured to:
performing aggregation analysis on resource characteristic information of all characteristic sources of nodes in a service grid to obtain aggregation analysis data; and serializing and storing the aggregation analysis data into a feature repository.
In an alternative embodiment, the set feature sources include built-in features and custom features, the built-in features including at least one of:
CPU characteristics, memory characteristics, network characteristics, operating system kernel characteristics, storage characteristics, peripheral component interconnect device characteristics.
In an optional embodiment, in implementing obtaining the resource feature information of the node where the workload is located according to the feature source required to be perceived by the workload, the feature obtaining module 62 is further configured to:
and periodically querying the feature repository according to the feature source required to be perceived by the workload to acquire the resource feature information of the feature source required to be perceived by the workload of the node where the workload is located.
In an alternative embodiment, the apparatus 60 for dynamically loading service grid agent configuration further comprises:
and the configuration module is used for configuring the agent dynamic loading description information, and the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid.
In an optional embodiment, when the dynamic loading of the description information by the configuration agent is implemented, the configuration module is further configured to:
the agent is defined in a declarative API manner to dynamically load description information.
The apparatus provided in this embodiment may be specifically configured to execute the scheme provided in any of the method embodiments, and specific functions and technical effects that can be achieved are not described herein again.
Fig. 7 is a schematic structural diagram of an electronic device according to an example embodiment of the present application. As shown in fig. 7, the electronic apparatus 70 includes: a processor 701, and a memory 702 communicatively coupled to the processor 701, the memory 702 storing computer-executable instructions.
The processor executes the computer execution instructions stored in the memory to implement the scheme provided by any of the above method embodiments, and the specific functions and the technical effects that can be achieved are not described herein again.
The embodiment of the present application further provides a computer-readable storage medium, where computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, the computer-executable instructions are used to implement the solutions provided in any of the above method embodiments, and specific functions and technical effects that can be achieved are not described herein again.
An embodiment of the present application further provides a computer program product, where the computer program product includes: the computer program is stored in a readable storage medium, at least one processor of the electronic device can read the computer program from the readable storage medium, and the at least one processor executes the computer program to enable the electronic device to execute the scheme provided by any one of the above method embodiments, and specific functions and achievable technical effects are not described herein again.
In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a certain order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and only for distinguishing between different operations, and the sequence number itself does not represent any execution order. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel. It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor do they limit the types of "first" and "second". The meaning of "a plurality" is two or more unless specifically limited otherwise.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (12)
1. A method for dynamic loading of service grid proxy configurations, comprising:
determining a feature source required to be sensed by a workload in a service grid according to the configured agent dynamic loading description information;
acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be sensed by the workload;
generating configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loading the configuration information into service grid agent configuration corresponding to the workload;
and dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
2. The method according to claim 1, wherein before obtaining resource feature information of a node where the workload is located according to a feature source required to be perceived by the workload, the method further comprises:
acquiring resource characteristic information of all characteristic sources of nodes in a service grid according to the set characteristic sources;
resource feature information of all feature sources of nodes in the service grid is stored in a feature repository in a serialized manner.
3. The method of claim 2, wherein serializing resource feature information of all feature sources of nodes in the service grid into a feature repository comprises:
performing aggregation analysis on resource characteristic information of all characteristic sources of nodes in a service grid to obtain aggregation analysis data;
serializing and storing the aggregated analysis data into a feature repository.
4. The method of claim 2, wherein the set feature sources comprise built-in features and custom features, the built-in features comprising at least one of:
CPU characteristics, memory characteristics, network characteristics, operating system kernel characteristics, storage characteristics, peripheral component interconnect device characteristics.
5. The method according to any one of claims 2 to 4, wherein the obtaining resource characteristic information of the node where the workload is located according to the characteristic source required to be perceived by the workload comprises:
and periodically querying the feature repository according to the feature source required to be perceived by the workload, so as to obtain resource feature information of the feature source required to be perceived by the workload of the node where the workload is located.
6. The method according to any one of claims 1-4, further comprising:
configuring the agent dynamic loading description information, wherein the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid.
7. The method of claim 6, wherein configuring the agent to dynamically load description information comprises:
the agent is defined to dynamically load description information in a declarative API manner.
8. An apparatus for dynamic loading of service grid proxy configurations, comprising:
the characteristic source determining module is used for determining a characteristic source required to be sensed by the workload in the service grid according to the configured agent dynamic loading description information;
the characteristic acquisition module is used for acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be perceived by the workload;
a dynamic loading module, configured to generate configuration information corresponding to the resource feature information according to the resource feature information of the node where the workload is located, and load the configuration information into a service grid agent configuration corresponding to the workload;
and the dynamic updating module is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
9. A system for dynamic loading of service grid agent configuration is characterized in that a service grid comprises a control layer, a data layer and a function application layer, wherein the function application layer runs a workload, the data layer runs a service grid agent corresponding to the workload, a bidirectional communication link is arranged between the workload and the corresponding service grid agent, and bidirectional communication links are arranged between different service grid agents;
the system comprises: the system comprises a configuration module and a feature source determining module which are positioned on a control surface layer, and a feature obtaining module, a dynamic loading module and a dynamic updating module which are positioned on a data surface layer;
the configuration module is used for configuring agent dynamic loading description information, and the agent dynamic loading description information defines a feature source required to be perceived by at least one workload in the service grid;
the characteristic source determining module is used for determining a characteristic source required to be sensed by a workload in a service grid according to the configured agent dynamic loading description information;
the characteristic acquisition module is used for acquiring resource characteristic information of a node where the workload is located according to a characteristic source required to be perceived by the workload;
the dynamic loading module is used for generating configuration information corresponding to the resource characteristic information according to the resource characteristic information of the node where the workload is located, and loading the configuration information into service grid agent configuration corresponding to the workload;
and the dynamic updating module is used for dynamically updating the service grid agent configuration to the service grid agent corresponding to the workload.
10. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement the method of any of claims 1-7.
11. A computer-readable storage medium having computer-executable instructions stored therein, which when executed by a processor, are configured to implement the method of any one of claims 1-7.
12. A computer program product, characterized in that it comprises a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210899901.3A CN115185611A (en) | 2022-07-28 | 2022-07-28 | Method, device, system and equipment for dynamic loading of service grid proxy configuration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210899901.3A CN115185611A (en) | 2022-07-28 | 2022-07-28 | Method, device, system and equipment for dynamic loading of service grid proxy configuration |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115185611A true CN115185611A (en) | 2022-10-14 |
Family
ID=83521737
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210899901.3A Pending CN115185611A (en) | 2022-07-28 | 2022-07-28 | Method, device, system and equipment for dynamic loading of service grid proxy configuration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115185611A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378944A (en) * | 2022-10-21 | 2022-11-22 | 阿里巴巴（中国）有限公司 | Network system, service grid configuration method, storage medium and electronic equipment |
-
2022
- 2022-07-28 CN CN202210899901.3A patent/CN115185611A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115378944A (en) * | 2022-10-21 | 2022-11-22 | 阿里巴巴（中国）有限公司 | Network system, service grid configuration method, storage medium and electronic equipment |
| CN115378944B (en) * | 2022-10-21 | 2023-03-31 | 阿里巴巴（中国）有限公司 | Network system, service grid configuration method, storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10198162B2 (en) | Method for installing or upgrading an application | |
| US7779091B2 (en) | Method and system for providing virtualized application workspaces | |
| CN112119374A (en) | Selectively providing mutual transport layer security using alternate server names | |
| US10216527B2 (en) | Automated software configuration management | |
| US20140047084A1 (en) | System and method for modifying a hardware configuration of a cloud computing system | |
| US20140047227A1 (en) | System and method for configuring boot-time parameters of nodes of a cloud computing system | |
| US20140047342A1 (en) | System and method for allocating a cluster of nodes for a cloud computing system based on hardware characteristics | |
| US20140047341A1 (en) | System and method for configuring cloud computing systems | |
| US20140047095A1 (en) | System and method for tuning a cloud computing system | |
| Kjorveziroski et al. | Kubernetes distributions for the edge: serverless performance evaluation | |
| Baresi et al. | Microservices: The evolution and extinction of web services? | |
| CN109614227B (en) | Task resource allocation method and device, electronic equipment and computer readable medium | |
| WO2016159949A1 (en) | Application analyzer for cloud computing | |
| US20220188170A1 (en) | Multi-Tenant Control Plane Management on Computing Platform | |
| US20200042356A1 (en) | System and Method for Resource Management | |
| US20210224102A1 (en) | Characterizing operation of software applications having large number of components | |
| CN110546615B (en) | Super dynamic JAVA management extension | |
| CN115185611A (en) | Method, device, system and equipment for dynamic loading of service grid proxy configuration | |
| US11831485B2 (en) | Providing selective peer-to-peer monitoring using MBeans | |
| US11777810B2 (en) | Status sharing in a resilience framework | |
| CN114579250A (en) | Method, device and storage medium for constructing virtual cluster | |
| CN110247802B (en) | Resource configuration method and device for cloud service single-machine environment | |
| Di Martino et al. | A comparison of two different approaches to cloud monitoring | |
| US20230409568A1 (en) | Monitoring metadata synchronization and aggregation | |
| Nilsson et al. | The AutoSPADA Platform: User-Friendly Edge Computing for Distributed Learning and Data Analytics in Connected Vehicles |
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 |