WO2020181684A1

WO2020181684A1 - Grayscale release management method, system and device, and storage medium

Info

Publication number: WO2020181684A1
Application number: PCT/CN2019/092692
Authority: WO
Inventors: 乐志能
Original assignee: 平安科技（深圳）有限公司
Priority date: 2019-03-12
Filing date: 2019-06-25
Publication date: 2020-09-17
Also published as: CN110071960A

Abstract

The present application relates to the technical field of grayscale release, and provides a grayscale release management method, apparatus, device and system. The method comprises: a grayscale release management platform setting a grayscale distribution proportion, and synchronizing the grayscale distribution proportion to a version release module; when version release is carried out, the version release module calculating the target number of candidate grayscale servers according to the grayscale distribution proportion and the number of production servers; the version release module selecting a target grayscale server from among the candidate grayscale servers, and after a new version is published, the version release module synchronizing the IP address of the grayscale server that has carried out grayscale release to a distribution engine; and the distribution engine dividing users of each version into a plurality of user groups according to the grayscale distribution proportion and the IP addresses of the grayscale server and carrying out category marking, confirming the server category corresponding to each user group, and distributing service data streams of different versions to the corresponding user groups according to the categories of the user groups to which the users belong. By using the solution, intelligent distribution can be realized, and the failure probability of manual distribution can be reduced.

Description

Method, system, equipment and storage medium for managing gray release

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office, the application number is 201910182457.1, and the invention title is "Methods, systems, equipment and storage media for managing gray release" on March 12, 2019. The reference is incorporated in this application.

Technical field

This application relates to the technical field of gray-scale publishing, and in particular, to a method, system, device, and storage medium for managing gray-scale publishing.

Background technique

Gray release refers to a release method that can smoothly transition between black and white. A/B testing can be performed on it, that is, some users continue to use product feature A, and some users start to use product feature B. If users have no objections to B, then gradually expand the scope and move all users to B. Come. Grayscale release can ensure the stability of the overall system, and problems can be found and adjusted during the initial grayscale to ensure product impact.

Currently in the market for grayscale releases, the administrator sets the number of grayscale servers and production servers. After determining the user scale that the number of grayscale servers can carry, set the maximum grayscale ratio when performing the grayscale setting, such as Set up 2 gray-scale servers and 10 production servers. Then, when performing gray-scale publishing, first publish to these two gray-scale servers, allowing up to 20% of user traffic to be switched to the gray-scale environment.

However, the inventor found that when setting this gray scale ratio, it is necessary to clarify the number of gray scale servers before calculating the gray scale. The gray scale cannot be adjusted adaptively based on user feedback, and the gray scale can only be manually determined. The number of degree servers then calculates the gray scale, which is inefficient and leads to untimely user traffic switching; secondly, the gray scale is completely dependent on the calculation of the manager, and if the calculation is wrong, it will cause production failure.

Summary of the invention

This application provides a method, system, device and storage medium for managing gray release, which can solve the technical defects proposed in the prior art.

In the first aspect, the present application provides a method for managing gray release, and the method includes:

The gray level release management platform sets the gray level diversion ratio, and synchronizes the gray level diversion ratio to the release module;

When the version is issued, the version distribution module calculates the target number of candidate grayscale servers for this grayscale release according to the grayscale diversion ratio and the current number of production servers;

The version distribution module selects a target grayscale server from the candidate grayscale servers, and the target grayscale server is used to perform a grayscale release of a new version;

After the target grayscale server completes the release of the new version, the version release module synchronizes the Internet Protocol IP address of the grayscale server that has been grayed out to the offload engine;

The offloading engine groups the users of each version according to the grayscale offload ratio and the IP address of the grayscale server undertaking this grayscale publishing task to obtain multiple user groups, and mark each user group as a category, And confirm the server category corresponding to each user group;

The distribution engine distributes service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.

In a possible design, the version distribution module calculates the target number of candidate grayscale servers for this grayscale release based on the grayscale split ratio and the current number of production servers, including:

The version distribution module calculates the target number according to the gray-scale publishing strategy, the gray-scale distribution ratio and the current number of production servers;

Wherein, the gray release strategy includes one of the following items:

Instruction information for selecting the target gray server from the candidate gray server for batch gray release;

Or, the interval length of each gray-scale release and the configuration information of the countermeasures when the release is abnormal, the configuration information includes at least one of the following items:

If the release of the version is abnormal, execute the switching and shunt strategy;

If an exception occurs during the release process, it will be suspended or rolled back;

If the verification is passed, the release process is automatically triggered and all users are switched to the new version.

In a possible design, the version distribution module calculates the target number according to the gray-scale publishing strategy, the gray-scale distribution ratio and the current number of production servers, including:

According to the gray-scale release strategy, the gray-scale distribution ratio, the number of current production servers, the number of current user visits, the total number of users using this production service, the number of users using the old version, and the number of users using the new version, calculate The target quantity.

