CN113010418B

CN113010418B - Progressive gray level publishing method and device

Info

Publication number: CN113010418B
Application number: CN202110239593.7A
Authority: CN
Inventors: 宋海涵; 魏雪; 王婧; 张丹阳
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2021-03-04
Filing date: 2021-03-04
Publication date: 2024-03-01
Anticipated expiration: 2041-03-04
Also published as: CN113010418A

Abstract

The invention provides a progressive gray level release method and device, which can be used in the financial field or other technical fields. The method comprises the following steps: transmitting a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset; if the first gray server is judged to pass the gray release test, triggering the gray version deployment of one server in the server cluster so that the one server becomes the next gray server; and sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test. The device is used for executing the method. The progressive gray level release method and device provided by the embodiment of the invention improve the reliability of gray level release.

Description

Progressive gray level publishing method and device

Technical Field

The invention relates to the technical field of computers, in particular to a progressive gray level publishing method and device.

Background

With the rapid development of internet technology, various internet application products are layered endlessly. In order to control potential running risks, customer experience is improved, a gray level release method is often adopted when a new version of an application product is released, most customers continue to use the old version of the application product, a small part of customers experience the new version of the application product, and if the customers feed back the new version of the application product well, the application range of the new version of the application product is further enlarged.

In the prior art, when gray level release of an application product is performed, a gray level release strategy needs to be set manually, and then the gray level release strategy is executed manually or in an automatic mode. The following problems exist in the implementation of gray level release of an application product through a gray level release strategy: (1) The core of the gray level release strategy is to determine the gray level ratio, the gray level ratio is subjectivity, the selected gray level ratio is based on the past experience, and the problems that the gray level test point range is too large to increase the production risk or the gray level test point range is too small to influence the gray level effect possibly exist. (2) The new version is comprehensively promoted through one to two gray test points, so that a gray mechanism cannot play a role well. If multiple gray scale test points are selected, the workload is greatly increased, and the manual execution of gray scale strategies is not facilitated. (3) When gray scale division is performed, customers are taken as division standards, and a part of customers experience new versions. Because the behavior of the client is subjective, if the client does not initiate a transaction request in the gray release period, the gray version program cannot be guaranteed to obtain sufficient effective call, so that the gray test time needs to be prolonged, the popularization of new products is affected, and the server resources are wasted.

Disclosure of Invention

Aiming at the problems in the prior art, the embodiment of the invention provides a progressive gray level publishing method and device, which can at least partially solve the problems in the prior art.

In one aspect, the present invention provides a progressive gray scale release method, including:

transmitting a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset;

if the first gray server is judged to pass the gray release test, triggering the gray version deployment of one server in the server cluster so that the one server becomes the next gray server;

and sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

In another aspect, the present invention provides a progressive gray scale distribution apparatus, comprising:

the transmission module is used for transmitting a transaction request to a first gray server based on a gray release rule so as to carry out gray release test on the first gray server; wherein the gray level distribution rule is preset;

The triggering module is used for triggering the gray version deployment of one server in the server cluster after judging and knowing that the first gray server passes the gray release test so as to enable the one server to be the next gray server;

and the test module is used for sending a transaction request to the next gray server based on the gray release rule so as to carry out gray release test on the next gray server until a preset number of servers in the server cluster pass the gray release test.

In yet another aspect, the present invention provides an electronic device including a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the progressive gray scale distribution method of any of the embodiments described above when the program is executed.

In yet another aspect, the present invention provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the progressive gray level distribution method of any of the embodiments described above.

According to the progressive gray level release method and device, a transaction request can be sent to the first gray level server based on the gray level release rule, gray level release test is conducted on the first gray level server, after the fact that the first gray level server passes the gray level release test is judged, gray level version deployment of one server in the server cluster is triggered, so that the one server becomes the next gray level server, gray level release test is conducted on the next gray level server based on the gray level release rule, gray level release is conducted progressively until the preset number of servers in the server cluster pass the gray level release test, gray level versions of application products can be tested fully, and reliability of gray level release is improved.

Drawings

In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:

fig. 1 is a flowchart of a progressive gray level distribution method according to an embodiment of the present invention.

Fig. 2 is a flowchart of a progressive gray level distribution method according to another embodiment of the present invention.

Fig. 3 is a flowchart of a progressive gray scale distribution method according to another embodiment of the present invention.

Fig. 4 is a flowchart of a progressive gray level distribution method according to still another embodiment of the present invention.

Fig. 5 is a flowchart of a progressive gray level distribution method according to still another embodiment of the present invention.

Fig. 6 is a schematic structural diagram of a progressive gray scale release device according to an embodiment of the present invention.

Fig. 7 is a schematic physical structure of an electronic device according to an embodiment of the invention.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.

In order to facilitate understanding of the technical solutions provided in the present application, the following description will first explain relevant content of the technical solutions of the present application. According to the progressive gray level publishing method provided by the embodiment of the invention, the transaction request is used as the gray level dividing standard, one part of the transaction request is sent to the gray level server through the routing mechanism, and the other part of the transaction request is sent to the normal server, so that the gray level server is ensured to be effectively called. The gray version installation method adopts sequential installation of servers. After the first server installs the gray version, the real-time processing amount of the first gray server for the transaction request is gradually increased according to the gray release rule, and after the real-time processing amount reaches the target value and passes the gray release test, the second server starts to install the gray version. And the second gray level server repeats the gray level release test logic of the first gray level server, and when the real-time processing amount of the transaction request reaches the target value and passes the gray level release test, a gray level version is installed for the third server, and the like, so that the progressive gray level release of the whole server cluster is realized.

The implementation process of the progressive gray scale distribution method provided by the embodiment of the invention is described below by taking a gray scale distribution server as an execution subject. It can be understood that the execution body of the progressive gray scale distribution method provided by the embodiment of the invention includes, but is not limited to, a gray scale distribution server.

Fig. 1 is a flow chart of a progressive gray scale release method according to an embodiment of the present invention, as shown in fig. 1, the progressive gray scale release method according to the embodiment of the present invention includes:

s101, sending a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset;

specifically, when gray level release of an application product is performed, the gray level release server may send a transaction request to a first gray level server based on a gray level release rule, where the first gray level server may receive the transaction request sent by the gray level release server and process the transaction request to implement a gray level release test. The gray level distribution server can monitor the condition that the first gray level server processes the transaction request. Wherein the gray level distribution rule is preset. The first greyscale server has installed a greyscale version of the application product.

S102, if judging that the first gray server passes the gray release test, triggering gray version deployment of one server in a server cluster so that the one server becomes the next gray server;

specifically, the gray level release server judges whether the first gray level server passes the gray level release test according to the processing condition of the first gray level server on the transaction request, if the first gray level server passes the gray level release test, the gray level release server indicates that the gray level version of the application product can be promoted, the gray level release server triggers the gray level version deployment of one server in the server cluster, and the one server becomes the next gray level server after the gray level version is installed. If the first gray server fails the gray release test, it indicates that the gray version of the application product has a problem, and improvement is needed.

For example, the installation package of the gray scale version of the application product is stored on a third party server, and the gray scale release server transmits a gray scale version deployment instruction to the third party server, so that the third party server transmits the installation package of the gray scale version of the application product to the one server. The server receives the installation package of the gray level version and installs the gray level version to become the next gray level server.

For example, the installation package of the gray-scale version of the application product may be stored in the gray-scale distribution server, and the gray-scale distribution server may send the installation package of the gray-scale version of the application product to the one server, where the one server installs the gray-scale version and becomes the next gray-scale server.

S103, sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

