CN113010418A - Progressive gray scale publishing method and device - Google Patents

Progressive gray scale publishing method and device Download PDF

Info

Publication number
CN113010418A
CN113010418A CN202110239593.7A CN202110239593A CN113010418A CN 113010418 A CN113010418 A CN 113010418A CN 202110239593 A CN202110239593 A CN 202110239593A CN 113010418 A CN113010418 A CN 113010418A
Authority
CN
China
Prior art keywords
gray scale
test
server
release
verification
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110239593.7A
Other languages
Chinese (zh)
Other versions
CN113010418B (en
Inventor
宋海涵
魏雪
王婧
张丹阳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202110239593.7A priority Critical patent/CN113010418B/en
Publication of CN113010418A publication Critical patent/CN113010418A/en
Application granted granted Critical
Publication of CN113010418B publication Critical patent/CN113010418B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

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

Description

Progressive gray scale 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, a variety of internet application products are emerging. In order to control potential operation risks and improve the experience of a client, a gray scale release method is often adopted when a new version of an application product is released, so that most of the clients continue to use the old version of the application product, and a small number of the clients experience the new version of the application product.
In the prior art, when gray scale publishing of an application product is performed, a gray scale publishing strategy needs to be set manually, and then the gray scale publishing strategy is executed manually or automatically. The gray release of the application product by the gray release strategy has the following problems: (1) the core of the gray scale issuing strategy is to determine the gray scale ratio, the determination of the gray scale ratio is subjective, the selected gray scale ratio is based on the past experience, and the problems that the production risk is increased due to the fact that the range of the gray scale test point is too large, or the gray scale effect is affected due to the fact that the range of the gray scale test point is too small may exist. (2) The new version is comprehensively popularized through one to two gray scale test points, so that a gray scale mechanism cannot well play a role. And if the gray scale test points are selected for multiple times, the workload is greatly increased, and the manual execution of the gray scale strategy is not facilitated. (3) When the gray scale division is carried out, a part of customers experience a new version by taking the customers as a division standard. Because the behavior of the client is subjective, if the client does not initiate a transaction request in the gray release period, it cannot be guaranteed that the gray version program is effectively called in sufficient quantity, so that the gray test point time needs to be prolonged, the popularization of a new product is affected, and meanwhile, server resources are wasted.
Disclosure of Invention
In view of the problems in the prior art, embodiments of the present invention provide a method and an apparatus for progressive grayscale release, which can at least partially solve the problems in the prior art.
In one aspect, the present invention provides a progressive grayscale publishing method, including:
sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset;
if the first gray scale server passes the gray scale release test, triggering the deployment of the gray scale version of one server in the server cluster so as to enable the one server to become the next gray scale server;
and sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
In another aspect, the present invention provides a progressive gradation issuing apparatus, including:
the sending module is used for sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset;
the triggering module is used for triggering the deployment of the gray scale version of one server in the server cluster after judging that the first gray scale server passes the gray scale release test, so that the one server becomes the next gray scale server;
and the test module is used for sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
In another aspect, the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the steps of the progressive grayscale publishing method according to any of the above embodiments.
In yet another aspect, the present invention provides a computer-readable storage medium, on which a computer program is stored, the computer program, when being executed by a processor, implementing the steps of the progressive grayscale publishing method according to any one of the above embodiments.
The progressive gray scale release method and the device provided by the embodiment of the invention can send a transaction request to the first gray scale server based on the gray scale release rule so as to perform gray scale release test on the first gray scale server, trigger the deployment of the gray scale version of one server in the server cluster after judging and knowing that the first gray scale server passes the gray scale release test, enable the one server to become the next gray scale server, perform the gray scale release test on the next gray scale server based on the gray scale release rule until a preset number of servers in the server cluster pass the gray scale release test, perform gray scale release progressively, can fully test the gray scale version of an application product, and improve the reliability of the gray scale release.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts. In the drawings:
fig. 1 is a schematic flowchart of a progressive grayscale publishing method according to an embodiment of the present invention.
Fig. 2 is a schematic flowchart of a progressive grayscale publishing method according to another embodiment of the present invention.
Fig. 3 is a flowchart illustrating a progressive grayscale publishing method according to another embodiment of the present invention.
Fig. 4 is a flowchart illustrating a progressive grayscale publishing method according to still another embodiment of the present invention.
Fig. 5 is a flowchart illustrating a progressive grayscale publishing method according to still another embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a progressive grayscale issuing device according to an embodiment of the present invention.
Fig. 7 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention are further described in detail below with reference to the accompanying drawings. The exemplary embodiments and descriptions of the present invention are provided to explain the present invention, but not to limit the present invention. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
In order to facilitate understanding of the technical solutions provided in the present application, the following first describes relevant contents of the technical solutions in the present application. According to the progressive gray scale release method provided by the embodiment of the invention, the transaction request is used as a standard of gray scale division, one part of the transaction request is sent to the gray scale server through a routing mechanism, and the other part of the transaction request is sent to the normal server, so that the gray scale server is ensured to be effectively called. The gray scale version installation method adopts the sequential installation of servers one by one. After the gray scale version is installed on the first server, the real-time processing amount of the first gray scale server to the transaction request is gradually increased according to the gray scale release rule, and after the real-time processing amount reaches a target value and passes the gray scale release test, the gray scale version is installed on the second server. And the second gray scale server repeats the gray scale release test logic of the first gray scale server, and when the real-time processing capacity of the transaction request reaches a target value and passes the gray scale release test, a gray scale version is installed for the third gray scale server, and so on, thereby realizing the gradual gray scale release of the whole server cluster.
The implementation process of the progressive grayscale publishing method provided by the embodiment of the invention is described below with a grayscale publishing server as an execution subject. It can be understood that the implementation subject of the progressive grayscale publishing method provided by the embodiment of the present invention includes, but is not limited to, a grayscale publishing server.
Fig. 1 is a schematic flow diagram of a progressive grayscale publishing method according to an embodiment of the present invention, and as shown in fig. 1, the progressive grayscale publishing method according to the embodiment of the present invention includes:
s101, sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset;
specifically, when gray scale publishing of an application product is performed, the gray scale publishing server may send a transaction request to a first gray scale server based on a gray scale publishing rule, and the first gray scale server may receive the transaction request sent by the gray scale publishing server and process the transaction request to implement a gray scale publishing test. The gray scale issuing server can monitor the condition that the first gray scale server processes the transaction request. Wherein the gray scale release rule is preset. The first grayscale server has installed a grayscale version of an application product.
S102, if the fact that the first gray scale server passes a gray scale release test is judged and known, triggering the deployment of a gray scale version of one server in a server cluster to enable the one server to become a next gray scale server;
specifically, the grayscale issuing server may determine whether the first grayscale server passes a grayscale issuing test according to a processing condition of the first grayscale server on the transaction request, and if the first grayscale server passes the grayscale issuing test, it indicates that the grayscale version of the application product can be popularized, the grayscale issuing server may trigger deployment of the grayscale version of one server in the server cluster, and the one server becomes a next grayscale server after the grayscale version is installed. If the first grayscale server fails to pass the grayscale release test, it indicates that the grayscale version of the application product has a problem and needs to be improved.
For example, the installation package of the grayscale version of the application product is stored on a third-party server, and the grayscale release server sends a grayscale version deployment instruction to the third-party server, so that the third-party server sends the installation package of the grayscale version of the application product to the server. The server receives the installation package of the gray scale version and installs the gray scale version to become the next gray scale server.
For example, the installation package of the grayscale version of the application product may be stored in the grayscale distribution server, and the grayscale distribution server transmits the installation package of the grayscale version of the application product to the server that installs the grayscale version and becomes the next grayscale server.
S103, sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
Specifically, after the server becomes a next gray scale server, the gray scale distribution server may send a transaction request to the next gray scale server based on a gray scale distribution rule, and the next gray scale server may receive the transaction request sent by the gray scale distribution server and process the transaction request to implement a gray scale distribution test. The gray scale release server can monitor the condition that the next gray scale server processes the transaction request, judge whether the next gray scale server passes the gray scale release test, continue to trigger the deployment of the gray scale version of one server in the server cluster after the next gray scale server passes the gray scale release test, obtain the next gray scale server, repeat the step of sending the transaction request to the next gray scale server based on the gray scale release rule to perform the gray scale release test on the next gray scale server until the number of the gray scale servers passing the gray scale release test in the server cluster is equal to the preset number. That is, the grayscale issuing server will trigger the grayscale version deployment of one server in the server cluster one by one and perform the grayscale issuing test. The process of the gray distribution test of each gray 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 some servers in the server cluster, and is set according to actual needs, which is not limited in the embodiment of the present invention.
The progressive gray scale release method provided by the embodiment of the invention can send a transaction request to the first gray scale server based on the gray scale release rule so as to perform gray scale release test on the first gray scale server, trigger the deployment of the gray scale version of one server in the server cluster after judging and knowing that the first gray scale server passes the gray scale release test, so that the one server becomes the next gray scale server, perform the gray scale release test on the next gray scale server based on the gray scale release rule until a preset number of servers in the server cluster pass the gray scale release test, and perform the gray scale release progressively, so that the gray scale version of an application product can be fully tested, and the reliability of the gray scale release is improved. Because the gray scale ratio is not required to be set, the artificial subjectivity in the gray scale releasing 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 do not need to be selected to experience a new version, gray scale release depending on feedback of the clients in the prior art can be avoided, and the gray scale version program cannot be guaranteed to be effectively called in sufficient quantity due to the fact that the gray scale clients do not initiate transaction requests in a gray scale period, so that gray scale test point time needs to be prolonged, popularization of new products is affected, and waste of server resources is avoided.
On the basis of the foregoing embodiments, further, the gray scale distribution rule includes:
sending a first test quantity of transaction requests to a test object; wherein the first test number is equal to an initial value;
if the testing time is judged to be more than or equal to the time parameter and the testing object meets the first index verification rule, updating the first testing quantity and resetting the testing time according to the step value, and sending transaction requests of the first testing quantity to the testing object until the first testing quantity is equal to the target value; wherein, 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 validation rule is preset.
Specifically, the gray scale issuing server sends a first test quantity of transaction requests to a test object, and the test object is a gray scale server. The test object receives the transaction request and processes the transaction request. The gray release 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 the processing-related information for each transaction request to the gray-scale distribution server. The gray scale 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 satisfies the first index validation rule based on the processing-related information of each transaction request. Wherein the test time is obtained by subtracting the 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 validation rule is preset, and includes but is not limited to log validation, service validation, database validation, batch job condition validation 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 returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, the service operation condition verification and the service response time verification, and is set according to actual needs, and the embodiment of the present invention is not limited. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null. The batch job condition verification includes but is not limited to DBF batch verification, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. And DBF batch verification, namely verifying whether the batch processing result is correct.
And the gray release server compares the test time with a time parameter, if the test time is greater than or equal to the time parameter and the test object meets the first index verification rule, the gray release server updates the first test quantity and resets the test time, namely, the sum of the first test quantity before updating and the step value is calculated as the updated first test quantity, and the test time is reset. And sending transaction requests with a first test quantity 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 processed first transaction request after the first test quantity is updated and the processing related information of each transaction request to the gray scale issuing server. The gray release server judges whether the test time is greater than or equal to the time parameter again and whether the test object meets the first index verification rule after the first test quantity is updated, after the test time is greater than or equal to the time parameter and the test object meets the first index verification rule are judged, the first test quantity and the test time are continuously updated, the process of sending the transaction requests of the first test quantity to the test object is repeated, 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 the first test quantity is updated is judged, and the process is repeated until the first test quantity is equal to the target value. That is, in the process of performing the gray scale issuing test on the test object, the gray scale issuing server gradually increases the transaction request processing amount of the test object based on the step value, and performs the gray scale issuing test on a single gray scale server progressively. The time parameter, the step value, and the target value are preset and set according to a test requirement, which is not limited in the embodiments of the present invention. It is understood that, if the test object does not satisfy the first criterion verification rule after the test time is greater than or equal to the time parameter, the gray release test on the test object may be terminated and failure of the gray release test is prompted.
The time parameter is a time interval from the previous gray scale expansion to the next gray scale expansion which is set manually, and the setting of the time parameter has the following functions: firstly, enough time is reserved for the calculation of test time and the acquisition of processing related information such as log information, service information, batch job information and the like; secondly, reserving the trial operation time of the gray release content for exposing the loophole and the risk of the gray version; thirdly, the risk caused by the fact that the gray scale expansion speed is too fast due to the fact that no time control exists is avoided.
For example, the first index validation rule includes log validation, service validation, database validation, and batch job condition validation, the log validation including keyword validation and return result validation, the service validation including service run condition validation and service response time validation, the database validation including expected value validation and acquired data validation, and the batch job condition validation including DBF batch validation. The test object can meet the first index validation rule only after passing log validation, service validation, database validation and batch job condition validation. The test object can pass log verification after passing key word verification and return result verification. The test object can pass the service verification after passing the service operation condition verification and the service response time verification. The test object can pass the database verification after passing the expected value verification and the acquisition 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, the determining that the first grayscale server passes the grayscale release test includes:
and if the first test quantity is judged to be equal to the target value, the test time is greater than or equal to the time parameter, and the first gray scale server meets the first index verification rule, determining that the first gray scale server passes the gray scale release test.
Specifically, the first test quantity is equal to a target value, and then, the gray scale issuing server continues to send the target value transaction requests to the first gray scale server, the first gray scale server continues to process the received transaction requests, and the first gray scale server may feed back, to the gray scale issuing server, start time of the first transaction request after the processed first test quantity is equal to the target value and processing related information of each transaction request. And recalculating the test time by the gray scale release server, 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, determining that the first gray scale server passes the gray scale release test.
The implementation process of the progressive grayscale publishing method provided by the embodiment of the present invention is described as a specific embodiment.
The initial value is set to 1000, the step value is 1000, the target value is 20000, and the time parameter is 6 hours.
After the gray scale version of the application product A is installed on the first gray scale server a in the server cluster, the gray scale release server performs environment verification. The environment verification includes, but is not limited to, configuration center verification, document verification, PAAS verification, and service status verification, and is set according to actual needs, which is not limited in the embodiments of the present invention. Configuration center verification includes, but is not limited to, Disconf configuration file content verification, Apollo configuration instance number verification, CMC dynamic variable verification. Document verification includes, but is not limited to, command verification, configuration file parameter verification, and script verification within a container. PAAS authentication includes, but is not limited to, deployment node authentication. Service status verification includes, but is not limited to, service provider verification. And the service provider verifies, including but not limited to judging whether the number of the servers is correct, whether the registration state of the service provider is normal, whether the running state is stable, and whether the service response time is within a preset time interval.
After the environment verification is passed, the gray scale issuing server sends 1000 transaction requests to a first gray scale server a, and the first gray scale server a processes the received transaction requests and returns the start time for processing the first transaction request and processing related information for processing each transaction request to the gray scale issuing server. And the gray scale release server calculates the test time based on the current time and the start time, and if the test time is more than or equal to 6 hours, whether the first gray scale server a meets a first index verification rule is continuously judged 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 grayscale server a passes log verification, service verification, database verification and batch job condition verification, the first grayscale server a satisfies the first index verification rule.
After the test time is greater than or equal to 6 hours and the first gray scale server a meets the first index verification rule, the gray scale issuing server updates the first test quantity to be 1000+1000 to 2000, the test time is set to 0, 2000 transaction requests are sent to the first gray scale server a, the first gray scale server a processes the received transaction requests and returns the start time for processing the first transaction request after the first test quantity is updated and processing related information for processing each transaction request to the gray scale issuing server. And the gray scale release server recalculates the test time based on the current time and the start time, and if the test time is more than or equal to 6 hours, continuously judges whether the first gray scale server a meets a first index verification rule, wherein the first index verification rule comprises service verification, database verification and batch operation condition verification. And if the first grayscale server a passes the service verification, the database verification and the batch job condition verification, the first grayscale server a meets the first index verification rule.
And the gray release server continuously updates the first test quantity, and repeats the process to perform the gray release test on the first gray server a until the updated first test quantity is equal to 20000. The gray scale issuing server sends 20000 transaction requests to the first gray scale server a, and the first gray scale server a processes the received transaction requests and returns the start time of processing the first transaction request after the first test quantity is equal to 20000 and processing related information of processing each transaction request to the gray scale issuing server. And the gray scale issuing server recalculates the testing time based on the current time and the starting time, and if the testing time is more than or equal to 6 hours, continuously judges whether the first gray scale server a meets the first index verification rule. If the first grayscale server a passes the service verification, the database verification and the batch job condition verification, the first grayscale server a passes the grayscale release test.
The gray scale release server sends a gray scale version deployment instruction to a third-party server, and the third-party server sends an installation package of the gray scale version of the application product A to a server b (a server which does not deploy the gray scale version) in the server cluster. The server b receives the installation package, and installs the grayscale version of the application product a through the installation package, and after the installation is completed, the server b becomes the next grayscale server.
And the gray scale release server performs environment verification. After the environment verification is passed, the gray release server sends a transaction request to the server b based on the gray release rule so as to perform a gray release test on the server b. The gray release test process of the server b is similar to the gray release test process of the first server a, and details are not repeated here.
After the server b passes the gray release test, the gray release server repeats the gray version deployment and gray release test process for one server (server without the gray version deployment) in the server cluster until all servers in the server cluster pass the gray release test.
The embodiment of the invention is particularly suitable for the condition that the transaction request is sufficient, and can carry out the gray release test on the gray server by using the sufficient transaction request so as to find the defect of the gray version.
Fig. 2 is a schematic flow chart of a progressive grayscale publishing method according to another embodiment of the present invention, and as shown in fig. 2, an implementation flow of the progressive grayscale publishing method according to the embodiment of the present invention is as follows:
in a first step, a transaction request is sent. The gray scale issuing server sends a first test quantity transaction request to the gray scale server. The gray scale server processes the received transaction requests and returns the start time for processing the transaction requests and the processing related information for processing each transaction request to the gray scale issuing server. And performing environment verification before sending the first test quantity of transaction requests, and sending the transaction requests after the environment verification is passed. The initial value is set to 1000, the step value is 1000, the target value is 20000, and the time parameter is 6 hours.
And secondly, judging whether to update the first test quantity. And the gray scale issuing server calculates the testing time based on the current time and the starting time, if the testing time is more than or equal to 6 hours, whether the gray scale server meets the first index verification rule is continuously judged based on the processing related information, if the gray scale server meets the first index verification rule, the first testing number needs to be updated, and the third step is carried out. If the test time is less than 6 hours, the gray release server continues to send transaction requests to the gray server. And if the testing time is more than or equal to 6 hours and the gray server is judged not to meet the first index verification rule, ending the gradual gray release process.
And thirdly, updating the first test quantity. And the gray release server updates the first test quantity and sets the test time to be 0, wherein the updated first test quantity is equal to the sum of the first test quantity before updating and the step value.
And fourthly, judging whether the target value is equal to the target value or not. The gray 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 carried out; and if the first test quantity is not equal to the target value, returning to the first step, and continuing to perform the gray release test on the gray server.
And step five, sending a transaction request. The gray scale issuing server sends 20000 transaction requests to the gray scale service, and the gray scale server processes the received transaction requests and returns the starting time for processing 20000 transaction requests and the processing related information for processing each transaction request to the gray scale issuing server.
And sixthly, judging whether the gray release test is passed or not. And the gray release server judges whether the first test quantity is equal to the target value, whether the test time is equal to the time parameter and whether the gray server meets the 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 server meets the first index verification rule, the gray release server passes the gray release test, the test time is reset to be 0, and then the seventh step is carried out. If the first test quantity is equal to the target value, 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 seventhly, judging whether the quantity is equal to the preset quantity or not. And counting the number N of the servers deploying the gray versions in the server cluster by the gray release server, and ending the gradual gray release process if the number N is equal to the preset number. And if the number N is less than the preset number, entering an eighth step.
And step eight, triggering gray-scale version deployment. The gray release server triggers the deployment of the gray version of one server in the server cluster so as to enable the one server to become the next gray server, sets the first test quantity equal to the initial value, and then enters the first step to perform the gray release test on the next gray server.
On the basis of the foregoing embodiments, further, the gray scale distribution rule includes:
sending a second test quantity 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 a 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 quantity after each update is equal to the sum of the second test quantity before the update and the step value; the second index validation rule is preset.
Specifically, the gray scale issuing server sends a second test quantity of transaction requests to a test object, and the test object is a gray scale server. The test object receives the transaction request and processes the transaction request. The gray release 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 information related to processing of each transaction request to the gray-scale distribution server. The gradation issuance server may determine whether the test object satisfies the second criterion verification rule based on the processing-related information of each transaction request. Wherein the processing related information comprises log information, service verification information, database verification information and the like. The second index validation rule includes, but is not limited to, log validation, service validation, database validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to actual experience, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, checking the service operation condition and the service response time, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null.
And the gray scale issuing 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 scale issuing server updates the second test quantity, namely, the sum of the second test quantity before updating and the step value is calculated as the updated second test quantity. And sending a second test quantity 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 scale release server. And the gray scale issuing server judges whether the test object meets the second index verification rule after the second test quantity is updated again, continues to update the second test quantity after the test object meets the second index verification rule, repeats the process of sending the transaction requests of the second test quantity to the test object and judging whether the test object meets the second index verification rule after the second test quantity is updated until the second test quantity is equal to the target value. That is, in the process of performing the gray scale issuing test on the test object, the gray scale issuing server gradually increases the transaction request processing amount of the test object based on the step value, and performs the gray scale issuing test on a single gray scale server progressively. The step value and the target value are preset and set according to a test requirement, which is not limited in the embodiments of the present invention. It is understood that if the test object does not satisfy the second index verification rule, the gray release test for the test object may be terminated and a failure of the gray release test is prompted.
For example, the second index validation rule includes log validation including keyword validation and return result validation, service validation including service operation condition validation and service response time validation, and database validation including expected value validation and acquired data validation. And 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 return result verification. The test object can pass the service verification after passing the service operation condition verification and the service response time verification. The test object can pass the database verification after passing the expected value verification and the acquisition data verification.
On the basis of the foregoing embodiments, further, the determining that the first grayscale server passes the grayscale release test includes:
and if the second test quantity is judged to be equal to the target value, determining that the first gray scale server passes the gray scale issuing test.
Specifically, the grayscale issuing server determines whether the second test number is equal to a target value, and if the second test number is equal to the target value, it can be confirmed that the first grayscale server passes the grayscale issuing test.
The implementation process of the progressive gray scale distribution method provided by the embodiment of the invention is further described in a specific embodiment.
The initial value was set to 50, the step value to 50, and the target value to 5000.
And after the first gray scale server c in the server cluster finishes the installation of the gray scale version of the application product B, the gray scale release server performs environment verification. The environment verification includes, but is not limited to, configuration center verification, document verification, PAAS verification, and service status verification, and is set according to actual needs, which is not limited in the embodiments of the present invention. Configuration center verification includes, but is not limited to, Disconf configuration file content verification, Apollo configuration instance number verification, CMC dynamic variable verification. Document verification includes, but is not limited to, command verification, configuration file parameter verification, and script verification within a container. PAAS authentication includes, but is not limited to, deployment node authentication. Service status verification includes, but is not limited to, service provider verification. And the service provider verifies, including but not limited to judging whether the number of the servers is correct, whether the registration state of the service provider is normal, whether the running state is stable, and whether the service response time is within a preset time interval.
After the environment verification is passed, the gray scale issuing server sends 50 transaction requests to a first gray scale server c, and the first gray scale server c processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. And the gray release server judges whether the first gray server c meets a second index verification rule, wherein the second index verification rule comprises log verification, service verification and database verification. If the first grayscale server c passes log verification, service verification, and database verification, the first grayscale server c satisfies the second criteria verification rule.
After the first gray scale server c meets the second index verification rule, the gray scale issuing server updates the second test quantity to 50+50 to 100, and then sends 100 transaction requests to the first gray scale server c, and the first gray scale server c processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. And the gray release server judges whether the first gray server c meets a second index verification rule, wherein the second index verification rule comprises log verification, service verification and database verification. If the first grayscale server c passes log verification, service verification, and database verification, the first grayscale server c satisfies the second criteria verification rule.
And the gray release server continuously updates the second test quantity, and repeats the process to perform the gray release test on the first gray server c until the updated second test quantity is equal to 5000.
The gray release server judges whether the second test quantity is equal to 5000, if the second test quantity is equal to 5000, the gray release server sends a gray version deployment instruction to a third-party server, and the third-party server sends an installation package of the gray version of the application product B to a server d (a server which does not deploy the gray version) in the server cluster. The server d receives the installation package, and installs the grayscale version of the application product B through the installation package, and after the installation is completed, the server d becomes the next grayscale server.
And the gray scale release server performs environment verification. After the environment verification is passed, the gray release server sends a transaction request to the server d based on the gray release rule to perform a gray release test on the server d. The gray release testing process of the server d is similar to the gray release testing process of the first server c, and details are not repeated here.
After the server d passes the gray release test, the gray release server repeats the gray version deployment and gray release test process for one server (server without the gray version deployment) in the server cluster until all servers in the server cluster pass the gray release test.
Fig. 3 is a schematic flow chart of a progressive grayscale publishing method according to another embodiment of the present invention, and as shown in fig. 3, an implementation flow of the progressive grayscale publishing method according to the embodiment of the present invention is as follows:
in a first step, a transaction request is sent. And the gray scale issuing server sends a second test quantity of transaction requests to the gray scale server. The gray scale server processes the received transaction requests and returns the start time for processing the transaction requests and the processing related information for processing each transaction request to the gray scale issuing server. And performing environment verification before sending the second test quantity of transaction requests, and sending the transaction requests after the environment verification is passed. The initial value is set to 50, the step value is set to 50, and the target value is set to 5000 in advance.
And step two, judging whether to update the second test quantity. And the gray scale issuing server judges whether the gray scale server meets a second index verification rule or not based on the processing related information, if the gray scale server meets the second index verification rule, the second test quantity needs to be updated, and the third step is carried out. And if the gray server is judged not to meet the second index verification rule, ending the gradual gray release process.
And thirdly, updating the second test quantity. And the gray release server updates the second test quantity, wherein the updated second test quantity is equal to the sum of the second test quantity before updating and the step value.
And fourthly, judging whether the target value is equal to the target value or not. The gray 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 release server is proved to pass the gray release test, and then the fifth step is carried out; and if the second test quantity is not equal to the target value, returning to the first step, and continuing to perform the gray release test on the gray server.
And fifthly, judging whether the number is equal to the preset number. And counting the number N of the servers deploying the gray versions in the server cluster by the gray release server, and ending the gradual gray release process if the number N is equal to the preset number. And if the number N is less than the preset number, entering a sixth step.
And sixthly, triggering the deployment of the gray-scale version. And triggering the deployment of the gray scale version of one server in the server cluster by the gray scale release server so as to enable the one server to become a next gray scale server, setting the second test quantity equal to the initial value, and then entering the first step to perform the gray scale release test on the next gray scale server.
On the basis of the foregoing embodiments, further, the gray scale distribution rule includes:
sending a third test quantity 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; wherein 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 validation rule is preset;
and sending a transaction request to the test object so that the test object continuously runs for a preset time.
Specifically, the gray scale issuing server sends a third test quantity of transaction requests to a test object, where the test object is a gray scale server. The test object receives the transaction request and processes the transaction request. The gray release 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 information related to processing of each transaction request to the gray-scale distribution server. The gradation issuance server may determine whether the test object satisfies the third index validation rule based on the processing-related information of each transaction request. Wherein the processing related information comprises log information, service verification information, database verification information and the like. The third index validation rule includes, but is not limited to, log validation, service validation, database validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, checking the service operation condition and the service response time, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null.
And the gray 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 release server updates the third test quantity, namely, the sum of the third test quantity before updating and the step value is calculated as the updated third test quantity. And sending a third test quantity 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 scale release server. And the gray scale issuing server judges whether the test object meets the third index validation rule after the third test quantity is updated again, continues to update the third test quantity after the test object meets the third index validation rule, repeats the process of sending the transaction requests of the third test quantity to the test object and judging whether the test object meets the third index validation rule after the third test quantity is updated until the third test quantity is equal to the target value. That is, the gray scale issuing server gradually increases the transaction request processing amount of the test object based on the step value in the process of performing the gray scale issuing test on the test object, and performs the gray scale issuing test on a single gray scale server progressively. The step value and the target value are preset and set according to a test requirement, which is not limited in the embodiments of the present invention. It is understood that if the test object does not satisfy the third criterion verification rule, the gray scale issuance test for the test object may be terminated and failure of the gray scale issuance test is prompted.
After the third test quantity is equal to the target value, the gray scale issuing server continues to send 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, and the embodiment of the present invention is not limited.
For example, the third index validation rule includes log validation including keyword validation and return result validation, service validation including service operation condition validation and service response time validation, and database validation including expected value validation and acquired data validation. And 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 return result verification. The test object can pass the service verification after passing the service operation condition verification and the service response time verification. The test object can pass the database verification after passing the expected value verification and the acquisition data verification.
On the basis of the foregoing embodiments, further, the determining that the first grayscale server passes the grayscale release test includes:
and if the third test quantity is judged to be equal to the target value and the test object meets the fourth index verification rule in the continuous operation preset time, determining that the first gray scale server passes the gray scale release test.
Specifically, after the third test quantity is equal to the target value, the grayscale issuing server may continue to send transaction requests to the first grayscale server, and the first grayscale server may feed back, to the grayscale issuing server, information related to processing of each transaction request within the preset time of continuous operation. If the gray scale issuing server determines that the first gray scale server satisfies the fourth index validation rule and determines that the third test number is equal to the target value, it may be determined that the first gray scale server passes the gray scale issuing test.
The fourth index validation rule is preset, and includes but is not limited to log validation, service validation, database validation, batch job condition validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, the service operation condition verification and the service response time verification, and is set according to actual needs, and the embodiment of the present invention is not limited. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null. The batch job condition verification includes but is not limited to DBF batch verification, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. And DBF batch verification, namely verifying whether the batch processing result is correct.
For example, the fourth index validation rule includes log validation including keyword validation and return result validation, service validation including service run condition validation and service response time validation, database validation including expected value validation and acquired data validation, and batch job condition validation including DBF batch validation. The test object can meet the fourth index validation rule only after passing log validation, service validation, database validation and batch job condition validation. The test object can pass log verification after passing key word verification and return result verification. The test object can pass the service verification after passing the service operation condition verification and the service response time verification. The test object can pass the database verification after passing the expected value verification and the acquisition data verification. The test object can pass the batch operation condition verification after passing the DBF batch verification.
The implementation process of the progressive grayscale publishing method provided by the embodiment of the present invention is further described below with a specific embodiment.
The initial value was set to 50, the step value to 50, and the target value to 5000.
And after the first gray scale server e in the server cluster finishes the installation of the gray scale version of the application product C, the gray scale release server performs environment verification. The environment verification includes, but is not limited to, configuration center verification, document verification, PAAS verification, and service status verification, and is set according to actual needs, which is not limited in the embodiments of the present invention. Configuration center verification includes, but is not limited to, Disconf configuration file content verification, Apollo configuration instance number verification, CMC dynamic variable verification. Document verification includes, but is not limited to, command verification, configuration file parameter verification, and script verification within a container. PAAS authentication includes, but is not limited to, deployment node authentication. Service status verification includes, but is not limited to, service provider verification. And the service provider verifies, including but not limited to judging whether the number of the servers is correct, whether the registration state of the service provider is normal, whether the running state is stable, and whether the service response time is within a preset time interval.
After the environment verification is passed, the gray scale issuing server sends 50 transaction requests to a first gray scale server e, and the first gray scale server e processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. And the gray release server judges whether the first gray server e meets a third index verification rule, wherein the third index verification rule comprises log verification, service verification and database verification. And if the first gray server e passes log verification, service verification and database verification, the first gray server e meets a third index verification rule.
After the first gray scale server e meets the third index verification rule, the gray scale issuing server updates the third test quantity to 50+50 to 100, and then sends 100 transaction requests to the first gray scale server e, and the first gray scale server e processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. And the gray release server judges whether the first gray server e meets a third index verification rule, wherein the third index verification rule comprises log verification, service verification and database verification. And if the first gray server e passes log verification, service verification and database verification, the first gray server e meets a third index verification rule.
And the gray release server continuously updates the third test quantity, and repeats the process to perform the gray release test on the first gray server e until the updated third test quantity is equal to 5000. The gray scale issuing server will continue to send transaction requests to the first gray scale server e, and maintain the first gray scale server e to continuously operate for 24 hours, the first gray scale server e processes the received transaction requests and returns the processing related information of processing each transaction request after the third test quantity is equal to 5000 to the gray scale issuing server. And the gray release server judges whether the third test quantity is equal to 5000 and whether the first gray 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 gradation 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 gradation server e passes the gradation issuance test.
The gray scale release server sends a gray scale version deployment instruction to a third-party server, and the third-party server sends an installation package of the gray scale version of the application product C to a server f (a server which does not deploy the gray scale version) in the server cluster. The server f receives the installation package and installs the grayscale version of the application product C through the installation package, and after the installation is completed, the server f becomes the next grayscale server.
And the gray scale release server performs environment verification. After the environment verification is passed, the gray scale issuing server sends a transaction request to the server f based on the gray scale issuing rule so as to perform a gray scale issuing test on the server f. The gray release test process of the server f is similar to the gray release test process of the first server e, and details are not repeated here.
After the server f passes the gray release test, the gray release server repeats the gray version deployment and gray release test process for one server (server not deploying the gray version) in the server cluster until all servers in the server cluster pass the gray release test.
Fig. 4 is a schematic flow chart of a progressive grayscale publishing method according to yet another embodiment of the present invention, and as shown in fig. 4, an implementation flow of the progressive grayscale publishing method according to the embodiment of the present invention is as follows:
in a first step, a transaction request is sent. And the gray release server sends a third test quantity of transaction requests to the gray server. The gray scale server processes the received transaction requests and returns the start time for processing the transaction requests and the processing related information for processing each transaction request to the gray scale issuing server. And performing environment verification before sending the third test number of transaction requests, and sending the transaction requests after the environment verification is passed. The preset initial value is 50, the step value is 50, the target value is 5000, and the preset time is 24 hours.
And step two, judging whether to update the third test quantity. And the gray scale issuing server judges whether the gray scale server meets a third index verification rule or not based on the processing related information, if the gray scale server meets the third index verification rule, the third test quantity needs to be updated, and the third step is carried out. And if the gray server is judged not to meet the third index verification rule, ending the gradual gray release process.
And thirdly, updating the third test quantity. And the gray release server updates the third test quantity, wherein the updated third test quantity is equal to the sum of the third test quantity before updating and the step value.
And fourthly, judging whether the target value is equal to the target value or not. The gray 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 carried out; and if the third test quantity is not equal to the target value, returning to the first step, and continuing to perform the gray release test on the gray server.
And step five, sending a transaction request. The gray scale issuing server can continuously send the transaction requests to the gray scale server, so that the gray scale server continuously operates for 24 hours, the gray scale server processes the received transaction requests and can feed back the processing related information of each transaction request within 24 hours of continuous operation to the gray scale issuing server.
And sixthly, judging whether the gray release test is passed or not. And the gray scale issuing server judges whether the third test quantity is equal to the target value or not, judges whether the gray scale server meets a fourth index verification rule or not based on the processing related information of each transaction request within 24 hours of continuous operation, and if the third test quantity is equal to the target value and the gray scale server meets the fourth index verification rule, determines that the gray scale server passes the gray scale issuing test, and then enters the seventh step. If the third test quantity is equal to the target value but the grayscale server does not satisfy the fourth criteria validation rule, the progressive grayscale release flow ends.
And seventhly, judging whether the quantity is equal to the preset quantity or not. And counting the number N of the servers deploying the gray versions in the server cluster by the gray release server, and ending the gradual gray release process if the number N is equal to the preset number. And if the number N is less than the preset number, entering an eighth step.
And step eight, triggering gray-scale version deployment. And triggering the deployment of the gray scale version of one server in the server cluster by the gray scale release server so as to enable the one server to become a next gray scale server, setting the third test quantity equal to the initial value, and then entering the first step to perform the gray scale release test on the next gray scale server.
On the basis of the foregoing embodiments, further, the gray scale distribution rule includes:
sending a fourth test quantity 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 a 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 size statistical parameter is judged to be equal to the integral multiple of the set number, sending a fourth test number of transaction requests to the test object so as to enable the test object to continuously run for the set time, updating the fourth test number according to the step size value after judging that the test object meets a sixth index verification rule in the continuous running of the set time and the fourth test number is smaller than the target value, and sending the fourth test number of transaction requests to the test object;
wherein 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 validation rule is preset; the step size statistical parameter is added by 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 scale issuing server sends a fourth test quantity of transaction requests to a test object, where the test object is a gray scale server. The test object receives the transaction request and processes the transaction request. The gray release 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 information related to processing of each transaction request to the gray-scale distribution server. The gradation issuance server may determine whether the test object satisfies a fifth index validation rule based on the processing-related information of each transaction request. Wherein the processing related information comprises log information, service verification information, database verification information and the like. The fifth index validation rule includes, but is not limited to, log validation, service validation, database validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, checking the service operation condition and the service response time, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null.
And the gray scale issuing server judges whether the test object meets the fifth index verification rule, if so, the gray scale issuing server updates the fourth test quantity and adds 1 to the step statistical parameter, namely, the sum of the fourth test quantity before updating and the step value is calculated as the updated fourth test quantity. And sending a fourth test quantity 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 scale release server. And the gray scale issuing server judges whether the test object meets a fourth index verification rule after the fourth test quantity is updated again, and judges whether the step length statistical parameter is equal to the integral multiple of the set quantity.
And after judging that the test object meets a fifth index verification rule and the step size statistical parameter is not equal to the integral multiple of the set number, continuing to update the fourth test number and adding 1 to the step size statistical parameter, repeating the process of sending the transaction requests 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 the target value. After the test object is judged to meet a fifth index verification rule and the step size statistical parameter is equal to the integral multiple of the set number, updating a fourth test number, adding 1 to the step size statistical parameter, sending transaction requests of the fourth test number to the test object so that the test object continuously runs for the set time, and feeding back processing related information of each transaction request in the set time of continuous running to the gray scale release server by the test object. And if the gray 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 is understood that, if the test object does not satisfy the fifth index validation rule or the sixth index validation rule, the gray scale issuance test for the test object may be terminated and a failure of the gray scale issuance test is prompted.
That is, the gray scale issuing server gradually increases the transaction request processing amount of the test object based on the step value in the process of performing the gray scale issuing test on the test object, and performs the gray scale issuing test on a single gray scale server progressively. And after the step size statistical parameter is equal to the integral multiple of the set number each time, the test object is continuously operated for the set time. The step value and the target value are preset and set according to a test requirement, which is not limited in the embodiments of the present invention. The sixth index validation rule is preset; and adding 1 to the step length statistical parameter after the fourth test quantity is updated every time, wherein the initial value of the step length 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 validation rule is preset, and includes but is not limited to log validation, service validation, database validation, batch job condition validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention.
The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, the service operation condition verification and the service response time verification, and is set according to actual needs, and the embodiment of the present invention is not limited. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null. The batch job condition verification includes but is not limited to DBF batch verification, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. And DBF batch verification, namely verifying whether the batch processing result is correct.
For example, the fifth index validation rule includes log validation including keyword validation and return result validation, service validation including service operation condition validation and service response time validation, and database validation including expected value validation and acquired data validation. And 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 return result verification. The test object can pass the service verification after passing the service operation condition verification and the service response time verification. The test object can pass the database verification after passing the expected value verification and the acquisition data verification.
The sixth index validation rule includes, but is not limited to, log validation, service validation, database validation, batch job condition validation, and the like, and is set according to actual needs, which is not limited in the embodiments of the present invention. The log verification includes but is not limited to keyword verification and returned result verification, and the log verification is set according to actual needs, which is not limited in the embodiment of the present invention. And verifying the keywords, namely verifying whether the keywords in the log information are correct, wherein the keywords are set according to the test requirements, and the embodiment of the invention is not limited. And returning result verification, namely judging whether the accuracy reaches 100% or not based on the log returning result in the log information, and whether abnormal error is reported or not. The service verification includes, but is not limited to, the service operation condition verification and the service response time verification, and is set according to actual needs, and the embodiment of the present invention is not limited. Database validation is a validation directed to the accuracy of database write tables, including but not limited to expected value validation and acquired data validation. The expected value verifies, i.e., checks whether the expected field value is written correctly. And (4) data verification, namely checking whether the necessary input field is not null. The batch job condition verification includes but is not limited to DBF batch verification, and the setting is performed according to actual needs, which is not limited in the embodiment of the present invention. And DBF batch verification, namely verifying whether the batch processing result is correct.
On the basis of the foregoing embodiments, further, the determining that the first grayscale server passes the grayscale release test includes:
if the fourth test quantity is judged to be equal to the target value and the step length statistical parameter is not equal to the integral multiple of the set quantity, determining that the first gray scale server passes the gray scale issuing test; or
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 continuous operation set time, determining that the first gray scale server passes the gray scale release test.
Specifically, the grayscale issuing server determines whether the fourth test number is equal to a target value, and determines whether the step size statistical parameter is equal to an integer multiple of the set number, and if 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 determined that the first grayscale server passes the grayscale issuing test.
After judging that the fourth test quantity is equal to a target value and the step length statistical parameter is equal to an integral multiple of the set quantity, the gray scale issuing server sends the target value transaction requests to a first gray scale server, so that the first gray scale server continuously operates for the set time, and the first gray scale server feeds back processing related information of each transaction request in the set time of continuous operation to the gray scale issuing server. If the gray scale issuing server judges that the fourth test number is equal to the target value, the step statistical parameter is equal to the integral multiple of the set number, and the first gray scale server meets the sixth index verification rule, it can be determined that the first gray scale server passes the gray scale issuing test.
The implementation process of the progressive gray scale distribution method provided by the embodiment of the invention is further described in a specific embodiment.
Setting an initial value of 50, a step value of 50, a target value of 5000, an initial value of step statistical parameters of 0, a set number of 5 and a set time of 3 hours.
And after the first gray scale server g in the server cluster finishes the installation of the gray scale version of the application product D, the gray scale release server performs environment verification. The environment verification includes, but is not limited to, configuration center verification, document verification, PAAS verification, and service status verification, and is set according to actual needs, which is not limited in the embodiments of the present invention. Configuration center verification includes, but is not limited to, Disconf configuration file content verification, Apollo configuration instance number verification, CMC dynamic variable verification. Document verification includes, but is not limited to, command verification, configuration file parameter verification, and script verification within a container. PAAS authentication includes, but is not limited to, deployment node authentication. Service status verification includes, but is not limited to, service provider verification. And the service provider verifies, including but not limited to judging whether the number of the servers is correct, whether the registration state of the service provider is normal, whether the running state is stable, and whether the service response time is within a preset time interval.
After the environment verification is passed, the gray scale issuing server sends 50 transaction requests to a first gray scale server g, and the first gray scale server g processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. The gray release server judges whether the first gray 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 grayscale server g passes log verification, service verification, and database verification, the first grayscale server g satisfies the fifth index verification rule.
After the first gray scale server g meets the fifth index verification rule, the gray scale issuing server updates the fourth test quantity to 50+50 to 100, adds 1 to the step size statistical parameter to obtain a calculated step size statistical parameter to 0+1 to 1, then sends 100 transaction requests to the first gray scale server g, and the first gray scale server g processes the received transaction requests and returns processing related information for processing each transaction request to the gray scale issuing server. The gray release server judges whether the first gray 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 grayscale server g passes log verification, service verification, and database verification, the first grayscale server g satisfies the fifth index verification rule.
And the gray scale issuing 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, the step length statistical parameter is not equal to the integral multiple of the set number, then the fourth test number is continuously updated, and the process is repeated to carry out the gray scale issuing test on the first gray scale server g. When the step size statistical parameter is 5, the remainder of dividing the step size statistical parameter 5 by the set number 5 is 0, the step size statistical parameter is equal to the integral multiple of the set number, the gray scale publishing server sends a fourth test number of transaction requests to the test object so that the test object continuously runs for 3 hours, and the test object can feed back processing related information of each transaction request within 3 hours of continuous running to the gray scale publishing server. And if the gray 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 scale issuing server continuously repeats the processes to carry out the gray scale issuing test on the first gray scale 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 issuing server may determine that the fourth test number is equal to 5000, and the step statistical parameter 49 is not an integral multiple of the set number 5, then the first gray scale server g passes the gray scale issuing test.
The gray scale release server sends a gray scale version deployment instruction to a third-party server, and the third-party server sends an installation package of the gray scale version of the application product D to a server h (a server which does not deploy the gray scale version) in the server cluster. The server h receives the installation package, and installs the grayscale version of the application product D through the installation package, and after the installation is completed, the server h becomes the next grayscale server.
And the gray scale release server performs environment verification. After the environment verification is passed, the gray scale issuing server sends a transaction request to the server h based on the gray scale issuing rule so as to perform a gray scale issuing test on the server h. The gray release test process of the server h is similar to the gray release test process of the first server g, and details are not repeated here.
After the server h passes the gray release test, the gray release server repeats the gray version deployment and gray release test process for one server (server without the gray version deployment) in the server cluster until all servers in the server cluster pass the gray release test.
Fig. 5 is a schematic flow chart of a progressive grayscale publishing method according to still another embodiment of the present invention, and as shown in fig. 5, an implementation flow of the progressive grayscale publishing method according to the embodiment of the present invention is as follows:
in a first step, a transaction request is sent. And the gray scale issuing server sends a fourth test quantity transaction request to the gray scale server. The gray scale server processes the received transaction requests and returns the start time for processing the transaction requests and the processing related information for processing each transaction request to the gray scale issuing server. And performing environment verification before sending the fourth test quantity of transaction requests, and sending the transaction requests after the environment verification is passed. Setting an initial value of 50, a step value of 50, a target value of 5000, an initial value of step statistical parameters of 0, a set number of 5 and a set time of 3 hours.
And secondly, judging whether a fifth index verification rule is met. And the gray scale issuing server judges whether the gray scale server meets a fifth index verification rule or not based on the processing related information, if so, the fourth test quantity needs to be updated, and the third step is carried out. And if the gray server is judged not to meet the fifth index verification rule, ending the gradual gray release process.
And thirdly, updating the fourth test quantity. And the gray release server updates the fourth test quantity, wherein the updated fourth test quantity is equal to the sum of the fourth test quantity before updating and the step value.
And fourthly, calculating step length statistical parameters. And the gray scale issuing server calculates the step length statistical parameter, wherein the calculated step length statistical parameter is equal to the step length statistical parameter before calculation plus 1.
And fifthly, judging whether the whole division can be performed. The gray scale issuing server calculates the remainder of dividing the step length statistical parameter by the set number of 5, if the remainder is not 0, the step length statistical parameter cannot divide the set number in whole, the step length statistical parameter is not equal to the integral multiple of the set number, and the sixth step is started; and if the remainder is 0, dividing the step size statistical parameter by the set number, wherein the step size statistical parameter is equal to the integral multiple of the set number, and entering the seventh step.
And sixthly, judging whether the target value is equal to the target value or not. The gradation issuance server judges whether or not the fourth test quantity is equal to the target value. If the fourth test quantity is equal to the target value, entering a twelfth step; and if the fourth test quantity is not equal to the target value, returning to the first step, and continuing to perform the gray release test on the gray server.
And step seven, sending a transaction request. The gray scale issuing server sends a fourth test number of transaction requests to the gray scale server so that the gray scale server continuously operates for a set time of 3 hours, and the gray scale server can feed back processing related information of each transaction request to the gray scale issuing server within 3 hours of continuous operation.
And step eight, judging whether the sixth index verification rule is met. And the gray scale issuing server judges whether the gray scale server meets a sixth index verification rule or not based on the processing related information returned by the gray scale server, and if the gray scale server meets the sixth index verification rule, the ninth step is carried out. And if the gray server is judged not to meet the sixth index verification rule, ending the progressive gray release process.
And ninthly, judging whether the target value is smaller than the target value. And the gray release server judges whether the fourth test quantity is less than the target value. If the fourth test quantity is less than the target value, entering a tenth step; if the fourth test quantity is equal to the target value, then proceed to the twelfth step.
And step ten, updating the fourth test quantity. And the gray release server updates the fourth test quantity, wherein the updated fourth test quantity is equal to the sum of the fourth test quantity before updating and the step value.
And step eleven, calculating step length statistical parameters. And the gray scale issuing server calculates the step size statistical parameter, the calculated step size statistical parameter is equal to the step size statistical parameter before calculation plus 1, and then the first step is returned.
And a twelfth step of judging whether the number is equal to the preset number. And counting the number N of the servers deploying the gray versions in the server cluster by the gray release server, and ending the gradual gray release process if the number N is equal to the preset number. If the number N is less than the preset number, the thirteenth step is entered.
And step thirteen, triggering the deployment of the gray-scale version. And triggering the deployment of the gray scale version of one server in the server cluster by the gray scale release server so as to enable the one server to become the next gray scale server, setting the fourth test quantity equal to the initial value, setting the initial value of the step length statistical parameter equal to 0, and then entering the first step to perform the gray scale release test on the next gray scale server.
Fig. 6 is a schematic structural diagram of a progressive grayscale issuing device according to an embodiment of the present invention, and as shown in fig. 6, the progressive grayscale issuing device according to the 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 grayscale server based on a grayscale release rule, so as to perform a grayscale release test on the first grayscale server; wherein the gray release rule is preset; the triggering module 602 is configured to trigger deployment of a grayscale version of one server in the server cluster after it is determined that the first grayscale server passes the grayscale release test, so that the one server becomes a next grayscale server; the testing module 603 is configured to send a transaction request to the next grayscale server based on the grayscale release rule, so as to perform a grayscale release test on the next grayscale server until a preset number of servers in the server cluster pass the grayscale release test.
Specifically, when gray scale publishing of an application product is performed, the sending module 601 may send a transaction request to a first gray scale server based on a gray scale publishing rule, and the first gray scale server may receive the transaction request sent by the sending module 601 and process the transaction request to implement a gray scale publishing test. The sending module 601 may monitor a situation that the first grayscale server processes the transaction request. Wherein the gray scale release rule is preset. The first grayscale server has installed a grayscale version of an application product.
The triggering module 602 may determine whether the first grayscale server passes the grayscale release test according to the processing of the first grayscale server on the transaction request, and if the first grayscale server passes the grayscale release test, it indicates that the grayscale version of the application product can be popularized, the triggering module 602 may trigger deployment of the grayscale version of one server in the server cluster, and the one server becomes the next grayscale server after the grayscale version is installed. If the first grayscale server fails to pass the grayscale release test, it indicates that the grayscale version of the application product has a problem and needs to be improved.
After the server becomes the next grayscale server, the test module 603 may send a transaction request to the next grayscale server based on the grayscale release rule, and the next grayscale server receives the transaction request sent by the test module 603 and processes the transaction request to implement the grayscale release test. The test module 603 may monitor a situation that the next grayscale server processes the transaction request, and determine whether the next grayscale server passes the grayscale release test, and after the next grayscale server passes the grayscale release test, continue to trigger deployment of the grayscale version of one server in the server cluster to obtain the next grayscale server, and repeat the step of sending the transaction request to the next grayscale server based on the grayscale release rule to perform the grayscale release test on the next grayscale server until the number of grayscale servers in the server cluster that pass the grayscale release test is equal to the preset number. That is, the test module 603 triggers the deployment of the grayscale version of one server in the server cluster one by one and performs the grayscale release test. The process of the gray distribution test of each gray 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 some servers in the server cluster, and is set according to actual needs, which is not limited in the embodiment of the present invention.
The progressive gray scale release device provided by the embodiment of the invention can send a transaction request to the first gray scale server based on the gray scale release rule so as to perform gray scale release test on the first gray scale server, trigger the deployment of the gray scale version of one server in the server cluster after judging and knowing that the first gray scale server passes the gray scale release test, so that the one server becomes the next gray scale server, perform the gray scale release test on the next gray scale server based on the gray scale release rule until a preset number of servers in the server cluster pass the gray scale release test, and perform the gray scale release progressively, so that the gray scale version of an application product can be fully tested, and the reliability of the gray scale release is improved. Because the gray scale ratio is not required to be set, the artificial subjectivity in the gray scale releasing 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 do not need to be selected to experience a new version, gray scale release depending on feedback of the clients in the prior art can be avoided, and the gray scale version program cannot be guaranteed to be effectively called in sufficient quantity due to the fact that the gray scale clients do not initiate transaction requests in a gray scale period, so that gray scale test point time needs to be prolonged, popularization of new products is affected, and waste of server resources is avoided.
The embodiment of the apparatus provided in the embodiment of the present invention may be specifically configured to execute the processing flows of the above method embodiments, and the functions of the apparatus are not described herein again, and refer to the detailed description of the above method embodiments.
The existing gray level issuing technology needs artificial gray level ratio definition, and the problem of overlarge defined gray level range sometimes can be caused by empirical judgment, so that the risk of issuing gray level content is increased; sometimes, the problem of too small gray scale defining range occurs, which results in the problem that sufficient effective gray scale samples cannot be obtained, and the gray scale effect is affected. In addition, the existing gray scale publishing is mostly controlled by controlling the number of gray scale cluster servers, so that the granularity of gray scale publishing is too coarse, the gray scale strategy is lack of flexibility, and the overall process of gray scale publishing is not easily managed.
The embodiment of the invention provides a progressive gray scale release method aiming at the defects in the existing gray scale release technology. The task of setting the gray scale ratio in the gray scale issuing process is omitted, the minimum unit of the gray scale issuing is refined, the flexibility and the effectiveness of the gray scale issuing strategy are enhanced, and meanwhile the risk in the gray scale issuing process is better controlled. The automatic publishing method is adopted, and the outstanding effect is achieved in replacing manual work. The method is particularly suitable for issuing high-risk online products such as accounts and funds of banks, financial institutions and internet financial companies.
It should be noted that the progressive grayscale issuing method and apparatus provided in the embodiment of the present invention may be used in the financial field, and may also be used in any technical field other than the financial field.
Fig. 7 is a schematic physical structure diagram of an electronic device according to an embodiment of the present invention, and 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 complete communication with each other through the communication bus 704. The processor 701 may call logic instructions in the memory 703 to perform the following method: sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset; if the first gray scale server passes the gray scale release test, triggering the deployment of the gray scale version of one server in the server cluster so as to enable the one server to become the next gray scale server; and sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
In addition, the logic instructions in the memory 703 can be implemented in the form of software functional units and stored in a computer readable storage medium when the software functional units are sold or used as independent products. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute 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), a magnetic disk or an optical disk, and 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, enable the computer to perform the method provided by the above-mentioned method embodiments, for example, comprising: sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset; if the first gray scale server passes the gray scale release test, triggering the deployment of the gray scale version of one server in the server cluster so as to enable the one server to become the next gray scale server; and sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
The present embodiment provides a computer-readable storage medium, which stores a computer program, where the computer program causes the computer to execute the method provided by the above method embodiments, for example, the method includes: sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset; if the first gray scale server passes the gray scale release test, triggering the deployment of the gray scale version of one server in the server cluster so as to enable the one server to become the next gray scale server; and sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
As will be appreciated by one skilled in the art, 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams 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 (12)