In a possible design, before the grayscale release management platform sets the grayscale split ratio, the method further includes:

The gray release management platform obtains information fed back by users, and the information fed back by users includes information fed back by users using the new version of the application, normal service information or abnormal service information;

The gray-scale release management platform sets an initial gray-scale ratio and a gray-scale release strategy, and the gray-scale release strategy refers to a gray-scale release according to a preset period and a preset gray-scale ratio until all versions are released;

The grayscale distribution management platform setting the grayscale distribution ratio includes:

According to the information fed back by the user and the gray level publishing strategy, the gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.

In a possible design, the gray-scale release management platform dynamically adjusts the gray-scale distribution ratio adapted to the current gray-scale release according to the information fed back by the user and the gray-scale release strategy, including:

If the proportion of normal service information fed back by the user is within the first numerical interval, the gray-scale release management platform increases the initial gray-scale proportion according to the first proportion;

If the ratio of the normal service information fed back by the user is within the second numerical interval, the gray-scale release management platform will increase the initial gray-scale ratio according to the second ratio; the first ratio is smaller than the second ratio, and the first The upper bound of a numerical interval is smaller than the lower bound of the second numerical interval.

In a possible design, at least one of the following grouping strategies is adopted when the users of each version are grouped:

The distribution engine divides users of the same version or users whose version is lower than the new version into a user group;

The offloading engine performs grouping according to at least one of the IP address, white list, user tag, service field, or service channel of the user terminal;

Alternatively, the offloading engine is grouped according to at least one of the brand, model, operating system, or network type of the user terminal.

In a possible design, the shunt engine shunts service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs, including:

The offloading engine offloads the old version of the business data to the user group that is not grayed out rules, and offloads the new version of the business data to the user group that is grayed out rules;

If the user is a user who is a gray-scale rule, the user who is a gray-scale rule has the right to access the new version in the gray-scale server.

In the second aspect, the present application provides a gray-scale release management system, which has the function of implementing the method corresponding to the method for managing gray-scale release provided in the first aspect. The functions can be realized by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, and the modules may be software and/or hardware.

In a possible design, the gray release management system includes:

The gray-scale release management platform is used to set the gray-scale distribution ratio, and synchronize the gray-scale distribution ratio to the version distribution module;

The version distribution module is used to calculate the target number of candidate grayscale servers for this grayscale release based on the grayscale split ratio and the current number of production servers when the version is issued; Select the target gray-scale server from the degree server, and the target gray-scale server is used for gray-scale publishing of a new version; after the target gray-scale server completes the release of the new version, the gray-scale that has been The Internet Protocol IP address of the server is synchronized to the offload engine;

The distribution engine is used to group users of each version to obtain multiple user groups according to the gray distribution ratio synchronized by the version distribution module and the IP address of the gray server that is responsible for this gray distribution task. Mark the category for each user group and confirm the server category corresponding to each user group;

The offloading engine is also used to offload service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.

In some possible designs, the release module is specifically used to:

Calculating the target number according to the gray-level publishing strategy, the gray-level distribution ratio and the current number of production servers;

Wherein, the gray release strategy includes one of the following items:

In a possible design, the release module is specifically used for:

In a possible design, before the grayscale release management platform sets the grayscale distribution ratio, it is also used to:

Acquiring information fed back by the user, the information fed back by the user including the information fed back by the user using the new version of the application, service normal information or service abnormal information;

Set the initial gray scale and gray scale release strategy, the gray scale release strategy refers to the gray scale release according to the preset cycle and preset gray scale until all versions are released;

In a possible design, the gray release management platform is specifically used for:

If the proportion of normal service information fed back by the user is within the first numerical interval, the initial gray scale is adjusted upward according to the first proportion;

If the proportion of the normal service information fed back by the user is in the second numerical interval, the initial gray scale is adjusted upward according to the second proportion; the first proportion is less than the second proportion, the upper bound of the first numerical interval Less than the lower bound of the second numerical interval.

In a possible design, the offloading engine uses at least one of the following grouping strategies to group users of each version:

Divide users of the same version or users whose version is lower than the new version into a user group;

Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;

Or, grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.

In a possible design, the shunt engine is specifically used for:

Distribute the business data of the old version to the user group that has not been grayed out rules, and divert the business data of the new version to the user group that is grayed out rules;

Another aspect of the present application provides a computer device, which includes at least one connected processor, a memory, a transmitter, and a receiver, wherein the memory is used to store program codes, and the processor is used to call The program code to perform the following operations;

Set the gray-scale split ratio, and synchronize the gray-scale split ratio to the version issuing module;