Specifically, after the one server becomes the next gray server, the gray release server may send a transaction request to the next gray server based on a gray release rule, where the next gray server may receive the transaction request sent by the gray release server and process the transaction request to implement a gray release test. The gray level release server can monitor the condition that the next gray level server processes the transaction request, judge whether the next gray level server passes the gray level release test, continuously trigger the gray level version deployment of one server in the server cluster after the next gray level server passes the gray level release test to obtain the next gray level server, and repeatedly send the transaction request to the next gray level server based on the gray level release rule so as to perform the gray level release test on the next gray level server until the number of the gray level servers passing the gray level release test in the server cluster is equal to the preset number. That is, the grayscale distribution server triggers the deployment of grayscale versions of one server in the server cluster one by one and performs grayscale distribution test. The gray level distribution test process of each gray level server is similar. The preset number may be equal to the number of all servers in the server cluster, or may be equal to the number of part of servers in the server cluster, which is set according to actual needs, and the embodiment of the present invention is not limited.

According to the progressive gray level release method provided by the embodiment of the invention, a transaction request can be sent to the first gray level server based on the gray level release rule, so that gray level release test is carried out on the first gray level server, after the first gray level server is judged to pass through the gray level release test, gray level version deployment of one server in the server cluster is triggered, so that one server becomes the next gray level server, gray level release test is carried out on the next gray level server based on the gray level release rule until the preset number of servers in the server cluster pass through the gray level release test, gray level version of an application product can be fully tested through progressive gray level release, and the reliability of gray level release is improved. Because the gray scale ratio is not required to be set, the man-made subjectivity in the gray scale release process is reduced, and the production risk caused by the overlarge gray scale test point range and the incomplete test caused by the overlarge recovery test point range are avoided. The method has the advantages that a part of clients are not required to experience a new version, gray release due to feedback of the clients in the prior art can be avoided, and in a gray period, the gray version program cannot be guaranteed to obtain sufficient effective call because the gray clients do not initiate transaction requests, so that gray test time is required to be prolonged, new product popularization is influenced, and meanwhile waste of server resources is avoided.

Further, on the basis of the above embodiments, the gray scale distribution rule includes:

transmitting a first test number of transaction requests to a test object; wherein the first test number is equal to an initial value;

if the test time is larger than or equal to the time parameter and the test object meets a first index verification rule, updating a first test quantity and resetting the test time according to the step value, and sending a plurality of transaction requests of the first test quantity to the test object until the first test quantity is equal to a target value; the first test quantity after each update is equal to the sum of the first test quantity before the update and the step value; the first index verification rule is preset.

Specifically, the gray level distribution server sends a first test number of transaction requests to a test object, where the test object is the gray level server. The test object receives and processes the transaction request. The gray level issuing server monitors the condition that the test object processes the transaction request. Wherein the first test number is equal to the initial value. The initial value is preset and is set according to the test requirement, and the embodiment of the invention is not limited.

The test object may feed back the start time of processing the first transaction request and processing related information for each transaction request to the gradation issue server. The gray level issuing server may obtain the test time of the test object according to the current time and the start time, and determine whether the test object meets the first index verification rule based on the processing related information of each transaction request. Wherein the test time is obtained by subtracting the above start time from the current time. The processing-related information includes log information, service verification information, database verification information, batch job information, and the like. The first index verification rule is preset, including but not limited to log verification, service verification, database verification, batch operation condition verification and the like, and is set according to actual needs, and the embodiment of the invention is not limited.

The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And verifying the keywords, namely verifying whether the keywords in the log information are correct or not, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. The service verification includes, but is not limited to, service running condition verification and service response time verification, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null. Batch job condition verification includes, but is not limited to, DBF batch verification, and is set according to actual needs, and embodiments of the present invention are not limited. The DBF batch verifies, namely verifies whether the batch processing result is correct.

And comparing the test time with a time parameter by the gray level release server, and if the test time is greater than or equal to the time parameter and the test object meets the first index verification rule, updating the first test quantity by the gray level release server and resetting the test time, namely calculating the sum of the first test quantity before updating and the step value as the updated first test quantity, and clearing the test time. And then sending the first test number of transaction requests to the test object, wherein the test object continues to process the received transaction requests, and the test object can feed back the start time of the first transaction request after updating the first test number and the processing related information of each transaction request to the gray level release server. The gray level release server re-judges whether the test time is greater than or equal to the time parameter and whether the test object meets the first index verification rule after updating the first test quantity, continuously updating the first test quantity and resetting the test time after judging that the test time is greater than or equal to the time parameter and the test object meets the first index verification rule, repeatedly sending the transaction requests of the first test quantity to the test object, judging whether the test time is greater than or equal to the time parameter and judging whether the test object meets the process of the first index verification rule after updating the first test quantity until the first test quantity is equal to the target value. In other words, the gray level release server gradually increases the transaction request processing amount of the test object based on the step value in the gray level release test process of the test object, and gradually performs the gray level release test on a single gray level server. The time parameter, the step value and the target value are preset and are set according to the test requirement, and the embodiment of the invention is not limited. It can be understood that if the test object does not satisfy the first index verification rule after the test time is greater than or equal to the time parameter, the gray scale release test of the test object may be terminated, and a failure of the gray scale release test may be prompted.

The time parameter is the time interval from the previous gray scale expansion to the next gray scale expansion which is set by people, and the setting of the time parameter has the following effects: firstly, obtaining and reserving enough time for test time calculation and processing related information such as log information, service information, batch operation information and the like; secondly, the trial operation time of gray release content is reserved, so that loopholes and risks of gray versions are exposed; thirdly, the risk caused by too high gray scale expansion speed due to no time control is avoided.

For example, the first index verification rule includes log verification, service verification, database verification and batch job condition verification, the log verification includes keyword verification and return result verification, the service verification includes running condition verification of the service and response time verification of the service, the database verification includes expected value verification and acquisition data verification, and the batch job condition verification includes DBF batch verification. The test object can meet the first index verification rule after passing log verification, service verification, database verification and batch operation condition verification. The test object can pass log verification after passing key word verification and returning result verification. The test object can pass service verification after passing service run condition verification and service response time verification. The test object can pass the database verification after passing the expected value verification and the acquired data verification. The test object can pass the batch operation condition verification after passing the DBF batch verification.

On the basis of the foregoing embodiments, further, if the judging that the first gray server passes the gray distribution test includes:

and if the first test quantity is judged to be equal to the target value, the test time is more than or equal to the time parameter, and the first gray server meets the first index verification rule, determining that the first gray server passes the gray release test.

Specifically, after the first test number is equal to the target value, the gray level distribution server continuously sends the target value transaction requests to a first gray level server, the first gray level server continuously processes the received transaction requests, and the first gray level server can feed back the start time of the first transaction request after the processed first test number is equal to the target value and the processing related information of each transaction request to the gray level distribution server. The gray scale release server recalculates the test time, and if the gray scale release server judges that the test time is greater than or equal to the time parameter and the first gray scale server meets the first index verification rule, the first gray scale server can be confirmed to pass the gray scale release test.

The implementation process of the progressive gray level distribution method provided by the embodiment of the invention is described in the following by a specific embodiment.

The initial value is set to 1000, the step value is set to 1000, the target value is set to 20000, and the time parameter is set to 6 hours.

After the first gray server a in the server cluster installs the gray version of the application product A, the gray release server performs environment verification. The environment verification includes but is not limited to configuration center verification, file verification, PAAS verification and service state verification, and is set according to actual needs, and the embodiment of the invention is not limited. Configuration center validation includes, but is not limited to, disconf profile content validation, apollo configuration instance number validation, CMC dynamic variable validation. File verification includes, but is not limited to, command verification, profile parameter verification, and in-container script verification. PAAS authentication includes, but is not limited to, deployment node authentication. Service state verification includes, but is not limited to, service provider verification. Service provider verification, including but not limited to determining whether the number of servers is correct, whether the registration status of the service provider is normal, whether the running status is smooth, and whether the service response time is within a preset time interval.

