Service registration control method and device, equipment, storage medium and program product

Abstract

The invention relates to a service registration control method and device, equipment, a storage medium and a program product. The method comprises the following steps: receiving metadata reported by a client, and performing metadata format verification; wherein the metadata comprises at least one of a data center, a network area, a cluster, a system name and a service name where the service is located; if the result of the metadata format verification is passed, selecting a first verification mode or a second verification mode to carry out secondary verification; obtaining a verification result corresponding to the first verification mode or the second verification mode; and determining whether to perform service registration or not according to the verification result. Therefore, the metadata can be verified through two different verification modes, so that a server can flexibly adapt to a registration control mode according to information contained in the metadata, and service registration control of multiple dimensions such as a machine room, a network area, a cluster, a system, service and a deployment environment is realized.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a service registration control method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Art

[0002] The registration center is one of the basic components of the microservice architecture. It provides basic functions such as service registration and service discovery, and plays a role as a link in the task planning system. When the mainstream registration center manages services in multiple computer rooms and clusters, it is still unable to control service registration based on environmental information.

[0003] In the existing technology, registration control is generally implemented based on client authentication, such as username and password, and Token. This registration method also requires the client to modify the server in the corresponding registration.

[0004] However, the above service registration control can only rely on the authentication of the client and server, and cannot control multiple dimensions such as the computer room, network area, cluster, system, service, deployment environment, etc. Summary of the invention

[0005] Based on this, it is necessary to provide a control method, device, computer equipment, computer-readable storage medium and computer program product that can realize service registration in multiple dimensions such as computer rooms, network areas, clusters, systems, services, and deployment environments in response to the above technical problems.

[0006] In a first aspect, the present application provides a method for controlling service registration, comprising:

[0007] Receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0008] If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification;

[0009] Obtaining a verification result corresponding to the first verification method or the second verification method;

[0010] According to the verification result, it is determined whether to register the service.

[0011] In one embodiment, the receiving metadata reported by the client and performing metadata format verification includes:

[0012] Receive metadata reported by the client, and parse the metadata to obtain several character strings;

[0013] Comparing the plurality of character strings with predefined elements; the predefined elements include: system name, service name, data center, network zone, and cluster;

[0014] If the metadata contains all the predefined elements, then the result of the metadata format check is determined to be passed;

[0015] If the metadata does not contain all the predefined elements, the result of the metadata format check is determined to be failed.

[0016] In one embodiment, if the result of the metadata format check is determined to be failed, the method further includes:

[0017] Service registration is not allowed, and a registration failure prompt message is sent to the corresponding client.

[0018] In one embodiment, the first verification method includes:

[0019] Verify the system name and service name in the metadata according to the service whitelist. If the system name and service name in the metadata are not in the service whitelist, generate a verification result that prohibits service registration, and store the generated registration failure instance information in the database.

[0020] If the system name and service name in the metadata are in the service whitelist, data center verification, network zone verification and cluster verification are performed respectively;

[0021] If the verification results of the data center verification, the network zone verification, and the cluster verification are all passed, generating a verification result that allows service registration;

[0022] If at least one of the verification results of the data center verification, the network zone verification, and the cluster verification fails, a verification result that does not allow service registration is generated, and registration failure information is recorded.

[0023] In one embodiment, the second verification method includes:

[0024] Verify the system name and service name in the metadata according to the service whitelist. If the system name and service name in the metadata are not in the service whitelist, generate a verification result that allows service registration, and record information that the metadata does not satisfy the service whitelist.

[0025] The system name and the service name in the metadata are verified according to the service whitelist, and if the system name and the service name in the metadata are in the service whitelist, a verification result is generated to allow service registration.

[0026] In one embodiment, determining whether to perform service registration according to the verification result includes:

[0027] If the verification result is that the service registration is allowed, the service registration is completed;

[0028] If the verification result is that service registration is not allowed, service registration is rejected.

[0029] In a second aspect, the present application also provides a control device for service registration, including:

[0030] A receiving module, used to receive metadata reported by a client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0031] The verification module is used to select the first verification method or the second verification method for secondary verification when the result of the metadata format verification is passed;

[0032] An acquisition module, used to acquire a verification result corresponding to the first verification method or the second verification method;

[0033] The registration module is used to determine whether to register the service according to the verification result.

[0034] In a third aspect, the present application further provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0035] Receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0036] If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification;

[0037] Obtaining a verification result corresponding to the first verification method or the second verification method;

[0038] According to the verification result, it is determined whether to register the service.

[0039] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the following steps are implemented:

[0040] Receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0041] If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification;

[0042] Obtaining a verification result corresponding to the first verification method or the second verification method;