When issuing a version, control the version-issuing module to calculate the target number of candidate gray-scale servers for this gray-scale release according to the gray-scale split ratio and the number of current production servers; from the candidate gray-scale servers Select the target gray-scale server in the gray-scale server, and the target gray-scale server is used for gray-scale release of a new version; after the target gray-scale server completes the release of the new version, the The Internet Protocol IP address is synchronized to the offload engine;

According to the synchronized gray distribution ratio and the IP address of the gray server responsible for the gray release task, the users of each version are grouped to obtain multiple user groups, and each user group is marked with a category, and each user group is confirmed The server category corresponding to the user group;

The distribution engine is controlled to distribute service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.

In a possible design, the processor is specifically configured to perform the following operations:

Wherein, the gray release strategy includes one of the following items:

In a possible design, the processor is further used to perform the following operations before setting the gray-scale split ratio:

In a possible design, the processor is specifically used for:

In a possible design, the processor uses at least one of the following grouping strategies to group users of each version:

Another aspect of the present application provides a volatile computer storage medium, which includes instructions, which when run on a computer, cause the computer to execute the methods described in the foregoing aspects.

Compared with the prior art, in the solution provided by the present application, the gray-scale release management platform sets the gray-scale distribution ratio, and synchronizes the gray-scale distribution ratio to the plate-issuing module; when the plate is issued, the plate-issuing module divides according to the gray level Calculate the target number of candidate grayscale servers based on the ratio and the number of production servers; the release module selects the target grayscale server from the candidate grayscale servers, and after the new version is released, the release module will publish the grayscale server's IP The address is synchronized to the offloading engine; the offloading engine divides the users of each version into multiple user groups according to the grayscale offload ratio and the IP address of the grayscale server and marks the category, confirms the server category corresponding to each user group, and according to the user belongs to The category of the user group, which divides the business data streams of different versions to the corresponding user group. The application can adaptively adjust the gray scale according to user feedback, automatically count the current number of gray servers and calculate the gray scale, improve the efficiency of gray release and switch user traffic in a timely manner.

Description of the drawings

FIG. 1 is a schematic diagram of a topology of a grayscale release management system in an embodiment of the application;

2 is a schematic flowchart of a method for managing gray release in an embodiment of the application;

FIG. 3 is a schematic diagram of a structure of a gray-scale release management system according to an embodiment of the application;

Fig. 4 is a schematic diagram of a structure of a computer device in an embodiment of the application.

The realization, functional characteristics, and advantages of the purpose of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

detailed description

It should be understood that the specific embodiments described herein are only used to explain the application, and not used to limit the application. The terms "first", "second", etc. in the description and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances so that the embodiments described herein can be implemented in an order other than the content illustrated or described herein. In addition, the terms "including" and "having" and any variations of them are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or modules is not necessarily limited to the clearly listed Those steps or modules may include other steps or modules that are not clearly listed or are inherent to these processes, methods, products, or equipment. The division of modules in this application is only a logical division In actual applications, there may be other divisions in implementation. For example, multiple modules may be combined or integrated in another system, or some features may be ignored or not implemented.

This application provides a method, system, equipment and storage medium for managing gray release, which can be used for the testing and release of new products, to obtain early user feedback, improve product functions, improve product quality, and allow users to participate in product testing, and strengthen and User interaction to reduce the range of users affected by product upgrades.

To solve the above technical problems, this application mainly provides the following technical solutions:

By first setting the grayscale distribution ratio, and then synchronize the set distribution ratio to the distribution module. When the distribution is performed, the distribution module reads the set distribution ratio, and then calculates the required grayscale based on the number of existing production servers. Degree server, and then select the gray server to release the new version in gray. After the new version is released, synchronize the host of the server with gray release to the offloading engine, and then if the user is a user who is subject to the gray rule, you can access Grayscale server, to access the new version in Grayscale server.

Subsequent managers who want to continue to modify the shunt ratio use the same process to synchronize the new gray-scale shunt ratio to the release module, and the release module recalculates the servers that need grayscale according to the ratio (if the shunt ratio is reduced compared to the original, It will roll back the original gray-scale server to the production server), and then synchronize the result to the offloading engine.

A gray-scale release management system (also referred to as a gray-scale system) as shown in FIG. 1 includes a gray-scale release management platform, a release module, and a distribution engine. Among them, the gray release management platform can be used to release the version to the designated server, and return the release progress and release log to the release module. The release module can be used to select the gray release strategy (also called the gray release rule), display the reason for the failure to release, display the release progress, and display the release log of the gray server. The distribution engine can be used to switch the traffic of the production server to the gray server, verify whether there is any traffic in the release window, and determine whether the release is allowed.

In this application, the shunt engine can use the following two access methods: one is http access, which is developed using a scripting language (such as lua), and is based on a web proxy server (such as Nginx) for grayscale; the other It is a dubbo access method, developed by java, and uses gray-scale load balancing to achieve gray-scale. This application does not limit the access mode of the offload engine. The release management platform, release module, and distribution engine in this application can be deployed centrally or separately. This application does not limit the deployment of the gray release management system.