After the environment verification is passed, the gray level release server sends 1000 transaction requests to a first gray level server a, and the first gray level server a processes the received transaction requests and returns the starting time of processing the first transaction request and processing related information of processing each transaction request to the gray level release server. And the gray level release server calculates the test time based on the current time and the starting time, and if the test time is more than or equal to 6 hours, continuously judges whether the first gray level server a meets a first index verification rule based on the processing related information, wherein the first index verification rule comprises log verification, service verification, database verification and batch operation condition verification. If the first gray server a passes log verification, service verification, database verification and batch job condition verification, the first gray server a satisfies a first index verification rule.

After the test time is greater than or equal to 6 hours and the first gray server a meets the first index verification rule, the gray release server updates the first test quantity to 1000+1000=2000, sets the test time to 0, sends 2000 transaction requests to the first gray server a, processes the received transaction requests by the first gray server a, and returns the start time for processing the first transaction requests and processing related information for processing each transaction request after the first test quantity is updated to the gray release server. And the gray level release server recalculates the test time based on the current time and the starting time, and if the test time is more than or equal to 6 hours, continuously judging whether the first gray level server a meets a first index verification rule, wherein the first index verification rule comprises service verification, database verification and batch operation condition verification. If the first gray server a passes service verification, database verification and batch job condition verification, the first gray server a satisfies a first index verification rule.

And the gray level release server continuously updates the first test quantity, and repeatedly performs gray level release test on the first gray level server a until the updated first test quantity is equal to 20000. The gray level release server sends 20000 transaction requests to a first gray level server a, the first gray level server a processes the received transaction requests and returns the start time of processing the first transaction requests and the processing related information of processing each transaction request after the first test quantity is equal to 20000 to the gray level release server. And the gray level release server recalculates the test time based on the current time and the starting time, and if the test time is more than or equal to 6 hours, continuously judging whether the first gray level server a meets the first index verification rule. If the first gray server a passes service verification, database verification and batch job condition verification, the first gray server a passes gray release test.

The gray level release server sends a gray level version deployment instruction to a third party server, and the third party server sends an installation package of the gray level version of the application product A to one server b (a server not deploying the gray level version) in the server cluster. The server b receives the installation package, installs the gray-scale version of the application product a through the installation package, and becomes the next gray-scale server after the installation is completed.

And the gray level release server performs environment verification. After the environment verification is passed, the gray level distribution server sends a transaction request to the server b based on the gray level distribution rule so as to perform gray level distribution test on the server b. The gray scale release test procedure of the server b is similar to that of the first server a, and will not be described here.

After the server b passes the gray release test, the gray release server repeats the gray release deployment and the gray release test flow of the server b for one server (the server not deploying the gray release) in the server cluster until all the servers in the server cluster pass the gray release test.

The embodiment of the invention is particularly suitable for the condition of sufficient transaction requests, and can perform gray release test on the gray server by enough transaction requests so as to find the defects of gray version.

Fig. 2 is a flow chart of a progressive gray scale release method according to another embodiment of the present invention, and as shown in fig. 2, the implementation flow of the progressive gray scale release method according to the embodiment of the present invention is as follows:

first, a transaction request is sent. The grayscale distribution server sends a first test number of transaction requests to the grayscale server. The gray server processes the received transaction requests and returns the start time of processing the transaction requests and the processing related information of processing each transaction request to the gray issuing server. Wherein the environment verification is performed before the first test number of transaction requests are transmitted, and the transmission of the transaction requests is performed after the environment verification is passed. The initial value is preset to be 1000, the step value is 1000, the target value is 20000, and the time parameter is 6 hours.

And a second step of judging whether to update the first test quantity. The gray level issuing server calculates the test time based on the current time and the starting time, if the test time is more than or equal to 6 hours, the gray level issuing server continuously judges whether the gray level server meets the first index verification rule based on the processing related information, and if the gray level server meets the first index verification rule, the first test quantity is required to be updated, and the third step is entered. If the test time is less than 6 hours, the gray scale publication server continues to send transaction requests to the gray scale server. If the test time is greater than or equal to 6 hours and the gray server is judged not to meet the first index verification rule, the progressive gray release process is ended.

And thirdly, updating the first test quantity. The gray level release server updates the first test quantity and sets the test time to 0, and the updated first test quantity is equal to the sum of the first test quantity before updating and the step value.

Fourth, it is judged whether or not the target value is equal to the target value. The gray level release server judges whether the first test quantity is equal to the target value, and if the first test quantity is equal to the target value, the fifth step is entered; if the first test number is not equal to the target value, returning to the first step, and continuing to perform the gray scale release test on the gray scale server.

And fifthly, sending a transaction request. The gray level release server sends 20000 transaction requests to the gray level service, and the gray level server processes the received transaction requests and returns the start time of processing 20000 transaction requests and the processing related information of processing each transaction request to the gray level release server.

And step six, judging whether the gray level release test is passed. The gray level release server judges whether the first test quantity is equal to a target value, whether the test time is equal to a time parameter and whether the gray level server meets a first index verification rule, if the first test quantity is equal to the target value, the test time is equal to the time parameter and the gray level server meets the first index verification rule, the gray level server is determined to pass the gray level release test, the test time is reset to 0, and then the seventh step is carried out. If the first test number is equal to the target value and the test time is equal to the time parameter, but the gray server does not meet the first index verification rule, the progressive gray release process is ended.

And seventh, judging whether the preset number is equal to the preset number. The gray level release server counts the number N of servers for deploying gray level versions in the server cluster, and if the number N is equal to the preset number, the progressive gray level release process is finished. If the number N is smaller than the preset number, the eighth step is entered.

And eighth step, triggering gray version deployment. The gray level release server triggers the gray level version deployment of one server in the server cluster so that the one server becomes the next gray level server, the first test quantity is set to be equal to the initial value, and then the first step is carried out to carry out gray level release test on the next gray level server.

transmitting a second test number of transaction requests to the test object; wherein the second test number is equal to an initial value;

if the test object is judged to meet the second index verification rule, updating the second test quantity according to the step value, and sending a transaction request of the second test quantity to the test object until the second test quantity is equal to the target value; wherein the second test number after each update is equal to the sum of the second test number before the update and the step value; the second index verification rule is preset.

Specifically, the gray level distribution server sends a second test number of transaction requests to a test object, where the test object is the gray level server. The test object receives and processes the transaction request. The gray level issuing server monitors the condition that the test object processes the transaction request. Wherein the second test number is equal to the initial value. The initial value is preset and is set according to the test requirement, and the embodiment of the invention is not limited.

The test object may feed back processing related information for each transaction request to the gradation issue server. The gradation release server may determine whether the test object satisfies a second index verification rule based on processing-related information of each transaction request. Wherein the processing-related information includes log information, service authentication information, database authentication information, and the like. The second index verification rule includes, but is not limited to, log verification, service verification, database verification, etc., and is set according to actual needs, and the embodiment of the invention is not limited. The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And the key word verification, namely verifying whether the key word in the log information is correct or not, wherein the key word is set according to actual experience, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. Service verification includes, but is not limited to, checking the running condition of the service and the response time of the service, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null.

And the gray level release server judges whether the test object meets the second index verification rule, and if the test object meets the second index verification rule, the gray level release server updates the second test quantity, namely calculates the sum of the second test quantity before updating and the step length value, and uses the sum as the updated second test quantity. And then sending a second test number of transaction requests to the test object, wherein the test object continues to process the received transaction requests, and the test object can feed back the processing related information of each transaction request to the gray level release server. The gray level release server re-judges whether the test object meets the second index verification rule after updating the second test quantity, continuously updates the second test quantity after judging that the test object meets the second index verification rule, repeats the process of sending the transaction request of the second test quantity to the test object, and judges whether the test object meets the second index verification rule after updating the second test quantity until the second test quantity is equal to the target value. In other words, the gray level release server gradually increases the transaction request processing amount of the test object based on the step value in the gray level release test process of the test object, and gradually performs the gray level release test on a single gray level server. The step value and the target value are preset and set according to the test requirement, and the embodiment of the invention is not limited. It can be appreciated that if the test object does not satisfy the second index verification rule, the gray scale release test for the test object may be terminated and failure of the gray scale release test may be prompted.