1. A progressive gradation issuance method, comprising:
sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset;
if the first gray scale server passes the gray scale release test, triggering the deployment of the gray scale version of one server in the server cluster so as to enable the one server to become the next gray scale server;
and sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
2. The method of claim 1, wherein the gray scale publication rule comprises:
sending a first test quantity of transaction requests to a test object; wherein the first test number is equal to an initial value;
if the testing time is judged to be more than or equal to the time parameter and the test object meets the first index verification rule, updating the first testing quantity and resetting the testing time according to the step value, and sending transaction requests of the first testing quantity to the test object until the first testing quantity is equal to the target value; wherein, 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 validation rule is preset.
3. The method of claim 2, wherein the determining that the first grayscale server passes the grayscale release 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 scale server meets the first index verification rule, determining that the first gray scale server passes the gray scale release test.
4. The method of claim 1, wherein the gray scale publication rule comprises:
sending a second test quantity 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 a 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 quantity after each update is equal to the sum of the second test quantity before the update and the step value; the second index validation rule is preset.
5. The method of claim 4, wherein the determining that the first grayscale server passes the grayscale release test comprises:
and if the second test quantity is judged to be equal to the target value, determining that the first gray scale server passes the gray scale issuing test.
6. The method of claim 1, wherein the gray scale publication rule comprises:
sending a third test quantity 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; wherein 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 validation rule is preset;
and sending a transaction request to the test object so that the test object continuously runs for a preset time.
7. The method of claim 6, wherein the determining that the first grayscale server passes the grayscale release test comprises:
and if the third test quantity is judged to be equal to the target value and the test object meets the fourth index verification rule in the continuous operation preset time, determining that the first gray scale server passes the gray scale release test.
8. The method of claim 1, wherein the gray scale publication rule comprises:
sending a fourth test quantity 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 a 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 size statistical parameter is judged to be equal to the integral multiple of the set number, sending a fourth test number of transaction requests to the test object so as to enable the test object to continuously run for the set time, updating the fourth test number according to the step size value after judging that the test object meets a sixth index verification rule in the continuous running of the set time and the fourth test number is smaller than the target value, and sending the fourth test number of transaction requests to the test object;
wherein 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 and sixth index validation rules are preset; the step size statistical parameter is added by 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 the determining that the first grayscale server passes the grayscale release test comprises:
if the fourth test quantity is judged to be equal to the target value and the step length statistical parameter is not equal to the integral multiple of the set quantity, determining that the first gray scale server passes the gray scale issuing test;
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 continuous operation set time, determining that the first gray scale server passes the gray scale release test.
10. A progressive gradation issuing apparatus, comprising:
the sending module is used for sending a transaction request to a first gray scale server based on a gray scale release rule so as to perform a gray scale release test on the first gray scale server; wherein the gray release rule is preset;
the triggering module is used for triggering the deployment of the gray scale version of one server in the server cluster after judging that the first gray scale server passes the gray scale release test, so that the one server becomes the next gray scale server;
and the test module is used for sending a transaction request to the next gray scale server based on the gray scale release rule so as to perform gray scale release test on the next gray scale server until a preset number of servers in the server cluster pass the gray scale release test.
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 steps of the method of any of claims 1 to 9 are implemented when the computer program is executed by the processor.
12. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 9.
CN202110239593.7A 2021-03-04 2021-03-04 Progressive gray level publishing method and device Active CN113010418B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110239593.7A CN113010418B (en) 2021-03-04 2021-03-04 Progressive gray level publishing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110239593.7A CN113010418B (en) 2021-03-04 2021-03-04 Progressive gray level publishing method and device