Referring to Fig. 2, the following describes a method for managing gray release in this application, and the method includes:

201. The gray-scale release management platform sets a gray-scale split ratio, and synchronizes the gray-scale split ratio to a version issuing module.

Among them, the gray-scale distribution ratio is calculated by the gray-scale release management background, which can be an independently deployed server.

In some embodiments, the gray-scale distribution ratio is generally set by the application publisher, for example, different gray-scale distribution ratios are set according to the current application version, and the gray-scale distribution ratio is restricted in combination with information such as the current number of production servers.

In this application, the release module refers to the release tool of the operation and maintenance personnel, which can automatically deploy the program package to the server. The release module will receive instructions from the grayscale platform, and calculate the need according to the shunt ratio set by the grayscale platform Distribute the version to several production servers, and after the completion of the version, the results will be synchronized to the gray management platform.

In some implementation manners, before the grayscale release management platform sets the grayscale split ratio, the method further includes:

1. Obtain user feedback information. The user feedback information includes user feedback information using the new version of the application, service normal information or service abnormal information; wherein the user feedback information includes user feedback using the new version of the application information. User feedback information is collected and managed by the gray management platform.

2. Set the initial gray scale and gray scale release strategy. The gray scale release strategy refers to the gray scale release according to the preset cycle and preset gray scale until all versions are released.

When setting the grayscale release strategy, you can perform grayscale at 10% per hour, and then all versions will be automatically released after 10 hours.

Correspondingly, when the gray distribution management platform sets the gray distribution ratio, the gray distribution ratio suitable for the current gray distribution can be dynamically adjusted according to the information fed back by the user and the gray distribution strategy.

In some implementation manners, the dynamically adjusting the gray-scale distribution ratio adapted to the current gray-scale publishing according to the information fed back by the user and the gray-scale publishing strategy includes:

If the proportion of normal service information fed back by the user is within the first numerical interval, the initial gray scale will be increased according to the first proportion; for example, when the normal proportion of the normal service information fed back is 60%-80%, the initial Increase the gray scale by 2 points.

If the proportion of the normal service information fed back by the user is in the second numerical interval, the initial gray scale is increased according to the second proportion; the first proportion is less than the second proportion, and the upper bound of the first numerical interval is less than The lower bound value of the second numerical interval. For example, when the normal ratio of the service normal information fed back is 80%-100%, the initial gray scale ratio is increased by 10 points.

It can be seen that when the information fed back by the user includes normal service information or abnormal service information, the degree of the initial gray scale is determined by a preset up- or down-adjustment method, which can achieve the smoothness of partial or full switching of user traffic, and achieve no Seamless switching and gradual release, leaving users unaware.

202. When a version is issued, the version distribution module calculates the target number of candidate grayscale servers for this grayscale release according to the grayscale distribution ratio and the current number of production servers.

In some embodiments, the version distribution module calculates the target number of candidate grayscale servers for this grayscale release based on the grayscale split ratio and the current number of production servers, including:

Wherein, the gray release strategy includes one of the following items:

1. Select the target grayscale server from the candidate grayscale servers to carry out the instruction information for batch grayscale release. For example, the default instructions for batch grayscale release are 30%, 30%, and 40% respectively.

2. The interval length of each gray-scale release and the configuration information of countermeasures when the release is abnormal.

In some implementation manners, the configuration information includes at least one of the following items:

(1) If the release of the version is abnormal, execute the switching and diversion strategy, the diversion strategy includes user scale, release frequency, function coverage, rollback strategy, operation strategy, and new and old system deployment strategy.

(2) If an exception occurs during the release process, the suspension or rollback to the original version. For example, the current production server deploys version 4.1. If the sound field server is selected as the target gray server to deploy version 4.2, if there is an interruption in the release process, it will roll back to version 4.1.

(3) If the verification is passed, the release process is automatically triggered and all users are switched to the new version.

In other implementations, when the release module calculates the target number of candidate grayscale servers, in addition to introducing the number of production servers and the grayscale distribution ratio, it can also introduce the current user's visits, the total number of users using the production service, and Dimensional information such as the number of users of the old version and the new version, and other dimensional information, so as to improve accuracy and allocate server resources reasonably. Specifically, the version release module may also be based on the gray-scale release strategy, the gray-scale split ratio, the number of current production servers, the current user’s access volume, the total number of users using this production service, and the number of users using the old version. The number of users, the number of users of the new version, and the target number are calculated.

203. The version issuing module selects a target grayscale server from the candidate grayscale servers.

Wherein, the target grayscale server is used to perform grayscale release of a new version.

In some embodiments, when selecting a target grayscale server, a candidate grayscale server with lighter load or strong hardware capability may be selected as the target grayscale server from the candidate grayscale servers based on a load balancing strategy.

204. After the target grayscale server completes the release of the new version, the version distribution module synchronizes the Internet Protocol IP address of the grayscale server that has been grayed out to the offloading engine.

In some implementations, when a new version is released, Nginx configuration files + LUA scripts may be used to achieve gray-scale publishing, to achieve gray-scale publishing based on cookies, or to achieve gray-scale publishing based on source IP addresses. Taking the cookie method as an example, the cookie key is queried according to the value of the version of the cookie; if the cookie value is V1, the user traffic is diverted to the server corresponding to hi-linux_01; if the cookie value is V2, the user traffic is diverted to The server corresponding to hi-linux_02; if the cookie values do not match, the user traffic will be diverted to the server corresponding to hi-linux_01 by default.

205. The distribution engine groups users of each version according to the gray distribution ratio and the IP address of the gray server that is responsible for the gray distribution task to obtain multiple user groups, and mark each user group Category, and confirm the server category corresponding to each user group.

In some implementation manners, at least one of the following grouping strategies is adopted when the users of each version are grouped:

The shunt engine divides users of the same version or users whose version is lower than the new version into a user group; for example, a game company has updated the game version, and the current new version is version 4.2. The current user level of the game company on the market is different. 1. Some users are subjectively unwilling to update due to the limited hardware of the terminal. Therefore, the versions of this game still circulating on the market are 3.0, 3.2, 4.0 and 4.1, and 3.0, 3.2, 4.0 and 4.1 are all lower than the current ones. Version 4.2 to be released. Since each production server only provides one game version service, in order to facilitate group release and group management, users who use version 3.0, version 3.2, version 4.0 and version 4.1 need to be divided into an independent user group. .

The offloading engine performs grouping according to at least one of the IP address of the user terminal, white list, user tag, business field, user common function or service channel; wherein, the white list refers to a white list composed of users with gray rules . User tags refer to tags labeled for users who use different versions. Business fields include voice services, video services, short message services, financial services, or government services. Service channels refer to the channels through which business services are provided, such as securities services or banking services.

Alternatively, the offloading engine is grouped according to at least one of the brand, model, operating system, or network type of the user terminal. The operating systems include Android system, Windows system, IOS system, Linux system and other operating systems, and this application does not limit the operating system. The network types include network types of network standards such as China Mobile, China Telecom, and China Unicom, and this application does not limit network types and operators. For example, taking Xiaomi mobile phones as an example, when grouping according to mobile phone models, users who use MIX2S and users who use 6X will be divided into different user groups; grouping according to network type, that is, GSM, CDMA, 3G, 4G will be used respectively Users of network standards such as 5G are divided into different user groups.

206. The shunt engine shunts service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.

In some implementation manners, the offloading engine offloads service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs, including:

Distribute the old version of the business data to the user group that has not been grayed out, and divert the new version of the business data to the user group that is grayed out. If the user is a user who is a gray-scale rule, the user who is a gray-scale rule has the right to access the new version in the gray-scale server. Users who are under the gray-scale rule can also be referred to as users in the gray-scale list. The users in the gray-scale list enjoy the new version of the service, which is not limited in this application.

Compared with existing mechanisms, on the one hand, this application can adaptively adjust the gray scale according to user feedback, automatically count the current number of gray servers and calculate the gray scale, and realize intelligent shunting without human intervention. Gray-scale server, thereby improving the efficiency of gray-scale publishing and switching user traffic in a timely manner. Since the gray scale is adaptively adjusted and user feedback is introduced, it can improve the accuracy of calculating the gray scale, avoid the problem of production failure due to the calculation of the gray scale, and reduce the accident caused by the error of the gray scale diversion personnel .

On the other hand, the grayscale release of this application is to directly perform the grayscale release on the original production server, and there is no need to build a new grayscale server. Therefore, after adjusting the distribution ratio, the distribution ratio will be distributed on the original production server. Select multiple production servers corresponding to the number of production servers for grayscale release.

The technical features mentioned in the respective embodiments or implementations corresponding to FIGS. 1 and 2 described above are also applicable to the embodiments corresponding to FIGS. 3 and 4 in this application, and similarities are not repeated here.

The foregoing describes a method for managing gray release in this application, and the following describes a system for executing the foregoing method for managing gray release.

As shown in FIG. 3, a schematic structural diagram of a gray release management system 30, which can be applied to the testing and release of new products. The gray-scale release management system 30 in the embodiment of the present application can implement the steps in the method for managing gray-scale release executed in the embodiment corresponding to FIG. 1 above. The functions implemented by the gray release management system 30 can be implemented by hardware, or implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions, and the modules may be software and/or hardware. The gray release management system 30 may include a gray release management platform 301, a release module 302, and a distribution engine 303. The functions of the gray release management platform 301, the release module 302, and the distribution engine 303 are implemented Reference may be made to the operations performed in the embodiment corresponding to FIG. 1, which will not be repeated here.