For example, the second index verification rule includes log verification including keyword verification and return result verification, service verification including running condition verification of the service and response time verification of the service, and database verification including expected value verification and acquisition data verification. The test object can meet the third index verification rule after passing log verification, service verification and database verification. The test object can pass log verification after passing key word verification and returning result verification. The test object can pass service verification after passing service run condition verification and service response time verification. The test object can pass the database verification after passing the expected value verification and the acquired data verification.

and if the second test quantity is judged to be equal to the target value, determining that the first gray server passes the gray release test.

Specifically, the gray scale distribution server determines whether the second test number is equal to the target value, and if the second test number is equal to the target value, it may be confirmed that the first gray scale server passes the gray scale distribution test.

The implementation process of the progressive gray level distribution method provided by the embodiment of the invention is further described in a specific embodiment.

The initial value is set to 50, the step value is set to 50, and the target value is set to 5000.

After the first gray server c in the server cluster installs the gray version of the application product B, the gray publishing server performs environment verification. The environment verification includes but is not limited to configuration center verification, file verification, PAAS verification and service state verification, and is set according to actual needs, and the embodiment of the invention is not limited. Configuration center validation includes, but is not limited to, disconf profile content validation, apollo configuration instance number validation, CMC dynamic variable validation. File verification includes, but is not limited to, command verification, profile parameter verification, and in-container script verification. PAAS authentication includes, but is not limited to, deployment node authentication. Service state verification includes, but is not limited to, service provider verification. Service provider verification, including but not limited to determining whether the number of servers is correct, whether the registration status of the service provider is normal, whether the running status is smooth, and whether the service response time is within a preset time interval.

After the environment verification is passed, the gray level issuing server sends 50 transaction requests to a first gray level server c, and the first gray level server c processes the received transaction requests and returns processing related information for processing each transaction request to the gray level issuing server. The gray level publishing server judges whether the first gray level server c meets a second index verification rule or not, and the second index verification rule comprises log verification, service verification and database verification. If the first gray server c passes the log verification, the service verification, and the database verification, the first gray server c satisfies the second index verification rule.

After the first gray server c meets the second index verification rule, the gray release server updates the second test quantity to be 50+50=100, then sends 100 transaction requests to the first gray server c, and the first gray server c processes the received transaction requests and returns processing related information for processing each transaction request to the gray release server. The gray level publishing server judges whether the first gray level server c meets a second index verification rule or not, and the second index verification rule comprises log verification, service verification and database verification. If the first gray server c passes the log verification, the service verification, and the database verification, the first gray server c satisfies the second index verification rule.

And the gray level release server continuously updates the second test quantity, and repeatedly performs gray level release test on the first gray level server c until the updated second test quantity is equal to 5000.

The gray level release server judges whether the second test number is equal to 5000, if the second test number is equal to 5000, the gray level release server sends a gray level version deployment instruction to a third party server, and the third party server sends an installation package of the gray level version of the application product B to one server d (a server not deploying the gray level version) in the server cluster. The server d receives the installation package, installs the gray-scale version of the application product B through the installation package, and becomes the next gray-scale server after the installation is completed.

And the gray level release server performs environment verification. After the environment verification is passed, the gray level distribution server sends a transaction request to the server d based on the gray level distribution rule so as to perform gray level distribution test on the server d. The gray scale distribution test procedure of the server d is similar to that of the first server c, and will not be described here.

After the server d passes the gray level release test, the gray level release server repeats the gray level version deployment and gray level release test flow of the server d for one server (the server without deploying the gray level version) in the server cluster until all the servers in the server cluster pass the gray level release test.

Fig. 3 is a flow chart of a progressive gray scale release method according to another embodiment of the present invention, and as shown in fig. 3, the implementation flow of the progressive gray scale release method according to the embodiment of the present invention is as follows:

first, a transaction request is sent. The gray level distribution server sends a second test number of transaction requests to the gray level server. The gray server processes the received transaction requests and returns the start time of processing the transaction requests and the processing related information of processing each transaction request to the gray issuing server. Wherein the environment verification is performed before the second test number of transaction requests are transmitted, and the transmission of the transaction requests is performed after the environment verification is passed. The initial value is preset to be 50, the step value is 50, and the target value is 5000.

And a second step of judging whether to update the second test quantity. The gray level distribution server judges whether the gray level server meets the second index verification rule or not based on the processing related information, and if the gray level server meets the second index verification rule, the gray level server needs to update the second test quantity and enters the third step. If the gray server is judged not to meet the second index verification rule, the progressive gray release process is ended.

And thirdly, updating the second test quantity. The gray level release server updates the second test quantity, and the updated second test quantity is equal to the sum of the second test quantity before updating and the step value.

Fourth, it is judged whether or not the target value is equal to the target value. The gray level release server judges whether the second test quantity is equal to the target value, if the second test quantity is equal to the target value, the gray level server passes the gray level release test, and then the fifth step is entered; if the second test number is not equal to the target value, returning to the first step, and continuing to perform the gray scale release test on the gray scale server.

And fifthly, judging whether the preset number is equal to the preset number. The gray level release server counts the number N of servers for deploying gray level versions in the server cluster, and if the number N is equal to the preset number, the progressive gray level release process is finished. If the number N is smaller than the preset number, the sixth step is entered.

And sixthly, triggering gray version deployment. The gray level release server triggers the gray level version deployment of one server in the server cluster so that the one server becomes the next gray level server, the second test quantity is set to be equal to the initial value, and then the first step is carried out to carry out gray level release test on the next gray level server.

transmitting a third test number of transaction requests to the test object; wherein the third test number is equal to an initial value;

if the test object is judged to meet the third index verification rule, updating a third test quantity according to the step value, and sending a transaction request of the third test quantity to the test object until the third test quantity is equal to the target value; the third test quantity after each update is equal to the sum of the third test quantity before the update and the step value; the third index verification rule is preset;

and sending a transaction request to the test object so that the test object runs continuously for a preset time.

Specifically, the gray level distribution server may send a third test number of transaction requests to a test object, where the test object is the gray level server. The test object receives and processes the transaction request. The gray level issuing server monitors the condition that the test object processes the transaction request. Wherein the third test number is equal to the initial value. The initial value is preset and is set according to the test requirement, and the embodiment of the invention is not limited.

The test object may feed back processing related information for each transaction request to the gradation issue server. The gradation release server may determine whether the test object satisfies a third index authentication rule based on processing-related information of each transaction request. Wherein the processing-related information includes log information, service authentication information, database authentication information, and the like. The third index verification rule includes, but is not limited to, log verification, service verification, database verification, etc., and is set according to actual needs, which is not limited by the embodiment of the present invention. The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And verifying the keywords, namely verifying whether the keywords in the log information are correct or not, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. Service verification includes, but is not limited to, checking the running condition of the service and the response time of the service, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null.

And the gray level release server judges whether the test object meets the third index verification rule, and if the test object meets the third index verification rule, the gray level release server updates the third test quantity, namely calculates the sum of the third test quantity before updating and the step length value, and uses the sum as the updated third test quantity. And then sending a third test number of transaction requests to the test object, wherein the test object continues to process the received transaction requests, and the test object can feed back the processing related information of each transaction request to the gray level release server. The gray level release server re-judges whether the test object meets the third index verification rule after updating the third test quantity, continuously updates the third test quantity after judging that the test object meets the third index verification rule, repeats the process of sending the transaction request of the third test quantity to the test object, and judges whether the test object meets the third index verification rule after updating the third test quantity until the third test quantity is equal to the target value. In the process of carrying out gray level release test on the test object, the gray level release server gradually increases the transaction request processing amount of the test object based on the step value, and carries out gray level release test on a single gray level server. The step value and the target value are preset and set according to the test requirement, and the embodiment of the invention is not limited. It can be appreciated that if the test object does not meet the third index validation rule, the gray scale release test for the test object may be terminated and a failure of the gray scale release test may be prompted.

After the third test quantity is equal to the target value, the gray level issuing server continuously sends a transaction request to the test object, so that the test object continuously runs for a preset time. The preset time is set according to actual needs, for example, 24 hours, which is not limited in the embodiment of the present invention.

For example, the third index verification rule includes log verification including keyword verification and return result verification, service verification including running condition verification of the service and response time verification of the service, and database verification including expected value verification and acquisition data verification. The test object can meet the third index verification rule after passing log verification, service verification and database verification. The test object can pass log verification after passing key word verification and returning result verification. The test object can pass service verification after passing service run condition verification and service response time verification. The test object can pass the database verification after passing the expected value verification and the acquired data verification.

And if the third test quantity is equal to the target value and the test object meets the fourth index verification rule in the preset time of continuous operation, determining that the first gray server passes the gray release test.

Specifically, after the third test number is equal to the target value, the gray level distribution server may continuously send a transaction request to the first gray level server, and the first gray level server may feed back, to the gray level distribution server, information related to processing of each transaction request in the preset time during which the transaction request is continuously operated. If the gradation release server determines that the first gradation server satisfies the fourth index authentication rule and determines that the third test quantity is equal to the target value, it may be confirmed that the first gradation server passes the gradation release test.

The fourth index verification rule is preset, and includes, but is not limited to, log verification, service verification, database verification, batch operation condition verification and the like, and is set according to actual needs, and the embodiment of the invention is not limited. The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And verifying the keywords, namely verifying whether the keywords in the log information are correct or not, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. The service verification includes, but is not limited to, service running condition verification and service response time verification, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null. Batch job condition verification includes, but is not limited to, DBF batch verification, and is set according to actual needs, and embodiments of the present invention are not limited. The DBF batch verifies, namely verifies whether the batch processing result is correct.

For example, the fourth index verification rule includes log verification, service verification, database verification and batch job condition verification, the log verification includes keyword verification and return result verification, the service verification includes running condition verification of the service and response time verification of the service, the database verification includes expected value verification and acquisition data verification, and the batch job condition verification includes DBF batch verification. The test object can meet the fourth index verification rule after passing log verification, service verification, database verification and batch operation condition verification. The test object can pass log verification after passing key word verification and returning result verification. The test object can pass service verification after passing service run condition verification and service response time verification. The test object can pass the database verification after passing the expected value verification and the acquired data verification. The test object can pass the batch operation condition verification after passing the DBF batch verification.

After the first gray server e in the server cluster installs the gray version of the application product C, the gray publishing server performs environment verification. The environment verification includes but is not limited to configuration center verification, file verification, PAAS verification and service state verification, and is set according to actual needs, and the embodiment of the invention is not limited. Configuration center validation includes, but is not limited to, disconf profile content validation, apollo configuration instance number validation, CMC dynamic variable validation. File verification includes, but is not limited to, command verification, profile parameter verification, and in-container script verification. PAAS authentication includes, but is not limited to, deployment node authentication. Service state verification includes, but is not limited to, service provider verification. Service provider verification, including but not limited to determining whether the number of servers is correct, whether the registration status of the service provider is normal, whether the running status is smooth, and whether the service response time is within a preset time interval.

After the environment verification is passed, the gray level release server sends 50 transaction requests to a first gray level server e, and the first gray level server e processes the received transaction requests and returns processing related information for processing each transaction request to the gray level release server. The gray level publishing server judges whether the first gray level server e meets a third index verification rule or not, and the third index verification rule comprises log verification, service verification and database verification. If the first gray server e passes the log verification, the service verification and the database verification, the first gray server e satisfies the third index verification rule.

After the first gray server e meets the third index verification rule, the gray release server updates the third test quantity to be 50+50=100, then sends 100 transaction requests to the first gray server e, and the first gray server e processes the received transaction requests and returns processing related information for processing each transaction request to the gray release server. The gray level publishing server judges whether the first gray level server e meets a third index verification rule or not, and the third index verification rule comprises log verification, service verification and database verification. If the first gray server e passes the log verification, the service verification and the database verification, the first gray server e satisfies the third index verification rule.

And the gray level release server continuously updates the third test quantity, and repeatedly performs gray level release test on the first gray level server e until the updated third test quantity is equal to 5000. The gray level release server can continuously send a transaction request to the first gray level server e, the first gray level server e is maintained to continuously operate for 24 hours, the first gray level server e processes the received transaction request and returns processing related information for processing each transaction request after the third test quantity is equal to 5000 to the gray level release server. The gray level release server judges whether the third test quantity is equal to 5000 and whether the first gray level server e meets a fourth index verification rule, wherein the fourth index verification rule comprises log verification, service verification, database verification and batch operation condition verification. If the first greyscale server e passes log verification, service verification, database verification, and batch job condition verification, and the third test number is equal to 5000, the first greyscale server e passes the greyscale release test.

The gray level release server sends a gray level version deployment instruction to a third party server, and the third party server sends an installation package of the gray level version of the application product C to one server f (a server not deploying the gray level version) in the server cluster. The server f receives the installation package, installs the gray-scale version of the application product C through the installation package, and becomes the next gray-scale server after the installation is completed.

And the gray level release server performs environment verification. After the environment verification is passed, the gray level distribution server sends a transaction request to the server f based on the gray level distribution rule so as to perform gray level distribution test on the server f. The gray scale release test procedure of the server f is similar to that of the first server e, and will not be described here.

After the server f passes the gray release test, the gray release server repeats the gray release deployment and the gray release test flow of the server f for one server (the server not deploying the gray release) in the server cluster until all the servers in the server cluster pass the gray release test.

Fig. 4 is a flow chart of a progressive gray scale release method according to still another embodiment of the present invention, as shown in fig. 4, the implementation flow of the progressive gray scale release method according to the embodiment of the present invention is as follows:

First, a transaction request is sent. The gray level distribution server sends a third test number of transaction requests to the gray level server. The gray server processes the received transaction requests and returns the start time of processing the transaction requests and the processing related information of processing each transaction request to the gray issuing server. Wherein the environment verification is performed before the third test number of transaction requests are transmitted, and the transmission of the transaction requests is performed after the environment verification is passed. The initial value is preset to be 50, the step value is 50, the target value is 5000, and the preset time is 24 hours.

And a second step of judging whether to update the third test quantity. The gray level distribution server judges whether the gray level server meets a third index verification rule based on the processing related information, and if the gray level server meets the third index verification rule, the gray level server needs to update a third test quantity and enters a third step. If the gray server is judged not to meet the third index verification rule, the progressive gray release process is ended.

And thirdly, updating the third test quantity. The gray level release server updates the third test quantity, and the updated third test quantity is equal to the sum of the third test quantity before updating and the step value.

Fourth, it is judged whether or not the target value is equal to the target value. The gray level release server judges whether the third test quantity is equal to the target value, and if the third test quantity is equal to the target value, the fifth step is entered; if the third test number is not equal to the target value, returning to the first step, and continuing to perform the gray scale release test on the gray scale server.

And fifthly, sending a transaction request. The gray level release server can continuously send the transaction request to the gray level server, so that the gray level server continuously operates for 24 hours, the gray level server processes the received transaction request and can feed back the processing related information of each transaction request continuously operating for 24 hours to the gray level release server.

And step six, judging whether the gray level release test is passed. The gray level distribution server judges whether the third test quantity is equal to the target value or not, judges whether the gray level server meets the fourth index verification rule or not based on the processing related information of each transaction request in the continuous operation for 24 hours, and if the third test quantity is equal to the target value and the gray level server meets the fourth index verification rule, determines that the gray level server passes the gray level distribution test and then enters the seventh step. If the third test quantity is equal to the target value, but the gray server does not meet the fourth index verification rule, the progressive gray distribution flow ends.

And eighth step, triggering gray version deployment. The gray level release server triggers the gray level version deployment of one server in the server cluster so that the one server becomes the next gray level server, sets the third test quantity equal to the initial value, and then enters the first step to perform gray level release test on the next gray level server.

