A method, device, storage medium, and computing device cluster for generating a dial test strategy

Abstract

The present application discloses a method, device, and computing device cluster for data analysis, which are used to improve the efficiency of formulating the dial test strategy for newly added network elements. It includes: obtaining a first correspondence list, a first mapping relationship list, and the network element type of a first network element. The first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping relationship list includes the mapping relationship between the first network service and the first metadata instance. The network element type of the first network element is the first network element type, and the first network element is a newly added network element in the first network. According to the network element type of the first network element, the first correspondence list, and the first mapping relationship list, a first mapping relationship between the first network element and the first metadata instance is generated for subsequent use in network operation. By creating the mapping relationship between the newly added network element and the currently existing network model, when there is a dial test requirement in the future, the dial test strategy can be efficiently generated based on this mapping relationship, reducing the labor cost.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of cloud computing, and in particular, to a method, an apparatus, and a computing device cluster for generating a probing strategy. Background Art

[0002] With the continuous expansion of the application scope of cloud computing technology, the cloud network service ecosystem is becoming increasingly prosperous, and the types of network services are emerging in an endless stream. There are a wide variety of network elements in the cloud data center network, and the network services carried by them are also diverse, which increases the difficulty of operation and maintenance management of the cloud network.

[0003] In order to manage and apply the cloud data center network, after technical personnel collect the operation status of the network services in the cloud data center network, they specify the probing strategy for the cloud data center network based on the operation status of the network services. Due to the version evolution of the operation of the cloud data center network, when new network services or network element nodes are added to the cloud data center network, the update of the probing strategy completely depends on technical personnel. When technical personnel are not familiar with the current operation and maintenance system or the cloud data center network, a large amount of time is required to formulate the probing strategy for the cloud data center network. How to eliminate the fluctuation of the probing strategy formulation efficiency caused by the familiarity of technical personnel with the cloud data center network has become an urgent problem to be solved. Summary of the Invention

[0004] The embodiments of the present application provide a method, an apparatus, and a computing device cluster for generating a probing strategy. It is used to realize the automatic adaptation of the service type of the newly added network element and the current network model, realize the formulation and distribution of the probing strategy for the newly added network element, and reduce the labor cost.

[0005] The first aspect of the embodiments of the present application provides a method for generating a probing strategy, including: obtaining a first correspondence list and a first mapping list, where the first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping list includes the mapping between the first network service and the first metadata instance; obtaining the network element type of the first network element, the network element type of the first network element being the first network element type, the first network element being included in the first network at the first moment and not being included in the first network at the second moment, and the first moment being after the second moment; generating a first mapping relationship according to the first network element type, the first correspondence list, and the first mapping list, where the first mapping relationship is the mapping between the first network element and the first metadata instance.

[0006] In an embodiment of the present application, after obtaining the first correspondence list and the first mapping relationship list, the network element type of the first network element is obtained. Since the first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping relationship list includes the mapping relationship between the first network service and the first metadata instance. Moreover, the network element type of the first network element is the first network element type, and the first network element is a network element that is included in the first network at the first moment and not included in the first network at the second moment, where the second moment is before the first moment. Therefore, the first mapping relationship between the first network element and the first metadata instance can be generated according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list. For subsequent use in network operation, by creating the mapping relationship between the network element type of the newly added network element and the currently existing network model, when there is a need for dial test in the future, the dial test policy can be efficiently generated according to this mapping relationship, reducing the labor cost.

[0007] In a possible implementation manner of the first aspect, obtaining the network element type of the first network element includes: if the first network element type is included in the first correspondence list, obtaining the network element type of the first network element.

[0008] In an embodiment of the present application, when obtaining the network element type of the first network element, when the network element type of the first network element exists in the first correspondence list, obtain the network element type of the first network element and perform subsequent processing. When the network element type of the first network element does not exist in the first correspondence list, no subsequent operation is required. By restricting the processing to only the network elements corresponding to the network element types with pre-stored correspondence relationships, redundant verification of the network elements that do not need to be dial tested is avoided, improving the flexibility and efficiency of the solution.

[0009] In a possible implementation manner of the first aspect, generating the first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list includes: searching for the network element type of the first network element in the first correspondence list to obtain the first network service that has a correspondence relationship with the first network element type; searching for the first network service in the first mapping relationship list to obtain the first metadata instance, where there is a mapping relationship between the first metadata instance and the first network service; generating the first mapping relationship, and the first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

[0010] In the embodiments of the present application, generating the first mapping relationship according to the network element type of the first network element, the first corresponding relationship list, and the first mapping relationship list can be specifically implemented through the following steps: Search for the network element type of the first network element in the first corresponding relationship list to obtain the first network service that has a corresponding relationship with the first network element type; further, search for the first network service in the first mapping relationship list to obtain the first metadata instance that has a mapping relationship with the first network service. Generate the first mapping relationship between the first network element and the first metadata instance. After determining the first network service corresponding to the first network element by using the first corresponding relationship list, then use the first mapping relationship list to determine the first metadata instance corresponding to the first network service. It can efficiently implement the matching of the dial test policy for the newly added network element.

[0011] In a possible implementation manner of the first aspect, searching for the first network service in the first mapping relationship list and obtaining the first metadata instance includes: If there is no computing node in the first network to provide computing power for the first network service, search for the first network service in the first mapping relationship list to obtain the first metadata instance.

[0012] In the embodiments of the present application, when searching for the first network service in the first mapping relationship list, it is also possible to pre-judge whether there is a computing node in the first network to provide computing power for the first network service. If not, search for the first network service in the first mapping relationship list to obtain the first metadata instance that has a mapping relationship with the first network service. By pre-judging whether there is a computing node in the first network to provide computing power for the first network service, it is possible to avoid repeatedly performing dial tests on network services that already have stable computing capabilities, further improving the dial test efficiency and saving the computing resources of the network.

[0013] In a possible implementation manner of the first aspect, the first metadata instance instructs the first computing node to perform the first calculation; the method further includes: generating a first message, the first message instructing the first computing node to perform the first calculation; sending the first message to the first computing node; obtaining the first calculation result sent by the first computing node, the first calculation result indicating whether the first computing node successfully performs the first calculation.

[0014] In the embodiments of the present application, when the first metadata instance instructs the first computing node to perform the first calculation, it is also possible to generate a first message according to the first mapping relationship after generating the first mapping relationship, the first message instructing the first computing node to perform the first calculation; after sending the first message to the first computing node, obtain the first calculation result sent by the first computing node, where the first calculation result indicates whether the first computing node successfully performs the first calculation. By generating the first message, sending the first message to the first computing node, and obtaining the first calculation result sent by the first computing node, it makes full use of the matched dial test policy to perform the dial test, improving the dial test efficiency.

[0015] In a possible implementation manner of the first aspect, the method further includes: analyzing the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element. By analyzing the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element in the embodiments of the present application, the integrity of the solution is improved.

[0016] In a possible implementation manner of the first aspect, the first metadata instance includes a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance.

[0017] In the second aspect of the embodiments of the present application, a device for generating a probing strategy is provided, including:

[0018] An obtaining unit, configured to obtain a first correspondence list and a first mapping list, where the first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping list includes the mapping relationship between the first network service and the first metadata instance;

[0019] The obtaining unit is further configured to obtain the network element type of the first network element. The network element type of the first network element is the first network element type. The first network element is included in the first network at the first moment and not included in the first network at the second moment, and the first moment is after the second moment;

[0020] A generating unit, configured to generate a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping list, where the first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

[0021] In a possible implementation manner of the second aspect, the obtaining unit is specifically configured to obtain the network element type of the first network element if the first network element type is included in the first correspondence list.

[0022] In a possible implementation manner of the second aspect, the generating unit is specifically configured to:

[0023] Search for the network element type of the first network element in the first correspondence list to obtain a first network service corresponding to the first network element type;

[0024] Search for the first network service in the first mapping list to obtain a first metadata instance, where there is a mapping relationship between the first metadata instance and the first network service;

[0025] Generate a first mapping relationship, where the first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

[0026] In a possible implementation of the second aspect, the generating unit is specifically configured to, when there is no computing node in the first network to provide computing power for the first network service, search for the first network service in the first mapping relationship list to obtain the first metadata instance.

[0027] In a possible implementation of the second aspect, the first metadata instance instructs the first computing node to perform the first calculation;

[0028] The generating unit is further configured to generate a first message, and the first message instructs the first computing node to perform the first calculation;

[0029] The apparatus further includes a sending unit, configured to send the first message to the first computing node;

[0030] The obtaining unit is further configured to obtain the first calculation result sent by the first computing node, and the first calculation result indicates whether the first computing node successfully performs the first calculation.

[0031] In a possible implementation of the second aspect, the apparatus further includes:

[0032] An analysis unit, configured to analyze the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element.

[0033] In a possible implementation of the second aspect, the first metadata instance includes a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance.

[0034] A device for generating a dial test policy according to a third aspect of the embodiments of the present application includes a processor and a memory. The memory is used to store instructions, and the processor is used to execute the instructions. When the processor executes the instructions, it executes the method in the foregoing first aspect or any implementation manner of the first aspect.

[0035] A computer-readable storage medium according to a fourth aspect of the embodiments of the present application is characterized in that it includes a program, which when running on a computer, causes the computer to execute the method in the foregoing first aspect or any implementation manner of the first aspect.

[0036] A computing device cluster according to a fifth aspect of the embodiments of the present application is characterized in that it includes at least one computing device, and each computing device includes a processor and a memory;

[0037] The processors of at least one computing device are used to execute the instructions stored in the memories of at least one computing device, so that the computing device cluster executes the method in the foregoing first aspect or any implementation manner of the first aspect. Description of the Drawings

[0038] Figure 1A schematic diagram of a structure of the cloud data center network provided for this application;

[0039] Figure 2 A schematic diagram of a method for data analysis provided for an embodiment of this application;

[0040] Figure 3 A schematic diagram of a first correspondence list provided for an embodiment of this application;

[0041] Figure 4 A schematic diagram of a first mapping list provided for an embodiment of this application;

[0042] Figure 5 Another schematic diagram of a first mapping list provided for an embodiment of this application;

[0043] Figure 6 Another schematic diagram of a first mapping list provided for an embodiment of this application;

[0044] Figure 7 Another schematic diagram of a method for data analysis provided for an embodiment of this application;

[0045] Figure 8 A schematic diagram of a structure of a data analysis device provided for an embodiment of this application;

[0046] Figure 9 Another schematic diagram of a structure of a data analysis device provided for an embodiment of this application;

[0047] Figure 10 A schematic diagram of a structure of a computing device cluster provided for an embodiment of this application;

[0048] Figure 11 Another schematic diagram of a structure of a computing device cluster provided for an embodiment of this application;

[0049] Figure 12 Another schematic diagram of a structure of a data analysis device provided for an embodiment of this application. Detailed implementation manners

[0050] The embodiments of this application will be described below with reference to the accompanying drawings in the embodiments of this application. The terms used in the implementation part of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. Those of ordinary skill in the art will know that with the development of technology and the emergence of new scenarios, the technical solutions provided by the embodiments of this application are also applicable to similar technical problems.

[0051] In the description, claims and the above-mentioned drawings of this application, terms such as "first", "second", etc. are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances, which is only a way of distinguishing objects with the same attributes when describing embodiments of this application. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion, so that a process, method, system, product or device comprising a series of units does not have to be limited to those units, but may include other units not clearly listed or inherent to these processes, methods, products or devices.

[0052] With the continuous expansion of the application scope of cloud computing technology, the cloud network service ecosystem is becoming increasingly prosperous, and the types of network services are emerging in an endless stream. There are a wide variety of network elements in the cloud data center network, and the network services it carries are also diverse, which increases the operation and maintenance management difficulty of the cloud network.

[0053] In order to manage and apply the cloud data center network, after technicians collect the operation status of the network services in the cloud data center network, they specify the dial test strategy for the cloud data center network based on the operation status of the network services. Due to the version evolution of the cloud data center network operation, when new network services or network element nodes are added to the cloud data center network, the update of the dial test strategy completely depends on technicians. When technicians are not familiar with the current operation and maintenance system or the cloud data center network, a large amount of time is required to formulate the dial test strategy for the cloud data center network. How to eliminate the influence of the technicians' familiarity with the cloud data center network on the efficiency of specifying the dial test strategy has become an urgent problem to be solved.

[0054] Based on the above problems, this application proposes that a list of corresponding relationships between network element types and network services corresponding to the network element types and a list of corresponding relationships between network services and network service metadata can be preset in the cloud data center network. The controller of the cloud data center periodically detects the configuration management database (CMDB) of the cloud data center. When a new network element node is detected in the CMDB, according to the network element node type carried by the new network element node, query the list of corresponding relationships between network element types and network services corresponding to the network element types to obtain the network services corresponding to the new network element node. Then, query the list of corresponding relationships between network services and network service metadata according to the network services corresponding to the new network element node to obtain the network service metadata corresponding to the new network node. According to the network service metadata corresponding to the new network node, generate a dial test task and send the dial test task to the relevant network elements in the dial test task to realize the management of the network services in the cloud data center network, eliminating the influence of the technicians' familiarity with the cloud data center network on the efficiency of formulating the dial test strategy.

[0055] First, the cloud data center network applied in this application is introduced. Please refer to Figure 1 , Figure 1 which is a schematic structural diagram of the cloud data center network provided by this application.

[0056] The cloud data center network includes a display UI, a configuration management database (CMDB), a controller, physical switches, computing nodes, and network element nodes.

[0057] The network element type recognition module in the controller is used to regularly check for newly added network elements in the CMDB. If there are newly added network elements in the CMDB, it determines the network element type of the network element according to the newly added network element, and further queries the network services associated with the network element.

[0058] The network element type and network service management module in the controller is used to maintain a list of corresponding relationships between network element types and network services associated with the network element. This list is preset in the network element type and network service management module by the user through a configuration file, so as to determine the network services associated with the newly added network element according to the network type of the newly added network element and the list of corresponding relationships between the network element type and the network services associated with the network element.

[0059] The network service metadata management module in the controller is used to define the metadata for creating network resources, and the computing nodes can create network resources by executing the metadata.

[0060] The network service metadata instance management module in the controller is used to create five-tuple related data required for the dial test policy, specifically including source IP related resources, destination IP related resources, and network service related resources.

[0061] The dial test node management module in the controller is used to identify all computing nodes in the cloud network and the access switches (top of rack, TOR) resources connected to the computing nodes. The network service metadata instance management module analyzes the computing nodes provided by the dial test node management module to obtain the nodes that need to formulate the dial test policy.

[0062] The dial test policy formulation module in the controller is used for the network service metadata instance to formulate the dial test policy according to the network provided by the network service metadata strength management module.

[0063] The task management module in the controller is used to send the dial test tasks generated by the dial test policy formulation module to the dial test system.

[0064] The probing result analysis module in the controller is used to collect the response messages sent by the probing system for the probing tasks, analyze the probing results of the probing tasks, generate the packet loss rate and delay data of the probing link, and further obtain the packet loss rate and delay data of the computing nodes.

[0065] After receiving the probing tasks sent by the controller, the physical switch, computing node, and network element node execute the probing tasks and send the response messages of the probing tasks to the controller according to the probing results.

[0066] Based on the above ideas and the cloud data center network structure, this application provides a solution to automatically match a suitable probing strategy for a newly added network element in the network. Since the network environment is ever-changing, this solution has different implementation means. The solutions provided by this application will be introduced below with reference to the accompanying drawings.

[0067] First, the solution provided by this application in a relatively simple network environment will be introduced. Please refer to Figure 2 , Figure 2 which is a schematic diagram of a method for data analysis provided by an embodiment of this application.

[0068] 201. The controller obtains the first correspondence list;

[0069] The controller obtains the first correspondence list, and the first correspondence list includes the correspondence between the first network element type and the first network service.

[0070] Exemplarily, the first correspondence list can be as Figure 3 shown, Figure 3 which is a schematic diagram of the first correspondence list provided by an embodiment of this application.

[0071] When the network element type of the network element is a virtual private cloud (VPC) forwarding network element, the network service of this network element can be VPC-peering or direct connect (DC) or elastic load balance (ELB) or elastic IP (EIP).

[0072] When the network type of the network element is a border routing network element, the network service can be EIP or network address translation (NAT).

[0073] When the network type of the network element is a NAT network element, the network service can be NAT.

[0074] When the network type of the network element is a load balancing network element, the network service can be ELB.

[0075] It should be noted that the description of the first correspondence list here is only an example. In actual applications, the first correspondence list only needs to include the correspondence between at least one network element type and at least one network service. Its specific form and content should be set according to the specific application scenario and are not limited here.

[0076] Specifically, the controller can obtain the first correspondence list configured by the user through the interaction interface, and can also obtain the first correspondence list stored in other nodes from other nodes through the network interface.

[0077] In some specific cases, it is also possible to learn the network element type and the pre-configured network service from multiple network element nodes to generate the first correspondence list, which is not limited here.

[0078] It can be understood that there is no clear order between step 201, step 202, and step 203. The description here is only an example, and it should be set according to the specific application scenario in actual applications.

[0079] 202. The controller obtains the network element type of the first network element;

[0080] The controller periodically checks whether there are new network element nodes in the CMDB. If there are, the controller obtains the network element type of the first network element, where the first network element is included in the first network at the first moment and not included in the first network at the second moment, and the first moment is after the second moment, that is, the first network element is a new network element node in the first network.

[0081] Specifically, referring to Figure 1 the cloud data center network structure shown, the network element node identification module in the controller regularly checks whether there are updates to the network element nodes in the CMDB.

[0082] If there are new network element nodes in the CMDB, after the controller reads the node type of the new network element node to obtain the network element type of the first network element, it executes step 203.

[0083] If there are no new network element nodes in the CMDB, the controller periodically executes step 202.

[0084] It can be understood that there is no clear order between step 202, step 201, and step 203. The description here is only an example, and it should be set according to the specific application scenario in actual applications.

[0085] 203. The controller obtains the first mapping list;

[0086] The controller obtains a first mapping relationship list, and the first mapping relationship list includes the mapping relationship between a first network service and a first metadata instance.

[0087] Specifically, the first metadata instance may include a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance, and there is no limitation in specific implementation cases.

[0088] Exemplarily, the first mapping relationship list may be as Figure 4 shown, Figure 4 which is a schematic diagram of the first mapping relationship list provided by an embodiment of the present application.

[0089] Figure 4 In [0000204], taking the first network services VPC-peering and Eip as examples, the possible expression forms of the first mapping relationship list are introduced. As Figure 4 shown, the service types in the first mapping relationship list include VPC-peering and Eip.

[0090] The source IP metadata of VPC-peering is:

[0091] Create vpc1

[0092] Create 192.168.1.0 / 24 / / Create a VPC-peering service at 192.168.1.0 / 24

[0093] Create compute / / Create a VPC-peering virtual machine network port resource at an arbitrarily assigned network address

[0094] The destination IP metadata of VPC-peering is:

[0095] Create vpc2

[0096] Create 192.169.1.0 / 24 / / Create a VPC-peering service at 192.169.1.0 / 24

[0097] Create compute / / Create a VPC-peering service computing task at an arbitrarily assigned network address

[0098] The network service metadata of VPC-peering is:

[0099] VPC-peering

[0100] POST / api / vpc1, parameters

[0101] The source IP metadata of Eip is as follows:

[0102] Create vpc1

[0103] Create 192.168.1.0 / 24 / / Create Eip service at 192.168.1.0 / 24

[0104] Create compute / / Create Eip service computing task at any assigned network address

[0105] Create floating

[0106] The destination IP metadata of Eip is as follows:

[0107] Create 192.168.1.1 / / Create Eip service at 192.168.1.1

[0108] The network service metadata of Eip is as follows:

[0109] Eip

[0110] POST / api / vpc1, parameters

[0111] It can be understood that the description of the first mapping relationship here is only an example. In actual applications, the content should be set and adjusted in combination with specific application scenarios, and no limitations are made here.

[0112] In a possible case, the first mapping relationship list may further include field descriptions and field extension descriptions of resource metadata of network service source IP and destination IP. Furthermore, the first metadata instance may instruct the first computing node to perform the first calculation, and the IP of the first computing node is the first source IP or the first destination IP.

[0113] Exemplarily, please refer to Figure 5 , Figure 5 , which is another schematic diagram of the first mapping relationship list provided by the embodiments of the present application.

[0114] From Figure 5 it can be seen that different metadata may include some descriptions for different fields, as shown in the following examples:

[0115] The VPC metadata includes the vpc_operation field and the vpc_name field. Among them, the vpc_operation field is used to describe the operation to be performed, such as, create. The vpc_name field is used to describe the name of the created instance, such as, VPC1.

[0116] The Subnet metadata includes a subnet_operation field and a subnet_cidr field. Among them, the subnet_operation field is used to describe the operation to be performed, such as "create". The subnet_cidr field is used to create the network segment of the subnet, such as "192.168.1.0 / 24".

[0117] The Port metadata includes a port_operation field and a port_type field. Among them, the port_operation field is used to describe the operation to be performed, such as "create". The port_type field is used to describe the type of the port to be created, such as "compute".

[0118] It can be understood that the description of the first mapping relationship list here is only an example. In actual applications, the content should be set and adjusted in combination with specific application scenarios, and no limitations are imposed here.

[0119] In another possible case, the first mapping relationship list may further include field descriptions and field extension instructions of network service metadata. For details, please refer to Figure 6 , Figure 6 which is another schematic diagram of the first mapping relationship list provided by the embodiments of this application.

[0120] The network service metadata includes a servicetype field and a list <api>Field, where the servicetype field is used to describe the network service name, such as eip or vpc-peering, etc. list <api>The field is used to describe the list of interfaces on which the creation of the network service depends.

[0121] The API includes the restful_api field, the operation field, and the parameter field. Among them, the restful_api field is used to describe the interfaces on which the creation of the network service depends. The operation field is used to describe the operation type of the API, such as post, get, update, or delete. The parameter field is used to describe the parameters of the interfaces on which the creation of the network service depends.

[0122] It can be understood that the description of the first mapping relationship list here is only an example. In actual applications, the content should be set and adjusted in combination with the specific application scenario, and no restrictions are imposed here.

[0123] It should be noted that Figure 5 and Figure 6 the descriptions of the first mapping relationship list in Figure 4 are all supplements based on the first mapping relationship list shown in Figure 4 In actual applications, depending on the specific situation, the first mapping relationship list is supplemented with Figure 5 and / or Figure 6 similar content in

[0124] Specifically, the controller can obtain the first mapping relationship list configured by the user through the interaction interface, and can also obtain the first mapping relationship list stored in other nodes from other nodes through the network interface.

[0125] In some specific cases, it is also possible to learn the network element type and the pre-configured network service from multiple network element nodes to generate the first mapping relationship list, and no restrictions are imposed here.

[0126] It can be understood that there is no clear sequence between step 203 and steps 201 and 202. The description here is only an example, and in actual applications, it should be set in combination with the specific application scenario.

[0127] 204. The controller generates a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list;

[0128] The controller generates a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list. The first mapping relationship is the mapping relationship between the first network element and the first metadata instance. Among them, the network element type of the first network element is the first network element type.

[0129] Specifically, after the network element node recognition module of the controller obtains the network element type of the first network element, it calls the network element type and network service management module to query the network element type of the first network element in the first relationship list, obtains the corresponding relationship between the first network element type and the first network service, and calls the network element type and network service management module to send a network service dial test request to the network service metadata module. The network service metadata module reads the mapping relationship between the first network service and the first metadata instance, and generates the first mapping relationship between the first network element and the first metadata instance.

[0130] It should be noted that the description of the specific operation of the controller to generate the first mapping relationship based on the network element type of the first network element, the first corresponding relationship list, and the first mapping relationship list is only an example here. In actual applications, operations can also be performed in different orders, and no restrictions are imposed here.

[0131] 205. The controller generates a first message according to the first mapping relationship;

[0132] After generating the first mapping relationship, the controller generates a first message according to the first mapping relationship. The first message instructs the first computing node to perform the first calculation.

[0133] The controller formulates a dial test policy for the newly added first network element. Since the first mapping relationship indicates the correspondence between the first network element and the first metadata instance, the controller generates a first message according to the first metadata instance. The first message is the carrier of the first network element dial test policy, and the first message instructs the first computing node to perform the first calculation.

[0134] 206. The controller sends the first message to the first computing node;

[0135] After generating the first message, the controller sends the first message to the first computing node according to the destination node ID of the first message.

[0136] 207. The first computing node performs the first calculation to obtain the first calculation result;

[0137] After obtaining the first message sent by the controller, the first computing node performs the first calculation according to the content of the first message.

[0138] Exemplarily, the first calculation can be that the first computing node calls the basic network resource interface in the network service metadata module or creates dial test-related network resources through the network interface. For example, creating lightweight network resources such as vpc, subnet, port, etc. resources. Among them, for the dial test probe port, only the network port resource needs to be issued, and there is no need to bind computing resources and storage resources.

[0139] It can be understood that the description of the first calculation performed by the first computing node here is only an example. In actual applications, the specific operations performed by the first node should be set in combination with the specific application scenarios, and no limitations are imposed here.

[0140] 208. The first computing node sends the first calculation result to the controller;

[0141] After performing the first calculation, the first computing node sends the first calculation result to the controller, and the first calculation result indicates whether the first calculation is executed successfully.

[0142] Exemplarily, when the first calculation is to send network port resources to the second network element, and after the first computing node successfully sends the network port resources to the second network element, the first computing node generates a first calculation result, and the first calculation result indicates that the first calculation is executed successfully.

[0143] Or, when the first calculation is to send network port resources to the second network element, and the first computing node fails to send the network port resources to the second network element, the first computing node generates a first calculation result, and the first calculation result indicates that the first calculation is executed failed.

[0144] It can be understood that the descriptions of the first calculation result and the content of the first calculation here are only examples. In actual applications, they should be set in combination with the specific application scenarios, and no limitations are imposed here.

[0145] 209. The controller generates a first detection result according to the first calculation result.

[0146] After obtaining the first calculation result sent by the first computing node, the controller generates a first detection result according to the first calculation result. The first detection result includes that the first network service is available, or the first network service is unavailable.

[0147] Furthermore, the controller can feedback the availability of the network service to the user through the interaction interface according to the first detection result, and no limitations are imposed here.

[0148] It can be understood that there may be one or more forwarding nodes between the controller and the computing node. In the embodiments of the present application, the controller sending the first message to the computing node and the computing node sending the first calculation result to the controller can both be realized by forwarding the message through one or more forwarding nodes. In actual applications, it should be set in combination with the specific application scenarios, and no limitations are imposed here.

[0149] In the embodiments of the present application, by obtaining a first correspondence list and a first mapping relationship list, where the first correspondence includes the correspondence between the first network element type and the first network element service, and the first mapping relationship list includes the correspondence between the first network element service and the first metadata instance. After detecting a newly added first network element in the cloud data network center and learning that the network element type of the first network element is the first network element type, a first mapping relationship between the first network element and the first metadata instance is generated according to the first correspondence list and the first mapping relationship list. And a first message is generated according to the first mapping relationship, and the first message is used to instruct a first computing node to perform a first computation. The first correspondence list and the second mapping relationship list are used to realize the automatic adaptation of the service type of the newly added network element and the current network model, realize the formulation and distribution of the dial test strategy for the newly added network element, reduce the labor cost, and also avoid the problem of the exponential increase in the difficulty of formulating the manual dial test strategy brought about by the continuous upgrade of the network.

[0150] Due to the diversity of the network environment, the solution provided by the present application is introduced below for a relatively complex network environment. Please refer to Figure 7 , Figure 7 which is another schematic diagram of the method for data analysis provided by the embodiments of the present application.

[0151] 701. The controller obtains the first correspondence list;

[0152] 702. The controller obtains the network element type of the first network element;

[0153] 703. The controller obtains the first mapping relationship list;

[0154] It can be understood that the implementation manners of steps 701 to 703 are similar to those of steps 201 to 203 in the foregoing Figure 2 . Please refer to steps 201 to 203 in Figure 2 , and details are not described herein again.

[0155] 704. The controller determines whether the network element type of the first network element exists in the first correspondence list;

[0156] After obtaining the network element type of the first network element, the controller determines whether the network element type of the first network element exists in the first correspondence list.

[0157] If not, step 702 is executed after the first period.

[0158] If it exists, step 705 is executed.

[0159] In the embodiments of the present application, after obtaining the network element type of a newly added network element in the network, it is determined whether the network element type of the newly added network element exists in a pre-configured first correspondence list. By restricting the controller to only perform subsequent processing on the network element types existing in the first correspondence list, the restriction on the network element types of the network elements to be tested is realized, unnecessary testing is avoided, and the execution efficiency and flexibility of the solution are improved.

[0160] 705. The controller queries the network element type of the first network element in the first correspondence list to obtain the first network service;

[0161] After the controller determines that the network element type of the first network element exists in the first correspondence list, it queries the network element type of the first network element in the first correspondence list to obtain the first network service.

[0162] 706. The controller determines whether there is a computing node in the first network that provides computing power for the first network service;

[0163] After the controller obtains the first network service corresponding to the network element type of the first network element, it detects the first network and determines whether there is a computing node in the first network that provides computing power for the first network service.

[0164] If there is a computing node in the first network that provides computing power for the first network service, step 702 is executed.

[0165] If there is no computing node in the first network that provides computing power for the first network service, step 707 is executed.

[0166] Specifically, the controller can use the test node management module set in the controller to identify all computing nodes in the cloud data network center and the TOR resources connected to the computing nodes. The computing nodes provided by the network service metadata instance test node management module are analyzed to determine whether a test strategy needs to be formulated for the first network service corresponding to the first network element under the current operating state of the cloud data network center.

[0167] For example, when the first computing node is connected to the first TOR, any computing node in the first TOR provides computing power for the first network service, and the network service corresponding to the newly added first network element is the first network service, 702 is executed.

[0168] When the first computing node is connected to the first TOR, no computing node in the first TOR provides computing power for the first network service, and the network service corresponding to the newly added first network element is the first network service, step 707 is executed.

[0169] It can be understood that the description of the solution for the controller to analyze the computing nodes in the cloud network data center and the TOR resources connected to the computing nodes, and the description of the operation timing for determining whether there are computing nodes in the first network to provide computing power for the first network service are only examples. In actual applications, the timing of adopting this solution can be determined in combination with specific application scenarios. For example, after the controller obtains the correspondence between the network element type of the first network element and the first network service, or, after the controller generates the first mapping relationship, this step is executed before generating the first message, and there is no limitation here.

[0170] 707. The controller queries the first network service in the first mapping relationship list to obtain the first metadata instance;

[0171] After the controller determines that there are no computing nodes in the first network to provide computing power for the first network service, the controller queries the first network service in the first mapping relationship list to obtain the first metadata instance that has a mapping relationship with the first network service.

[0172] 708. The controller generates the first mapping relationship between the first network element and the first metadata instance;

[0173] After the controller queries the mapping relationship between the first network service and the first metadata instance, the controller generates the first mapping relationship between the first network element and the first metadata instance.

[0174] 709. The controller generates the first message according to the first mapping relationship;

[0175] 710. The controller sends the first message to the first computing node;

[0176] 711. The first computing node performs the first calculation to obtain the first calculation result;

[0177] 712. The first computing node sends the first calculation result to the controller;

[0178] 713. The controller generates the first detection result according to the first calculation result.

[0179] It can be understood that the operations from step 709 to step 713 are similar to the implementation manners of steps 205 to step 209 in the foregoing Figure 2 Please refer to steps 205 to step 209 in Figure 2 steps 205 to step 209, and details are not described herein again.

[0180] It can be understood that there may be one or more forwarding nodes between the controller and the computing node. In the embodiments of the present application, the controller sending the first message to the computing node and the computing node sending the first calculation result to the controller can both be realized by message forwarding via one or more forwarding nodes. In actual applications, it should be set in combination with specific application scenarios, and there is no limitation here.

[0181] In the embodiments of the present application, when looking up the first network service in the first mapping relationship list, it is also possible to pre-judge whether there is a computing node in the first network that provides computing power for the first network service. If not, look up the first network service in the first mapping relationship list to obtain the first metadata instance that has a mapping relationship with the first network service. By pre-judging whether there is a computing node in the first network that provides computing power for the first network service, it is possible to avoid repeatedly performing dial tests on network services that already have stable computing capabilities, further improving the dial test efficiency and saving the computing resources of the network.

[0182] The method for data analysis proposed in the present application has been introduced above. Next, the device provided in the embodiments of the present application will be introduced with reference to the accompanying drawings:

[0183] Please refer to Figure 8 , Figure 8 which is a schematic structural diagram of the data analysis device provided in the embodiments of the present application.

[0184] A data analysis device includes:

[0185] An acquisition unit 801, configured to acquire a first correspondence list and a first mapping relationship list. The first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping relationship list includes the mapping relationship between the first network service and the first metadata instance;

[0186] The acquisition unit 801 is further configured to acquire the network element type of the first network element. The network element type of the first network element is the first network element type. The first network element is included in the first network at the first moment and not included in the first network at the second moment, and the first moment is after the second moment;

[0187] A generation unit 802, configured to generate a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list. The first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

[0188] Optionally, the acquisition unit 801 is specifically configured to acquire the network element type of the first network element if the first network element type is included in the first correspondence list.

[0189] Optionally, the generation unit 802 is specifically configured to:

[0190] Look up the network element type of the first network element in the first correspondence list to obtain the first network service that has a correspondence relationship with the first network element type;

[0191] Look up the first network service in the first mapping relationship list to obtain the first metadata instance. There is a mapping relationship between the first metadata instance and the first network service;

[0192] Generate a first mapping relationship, where the first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

[0193] Optionally, the generating unit 802 is specifically configured to, if there is no computing node in the first network to provide computing power for the first network service, search for the first network service in the first mapping relationship list to obtain the first metadata instance.

[0194] Optionally, the first metadata instance instructs the first computing node to perform a first calculation;

[0195] The generating unit 802 is further configured to generate a first message, where the first message instructs the first computing node to perform a first calculation;

[0196] The apparatus further includes a sending unit 803, configured to send the first message to the first computing node;

[0197] The obtaining unit 801 is further configured to obtain a first calculation result sent by the first computing node, where the first calculation result indicates whether the first computing node successfully performs the first calculation.

[0198] Optionally, the apparatus further includes:

[0199] An analysis unit 804, configured to analyze the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element.

[0200] Optionally, the first metadata instance includes a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance.

[0201] Please refer to Figure 9 , Figure 9 which is another structural schematic diagram of the data analysis apparatus provided in the embodiment of the present application.

[0202] The data analysis apparatus 900 includes: a bus 902, a processor 904, a memory 906, and a communication interface 908. The processor 904, the memory 906, and the communication interface 908 communicate with each other through the bus 902. The data analysis apparatus 900 may be a server or a terminal device. It should be understood that the present application does not limit the number of the processor 904 and the memory 906 in the data analysis apparatus 900.

[0203] The bus 902 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. For the convenience of representation, Figure 9 It is represented by only one line in the figure, but it does not mean that there is only one bus or one type of bus. The bus 902 may include a path for transmitting information between various components of the device 900 for data analysis (for example, the memory 906, the processor 904, and the communication interface 908).

[0204] The processor 904 may include any one or more of processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0205] The memory 906 may include a volatile memory, such as a random access memory (RAM). The processor 904 may also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD), or a solid state drive (SSD).

[0206] The memory 906 stores executable program codes, and the processor 904 executes the executable program codes to respectively implement the functions of the foregoing obtaining unit 801, generating unit 802, sending unit 803, and analyzing unit 804, so as to implement any one of the methods in the data storage method. That is, the memory 906 stores instructions for executing any one of the methods in the data analysis method.

[0207] Alternatively, the memory 906 stores executable codes, and the processor 904 executes the executable codes to respectively implement the functions of the foregoing access point, so as to implement any one of the methods in the data storage method. That is, the memory 906 stores instructions for executing any one of the methods in the data storage method.

[0208] The communication interface 908 uses a transceiver module such as, but not limited to, a network interface card or a transceiver to implement the communication between the device 900 for data analysis and other devices or communication networks.

[0209] Please refer to Figure 10 , Figure 10 which is a schematic structural diagram of a computing device cluster provided by an embodiment of the present application.

[0210] The computing device cluster includes at least one device for data analysis. The device 900 for data analysis can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smart phone.

[0211] As Figure 10 shown, the computing device cluster includes at least one device 900 for data analysis. Instructions for performing any of the methods in the method for data storage can be stored in the memory 906 of one or more devices 900 for data analysis in the computing device cluster.

[0212] In some possible implementation manners, partial instructions for performing any of the methods in the method for data storage can also be stored separately in the memory 906 of one or more devices 900 for data analysis in the computing device cluster. In other words, a combination of one or more devices 900 for data analysis can jointly execute the instructions for performing any of the methods in the method for data storage.

[0213] It should be noted that different memories 906 in different devices 900 for data analysis in the computing device cluster can store different instructions, which are respectively used to perform partial functions of the cloud management platform. That is, the instructions stored in the memories 906 of different devices 900 for data analysis can implement the functions of one or more of the acquisition unit 801, the generation unit 802, the sending unit 803, and the analysis unit 804.

[0214] In some possible implementation manners, one or more data storage devices in the computing device cluster can be connected through a network. Among them, the network can be a wide area network or a local area network, etc.

[0215] Please refer to Figure 11 , Figure 11 which is another schematic structural diagram of the computing device cluster provided by the embodiment of the present application.

[0216] As Figure 11 shown, two devices 900A and 900B for data analysis are connected through a network. Specifically, they are connected to the network through the communication interfaces in each computing device. In this type of possible implementation manner, instructions for implementing the functions of the acquisition unit 801 and the generation unit 802 are stored in the memory 906 of the device 900A for data analysis. At the same time, instructions for implementing the functions of the sending unit 803 and the analysis unit 804 are stored in the memory 906 of the device 900B for data analysis.

[0217] It should be understood that Figure 11 The functions of the data analysis device 900A shown in the figure can also be completed by multiple data analysis devices 900. Similarly, the functions of the data analysis device 900B can also be completed by multiple data analysis devices 900.

[0218] The embodiments of the present application also provide another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similarly referred to Figure 10 and Figure 11 the connection method of the computing device cluster. The difference is that in the memory 906 of one or more data analysis devices 900 in the computing device cluster, there can be stored instructions for performing any one of the methods in the data storage method.

[0219] In some possible implementation manners, in the memory 906 of one or more data analysis devices 900 in the computing device cluster, there can also be respectively stored partial instructions for performing any one of the methods in the data storage method. In other words, the combination of one or more data analysis devices 900 can jointly execute the instructions for performing any one of the methods in the data storage method.

[0220] It should be noted that the memories 906 in different data analysis devices 900 in the computing device cluster can store different instructions for performing partial functions of the data analysis device.

[0221] Combined with the specific usage method, the embodiments of the present application also provide another structural schematic diagram of the data analysis device. As Figure 12 shown, the data analysis device includes a network element node identification module, a network element type and network service management module, a network service metadata instance management module, and a network service metadata management module.

[0222] The network element node identification module is used to periodically check whether there are newly added network element nodes in the configuration management database. When there are, it queries the network service corresponding to the newly added network element from the network element type and network service management module;

[0223] The network type and network service management module is used to manage the correspondence between network element types and network services, and periodically check the update situation of the correspondence between network elements and network services in the configuration file.

[0224] After the network element node identification module determines the network service corresponding to the newly added network element, it sends a network service dial test request to the network service metadata instance management module.

[0225] The network service metadata instance management module is used to read network service metadata instances, determine the source IP metadata instance, destination IP metadata instance, and network service metadata instance corresponding to the network service, so as to formulate and manage the dial test resource creation policy. It can also update the correspondence between the network service metadata instance and the network element type by regularly checking the configuration file. After determining the network service metadata instance corresponding to the network element, it calls the interface to create resources according to the creation policy, and realizes the dial test of the basic network resource interface and the general network interface in the network service metadata management module. It also customizes the dial test policy, distributes the dial test policy, collects the dial test results, and analyzes the dial test results according to the dial test resource creation policy.

[0226] It should be noted that Figure 12 The specific structure and working content of the data analysis device described in [reference] are only one possible situation. In actual applications, the functional modules should be set according to the specific application scenarios to implement the specific steps and functions, which are not limited here.

[0227] The embodiment of the present application also provides a computer-readable storage medium, including computer-readable instructions. When the computer-readable instructions run on a computer, the computer is caused to execute any implementation manner shown in the foregoing method embodiments.

[0228] The embodiment of the present application also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions run on a computer, the computer is caused to execute any implementation manner shown in the foregoing method embodiments.

[0229] The present application also provides a chip or a chip system. The chip may include a processor. The chip may also include a memory (or storage module) and / or a transceiver (or communication module), or the chip is coupled to the memory (or storage module) and / or the transceiver (or communication module). Among them, the transceiver (or communication module) can be used to support the chip for wired and / or wireless communication, and the memory (or storage module) can be used to store a program or a set of instructions. The processor calls the program or the set of instructions to implement the operations performed by the terminal or the network device in any possible implementation manner of the foregoing method embodiments and method embodiments. The chip system may include the above chip, or may include the above chip and other discrete devices, such as a memory (or storage module) and / or a transceiver (or communication module).

[0230] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments, and will not be elaborated here.

[0231] In several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces, and the indirect coupling or communication connection of the device or unit can be in electrical, mechanical, or other forms.

[0232] The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0233] In addition, in each embodiment of the present application, the functional units can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0234] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in each embodiment of the present application. The foregoing storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs that can store program codes.< / api> < / api>

Claims

1. A method for generating a probing strategy, characterized in that, it includes: Obtain a first correspondence list and a first mapping relationship list, where the first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping relationship list includes the mapping relationship between the first network service and the first metadata instance. The first metadata instance includes a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance; Obtain the network element type of the first network element. The network element type of the first network element is the first network element type. The first network element is included in the first network at the first moment and not included in the first network at the second moment. The first moment is after the second moment; Generate a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list. The first mapping relationship is the mapping relationship between the first network element and the first metadata instance, and the first mapping relationship is used to generate the probing strategy of the first network element.

2. The method according to claim 1, characterized in that, Obtaining the network element type of the first network element includes: If the network element type of the first network element is included in the first correspondence list, obtain the network element type of the first network element.

3. The method according to claim 1 or 2, characterized in that, The generating a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list includes: Search for the network element type of the first network element in the first correspondence list to obtain the first network service that has a correspondence relationship with the first network element type; Search for the first network service in the first mapping relationship list to obtain the first metadata instance, and there is a mapping relationship between the first metadata instance and the first network service; Generate a first mapping relationship, and the first mapping relationship is the mapping relationship between the first network element and the first metadata instance.

4. The method according to claim 3, characterized in that, The searching for the first network service in the first mapping relationship list to obtain the first metadata instance includes: If there is no computing node in the first network that provides computing power for the first network service, search for the first network service in the first mapping relationship list to obtain the first metadata instance.

5. The method according to any one of claims 1 to 2, characterized in that, The first metadata instance instructs the first computing node to perform a first calculation; The method further includes: Generate a first message, and the first message instructs the first computing node to perform a first calculation; Send the first message to the first computing node; Obtain the first calculation result sent by the first computing node, and the first calculation result indicates whether the first computing node successfully performs the first calculation.

6. The method according to claim 5, characterized in that, The method further includes: Analyze the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element.

7. An apparatus for generating a probing strategy, characterized in that, it includes: An acquisition unit, configured to acquire a first correspondence list and a first mapping relationship list, where the first correspondence list includes the correspondence between the first network element type and the first network service, and the first mapping relationship list includes the mapping relationship between the first network service and the first metadata instance, and the first metadata instance includes a first source IP metadata instance, a first destination IP metadata instance, and a first network service metadata instance; The acquisition unit is further configured to acquire the network element type of the first network element, the network element type of the first network element being the first network element type, the first network element being included in the first network at a first moment and not being included in the first network at a second moment, the first moment being after the second moment; A generation unit, configured to generate a first mapping relationship according to the network element type of the first network element, the first correspondence list, and the first mapping relationship list, the first mapping relationship being the mapping relationship between the first network element and the first metadata instance, and the first mapping relationship being used to generate the probing strategy of the first network element.

8. The apparatus according to claim 7, characterized in that, The acquisition unit is specifically configured to, if the network element type of the first network element is included in the first correspondence list, acquire the network element type of the first network element.

9. The apparatus according to claim 7 or 8, characterized in that, The generation unit is specifically configured to: Search for the network element type of the first network element in the first correspondence list to obtain the first network service having a correspondence relationship with the first network element type; Search for the first network service in the first mapping relationship list to obtain the first metadata instance, where there is a mapping relationship between the first metadata instance and the first network service; Generate a first mapping relationship, the first mapping relationship being the mapping relationship between the first network element and the first metadata instance.

10. The apparatus according to claim 9, characterized in that, The generation unit is specifically configured to, if there is no computing node in the first network to provide computing power for the first network service, search for the first network service in the first mapping relationship list to obtain the first metadata instance.

11. The apparatus according to any one of claims 7 to 8, characterized in that, The first metadata instance instructs a first computing node to perform a first calculation; The generation unit is further configured to generate a first message, the first message instructing the first computing node to perform the first calculation; The apparatus further includes a sending unit, configured to send the first message to the first computing node; The acquisition unit is further configured to acquire a first calculation result sent by the first computing node, the first calculation result indicating whether the first computing node successfully performs the first calculation.

12. The apparatus according to claim 11, characterized in that, The apparatus further includes: An analysis unit, configured to analyze the first calculation result to obtain the packet loss rate of the first network element and the delay data of the first network element.

13. An apparatus for generating a probing strategy, It is characterized in that it includes a processor and a memory, the memory is used for storing instructions, and the processor is used for executing the instructions. When the processor executes the instructions, it executes the method according to any one of claims 1 to 6.

14. A computer-readable storage medium It is characterized in that it includes a program which, when running on a computer, causes the computer to execute the method according to any one of claims 1 to 6.

15. A cluster of computing devices It is characterized in that it includes at least one computing device, and each computing device includes a processor and a memory; the processor of the at least one computing device is used for executing the instructions stored in the memory of the at least one computing device, so that the cluster of computing devices executes the method according to any one of claims 1 to 6.

Images