In some embodiments, the gray-scale release management platform 301 can be used to set the gray-scale distribution ratio, and synchronize the gray-scale distribution ratio to the version issuing module 302;

The version distribution module 302 can be used to calculate the target number of candidate grayscale servers for this grayscale release based on the grayscale distribution ratio and the current number of production servers when the version is issued; Select the target gray-scale server from the degree server, and the target gray-scale server is used for gray-scale publishing of a new version; after the target gray-scale server completes the release of the new version, the gray-scale that has been The Internet Protocol IP address of the server is synchronized to the offloading engine 303;

The distribution engine 303 can be used to group users of each version to obtain multiple user groups according to the gray distribution ratio synchronized by the release module and the IP address of the gray server that is responsible for this gray distribution task. Mark the category for each user group and confirm the server category corresponding to each user group;

The offloading engine 303 is also used to offload service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.

In the embodiment of the present application, the gray-scale release management platform 301 synchronizes the set gray-scale distribution ratio to the version-issuing module 302; when the version is issued, the version-issuance module 302 calculates candidates based on the gray-level distribution ratio and the number of production servers The target number of grayscale servers, select the target grayscale server from the candidate grayscale servers, and after the new version is released, the release module 302 synchronizes the IP address of the grayscale server that has been released to the offload engine 303; offload engine 303 Divide the users of each version into multiple user groups and mark the categories according to the gray distribution ratio and the IP address of the gray server, confirm the server category corresponding to each user group, and divide the different versions according to the category of the user group to which the user belongs The business data stream is diverted to the corresponding user group. With this solution, the gray scale can be adjusted adaptively based on user feedback, and the current number of gray scale servers can be automatically counted and the gray scale calculated. Intelligent distribution is realized, and no human intervention is required to set up gray scale servers, thereby improving the gray scale release. Efficiently and timely switch user traffic, reducing the probability of manual diversion errors.

In some implementation manners, the release module 302 is specifically configured to:

Wherein, the gray release strategy includes one of the following items:

In some implementation manners, before the grayscale release management platform 301 sets the grayscale split ratio, it is also used to:

In some embodiments, the gray release management platform 301 is specifically used for:

In some implementation manners, the offloading engine 303 uses at least one of the following grouping strategies to group users of each version:

In some implementation manners, the shunt engine 303 is specifically used for:

The above describes the gray release management system 30 in the embodiment of the present application from the perspective of modular functional entities. The following describes a computer device from the perspective of hardware, as shown in FIG. 4, which includes: a processor, a memory, and a transceiver (It may also be an input and output unit, not identified in FIG. 4) and a computer program stored in the memory and running on the processor. For example, the computer program may be a program corresponding to the method for managing grayscale release in the embodiment corresponding to FIG. 1. For example, when a computer device implements the functions of the gray-scale release management system 30 as shown in FIG. 3, the processor executes the computer program to realize the execution by the gray-scale release management system 30 in the embodiment corresponding to FIG. 3 above. Each step in the method for managing gray release; or, when the processor executes the computer program, the function of each module in the gray release management system 30 of the embodiment corresponding to FIG. 3 is realized. For another example, the computer program may be a program corresponding to the method for managing grayscale release in the embodiment corresponding to FIG. 1.

The so-called processor can be a central processing unit (Central Processing Unit, CPU), other general-purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), ready-made Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The processor is the control center of the computer equipment, and various interfaces and lines are used to connect various parts of the entire computer equipment.

The memory may be used to store the computer program and/or module, and the processor implements the computer by running or executing the computer program and/or module stored in the memory, and calling data stored in the memory. Various functions of the device. The memory may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.); the storage data area may store Data created based on the use of mobile phones (such as audio data, video data, etc.), etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disks, memory, plug-in hard disks, smart media cards (SMC), and secure digital (SD) cards , Flash Card, at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The transceiver can also be replaced by a receiver and a transmitter, and can be the same or different physical entities. When they are the same physical entity, they can be collectively referred to as transceivers. The transceiver can be an input and output unit.