transmitting a fourth test number of transaction requests to the test object; wherein the fourth test number is equal to an initial value;

if the test object is judged to meet the fifth index verification rule, updating the fourth test quantity according to the step value, and sending a transaction request of the fourth test quantity to the test object until the fourth test quantity is equal to the target value; if the step length statistic parameter is judged to be equal to integer times of the set number, a fourth test number transaction request is sent to the test object so that the test object runs continuously for a set time, after the test object is judged to be in continuous running for the set time and the fourth test number is smaller than the target value and meets a sixth index verification rule, the fourth test number is updated according to the step length value, and the fourth test number transaction request is sent to the test object;

The fourth test quantity after each update is equal to the sum of the fourth test quantity before the update and the step value; the fifth index verification rule is preset; the step length statistical parameter is added with 1 after the fourth test quantity is updated each time; the set number is a positive integer greater than or equal to 2.

Specifically, the gray level distribution server may send a fourth test number of transaction requests to a test object, where the test object is the gray level server. The test object receives and processes the transaction request. The gray level issuing server monitors the condition that the test object processes the transaction request. Wherein the fourth test number is equal to the initial value. The initial value is preset and is set according to the test requirement, and the embodiment of the invention is not limited.

The test object may feed back processing related information for each transaction request to the gradation issue server. The gradation release server may determine whether the test object satisfies a fifth index verification rule based on processing-related information of each transaction request. Wherein the processing-related information includes log information, service authentication information, database authentication information, and the like. The fifth index verification rule includes, but is not limited to, log verification, service verification, database verification, etc., and is set according to actual needs, and the embodiment of the invention is not limited. The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And verifying the keywords, namely verifying whether the keywords in the log information are correct or not, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. Service verification includes, but is not limited to, checking the running condition of the service and the response time of the service, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null.

And the gray level release server judges whether the test object meets the fifth index verification rule, if the test object meets the fifth index verification rule, the gray level release server updates the fourth test quantity and adds 1 to the step length statistical parameter, namely, calculates the sum of the fourth test quantity before updating and the step length value to be used as the fourth test quantity after updating. And then sending a fourth test number of transaction requests to the test object, wherein the test object continues to process the received transaction requests, and the test object can feed back the processing related information of each transaction request to the gray level release server. And the gray level release server judges whether the test object meets a fourth index verification rule after updating the fourth test quantity, and judges whether the step length statistical parameter is equal to integer multiple of the set quantity.

And after judging that the test object meets a fifth index verification rule and the step length statistical parameter is not equal to the integer multiple of the set number, continuously updating the fourth test number, adding 1 to the step length statistical parameter, repeating the process of sending the transaction request of the fourth test number to the test object, and judging whether the test object meets the fourth index verification rule after updating the fourth test number until the fourth test number is equal to a target value. After the test object is judged to meet the fifth index verification rule and the step length statistical parameter is equal to the integral multiple of the set number, updating the fourth test number, adding 1 to the step length statistical parameter, and sending a transaction request of the fourth test number to the test object so that the test object runs continuously for a set time, wherein the test object can feed back processing related information of each transaction request in the set time to the gray level release server. And if the gray level release server judges that the test object meets the sixth index verification rule and the fourth test quantity is smaller than the target value, updating the fourth test quantity according to the step value and sending a transaction request of the fourth test quantity to the test object. It can be appreciated that if the test object does not satisfy the fifth index verification rule or the sixth index verification rule, the gray scale release test for the test object may be terminated, and a failure of the gray scale release test may be prompted.

In the process of carrying out gray level release test on the test object, the gray level release server gradually increases the transaction request processing amount of the test object based on the step value, and carries out gray level release test on a single gray level server. And after each time the step length statistical parameter is equal to the integral multiple of the set number, enabling the test object to continuously run for a set time. The step value and the target value are preset and set according to the test requirement, and the embodiment of the invention is not limited. The sixth index verification rule is preset; the step size statistical parameter is added with 1 after the fourth test quantity is updated each time, and the initial value of the step size statistical parameter is 0. The set number is a positive integer greater than or equal to 2. The setting time is set according to actual needs, and the embodiment of the invention is not limited. The sixth index verification rule is preset, including but not limited to log verification, service verification, database verification, batch operation condition verification, and the like, and is set according to actual needs, and the embodiment of the invention is not limited.

For example, the fifth index verification rule includes log verification including keyword verification and return result verification, service verification including running condition verification of the service and response time verification of the service, and database verification including expected value verification and acquisition data verification. The test object can meet the third index verification rule after passing log verification, service verification and database verification. The test object can pass log verification after passing key word verification and returning result verification. The test object can pass service verification after passing service run condition verification and service response time verification. The test object can pass the database verification after passing the expected value verification and the acquired data verification.

The sixth index verification rule includes, but is not limited to, log verification, service verification, database verification, batch operation condition verification, and the like, and is set according to actual needs, and the embodiment of the invention is not limited. The log verification includes, but is not limited to, keyword verification and return result verification, and is set according to actual needs, and the embodiment of the invention is not limited. And verifying the keywords, namely verifying whether the keywords in the log information are correct or not, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And (3) returning a result to verify, namely judging whether the accuracy reaches 100% or not based on a log returning result in log information, and judging whether the error reporting is abnormal or not. The service verification includes, but is not limited to, service running condition verification and service response time verification, and is set according to actual needs, and the embodiment of the invention is not limited. Database verification is verification of accuracy of writing a table to a database, including, but not limited to, expected value verification and acquisition data verification. Expected value verification, i.e., verifying whether the expected field value is written correctly. And (4) taking data for verification, namely checking whether the necessary field is not null. Batch job condition verification includes, but is not limited to, DBF batch verification, and is set according to actual needs, and embodiments of the present invention are not limited. The DBF batch verifies, namely verifies whether the batch processing result is correct.

if the fourth test quantity is equal to the target value and the step length statistical parameter is not equal to the integer multiple of the set quantity, determining that the first gray server passes a gray release test; or alternatively

And if the fourth test quantity is equal to the target value, the step length statistical parameter is equal to the integral multiple of the set quantity, and the test object meets the sixth index verification rule in the set time of continuous operation, determining that the first gray server passes the gray release test.

Specifically, the gray scale distribution server determines whether the fourth test number is equal to a target value, determines whether the step size statistical parameter is equal to an integer multiple of the set number, and if it is determined whether the fourth test number is equal to the target value, and the step size statistical parameter is not equal to the integer multiple of the set number, it may be confirmed that the first gray scale server passes the gray scale distribution test.

After the gray level release server judges that the fourth test quantity is equal to the target value and the step length statistical parameter is equal to the integral multiple of the set quantity, the gray level release server sends the target value transaction requests to a first gray level server, so that the first gray level server continuously operates for the set time, and the first gray level server feeds back processing related information of each transaction request in the continuously operated set time to the gray level release server. And if the gray level distribution server judges that the fourth test quantity is equal to the target value, the step length statistical parameter is equal to the integral multiple of the set quantity and the first gray level server meets the sixth index verification rule, the first gray level server can be confirmed to pass the gray level distribution test.

Setting the initial value as 50, the step value as 50, the target value as 5000, the initial value of the step statistical parameter as 0, the number as 5 and the time as 3 hours.

After the first gray server g in the server cluster installs the gray version of the application product D, the gray publishing server performs environment verification. The environment verification includes but is not limited to configuration center verification, file verification, PAAS verification and service state verification, and is set according to actual needs, and the embodiment of the invention is not limited. Configuration center validation includes, but is not limited to, disconf profile content validation, apollo configuration instance number validation, CMC dynamic variable validation. File verification includes, but is not limited to, command verification, profile parameter verification, and in-container script verification. PAAS authentication includes, but is not limited to, deployment node authentication. Service state verification includes, but is not limited to, service provider verification. Service provider verification, including but not limited to determining whether the number of servers is correct, whether the registration status of the service provider is normal, whether the running status is smooth, and whether the service response time is within a preset time interval.