[0043] According to the verification result, it is determined whether to register the service.

[0044] In a fifth aspect, the present application further provides a computer program product, including a computer program, which implements the following steps when executed by a processor:

[0045] Receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0046] If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification;

[0047] Obtaining a verification result corresponding to the first verification method or the second verification method;

[0048] According to the verification result, it is determined whether to register the service.

[0049] The control method, device, computer equipment, computer-readable storage medium and computer program product of the service registration receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network area, cluster, system name and service name where the service is located; thereby collecting the environmental information where the service instance is located, so that the dimension of the service registration can include the data center, network area, cluster, system name, service name and the like where the service is located. If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification; the verification result corresponding to the first verification method or the second verification method is obtained; and according to the verification result, it is determined whether to register the service. Thus, the metadata can be verified by two different verification methods, so that the server can flexibly adapt the registration control method according to the information contained in the metadata, and realize service registration control in multiple dimensions such as computer room, network area, cluster, system, service, and deployment environment. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0051] Figure 1 An application environment diagram of a control method for service registration in one embodiment;

[0052] Figure 2 A flowchart of a control method for service registration in one embodiment;

[0053] Figure 3 A schematic diagram of a verification process of two different verification methods in one embodiment;

[0054] Figure 4 A schematic diagram of a verification process of a forced control verification method in an embodiment;

[0055] Figure 5 A schematic flow chart of a control method for service registration in another embodiment;

[0056] Figure 6 A structural block diagram of a control device for service registration in one embodiment;

[0057] Figure 7 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0059] The service registration control method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. The client 101 communicates with the server 102 through the network. The client 101 reports metadata to the server 102 through the network. The server 102 receives the metadata reported by the client 101 and performs metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located; if the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification; the verification result corresponding to the first verification method or the second verification method is obtained; according to the verification result, it is determined whether to register the service. The client 101 can be, but is not limited to, various personal computers, laptops, smart phones, tablet computers, Internet of Things devices and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart car devices, projection devices, etc. Portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. The server 104 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud computing services.

[0060] In an exemplary embodiment, Figure 2 As shown, a service registration control method is provided, which is applied to Figure 1 The server in the example is used to illustrate, including the following steps 201 to 204. Among them:

[0061] Step 201: receiving metadata reported by the client and performing metadata format verification.

[0062] The metadata includes: at least one of the data center where the service is located, the network zone, the cluster, the system name, and the service name.

[0063] In this embodiment, when the client needs to register for a service, it reports metadata to the server (registration center). The metadata includes the data center, network zone, cluster, system name, and service name where the service is located. If the registration metadata does not contain the specified multiple elements, registration is not allowed and a registration failure message is displayed.

[0064] Exemplarily, metadata reported by a client is received, and the metadata is parsed to obtain a number of character strings; the number of character strings are compared with predefined elements; the predefined elements include: system name, service name, data center, network zone, cluster; if the metadata contains all the predefined elements, the result of the metadata format check is determined to be passed; if the metadata does not contain all the predefined elements, the result of the metadata format check is determined to be failed.

[0065] Optionally, if the result of the metadata format verification is determined to be failed, service registration is not allowed, and a registration failure prompt message is sent to the corresponding client.

[0066] Step 202: If the result of the metadata format verification is passed, the first verification method or the second verification method is selected to perform a secondary verification.

[0067] In this embodiment, the first verification method may be a forced control method, and the second verification method may be a non-control method. Figure 3 As shown in the figure, after the metadata verification, it is divided into two branches, corresponding to the two verification methods of strong control and no control. It should be noted that these two methods are selective, that is, they can be flexibly selected according to the actual environment of the service.

[0068] Exemplarily, the first verification method includes: verifying the system name and service name in the metadata according to the service whitelist; if the system name and service name in the metadata are not in the service whitelist, generating a verification result that does not allow service registration, and storing the generated registration failure instance information in the database; if the system name and service name in the metadata are in the service whitelist, performing data center verification, network area verification and cluster verification respectively; if the verification results of the data center verification, the network area verification and the cluster verification are all passed, generating a verification result that allows service registration; if at least one of the verification results of the data center verification, the network area verification and the cluster verification is failed, generating a verification result that does not allow service registration, and recording the registration failure information.

[0069] In this embodiment, see Figure 4As shown, when the service registration reports metadata to the server, the system name and service name will be checked first. If the system name and service name are not in the registration whitelist, the registration will be rejected; at the same time, the registration failure instance information will be stored in the database. If the system name and service name are in the registration whitelist, the data center, network area, and cluster in the metadata will be further compared to see if they are in the set data center, network area, and cluster. If they are all in the set data center, network area, and cluster, service registration is allowed; if at least one is not in the set data center, network area, and cluster, registration is rejected and failure information is recorded. Among them, the verification data structure may include: system name (systemName), service name (project Name), data center (data Center), network area (network Area), and cluster (logical Cluster).