The memory may be integrated in the processor, or may be provided separately from the processor.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of this application essentially or the part that contributes to the existing technology can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM/RAM), including Several instructions are used to make a terminal (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the method described in each embodiment of the present application.

The embodiments of the present application are described above with reference to the accompanying drawings, but the present application is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art are Under the enlightenment of this application, without departing from the purpose of this application and the scope of protection of the claims, many forms can be made, any equivalent structure or equivalent process transformation made by using the content of the description and drawings of this application, or Directly or indirectly used in other related technical fields, these are all protected by this application.

Claims

A method for managing gray release, the method comprising:

The gray level release management platform sets the gray level diversion ratio, and synchronizes the gray level diversion ratio to the release module;

When the version is issued, the version distribution module calculates the target number of candidate grayscale servers for this grayscale release according to the grayscale split ratio and the current number of production servers;

The version distribution module selects a target grayscale server from the candidate grayscale servers, and the target grayscale server is used to perform a grayscale release of a new version;

After the target grayscale server completes the release of the new version, the version release module synchronizes the Internet Protocol IP address of the grayscale server that has been grayed out to the offload engine;

The offloading engine groups the users of each version according to the grayscale offload ratio and the IP address of the grayscale server undertaking this grayscale publishing task to obtain multiple user groups, and mark each user group as a category, And confirm the server category corresponding to each user group;

The distribution engine distributes service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.
The method according to claim 1, wherein the version distribution module calculates the target number of candidate grayscale servers for this grayscale release based on the grayscale diversion ratio and the current number of production servers, including:

The version distribution module calculates the target number according to the gray-scale publishing strategy, the gray-scale distribution ratio and the current number of production servers;

Wherein, the gray release strategy includes one of the following items:

Instruction information for selecting the target gray server from the candidate gray server for batch gray release;

Or, the interval length of each gray-scale release and the configuration information of the countermeasures when the release is abnormal, the configuration information includes at least one of the following items:

If the release of the version is abnormal, execute the switching and shunt strategy;

If an exception occurs during the release process, it will be suspended or rolled back;

If the verification is passed, the release process is automatically triggered and all users are switched to the new version.
The method according to claim 2, wherein the version distribution module calculates the target number according to the gray-level publishing strategy, the gray-level distribution ratio and the current number of production servers, including:

According to the gray-scale release strategy, the gray-scale distribution ratio, the number of current production servers, the number of current user visits, the total number of users using this production service, the number of users using the old version, and the number of users using the new version, calculate The target quantity.
The method according to claim 2 or 3, before the gray-scale release management platform sets the gray-scale split ratio, the method further comprises:

The gray release management platform obtains information fed back by users, and the information fed back by users includes information fed back by users using the new version of the application, normal service information or abnormal service information;

Set the initial gray scale and gray scale release strategy, the gray scale release strategy refers to the gray scale release according to the preset cycle and preset gray scale until all versions are released;

The grayscale distribution management platform setting the grayscale distribution ratio includes:

The gray-scale release management platform dynamically adjusts the gray-scale distribution ratio adapted to the current gray-scale release according to the information fed back by the user and the gray-scale release strategy.
The method according to claim 4, wherein the grayscale release management platform dynamically adjusts the grayscale distribution ratio adapted to the current grayscale release according to the information fed back by the user and the grayscale release strategy, including:

If the proportion of normal service information fed back by the user is within the first numerical interval, the gray-scale release management platform increases the initial gray-scale proportion according to the first proportion;

If the ratio of the normal service information fed back by the user is within the second numerical interval, the gray-scale release management platform will increase the initial gray-scale ratio according to the second ratio; the first ratio is smaller than the second ratio, and the first The upper bound of a numerical interval is smaller than the lower bound of the second numerical interval.
The method according to claim 5, wherein at least one of the following grouping strategies is adopted when the users of each version are grouped:

The distribution engine divides users of the same version or users whose version is lower than the new version into a user group;

The offloading engine performs grouping according to at least one of the IP address, white list, user tag, service field, or service channel of the user terminal;

Alternatively, the offloading engine is grouped according to at least one of the brand, model, operating system, or network type of the user terminal.
According to the method of claim 6, the offloading engine offloads service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs, including:

The offloading engine offloads the old version of the business data to the user group that is not under the grayscale rule, and offloads the new version of the business data to the user group that is the grayscale rule;

If the user is a user who is a gray-scale rule, the user who is a gray-scale rule has the right to access the new version in the gray-scale server.
A gray-scale release management system, the system includes:

The gray-scale release management platform is used to set the gray-scale distribution ratio, and synchronize the gray-scale distribution ratio to the version distribution module;

The version distribution module is used to calculate the target number of candidate grayscale servers for this grayscale release based on the grayscale split ratio and the current number of production servers when the version is issued; Select the target gray-scale server from the degree server, and the target gray-scale server is used for gray-scale publishing of a new version; after the target gray-scale server completes the release of the new version, the gray-scale that has been The Internet Protocol IP address of the server is synchronized to the offload engine;

The distribution engine is used to group users of each version to obtain multiple user groups according to the gray distribution ratio synchronized by the version distribution module and the IP address of the gray server that is responsible for this gray distribution task. Mark the category for each user group and confirm the server category corresponding to each user group;

The offloading engine is also used to offload service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.
According to the method of claim 8, the release module is specifically configured to:

Calculating the target number according to the gray-level publishing strategy, the gray-level distribution ratio and the current number of production servers;

Wherein, the gray release strategy includes one of the following items:

Instruction information for selecting the target gray server from the candidate gray server for batch gray release;

Or, the interval length of each gray-scale release and the configuration information of the countermeasures when the release is abnormal, the configuration information includes at least one of the following items:

If the release of the version is abnormal, execute the switching and shunt strategy;

If an exception occurs during the release process, it will be suspended or rolled back;

If the verification is passed, the release process is automatically triggered and all users are switched to the new version.
According to the method of claim 9, the release module is specifically configured to:

According to the gray-scale release strategy, the gray-scale distribution ratio, the number of current production servers, the number of current user visits, the total number of users using this production service, the number of users using the old version, and the number of users using the new version, calculate The target quantity.
According to the method of claim 9 or 10, before the gray-scale release management platform sets the gray-scale distribution ratio, it is further used for:

Acquiring information fed back by the user, the information fed back by the user including the information fed back by the user using the new version of the application, service normal information or service abnormal information;

Set the initial gray scale and gray scale release strategy, the gray scale release strategy refers to the gray scale release according to the preset cycle and preset gray scale until all versions are released;

According to the information fed back by the user and the gray level publishing strategy, the gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
According to the method of claim 11, the gray release management platform is specifically configured to:

If the proportion of normal service information fed back by the user is within the first numerical interval, the initial gray scale is adjusted upward according to the first proportion;

If the proportion of the normal service information fed back by the user is in the second numerical interval, the initial gray scale is adjusted upward according to the second proportion; the first proportion is less than the second proportion, the upper bound of the first numerical interval Less than the lower bound of the second numerical interval.
According to the method of claim 12, the distribution engine uses at least one of the following grouping strategies to group users of each version:

Divide users of the same version or users whose version is lower than the new version into a user group;

Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;

Or, grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.
A computer device, the computer device includes:

At least one processor, memory and transceiver;

Wherein, the memory is used to store program code, and the processor is used to call the program code stored in the memory to perform the following operations;

Set the gray-scale split ratio, and synchronize the gray-scale split ratio to the version issuing module;

When issuing a version, control the version-issuing module to calculate the target number of candidate gray-scale servers for this gray-scale release according to the gray-scale split ratio and the number of current production servers; from the candidate gray-scale servers Select the target gray-scale server in the gray-scale server, and the target gray-scale server is used for gray-scale release of a new version; after the target gray-scale server completes the release of the new version, the The Internet Protocol IP address is synchronized to the offload engine;

According to the synchronized gray distribution ratio and the IP address of the gray server responsible for the gray release task, the users of each version are grouped to obtain multiple user groups, and each user group is marked with a category, and each user group is confirmed The server category corresponding to the user group;

The distribution engine is controlled to distribute service data streams of different versions to corresponding user groups according to the category of the user group to which the user belongs.
The device according to claim 14, wherein the processor is specifically configured to perform the following operations:

Calculating the target number according to the gray-level publishing strategy, the gray-level distribution ratio and the current number of production servers;

Wherein, the gray release strategy includes one of the following items:

Instruction information for selecting the target gray server from the candidate gray server for batch gray release;

Or, the interval length of each gray-scale release and the configuration information of the countermeasures when the release is abnormal, the configuration information includes at least one of the following items:

If the release of the version is abnormal, execute the switching and shunt strategy;

If an exception occurs during the release process, it will be suspended or rolled back;

If the verification is passed, the release process is automatically triggered and all users are switched to the new version.
The device according to claim 15, wherein the processor is specifically configured to perform the following operations:

According to the gray-scale release strategy, the gray-scale distribution ratio, the number of current production servers, the number of current user visits, the total number of users using this production service, the number of users using the old version, and the number of users using the new version, calculate The target quantity.
The device according to claim 15 or 16, wherein the processor is further configured to perform the following operations before setting the gray scale split ratio:

Acquiring information fed back by the user, the information fed back by the user including the information fed back by the user using the new version of the application, service normal information or service abnormal information;

Set the initial gray scale and gray scale release strategy, the gray scale release strategy refers to the gray scale release according to the preset cycle and preset gray scale until all versions are released;

According to the information fed back by the user and the gray level publishing strategy, the gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
The device according to claim 17, wherein the processor is specifically configured to:

If the proportion of normal service information fed back by the user is within the first numerical interval, the initial gray scale is adjusted upward according to the first proportion;

If the proportion of the normal service information fed back by the user is in the second numerical interval, the initial gray scale is adjusted upward according to the second proportion; the first proportion is less than the second proportion, the upper bound of the first numerical interval Less than the lower bound of the second numerical interval.
The device according to claim 18, wherein the processor uses at least one of the following grouping strategies to group users of each version:

Divide users of the same version or users whose version is lower than the new version into a user group;

Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;

Or, grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.
A non-volatile computer storage medium, which includes instructions, which when run on a computer, causes the computer to execute the method according to any one of claims 1-7.