After the environment verification is passed, the gray level release server sends 50 transaction requests to a first gray level server g, and the first gray level server g processes the received transaction requests and returns processing related information for processing each transaction request to the gray level release server. The gray level publishing server judges whether the first gray level server g meets a fifth index verification rule, wherein the fifth index verification rule comprises log verification, service verification and database verification. If the first gray server g passes log verification, service verification, and database verification, the first gray server g satisfies the fifth index verification rule.

After the first gray server g meets the fifth index verification rule, the gray release server updates the fourth test quantity to be 50+50=100, adds 1 to the step length statistical parameter to obtain the calculated step length statistical parameter to be 0+1=1, then sends 100 transaction requests to the first gray server g, and the first gray server g processes the received transaction requests and returns processing related information for processing each transaction request to the gray release server. The gray level publishing server judges whether the first gray level server g meets a fifth index verification rule, wherein the fifth index verification rule comprises log verification, service verification and database verification. If the first gray server g passes log verification, service verification, and database verification, the first gray server g satisfies the fifth index verification rule.

And the gray level release server calculates the remainder of dividing the step length statistical parameter by the set number, wherein the remainder of dividing 1 by 5 is 1, and the step length statistical parameter is not equal to the integer multiple of the set number, then the fourth test number is continuously updated, and the process is repeated to carry out gray level release test on the first gray level server g. When the step length statistical parameter is 5, the remainder of dividing the step length statistical parameter 5 by the set number 5 is 0, the step length statistical parameter is equal to the integral multiple of the set number, the gray scale release server sends a fourth transaction request of the test number to the test object so that the test object runs continuously for 3 hours, and the test object can feed back the processing related information of each transaction request in the continuous running for 3 hours to the gray scale release server. And if the gray level release server judges that the test object meets the sixth index verification rule and the fourth test quantity is smaller than the target value, updating the fourth test quantity according to the step value and sending a transaction request of the fourth test quantity to the test object.

And the gray level release server continues to repeat the process to perform gray level release test on the first gray level server g until the updated fourth test quantity is equal to 5000. When the fourth test number is 5000, the step size statistical parameter is 49. The gray scale distribution server may determine that the fourth test number is equal to 5000 and that the step size statistical parameter 49 is not an integer multiple of the set number 5, then the first gray scale server g passes the gray scale distribution test.

The gray level release server sends a gray level version deployment instruction to a third party server, and the third party server sends an installation package of the gray level version of the application product D to one server h (a server not deploying the gray level version) in the server cluster. The server h receives the installation package, installs the gray-scale version of the application product D through the installation package, and becomes the next gray-scale server after the installation is completed.

And the gray level release server performs environment verification. After the environment verification is passed, the gray level distribution server sends a transaction request to the server h based on the gray level distribution rule so as to perform gray level distribution test on the server h. The gray level distribution test procedure of the server h is similar to that of the first server g, and will not be described here.

After the server h passes the gray release test, the gray release server repeats the gray release deployment and the gray release test flow of the server h for one server (the server not deploying the gray release) in the server cluster until all the servers in the server cluster pass the gray release test.

Fig. 5 is a flow chart of a progressive gray scale release method according to another embodiment of the present invention, and as shown in fig. 5, the implementation flow of the progressive gray scale release method according to the embodiment of the present invention is as follows:

First, a transaction request is sent. The gray level distribution server sends a fourth test number of transaction requests to the gray level server. The gray server processes the received transaction requests and returns the start time of processing the transaction requests and the processing related information of processing each transaction request to the gray issuing server. Wherein the environment verification is performed before the fourth test number of transaction requests are transmitted, and the transmission of the transaction requests is performed after the environment verification is passed. Setting the initial value as 50, the step value as 50, the target value as 5000, the initial value of the step statistical parameter as 0, the number as 5 and the time as 3 hours.

And step two, judging whether the fifth index verification rule is satisfied. The gray level distribution server judges whether the gray level server meets the fifth index verification rule or not based on the processing related information, and if the gray level server meets the fifth index verification rule, the fourth test quantity needs to be updated, and the third step is entered. If the gray server is judged not to meet the fifth index verification rule, the progressive gray release process is ended.

And thirdly, updating the fourth test quantity. The gray level release server updates the fourth test quantity, and the updated fourth test quantity is equal to the sum of the fourth test quantity before updating and the step value.

And step four, calculating step length statistical parameters. The gray level release server calculates the step length statistical parameter, and the calculated step length statistical parameter is equal to the step length statistical parameter before calculation plus 1.

And fifthly, judging whether the division can be completed or not. The gray level distribution server calculates the remainder of dividing the step length statistical parameter by the set number 5, wherein the remainder is not 0, and then the step length statistical parameter cannot be divided by the set number, and the step length statistical parameter is not equal to the integer multiple of the set number, and the sixth step is carried out; and if the remainder is 0, the step length statistical parameter can divide the set number by a whole number, and the step length statistical parameter is equal to the integral multiple of the set number to enter a seventh step.

And sixthly, judging whether the target value is equal to the target value. The gradation release server judges whether the fourth test quantity is equal to the target value. If the fourth test quantity is equal to the target value, a twelfth step is entered; if the fourth test number is not equal to the target value, returning to the first step, and continuing to perform the gray scale release test on the gray scale server.

Seventh, a transaction request is sent. The gray level release server sends a fourth test number of transaction requests to the gray level server so that the gray level server runs continuously for 3 hours, and the gray level server can feed back the processing related information of each transaction request in the continuous running for 3 hours to the gray level release server.

And eighth step, judging whether the sixth index verification rule is satisfied. The gradation release server judges whether the gradation server satisfies the sixth index authentication rule based on the processing-related information returned from the gradation server, and if the gradation server satisfies the sixth index authentication rule, proceeds to the ninth step. If the gray server is judged not to meet the sixth index verification rule, the progressive gray distribution flow is ended.

And ninth, judging whether the target value is smaller than the target value. The gradation release server judges whether the fourth test quantity is smaller than the target value. If the fourth test quantity is less than the target value, a tenth step is entered; if the fourth test number is equal to the target value, a twelfth step is entered.

And a tenth step of updating the fourth test quantity. The gray level release server updates the fourth test quantity, and the updated fourth test quantity is equal to the sum of the fourth test quantity before updating and the step value.

And eleventh step, calculating step length statistical parameters. The gray level distribution server calculates the step length statistic parameters, wherein the calculated step length statistic parameters are equal to the step length statistic parameters before calculation plus 1, and then the step length distribution server returns to the first step.

And twelfth, judging whether the preset number is equal to the preset number. The gray level release server counts the number N of servers for deploying gray level versions in the server cluster, and if the number N is equal to the preset number, the progressive gray level release process is finished. If the number N is smaller than the preset number, a thirteenth step is entered.

And thirteenth step, triggering gray version deployment. The gray level release server triggers the gray level version deployment of one server in the server cluster so that the one server becomes the next gray level server, the fourth test quantity is set to be equal to an initial value, the initial value of the step length statistical parameter is equal to 0, and then the first step is entered to carry out gray level release test on the next gray level server.

Fig. 6 is a schematic structural diagram of a progressive gray scale publishing device according to an embodiment of the present invention, as shown in fig. 6, the progressive gray scale publishing device according to an embodiment of the present invention includes a sending module 601, a triggering module 602, and a testing module 603, where:

the sending module 601 is configured to send a transaction request to a first gray server based on a gray distribution rule, so as to perform a gray distribution test on the first gray server; wherein the gray level distribution rule is preset; the triggering module 602 is configured to trigger deployment of a gray version of one server in the server cluster after judging that the first gray server passes the gray release test, so that the one server becomes a next gray server; the test module 603 is configured to send a transaction request to the next gray server based on the gray distribution rule, so as to perform a gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