[0070] Exemplarily, the second verification method includes: verifying the system name and service name in the metadata according to the service whitelist, if the system name and service name in the metadata are not in the service whitelist, generating a verification result that allows service registration, and recording information that the metadata does not meet the service whitelist; verifying the system name and service name in the metadata according to the service whitelist, if the system name and service name in the metadata are in the service whitelist, generating a verification result that allows service registration.

[0071] In this embodiment, service registration is allowed regardless of whether the system name and service name are in the service whitelist, so this verification method is also called a non-control method. However, when the system name and service name included in the metadata are not in the service whitelist, the information that the service does not meet the service whitelist will be recorded synchronously for subsequent review.

[0072] Step 203, obtaining the verification result corresponding to the first verification method or the second verification method.

[0073] In this embodiment, when the client registers the service, the service metadata (system name, service name, data center, network zone, cluster) can be used to perform flexible and configurable service registration control. That is, the first verification method or the second verification method can be selected as needed.

[0074] Step 204: Determine whether to register the service based on the verification result.

[0075] In this embodiment, whether to perform service registration is determined according to the verification result corresponding to the first verification method or the second verification method.

[0076] Exemplarily, if the verification result is that the service registration is allowed, the service registration is completed; if the verification result is that the service registration is not allowed, the service registration is rejected.

[0077] Compared with the existing service registration control method, this embodiment does not need to rely on client and server authentication, and can control multiple dimensions such as the computer room, network area, cluster, system, service, and deployment environment, thereby achieving multi-dimensional service registration control, supplementing the lack of service registration control granularity, adding finer-grained service registration control, and improving the security of microservices in distributed systems.

[0078] In the above service registration control method, metadata reported by the client is received and metadata format verification is performed; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located; thereby collecting the environment information where the service instance is located, so that the dimensions of the service registration can include the data center, network zone, cluster, system name, service name, etc. where the service is located. If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification; the verification result corresponding to the first verification method or the second verification method is obtained; and according to the verification result, it is determined whether to register the service. Thus, the metadata can be verified by two different verification methods, so that the server can flexibly adapt the registration control method according to the information contained in the metadata, and realize service registration control in multiple dimensions such as computer room, network zone, cluster, system, service, and deployment environment.

[0079] In another exemplary embodiment, Figure 5 As shown, a service registration control method is provided, which is applied to Figure 1 The server in the example is used to illustrate, including the following steps 501 to 507. Among them:

[0080] Step 501: receiving metadata reported by the client.

[0081] Step 502 , perform metadata format verification on the metadata to determine whether the verification result is passed. If it is passed, execute step 503 ; if it is not passed, execute step 507 .

[0082] Step 503: Select the first verification method or the second verification method to perform a secondary verification.

[0083] Step 504, obtaining the verification result corresponding to the first verification method or the second verification method.

[0084] Step 505 , determine whether the verification result is that the service registration is allowed, if so, execute step 506 , if not, execute step 507 .

[0085] Step 506, complete service registration.

[0086] Step 507: Refuse to register for the service.

[0087] In this embodiment, by collecting the environment information of the service instance, the registration center server receives the metadata information and performs format verification and secondary verification on the metadata to determine whether the service registration can be performed. The metadata contains information of multiple dimensions, and the information of each dimension is verified separately during the format verification and secondary verification process, thereby achieving multi-dimensional service registration control.

[0088] This embodiment makes up for the deficiency of service registration control granularity, adds finer-grained service registration control, and improves the security of microservices in a distributed system.

[0089] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0090] Based on the same inventive concept, the embodiment of the present application also provides a service registration control device for implementing the service registration control method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in the embodiments of one or more service registration control devices provided below can refer to the limitations of the service registration control method above, and will not be repeated here.

[0091] In an exemplary embodiment, Figure 6 As shown, a control device for service registration is provided, including: a receiving module 601, a verification module 602, an acquisition module 603 and a registration module 604, wherein:

[0092] The receiving module 601 is used to receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located;

[0093] Verification module 602, used for selecting the first verification method or the second verification method for secondary verification when the result of metadata format verification is passed;

[0094] An acquisition module 603 is used to acquire a verification result corresponding to the first verification method or the second verification method;

[0095] The registration module 604 is used to determine whether to perform service registration according to the verification result.

