Gray release management method, device and equipment and computer readable storage medium
By defining the target APPID and managing traffic weights during canary releases, the problem of low efficiency in canary releases is solved, and the convenience and comprehensiveness of canary verification are achieved, ensuring the rationality and efficiency of version releases.
Patent Information
- Application Number
- CN201910495487.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-06-06
- Publication Date
- 2026-02-06
- Estimated Expiration
- 2039-06-06
AI Technical Summary
The existing canary release method is inefficient and has incompatibility issues between the old and new interfaces, resulting in incomplete verification.
By determining the grayscale verification example and target APPID during grayscale release, it is determined whether the business request is a grayscale verification request, and it is sent to the grayscale instance machine for verification. The traffic weight of the grayscale instance machine is set to a minimum value to centrally process the verification request, generate a grayscale verification report, and perform rollback.
It achieves convenience and comprehensiveness in gray-scale verification, improves verification efficiency, avoids the impact of full release anomalies and the problem of incomplete random gray-scale verification, and ensures the rationality and efficiency of version release.
Smart Images
Figure CN110244965B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of Fintech, and in particular to a gray release management method and device, equipment and a computer readable storage medium. BACKGROUND
[0002] With the rapid development of Internet technology, especially Internet Fintech, more and more technologies (big data, distributed, Blockchain, artificial intelligence, etc.) are applied in the financial field.
[0003] Taking large commercial banks as an example, they usually have hundreds of business systems and hundreds of millions of users. In this case, when upgrading or releasing the bank business system, two methods can be used. Method one is to verify after full release. This method cannot find problems in advance, and if there is an exception, the impact is large. Method two is to verify after random gray release. This gray release method may have the phenomenon of new interfaces upstream and old interfaces downstream. Multiple verifications are required during gray verification to ensure comprehensive and accurate verification, resulting in low verification efficiency. SUMMARY
[0004] The main purpose of the present application is to provide a gray release management method, device, equipment and computer readable storage medium, which aims to solve the technical problems of current gray release methods and low efficiency of gray verification.
[0005] To achieve the above purpose, the present application provides a gray release management method, which comprises the following steps:
[0006] During gray release, determine the gray verification example corresponding to the gray release, and the target APPID corresponding to the gray verification example;
[0007] When receiving a business request, obtain the input parameter APPID corresponding to the business request;
[0008] According to the target APPID and the input parameter APPID, determine whether the business request is a gray verification request;
[0009] If the business request is a gray verification request, the business request is sent to a gray instance machine to verify the business request through the gray instance machine.
[0010] Optionally, after the step of determining the gray verification example corresponding to the gray release, and the target APPID corresponding to the gray verification example during gray release, the method comprises:
[0011] Determine the business application corresponding to the gray release, and nest the gray verification instance in the business application to form a target application to be released;
[0012] When receiving a version upgrade request sent by a target test terminal, send the target application to the target test terminal, so that the target test terminal triggers a service request carrying the target APPID based on the target application.
[0013] Optionally, the step of determining whether the service request is a gray verification request according to the target APPID and the input APPID comprises:
[0014] Comparing the target APPID with the input APPID to determine whether the target APPID and the input APPID are the same;
[0015] If the target APPID and the input APPID are the same, the service request is a gray verification request;
[0016] If the target APPID and the input APPID are different, the service request is not a gray verification request.
[0017] Optionally, after the step of determining the gray verification instance corresponding to the gray release and the target APPID corresponding to the gray verification instance during the gray release, the method further comprises:
[0018] Determine the gray instance machine corresponding to the gray release, and adjust the traffic weight of the gray instance machine from an initial value to a preset minimum value;
[0019] After the step of sending the service request to the gray instance machine to verify the service request through the gray instance machine if the service request is a gray verification request, the method further comprises:
[0020] When receiving the verification result fed back by the gray instance machine, determine whether the verification result is a verification pass;
[0021] If the verification result is a verification pass, perform full release and adjust the traffic weight of the gray instance machine back to the initial value.
[0022] Optionally, after the step of determining whether the verification result is a verification pass when receiving the verification result fed back by the gray instance machine, the method further comprises:
[0023] If the verification result is a verification fail, input the verification result into a preset report template to generate a gray verification report, and perform version rollback.
[0024] Optionally, after the step of judging whether the service request is a gray verification request according to the target APPID and the parameter APPID, the method comprises the following steps of:
[0025] If the service request is not a gray verification request, the service request is sent to a load balancer, the service request is sent to a service processing machine through the load balancer, and the service request is processed through the service processing machine.
[0026] In addition, to achieve the above-mentioned purpose, the application further provides a gray release management device, which comprises:
[0027] A release allocation module is configured to determine a gray verification example corresponding to the gray release and a target APPID corresponding to the gray verification example during the gray release.
[0028] A request receiving module is configured to acquire a parameter APPID corresponding to a service request when the service request is received.
[0029] A request judging module is configured to judge whether the service request is a gray verification request according to the target APPID and the parameter APPID.
[0030] A sending verification module is configured to send the service request to a gray instance machine to verify the service request through the gray instance machine if the service request is a gray verification request.
[0031] Optionally, the gray release management device comprises:
[0032] An example nesting module is configured to determine a business application corresponding to the gray release, and to nest the gray verification example in the business application to form a target application to be released.
[0033] A program sending module is configured to send the target application to a target test terminal to make the target test terminal trigger a service request carrying the target APPID based on the target application when a version upgrade request sent by the target test terminal is received.
[0034] Optionally, the request judging module comprises:
[0035] An information comparing unit is configured to compare the target APPID with the parameter APPID to judge whether the target APPID is the same as the parameter APPID.
[0036] A first judging unit is configured to judge that the service request is a gray verification request if the target APPID is the same as the parameter APPID.
[0037] The second determining unit is configured to determine that the service request is not a gray release verification request if the target APPID is different from the parameter APPID.
[0038] Optionally, the gray release management apparatus comprises:
[0039] The first adjusting module is configured to determine a gray instance machine corresponding to the gray release, and adjust a traffic weight of the gray instance machine from an initial value to a preset minimum value.
[0040] The gray release management apparatus further comprises:
[0041] The result judging module is configured to judge whether the verification result is passed when receiving the verification result fed back by the gray instance machine.
[0042] The second adjusting module is configured to perform full release and adjust the traffic weight of the gray instance machine back to the initial value if the verification result is passed.
[0043] Optionally, the gray release management apparatus further comprises:
[0044] The report generating module is configured to input the verification result into a preset report template, generate a gray verification report, and perform version rollback if the verification result is not passed.
[0045] Optionally, the gray release management apparatus further comprises:
[0046] The sending executing module is configured to send the service request to a load balancer, send the service request to a service processing machine through the load balancer, and process the service request through the service processing machine if the service request is not a gray verification request.
[0047] In addition, to achieve the above-mentioned purpose, the present application further provides a gray release management device, which comprises a memory, a processor, and a gray release verification program stored in the memory and executable on the processor. The gray release verification program is executed by the processor to realize the steps of the gray release management method.
[0048] In addition, to achieve the above-mentioned purpose, the present application further provides a computer readable storage medium, which stores a gray release verification program. The gray release verification program is executed by a processor to realize the steps of the gray release management method.
[0049] The application provides a gray release management method, device and equipment and a computer readable storage medium. In the embodiment of the application, when the gray release is performed, the gray verification example corresponding to the gray release is determined, and the target APPID corresponding to the gray verification example is determined; when a service request is received, the input parameter APPID corresponding to the service request is obtained; according to the target APPID and the input parameter APPID, it is judged whether the service request is a gray verification request; if the service request is a gray verification request, the service request is sent to a gray instance machine to verify the service request through the gray instance machine. In the embodiment of the application, when the gray release is performed, the target APPID is allocated through the gray verification example, and the service request corresponding to the target APPID is sent to the gray instance machine as a gray verification request to process the gray verification request in the gray instance machine, so that the gray verification is more convenient and comprehensive. At the same time, in the embodiment, the separation processing of the new and old version service requests is realized, and when the gray verification request in the gray instance machine is not passed, the rollback can be quickly performed, and the efficiency of the gray verification is improved. BRIEF DESCRIPTION OF DRAWINGS
[0050] Figure 1 is a device structure schematic diagram of a hardware running environment related to the embodiment of the application.
[0051] Figure 2 is a flowchart of the first embodiment of the gray release management method of the application.
[0052] Figure 3 is a flowchart of the third embodiment of the gray release management method of the application.
[0053] Figure 4 is a functional module schematic diagram of an embodiment of the gray release management device of the application.
[0054] The implementation, functional features and advantages of the application will be further described with reference to the embodiments and the accompanying drawings. DETAILED DESCRIPTION
[0055] It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.
[0056] As shown in Figure 1 , the Figure 1 is a device structure schematic diagram of a hardware running environment related to the embodiment of the application.
[0057] The gray release management device in the embodiment of the application can be a PC or a server device, and a Java virtual machine runs on the device.
[0058] As shown in Figure 1As shown in the figure, the gray release management device can include a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, and a communication bus 1002. The communication bus 1002 is used to realize the connection communication between the components. The user interface 1003 can include a display screen (Display), an input unit such as a keyboard (Keyboard), and the optional user interface 1003 can also include a standard wired interface, a wireless interface. The network interface 1004 can optionally include a standard wired interface, a wireless interface (such as a WI-FI interface). The memory 1005 can be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a magnetic disk memory. The memory 1005 can also be an independent storage device from the aforementioned processor 1001.
[0059] Those skilled in the art can understand that, Figure 1 The device structure shown in the figure does not constitute a limitation on the device, and can include more or fewer components than the figure, or combine certain components, or different component arrangements.
[0060] As Figure 1 As shown in the figure, the memory 1005 as a computer storage medium can include an operating system, a network communication module, a user interface module, and a gray release verification program.
[0061] In Figure 1 In the device shown in the figure, the network interface 1004 is mainly used to connect the background server and communicate data with the background server; the user interface 1003 is mainly used to connect the user end (user end) and communicate data with the user end; and the processor 1001 can be used to call the computer program stored in the memory 1005 corresponding to the gray release verification, and execute the operations in the following gray release management method.
[0062] Based on the above hardware structure, the gray release management method embodiment of the present application is proposed.
[0063] Referring to Figure 2 , Figure 2 The flowchart of the first embodiment of the gray release management method of the present application is shown. The method comprises:
[0064] Step S10, during the gray release, determining the gray verification example corresponding to the gray release, and the target APPID corresponding to the gray verification example.
[0065] The gray release management method in the embodiment is applied to a gray release management device. The gray release management device is used for version release of a service system with a large number of users. The gray release management device can be arranged in a financial institution, including a bank, an insurance institution, a securities institution, and the like. The bank is taken as an example for description. When the bank system is upgraded, all financial services do not need to be suspended. The gray release management method does not affect the normal financial services.
[0066] The gray release management device receives a gray release request. The triggering manner of the gray release request is not limited. That is, the gray release request can be triggered by a user, for example, a software developer triggers the gray release request by clicking a "version release" button of the gray release management device. Or, the gray release management device automatically triggers the gray release request, for example, the gray release management device automatically triggers the gray release request when receiving a new version code.
[0067] When the gray release request is received, the gray release management device determines a gray verification example corresponding to the gray release and a target APPID (application identification) corresponding to the gray verification example, so that the gray release management device determines the type of a service request according to the target APPID.
[0068] Specifically, after step S10, the method further includes the following steps.
[0069] In step a1, a business application corresponding to the gray release is determined, and the gray verification example is nested in the business application to form a target application to be released.
[0070] In step a2, when a version upgrade request sent by a target test terminal is received, the target application is sent to the target test terminal, so that the target test terminal triggers a service request carrying the target APPID based on the target application.
[0071] In the embodiment, after the gray release management device determines the gray verification example corresponding to the gray release, the gray release management device determines a business application corresponding to the gray release (the business application can be understood as a currently used old version application code). The gray release management device nests the gray verification example in the business application to form a target application to be released.
[0072] After the gray release management device generates the target application program, the gray release management device extracts part of users from the user group as target test users, and sends an upgrade prompt to the target test terminal corresponding to the target test user. The target test user triggers a version upgrade request in the target test terminal based on the upgrade prompt; when the gray release management device receives the version upgrade request sent by the target test terminal, the gray release management device sends the target application program to the target test terminal.
[0073] The target test user uses the target application program in the target test terminal, that is, the target test user triggers a business request based on the target application program, and the business request carries the target APPID. The target test terminal sends the business request to the gray release management device.
[0074] Step S20, when receiving the business request, acquiring the input parameter APPID corresponding to the business request.
[0075] The gray release management device receives the business request sent by the client. In this embodiment, the business request received by the gray release management device can include two types: one is that the target test user triggers a business request based on the target application program, and the other is that a user other than the target test user triggers a business request based on the business application program. The gray release management device determines the type of the business request by acquiring the input parameter APPID corresponding to the business request, so as to determine the processing step of the business request, that is,
[0076] Step S30, judging whether the business request is a gray verification request according to the target APPID and the input parameter APPID.
[0077] Specifically, including:
[0078] Step b1, comparing the target APPID with the input parameter APPID to judge whether the target APPID is same as the input parameter APPID;
[0079] Step b2, if the target APPID is same as the input parameter APPID, the business request is a gray verification request;
[0080] Step b3, if the target APPID is different from the input parameter APPID, the business request is not a gray verification request.
[0081] In this embodiment, the gray release management device compares the input parameter APPID corresponding to the business request with the target APPID, determines whether the business request is a gray verification request by judging whether the target APPID is same as the input parameter APPID, and allocates a business processing device for the business request. Specifically:
[0082] Step S40, if the service request is a gray verification request, the service request is sent to the gray instance machine to verify the service request by the gray instance machine.
[0083] In this embodiment, when the user quantity is large, multiple service processing machines are usually set to form a service machine group, and the load balancer balances the service quantity of each service processing machine in the service machine group. When the gray release is performed, one service processing machine in the service machine group is selected as a gray instance machine. When the gray release management device determines that the service request is a gray verification request, the gray release management device sends the gray verification request to the gray instance machine to verify the service request by the gray instance machine. In addition, when the gray release management device determines that the service request is not a gray verification request, the gray release management device sends the service request to a service processing machine other than the gray instance machine to process the service request by the service processing machine.
[0084] The technical solution in this embodiment is applied in the financial field. Under the premise of not affecting normal financial transactions, normal version release is realized. For example, when the bank system version is released, the gray release management device sets one service processing machine as a gray instance machine to process the gray verification request. It can be understood that the bank system corresponds to a load balancer and multiple service processing servers. The load balancer and the multiple service processing servers realize a distributed architecture. The load balancer is a master node, and the multiple service processing servers are slave nodes. The optional service processing servers have a master machine and a backup machine. In the case of master machine failure, the backup machine provides services.
[0085] In this embodiment, the gray release management device determines whether the service request is a gray verification request according to the APPID corresponding to the service request. When the service request is a gray verification request, the service request is sent to the gray instance machine to verify the service request by the gray instance machine. This avoids the problem that the influence range of users is large when an exception occurs in full release. It also avoids the problem that in random gray, both the upstream and the downstream are random gray instances, which leads to incomplete gray verification. This realizes comprehensive and convenient gray verification and improves the efficiency of gray verification.
[0086] Further, based on the first embodiment of the gray release management method of the present application, the second embodiment of the gray release management method of the present application is proposed.
[0087] In this embodiment, the gray release management device sets the traffic of the gray instance machine, so that the normal service processing is not affected during the gray release verification. Specifically,
[0088] In this embodiment, after step S10 of the first embodiment, the following steps are further included: determining the gray instance machine corresponding to the gray release, and adjusting the traffic weight of the gray instance machine from an initial value to a preset minimum value.
[0089] When the gray release management device receives the gray release request, a service processing machine in the service machine group is set as a gray instance machine. If each running parameter of the gray instance machine is kept unchanged, the gray instance machine needs to process both normal service requests and gray verification requests, which will increase the load of the gray instance machine. In addition, when the gray instance machine determines that the gray verification request fails to pass the verification, the rollback operation will be inconvenient.
[0090] For example, the service machine group includes five service processing machines, and the five service processing machines are equally divided into traffic. The traffic weights of the five service processing machines are 20:20:20:20:20. One gray instance machine in the five service processing machines needs to process both normal service requests sent by the load balancer and gray verification requests, which will increase the load of the gray instance machine. In addition, when the gray instance machine fails to pass the verification of the gray verification request, the gray instance machine includes both service requests and gray verification requests, which will make the rollback operation more troublesome.
[0091] To avoid the above situation, the gray release management device adjusts the traffic weight of the gray instance machine to a preset minimum value. The preset minimum value can be flexibly set according to specific conditions. For example, the preset minimum value is set to 0. In this embodiment, after the traffic weight of the gray instance machine is adjusted to the preset minimum value, the gray instance machine receives a small number of service requests sent by the load balancer or even zero, and the gray instance machine can focus on processing gray verification requests.
[0092] In this embodiment, after the gray release is completed, the gray release management device adjusts the traffic weight of the gray instance machine back to the initial value. After step S40 of the first embodiment, the method further includes the following steps.
[0093] Step S50: When the verification result fed back by the gray instance machine is received, it is determined whether the verification result is a verification pass.
[0094] The gray release management device receives the verification result fed back by the gray instance machine, and determines whether the verification result is a verification pass to determine the subsequent processing step, that is,
[0095] Step S60: If the verification result is a verification pass, full release is performed, and the traffic weight of the gray instance machine is adjusted back to the initial value.
[0096] If the verification result is a verification pass, the gray release management device performs full release on the target application program corresponding to the gray release. After the full release of the target application program, the gray release management device adjusts the traffic weight of the gray instance machine back to the initial value, which is the value before the traffic of the gray instance machine is adjusted.
[0097] In this embodiment, the gray release management device determines that the verification result is passed, and performs full release of the target application program, effectively avoiding the case that the target application program abnormally affects many customers. At the same time, the gray release management device adjusts the traffic weight of the gray instance machine back to the initial value, so that the gray instance machine normally processes business requests as a business processing machine, to ensure the processing efficiency of the business requests.
[0098] In step S70, if the verification result is not passed, the verification result is input into a preset report template to generate a gray verification report, and version rollback is performed.
[0099] If the verification result is not passed, the gray release management device inputs the verification result into a preset report template (the preset report template is a preset gray verification report template) to generate a gray verification report. In addition, the gray release management device acquires the business request corresponding to the target APPID in the gray instance machine, and rolls back the business corresponding to the business request.
[0100] In this embodiment, by setting the traffic weight of the gray instance machine, the gray instance machine can process the gray verification request when the gray release is performed without affecting the normal business process. When the gray release management device determines that the gray verification request is passed, full release is performed. When the gray release management device determines that the gray verification request is not passed, rollback can be quickly performed without affecting the normal business.
[0101] Further, with reference to Figure 3 , based on the above-mentioned embodiment of the gray release management method of the present application, the third embodiment of the gray release management method of the present application is proposed.
[0102] This embodiment is a step after step S30 in the first embodiment. In this embodiment, the processing mode of the gray release management device when the business request is not a gray verification request is specifically explained, which includes:
[0103] In step S80, if the business request is not a gray verification request, the business request is sent to a load balancer, and the business request is sent to other business processing machines except the gray instance machine through the load balancer, so that the business processing machines process the business request.
[0104] In the embodiment, when the gray release management device determines that the service request is not the gray verification request, the gray release management device sends the service request to the load balancer, and sends the service request to the other service processing machine except the gray instance machine through the load balancer, so that the service processing machine processes the service request. In the embodiment, during the gray release process, the normal business transaction is not affected, so that the gray release is more reasonable.
[0105] With reference to Figure 4 The application further provides a gray release management device, which comprises:
[0106] a release allocation module, configured to determine a gray verification instance corresponding to the gray release and a target APPID corresponding to the gray verification instance during the gray release;
[0107] a request receiving module, configured to acquire an input parameter APPID corresponding to a service request when the service request is received;
[0108] a request judging module, configured to judge whether the service request is a gray verification request according to the target APPID and the input parameter APPID;
[0109] a sending verification module, configured to send the service request to a gray instance machine to verify the service request through the gray instance machine if the service request is the gray verification request.
[0110] In an embodiment, the request judging module comprises:
[0111] an information comparing unit, configured to compare the target APPID with the input parameter APPID to judge whether the target APPID is same as the input parameter APPID;
[0112] a first judging unit, configured to judge that the service request is the gray verification request if the target APPID is same as the input parameter APPID;
[0113] a second judging unit, configured to judge that the service request is not the gray verification request if the target APPID is different from the input parameter APPID.
[0114] In an embodiment, the gray release management device further comprises:
[0115] determining a gray instance machine corresponding to the gray release, and adjusting a traffic weight of the gray instance machine from an initial value to a preset minimum value;
[0116] The gray release management device further comprises:
[0117] A result judging module is configured to judge whether the verification result is passed when the verification result fed back by the gray instance machine is received.
[0118] A second adjusting module is configured to perform full release and adjust the traffic weight of the gray instance machine back to the initial value if the verification result is passed.
[0119] In an embodiment, the gray release management apparatus further comprises:
[0120] A report generating module is configured to input the verification result into a preset report template, generate a gray verification report, and perform version rollback if the verification result is not passed.
[0121] In an embodiment, the gray release management apparatus comprises:
[0122] An example nesting module is configured to determine a business application corresponding to the gray release, and nest the gray verification example in the business application to form a target application to be released.
[0123] A program sending module is configured to send the target application to a target test terminal when receiving a version upgrade request sent by the target test terminal, so that the target test terminal triggers a business request carrying the target APPID based on the target application.
[0124] In an embodiment, the gray release management apparatus further comprises:
[0125] A sending executing module is configured to send the business request to a load balancer and send the business request to a business processing machine through the load balancer if the business request is not a gray verification request, so that the business processing machine processes the business request.
[0126] The method performed by each program module can refer to each embodiment of the gray release management method of the present application, and will not be repeated here.
[0127] The present application further provides a computer readable storage medium.
[0128] The gray release verification program is stored on the computer readable storage medium of the present application, and the gray release verification program is executed by a processor to implement the steps of the gray release management method as described above.
[0129] The method implemented when the gray release verification program running on the processor is executed can refer to each embodiment of the gray release management method of the present application, and will not be repeated here.
[0130] It should be noted that, in this document, the terms "comprises", "comprising", or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but can include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element preceded by "comprises... a" does not, without more constraints, foreclose the existence of additional identical elements in the process, method, article, or system that comprises the recited element.
[0131] The above-mentioned embodiment numbers of the present application are only for description, and do not represent the advantages and disadvantages of the embodiments.
[0132] From the above description of the embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be realized by means of software and the necessary general hardware platform, and of course, they can also be realized by hardware, but in many cases, the former is a better embodiment. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which is stored in a storage medium (such as a ROM / RAM, a magnetic disk, or an optical disk) as described above, and includes a number of instructions for making a terminal device (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of the present application.
[0133] The above is only the preferred embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent flow transformation made by using the content of the specification and drawings of the present application, or directly or indirectly applied to other related technical fields, are also included in the patent protection scope of the present application.
Claims
1. A gray release management method characterized by, The gray release management method comprises the following steps: When the gray release is performed, a gray verification example corresponding to the gray release is determined, and a target APPID corresponding to the gray verification example is determined; When a service request is received, an input parameter APPID corresponding to the service request is obtained; It is determined whether the service request is a gray verification request according to the target APPID and the input parameter APPID; If the service request is a gray verification request, the service request is sent to a gray instance machine, so that the service request is verified by the gray instance machine; the gray instance machine is determined from a service machine group; After the step of determining the gray verification example corresponding to the gray release and the target APPID corresponding to the gray verification example when the gray release is performed, the following steps are included: The gray instance machine corresponding to the gray release is determined, and the traffic weight of the gray instance machine is adjusted from an initial value to a preset minimum value; The business application corresponding to the gray release is determined, and the gray verification example is nested in the business application to form a target application to be released; When a version upgrade request sent by a target test terminal is received, the target application is sent to the target test terminal, so that the target test terminal triggers a service request carrying the target APPID based on the target application.
2. The gray release management method of claim 1, wherein, The step of determining whether the service request is a gray verification request according to the target APPID and the input parameter APPID comprises: The target APPID and the input parameter APPID are compared to determine whether the target APPID and the input parameter APPID are the same; If the target APPID and the input parameter APPID are the same, the service request is a gray verification request; If the target APPID and the input parameter APPID are different, the service request is not a gray verification request.
3. The gray scale release management method of claim 1, wherein, After the step of sending the service request to the gray instance machine to verify the service request by the gray instance machine if the service request is a gray verification request, the following steps are included: When the verification result fed back by the gray instance machine is received, it is determined whether the verification result is verified; If the verification result is verified, full release is performed, and the traffic weight of the gray instance machine is adjusted back to the initial value.
4. The gray-scale release management method of claim 3, wherein, After the step of determining whether the verification result is verified when the verification result fed back by the gray instance machine is received, the following steps are included: If the verification result is not verified, the verification result is input into a preset report template to generate a gray verification report, and version rollback is performed.
5. The gray-scale release management method according to any one of claims 1 to 4, characterized by, After the step of determining whether the service request is a gray verification request according to the target APPID and the input parameter APPID, the following steps are included: If the service request is not a gray verification request, the service request is sent to a load balancer, and the service request is sent to a business processing machine through the load balancer, so that the service request is processed by the business processing machine.
6. A gray release management apparatus characterized by comprising: The gray release management device comprises: The release allocation module is configured to determine a gray verification example corresponding to the gray release and a target APPID corresponding to the gray verification example during the gray release; The request receiving module is configured to acquire an input parameter APPID corresponding to a service request when the service request is received; The request judging module is configured to judge whether the service request is a gray verification request according to the target APPID and the input parameter APPID; The sending verification module is configured to send the service request to a gray instance machine to verify the service request by the gray instance machine if the service request is a gray verification request; the gray instance machine is determined from a service machine group; The example nesting module is configured to determine a business application corresponding to the gray release and nest the gray verification example in the business application to form a target application to be released; The program sending module is configured to send the target application to a target test terminal to make the target test terminal trigger a service request carrying the target APPID based on the target application when a version upgrade request sent by the target test terminal is received; The first adjusting module is configured to determine a gray instance machine corresponding to the gray release and adjust a traffic weight of the gray instance machine from an initial value to a preset minimum value.
7. The gray release management apparatus of claim 6, wherein The gray release management device comprises: The result judging module is configured to judge whether a verification result is passed when the verification result fed back by the gray instance machine is received; The second adjusting module is configured to perform full release and adjust the traffic weight of the gray instance machine back to the initial value if the verification result is passed.
8. A gray release management apparatus characterized by comprising: The gray release management device comprises a memory, a processor and a gray release verification program stored in the memory and executable on the processor, and the gray release verification program implements the steps of the gray release management method according to any one of claims 1 to 5 when executed by the processor.
9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a gray release verification program, and the gray release verification program implements the steps of the gray release management method according to any one of claims 1 to 5 when executed by the processor.
10. A computer program product, characterised in that, The computer program product stores instructions, and the instructions make the computer execute the steps of the gray release management method according to any one of claims 1 to 5 when the computer reads and executes the instructions.
Citation Information
Patent Citations
Application page switching method, apparatus and device
CN108595234A