Specifically, when the gray level distribution of the application product is performed, the sending module 601 may send a transaction request to a first gray level server based on a gray level distribution rule, where the first gray level server receives the transaction request sent by the sending module 601 and processes the transaction request to implement a gray level distribution test. The sending module 601 may monitor the situation that the first gray server processes the transaction request. Wherein the gray level distribution rule is preset. The first greyscale server has installed a greyscale version of the application product.

The triggering module 602 may determine whether the first gray server passes the gray release test according to the processing of the transaction request by the first gray server, if the first gray server passes the gray release test, the gray version of the application product may be promoted, and then the triggering module 602 may trigger the gray version deployment of one server in the server cluster, where the one server becomes the next gray server after the gray version is installed. If the first gray server fails the gray release test, it indicates that the gray version of the application product has a problem, and improvement is needed.

After the one server becomes the next gray server, the test module 603 may send a transaction request to the next gray server based on the gray distribution rule, where the next gray server receives the transaction request sent by the test module 603 and processes the transaction request to implement the gray distribution test. The test module 603 may monitor the situation that the next gray server processes the transaction request, determine whether the next gray server passes the gray release test, after the next gray server passes the gray release test, continuously trigger the deployment of the gray version of one server in the server cluster to obtain the next gray server, and repeatedly send the transaction request to the next gray server based on the gray release rule, so as to perform the gray release test on the next gray server until the number of gray servers passing the gray release test in the server cluster is equal to the preset number. That is, the test module 603 triggers the deployment of the gray scale version of one server in the server cluster one by one and performs the gray scale release test. The gray level distribution test process of each gray level server is similar. The preset number may be equal to the number of all servers in the server cluster, or may be equal to the number of part of servers in the server cluster, which is set according to actual needs, and the embodiment of the present invention is not limited.

According to the progressive gray level release device provided by the embodiment of the invention, a transaction request can be sent to the first gray level server based on the gray level release rule, so that gray level release test is carried out on the first gray level server, after the first gray level server is judged to pass through the gray level release test, gray level version deployment of one server in the server cluster is triggered, so that one server becomes the next gray level server, gray level release test is carried out on the next gray level server based on the gray level release rule until the preset number of servers in the server cluster pass through the gray level release test, gray level version of an application product can be fully tested through progressive gray level release, and the reliability of gray level release is improved. Because the gray scale ratio is not required to be set, the man-made subjectivity in the gray scale release process is reduced, and the production risk caused by the overlarge gray scale test point range and the incomplete test caused by the overlarge recovery test point range are avoided. The method has the advantages that a part of clients are not required to experience a new version, gray release due to feedback of the clients in the prior art can be avoided, and in a gray period, the gray version program cannot be guaranteed to obtain sufficient effective call because the gray clients do not initiate transaction requests, so that gray test time is required to be prolonged, new product popularization is influenced, and meanwhile waste of server resources is avoided.

The embodiment of the apparatus provided in the embodiment of the present invention may be specifically used to execute the processing flow of each method embodiment, and the functions thereof are not described herein again, and may refer to the detailed description of the method embodiments.

The existing gray level release technology needs to manually define the gray level ratio, and the problem that the defined gray level range is overlarge is sometimes caused by experience judgment, so that the gray level content release risk is increased; sometimes, the problem that the gray scale demarcation range is too small can occur, so that a sufficient amount of effective gray scale samples cannot be obtained, and the gray scale effect is affected. In addition, the number of gray scale cluster servers is controlled to control the gray scale release in most of the existing gray scale release, so that the granularity of the gray scale release is too coarse, the gray scale strategy lacks flexibility, and the management of the whole gray scale release process is not facilitated.

Aiming at the defects in the existing gray level release technology, the embodiment of the invention provides a progressive gray level release method. The task of setting the gray scale ratio in the gray scale release process is omitted, meanwhile, the minimum unit of gray scale release is thinned, the flexibility and the effectiveness of a gray scale release strategy are enhanced, and meanwhile, the risk in the gray scale release process is better controlled. The automatic release method is adopted, and has outstanding effect in replacing manual work. The method is particularly suitable for the release of high-risk online products such as accounts, funds and the like of banks, financial institutions and Internet financial companies.

It should be noted that, the progressive gray scale release method and the device provided by the embodiment of the invention can be used in the financial field and also can be used in any technical field except the financial field, and the application field of the progressive gray scale release method and the device is not limited by the embodiment of the invention.

Fig. 7 is a schematic physical structure of an electronic device according to an embodiment of the present invention, as shown in fig. 7, the electronic device may include: a processor (processor) 701, a communication interface (Communications Interface) 702, a memory (memory) 703 and a communication bus 704, wherein the processor 701, the communication interface 702 and the memory 703 communicate with each other through the communication bus 704. The processor 701 may call logic instructions in the memory 703 to perform the following method: transmitting a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset; if the first gray server is judged to pass the gray release test, triggering the gray version deployment of one server in the server cluster so that the one server becomes the next gray server; and sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

Further, the logic instructions in the memory 703 may be implemented in the form of software functional units and may be stored in a computer readable storage medium when sold or used as a stand alone product. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, are capable of performing the methods provided by the above-described method embodiments, for example comprising: transmitting a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset; if the first gray server is judged to pass the gray release test, triggering the gray version deployment of one server in the server cluster so that the one server becomes the next gray server; and sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

The present embodiment provides a computer-readable storage medium storing a computer program that causes the computer to execute the methods provided by the above-described method embodiments, for example, including: transmitting a transaction request to a first gray server based on a gray release rule so as to perform gray release test on the first gray server; wherein the gray level distribution rule is preset; if the first gray server is judged to pass the gray release test, triggering the gray version deployment of one server in the server cluster so that the one server becomes the next gray server; and sending a transaction request to the next gray server based on the gray distribution rule so as to perform gray distribution test on the next gray server until a preset number of servers in the server cluster pass the gray distribution test.

It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Claims

1. A progressive gray scale distribution method, comprising:

2. The method of claim 1, wherein the gray scale distribution rule comprises:

if the test time is larger than or equal to the time parameter and the test object meets the first index verification rule, updating the first test quantity and resetting the test time according to the step value, and sending a transaction request of the first test quantity to the test object until the first test quantity is equal to the target value; the first test quantity after each update is equal to the sum of the first test quantity before the update and the step value; the first index verification rule is preset.

3. The method of claim 2, wherein if the first gray server is determined to pass the gray distribution test comprises:

and if the first test quantity is judged to be equal to the target value, the test time is equal to the time parameter, and the first gray server meets the first index verification rule, determining that the first gray server passes the gray release test.

4. The method of claim 1, wherein the gray scale distribution rule comprises:

5. The method of claim 4, wherein if the first gray server is determined to pass the gray distribution test comprises:

6. The method of claim 1, wherein the gray scale distribution rule comprises:

if the test object is judged to meet the third index verification rule, updating the third test quantity according to the step value, and sending a transaction request of the third test quantity to the test object until the third test quantity is equal to the target value; the third test quantity after each update is equal to the sum of the third test quantity before the update and the step value; the third index verification rule is preset;

7. The method of claim 6, wherein if the first gray server is determined to pass the gray distribution test comprises:

and if the third test quantity is equal to the target value and the test object meets a fourth index verification rule in the preset time of continuous operation, determining that the first gray server passes the gray release test.

8. The method of claim 1, wherein the gray scale distribution rule comprises:

The fourth test quantity after each update is equal to the sum of the fourth test quantity before the update and the step value; the fifth index verification rule and the sixth index verification rule are preset; the step length statistical parameter is added with 1 after the fourth test quantity is updated each time; the set number is a positive integer greater than or equal to 2.

9. The method of claim 8, wherein if the first gray server is determined to pass the gray distribution test comprises:

if the fourth test quantity is equal to the target value and the step length statistical parameter is not equal to the integer multiple of the set quantity, determining that the first gray server passes a gray release test;

10. A progressive gray scale distribution device, comprising:

11. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any one of claims 1 to 9 when the computer program is executed by the processor.

12. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 9.