[0096] Exemplarily, the receiving module 601 is specifically used to: receive metadata reported by the client, and parse the metadata to obtain a number of character strings; compare the several character strings with pre-defined elements; the pre-defined elements include: system name, service name, data center, network area, cluster; if the metadata contains all the pre-defined elements, then the result of the metadata format check is determined to be passed; if the metadata does not contain all the pre-defined elements, then the result of the metadata format check is determined to be failed.

[0097] Exemplarily, the verification module 602 is further used to: if the result of the metadata format verification is determined to be failed, not allowing service registration, and sending a registration failure prompt message to the corresponding client.

[0098] Exemplarily, the first verification method includes: verifying the system name and service name in the metadata according to the service whitelist; if the system name and service name in the metadata are not in the service whitelist, generating a verification result that does not allow service registration, and storing the generated registration failure instance information in the database; if the system name and service name in the metadata are in the service whitelist, performing data center verification, network area verification and cluster verification respectively; if the verification results of the data center verification, the network area verification and the cluster verification are all passed, generating a verification result that allows service registration; if at least one of the verification results of the data center verification, the network area verification and the cluster verification is failed, generating a verification result that does not allow service registration, and recording the registration failure information.

[0099] Exemplarily, the second verification method includes: verifying the system name and service name in the metadata according to the service whitelist, if the system name and service name in the metadata are not in the service whitelist, generating a verification result that allows service registration, and recording information that the metadata does not meet the service whitelist; verifying the system name and service name in the metadata according to the service whitelist, if the system name and service name in the metadata are in the service whitelist, generating a verification result that allows service registration.

[0100] Exemplarily, the registration module 604 is specifically used to: if the verification result is that the service registration is allowed, then complete the service registration; if the verification result is that the service registration is not allowed, then refuse to register the service.

[0101] Each module in the control device for service registration can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0102] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Figure 7 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store metadata reported by the client. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a control method for service registration is implemented.

[0103] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0104] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0105] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0106] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0107] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0108] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0109] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0110] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A control method for service registration, characterized in that: The method comprises: Receive metadata reported by the client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located; If the result of the metadata format verification is passed, the first verification method or the second verification method is selected for secondary verification; Obtaining a verification result corresponding to the first verification method or the second verification method; According to the verification result, it is determined whether to register the service.

2. The method according to claim 1, characterized in that The receiving of metadata reported by the client and performing metadata format verification includes: Receive metadata reported by the client, and parse the metadata to obtain several character strings; Comparing the plurality of character strings with predefined elements; the predefined elements include: system name, service name, data center, network zone, and cluster; If the metadata contains all the predefined elements, then the result of the metadata format check is determined to be passed; If the metadata does not contain all the predefined elements, the result of the metadata format check is determined to be failed.

3. The method according to claim 2, characterized in that If the result of the metadata format verification is determined to be unsuccessful, the method further includes: Service registration is not allowed, and a registration failure prompt message is sent to the corresponding client.

4. The method according to any one of claims 1 to 3, characterized in that: The first verification method includes: Verify the system name and service name in the metadata according to the service whitelist. If the system name and service name in the metadata are not in the service whitelist, generate a verification result that prohibits service registration, and store the generated registration failure instance information in the database. If the system name and service name in the metadata are in the service whitelist, data center verification, network zone verification and cluster verification are performed respectively; If the verification results of the data center verification, the network zone verification, and the cluster verification are all passed, generating a verification result that allows service registration; If at least one of the verification results of the data center verification, the network zone verification, and the cluster verification fails, a verification result that does not allow service registration is generated, and registration failure information is recorded.

5. The method according to any one of claims 1 to 3, characterized in that: The second verification method includes: Verify the system name and service name in the metadata according to the service whitelist. If the system name and service name in the metadata are not in the service whitelist, generate a verification result that allows service registration, and record information that the metadata does not satisfy the service whitelist. The system name and the service name in the metadata are verified according to the service whitelist, and if the system name and the service name in the metadata are in the service whitelist, a verification result is generated to allow service registration.

6. The method according to any one of claims 1 to 3, characterized in that: The determining whether to perform service registration according to the verification result includes: If the verification result is that the service registration is allowed, the service registration is completed; If the verification result is that service registration is not allowed, service registration is rejected.

7. A control device for service registration, characterized in that: The device comprises: A receiving module, used to receive metadata reported by a client and perform metadata format verification; wherein the metadata includes: at least one of the data center, network zone, cluster, system name, and service name where the service is located; The verification module is used to select the first verification method or the second verification method for secondary verification when the result of the metadata format verification is passed; An acquisition module, used to acquire a verification result corresponding to the first verification method or the second verification method; The registration module is used to determine whether to register the service according to the verification result.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images