Publications (2)

Publication Number Publication Date
CN113010418A true CN113010418A (en) 2021-06-22
CN113010418B CN113010418B (en) 2024-03-01

Family

ID=76405056

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110239593.7A Active CN113010418B (en) 2021-03-04 2021-03-04 Progressive gray level publishing method and device

Country Status (1)

Country Link
CN (1) CN113010418B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109710675A (en) * 2018-12-26 2019-05-03 深圳乐信软件技术有限公司 A kind of storing data library switching method, device, server and storage medium
WO2020119426A1 (en) * 2018-12-13 2020-06-18 深圳壹账通智能科技有限公司 Gray scale testing method, server and computer readable storage medium

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020119426A1 (en) * 2018-12-13 2020-06-18 深圳壹账通智能科技有限公司 Gray scale testing method, server and computer readable storage medium
CN109710675A (en) * 2018-12-26 2019-05-03 深圳乐信软件技术有限公司 A kind of storing data library switching method, device, server and storage medium

Also Published As

Publication number Publication date
CN113010418B (en) 2024-03-01

Similar Documents

Publication Publication Date Title
CN113330723B (en) Patch management in a hybrid computing environment
CN110162382B (en) Container-based gray level publishing method, device, computer equipment and storage medium
CN110825394A (en) Automatic application program initialization method and system for cloud mobile phone and storage medium
CN109445827B (en) Game updating method and device, electronic equipment and storage medium
CN112612607A (en) Data processing method, device, computer equipment and medium based on message queue
CN114896166A (en) Scene library construction method and device, electronic equipment and storage medium
CN111949277A (en) Intelligent gray scale release production method and device, computer equipment and storage medium
CN108268605B (en) Shared space resource management method and system
CN113010418B (en) Progressive gray level publishing method and device
CN112286650A (en) Method and device for issuing distributed service
CN109710285B (en) Equipment upgrading method and system
CN111324481A (en) Linux platform repairing method and device
CN113076248B (en) Application processing method, device and equipment and readable storage medium
CN111930476B (en) Task scheduling method and device and electronic equipment
CN109857629B (en) Scanning detection method and device
CN113553180B (en) Container scheduling method and device and electronic equipment
CN107220897B (en) Income posting processing method and device and processing system
CN115983991A (en) Flow adjusting method, device, equipment and medium
CN114553855B (en) Plug-in gray level issuing method and device, electronic equipment and storage medium
CN114443102A (en) Gray level switching method and device for transaction upgrading
CN113850428A (en) Job scheduling prediction processing method and device and electronic equipment
CN106878369B (en) Service processing method and device
CN113127359A (en) Method and device for obtaining test data
CN112667256A (en) OpenStack cross-version upgrading method based on kolla-allowed
CN113052687B (en) Transaction route distribution method and related device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant