WO2020181684A1 - Procédé, système, et dispositif de lancement nuancé et support d'informations - Google Patents

Procédé, système, et dispositif de lancement nuancé et support d'informations Download PDF

Info

Publication number
WO2020181684A1
WO2020181684A1 PCT/CN2019/092692 CN2019092692W WO2020181684A1 WO 2020181684 A1 WO2020181684 A1 WO 2020181684A1 CN 2019092692 W CN2019092692 W CN 2019092692W WO 2020181684 A1 WO2020181684 A1 WO 2020181684A1
Authority
WO
WIPO (PCT)
Prior art keywords
gray
release
scale
version
user
Prior art date
Application number
PCT/CN2019/092692
Other languages
English (en)
Chinese (zh)
Inventor
乐志能
Original Assignee
平安科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2020181684A1 publication Critical patent/WO2020181684A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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;
  • 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 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;
  • the gray release strategy includes one of the following items:
  • the configuration information includes at least one of the following items:
  • the release process is automatically triggered and all users are switched to the new version.
  • 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:
  • the gray-scale distribution ratio calculate The target quantity.
  • the method 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:
  • the gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
  • 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:
  • the gray-scale release management platform increases the initial gray-scale proportion according to the first proportion
  • 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.
  • 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;
  • the offloading engine is grouped according to at least one of the brand, model, operating system, or network type of the user terminal.
  • 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;
  • the user who is a gray-scale rule has the right to access the new version in the gray-scale server.
  • 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.
  • 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.
  • the release module is specifically used to:
  • the gray release strategy includes one of the following items:
  • the configuration information includes at least one of the following items:
  • the release process is automatically triggered and all users are switched to the new version.
  • the release module is specifically used for:
  • the gray-scale distribution ratio calculate The target quantity.
  • the grayscale release management platform sets the grayscale distribution ratio, it is also used to:
  • 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 gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
  • the gray release management platform is specifically used for:
  • the initial gray scale is adjusted upward according to the first proportion
  • 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 offloading engine uses at least one of the following grouping strategies to group users of each version:
  • Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;
  • grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.
  • the shunt engine is specifically used for:
  • the user who is a gray-scale rule has the right to access the new version in the gray-scale server.
  • control 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;
  • 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 processor is specifically configured to perform the following operations:
  • the gray release strategy includes one of the following items:
  • the configuration information includes at least one of the following items:
  • the release process is automatically triggered and all users are switched to the new version.
  • the processor is specifically configured to perform the following operations:
  • the gray-scale distribution ratio calculate The target quantity.
  • the processor is further used to perform the following operations before setting the gray-scale split ratio:
  • 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 gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
  • the processor is specifically used for:
  • the initial gray scale is adjusted upward according to the first proportion
  • 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 processor uses at least one of the following grouping strategies to group users of each version:
  • Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;
  • grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.
  • 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.
  • 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
  • FIG. 1 is a schematic diagram of a topology of a grayscale release management system in an embodiment of the application
  • FIG. 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.
  • 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.
  • this application mainly provides the following technical solutions:
  • the distribution module By first setting the grayscale distribution ratio, and then synchronize the set distribution ratio to the distribution module.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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
  • Nginx web proxy server
  • gray-scale load balancing gray-scale
  • the gray-scale release management platform sets a gray-scale split ratio, and synchronizes the gray-scale split ratio to a version issuing module.
  • the gray-scale distribution ratio is calculated by the gray-scale release management background, which can be an independently deployed server.
  • 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.
  • 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.
  • the method before the grayscale release management platform sets the grayscale split ratio, the method further includes:
  • 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.
  • 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 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.
  • 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:
  • 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.
  • 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.
  • 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.
  • 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.
  • 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;
  • the gray release strategy includes one of the following items:
  • the target grayscale server from the candidate grayscale servers to carry out the instruction information for batch grayscale release.
  • the default instructions for batch grayscale release are 30%, 30%, and 40% respectively.
  • the configuration information includes at least one of the following items:
  • the diversion strategy includes user scale, release frequency, function coverage, rollback strategy, operation strategy, and new and old system deployment strategy.
  • 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.
  • the release module 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.
  • 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.
  • the version issuing module selects a target grayscale server from the candidate grayscale servers.
  • the target grayscale server is used to perform grayscale release of a new version.
  • 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.
  • the version distribution module synchronizes the Internet Protocol IP address of the grayscale server that has been grayed out to the offloading engine.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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 Huawei 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.
  • 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.
  • 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 user 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.
  • 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.
  • 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 .
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the release module 302 is specifically configured to:
  • the gray release strategy includes one of the following items:
  • the configuration information includes at least one of the following items:
  • the release process is automatically triggered and all users are switched to the new version.
  • the release module 302 is specifically configured to:
  • the gray-scale distribution ratio calculate The target quantity.
  • the grayscale release management platform 301 sets the grayscale split ratio, it is also used to:
  • 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 gray level distribution ratio adapted to the current gray level publishing is dynamically adjusted.
  • the gray release management platform 301 is specifically used for:
  • the initial gray scale is adjusted upward according to the first proportion
  • 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 offloading engine 303 uses at least one of the following grouping strategies to group users of each version:
  • Grouping according to at least one of the IP address of the user terminal, whitelist, user tag, business field or service channel;
  • grouping is performed according to at least one of the brand, model, operating system, or network type of the user terminal.
  • the shunt engine 303 is specifically used for:
  • the user who is a gray-scale rule has the right to access the new version in the gray-scale server.
  • 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.
  • the computer program may be a program corresponding to the method for managing grayscale release in the embodiment corresponding to FIG. 1.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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. ⁇
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention se rapporte au domaine technique du lancement nuancé et concerne un procédé, appareil, dispositif et système de gestion de lancement de version nuancé. Le procédé consiste : par une plateforme de gestion de lancement nuancé, à définir une proportion de distribution nuancée et à synchroniser la proportion de distribution nuancée avec un module de lancement de version ; lorsque le lancement de version est mené à bien, à calculer, par le module de lancement de version, le nombre cible de serveurs de lancement nuancé candidats en fonction de la proportion de distribution nuancée et du nombre de serveurs de production ; à sélectionner, par le module de lancement de version, un serveur de lancement nuancé cible parmi les serveurs de lancement nuancé candidats, et après la publication d'une nouvelle version, à synchroniser, par le module de lancement de version, l'adresse IP du serveur de lancement nuancé qui a mené à bien le lancement à destination d'un moteur de distribution ; et à répartir, par le moteur de distribution, les utilisateurs de chaque version en une pluralité de groupes d'utilisateurs en fonction de la proportion de distribution nuancée et des adresses IP du serveur de lancement nuancé et à mener à bien un marquage par catégorie, à confirmer la catégorie de serveur correspondant à chaque groupe d'utilisateurs, et à distribuer des flux de données de service de différentes versions aux groupes d'utilisateurs correspondants en fonction des catégories des groupes d'utilisateurs auxquels appartiennent les utilisateurs. L'utilisation de la solution permet la réalisation d'une distribution intelligente et la réduction de la probabilité de défaillance associée à distribution manuelle.
PCT/CN2019/092692 2019-03-12 2019-06-25 Procédé, système, et dispositif de lancement nuancé et support d'informations WO2020181684A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910182457.1 2019-03-12
CN201910182457.1A CN110071960A (zh) 2019-03-12 2019-03-12 管理灰度发布的方法、系统、设备及存储介质

Publications (1)

Publication Number Publication Date
WO2020181684A1 true WO2020181684A1 (fr) 2020-09-17

Family

ID=67366158

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/092692 WO2020181684A1 (fr) 2019-03-12 2019-06-25 Procédé, système, et dispositif de lancement nuancé et support d'informations

Country Status (2)

Country Link
CN (1) CN110071960A (fr)
WO (1) WO2020181684A1 (fr)

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112035126A (zh) * 2020-09-22 2020-12-04 北京百度网讯科技有限公司 用于灰度发布的处理方法和装置、电子设备和存储介质
CN112346738A (zh) * 2020-11-30 2021-02-09 深圳市欧瑞博科技股份有限公司 智能灰度发布方法、装置、电子设备及存储介质
CN112433749A (zh) * 2020-11-24 2021-03-02 中国建设银行股份有限公司 一种应用的灰度发布方法和装置、服务器、客户端
CN112486560A (zh) * 2020-11-24 2021-03-12 云南电网有限责任公司信息中心 一种应用资源拓扑管理系统
CN112650523A (zh) * 2020-12-02 2021-04-13 青岛海尔科技有限公司 用于灰度发布的数据分流方法及装置、设备
CN112653579A (zh) * 2020-12-16 2021-04-13 中国人寿保险股份有限公司 一种基于OpenResty的灰度发布方法及相关设备
CN112685060A (zh) * 2020-12-24 2021-04-20 深圳前海微众银行股份有限公司 灰度发布方法、装置，终端设备及计算机存储介质
CN112835606A (zh) * 2021-03-31 2021-05-25 中国工商银行股份有限公司 灰度发布方法、装置、电子设备、介质和程序产品
CN112835617A (zh) * 2021-03-02 2021-05-25 北京字节跳动网络技术有限公司 一种灰度发布方法、装置、服务器及可读介质
CN112905210A (zh) * 2021-03-24 2021-06-04 青岛聚看云科技有限公司 服务器及灰度发布方法
CN113138774A (zh) * 2021-05-11 2021-07-20 中国工商银行股份有限公司 灰度发布方法、装置、电子设备、介质和程序产品
CN113282326A (zh) * 2021-06-21 2021-08-20 多点生活(成都)科技有限公司 灰度升级的方法、装置、电子设备和可读存储介质
CN113377381A (zh) * 2021-06-30 2021-09-10 北京百度网讯科技有限公司 小程序包的分发方法、装置、电子设备和介质
CN113391823A (zh) * 2021-06-15 2021-09-14 中国工商银行股份有限公司 灰度发布方法、装置及系统
CN113542387A (zh) * 2021-07-09 2021-10-22 平安银行股份有限公司 系统发布方法、装置、电子设备及存储介质
CN113676549A (zh) * 2021-09-02 2021-11-19 京东科技信息技术有限公司 应用请求的分流方法及应用网关、电子设备、存储介质
CN113760316A (zh) * 2020-10-22 2021-12-07 北京沃东天骏信息技术有限公司 一种应用的配置系统和方法
CN114363343A (zh) * 2021-12-30 2022-04-15 上海浦东发展银行股份有限公司 基于微服务架构的请求数据处理方法、装置、计算机设备
CN114390105A (zh) * 2022-03-01 2022-04-22 阿里巴巴（中国）有限公司 基于测试的企业用户分流方法及设备
CN114553855A (zh) * 2020-11-25 2022-05-27 北京奇艺世纪科技有限公司 插件灰度发布方法、装置、电子设备及存储介质
CN114579162A (zh) * 2022-05-07 2022-06-03 杭州又拍云科技有限公司 一种基于事件驱动和水平触发的灰度发布方法
CN114968274A (zh) * 2022-07-29 2022-08-30 之江实验室 一种基于灰度发布的自动化快速部署前置机的方法及系统
CN116578335A (zh) * 2023-07-13 2023-08-11 建信金融科技有限责任公司 灰度发布系统、方法、设备、介质及产品
CN117170718A (zh) * 2023-11-02 2023-12-05 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110633207A (zh) * 2019-08-14 2019-12-31 平安普惠企业管理有限公司 基于灰度测试的操作请求处理方法、系统和计算机设备
CN110688134B (zh) * 2019-08-29 2023-02-17 创新先进技术有限公司 灰度发布的方法及装置
CN110609701A (zh) * 2019-08-29 2019-12-24 凡普数字技术有限公司 提供服务的方法、装置和存储介质
CN110798502B (zh) * 2019-09-18 2022-06-17 平安科技（深圳）有限公司 基于微服务框架的灰度发布方法、装置和计算机设备
CN110716730B (zh) * 2019-10-14 2023-09-26 网易（杭州）网络有限公司 灰度发布方法、装置、设备及计算机可读存储介质
CN110784530A (zh) * 2019-10-22 2020-02-11 聚好看科技股份有限公司 灰度的发布方法和服务器
CN110928555B (zh) * 2019-11-21 2023-04-18 广州品唯软件有限公司 一种灰度发布控制方法、装置、计算机设备及存储介质
CN111104634B (zh) * 2019-12-20 2023-08-29 北京达佳互联信息技术有限公司 灰度用户的方法、服务器及存储介质
CN111488159A (zh) * 2019-12-20 2020-08-04 杭州当虹科技股份有限公司 一种能够动态配置的灰度发布方法
CN111338824B (zh) * 2020-02-27 2023-08-15 中国联合网络通信集团有限公司 灰度发布方法、装置、电子设备及存储介质
CN111290779B (zh) * 2020-03-04 2023-07-07 北京三快在线科技有限公司 灰度发布方法、装置、存储介质和电子设备
CN111399875B (zh) * 2020-03-06 2023-09-05 咪咕文化科技有限公司 灰度升级控制方法、装置、电子设备及存储介质
CN111464520B (zh) * 2020-03-26 2022-12-09 银联商务股份有限公司 一种数据处理方法、装置、存储介质及电子设备
CN112187662B (zh) * 2020-09-16 2023-03-28 银盛支付服务股份有限公司 一种基于Apollo的流量分发方法
CN112114869A (zh) * 2020-09-18 2020-12-22 聚好看科技股份有限公司 一种服务器、灰度发布方法、装置及介质
CN112162762B (zh) * 2020-10-16 2024-04-02 中国工商银行股份有限公司 灰度发布方法、灰度发布装置和电子设备
CN112346777A (zh) * 2020-11-20 2021-02-09 浙江百应科技有限公司 一种应用程序平滑发布方法及装置
CN112506559B (zh) * 2020-12-14 2024-02-06 招商局金融科技有限公司 基于网关的灰度发布方法、装置、电子设备及存储介质
CN112732274B (zh) * 2021-01-08 2024-06-04 上海汇付支付有限公司 基于灰度发布的容器应用发布方法以及管理平台
CN113051182B (zh) * 2021-04-30 2024-02-09 中国工商银行股份有限公司 一种基于分布式事务的灰度发布方法、装置及设备
CN113435782A (zh) * 2021-07-15 2021-09-24 支付宝(杭州)信息技术有限公司 业务变更方法及装置
CN113434432B (zh) * 2021-07-20 2022-11-08 北京百度网讯科技有限公司 一种推荐平台的性能测试方法、装置、设备、及介质
CN114217821A (zh) * 2022-02-21 2022-03-22 深圳市秦丝科技有限公司 多服务器代码灰度发布方法、装置、电子设备及存储介质
CN115408285B (zh) * 2022-08-31 2023-06-20 北京发现角科技有限公司 一种灰度测试方法、装置、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105099988A (zh) * 2014-04-24 2015-11-25 阿里巴巴集团控股有限公司 用于支持灰度发布的方法、访问方法以及装置和系统
CN105955761A (zh) * 2016-06-30 2016-09-21 乐视控股（北京）有限公司 基于docker的灰度发布装置及方法
CN108768875A (zh) * 2018-05-31 2018-11-06 康键信息技术（深圳）有限公司 应用的灰度发布方法、装置及计算机可读存储介质

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105335204A (zh) * 2014-07-29 2016-02-17 株式会社日立制作所 软件程序的灰度发布控制方法和灰度发布控制装置
CN104881734A (zh) * 2015-05-11 2015-09-02 广东小天才科技有限公司 一种基于灰度发布引导产品改进的方法、装置及系统
CN106066791A (zh) * 2016-05-25 2016-11-02 合网络技术（北京）有限公司 应用的灰度发布方法及装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105099988A (zh) * 2014-04-24 2015-11-25 阿里巴巴集团控股有限公司 用于支持灰度发布的方法、访问方法以及装置和系统
CN105955761A (zh) * 2016-06-30 2016-09-21 乐视控股（北京）有限公司 基于docker的灰度发布装置及方法
CN108768875A (zh) * 2018-05-31 2018-11-06 康键信息技术（深圳）有限公司 应用的灰度发布方法、装置及计算机可读存储介质

Cited By (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112035126B (zh) * 2020-09-22 2023-10-20 北京百度网讯科技有限公司 用于灰度发布的处理方法和装置、电子设备和存储介质
CN112035126A (zh) * 2020-09-22 2020-12-04 北京百度网讯科技有限公司 用于灰度发布的处理方法和装置、电子设备和存储介质
CN113760316A (zh) * 2020-10-22 2021-12-07 北京沃东天骏信息技术有限公司 一种应用的配置系统和方法
CN112433749A (zh) * 2020-11-24 2021-03-02 中国建设银行股份有限公司 一种应用的灰度发布方法和装置、服务器、客户端
CN112486560A (zh) * 2020-11-24 2021-03-12 云南电网有限责任公司信息中心 一种应用资源拓扑管理系统
CN112486560B (zh) * 2020-11-24 2023-09-29 云南电网有限责任公司信息中心 一种应用资源拓扑管理系统
CN114553855B (zh) * 2020-11-25 2024-04-05 北京奇艺世纪科技有限公司 插件灰度发布方法、装置、电子设备及存储介质
CN114553855A (zh) * 2020-11-25 2022-05-27 北京奇艺世纪科技有限公司 插件灰度发布方法、装置、电子设备及存储介质
CN112346738A (zh) * 2020-11-30 2021-02-09 深圳市欧瑞博科技股份有限公司 智能灰度发布方法、装置、电子设备及存储介质
CN112650523A (zh) * 2020-12-02 2021-04-13 青岛海尔科技有限公司 用于灰度发布的数据分流方法及装置、设备
CN112650523B (zh) * 2020-12-02 2023-06-16 青岛海尔科技有限公司 用于灰度发布的数据分流方法及装置、设备
CN112653579B (zh) * 2020-12-16 2023-05-23 中国人寿保险股份有限公司 一种基于OpenResty的灰度发布方法及相关设备
CN112653579A (zh) * 2020-12-16 2021-04-13 中国人寿保险股份有限公司 一种基于OpenResty的灰度发布方法及相关设备
CN112685060A (zh) * 2020-12-24 2021-04-20 深圳前海微众银行股份有限公司 灰度发布方法、装置，终端设备及计算机存储介质
CN112835617B (zh) * 2021-03-02 2024-04-02 北京字节跳动网络技术有限公司 一种灰度发布方法、装置、服务器及可读介质
CN112835617A (zh) * 2021-03-02 2021-05-25 北京字节跳动网络技术有限公司 一种灰度发布方法、装置、服务器及可读介质
CN112905210B (zh) * 2021-03-24 2023-09-15 青岛聚看云科技有限公司 服务器及灰度发布方法
CN112905210A (zh) * 2021-03-24 2021-06-04 青岛聚看云科技有限公司 服务器及灰度发布方法
CN112835606B (zh) * 2021-03-31 2024-01-30 中国工商银行股份有限公司 灰度发布方法、装置、电子设备、介质
CN112835606A (zh) * 2021-03-31 2021-05-25 中国工商银行股份有限公司 灰度发布方法、装置、电子设备、介质和程序产品
CN113138774B (zh) * 2021-05-11 2024-02-09 中国工商银行股份有限公司 灰度发布方法、装置、电子设备和介质
CN113138774A (zh) * 2021-05-11 2021-07-20 中国工商银行股份有限公司 灰度发布方法、装置、电子设备、介质和程序产品
CN113391823A (zh) * 2021-06-15 2021-09-14 中国工商银行股份有限公司 灰度发布方法、装置及系统
CN113282326B (zh) * 2021-06-21 2023-05-16 多点生活(成都)科技有限公司 灰度升级的方法、装置、电子设备和可读存储介质
CN113282326A (zh) * 2021-06-21 2021-08-20 多点生活(成都)科技有限公司 灰度升级的方法、装置、电子设备和可读存储介质
CN113377381A (zh) * 2021-06-30 2021-09-10 北京百度网讯科技有限公司 小程序包的分发方法、装置、电子设备和介质
CN113377381B (zh) * 2021-06-30 2023-11-14 北京百度网讯科技有限公司 小程序包的分发方法、装置、电子设备和介质
CN113542387B (zh) * 2021-07-09 2023-07-04 平安银行股份有限公司 系统发布方法、装置、电子设备及存储介质
CN113542387A (zh) * 2021-07-09 2021-10-22 平安银行股份有限公司 系统发布方法、装置、电子设备及存储介质
CN113676549A (zh) * 2021-09-02 2021-11-19 京东科技信息技术有限公司 应用请求的分流方法及应用网关、电子设备、存储介质
CN114363343B (zh) * 2021-12-30 2024-04-30 上海浦东发展银行股份有限公司 基于微服务架构的请求数据处理方法、装置、计算机设备
CN114363343A (zh) * 2021-12-30 2022-04-15 上海浦东发展银行股份有限公司 基于微服务架构的请求数据处理方法、装置、计算机设备
CN114390105A (zh) * 2022-03-01 2022-04-22 阿里巴巴（中国）有限公司 基于测试的企业用户分流方法及设备
CN114579162A (zh) * 2022-05-07 2022-06-03 杭州又拍云科技有限公司 一种基于事件驱动和水平触发的灰度发布方法
CN114579162B (zh) * 2022-05-07 2022-08-23 杭州又拍云科技有限公司 一种基于事件驱动和水平触发的灰度发布方法
CN114968274A (zh) * 2022-07-29 2022-08-30 之江实验室 一种基于灰度发布的自动化快速部署前置机的方法及系统
CN116578335B (zh) * 2023-07-13 2023-10-03 建信金融科技有限责任公司 灰度发布系统、方法、设备、介质及产品
CN116578335A (zh) * 2023-07-13 2023-08-11 建信金融科技有限责任公司 灰度发布系统、方法、设备、介质及产品
CN117170718A (zh) * 2023-11-02 2023-12-05 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备
CN117170718B (zh) * 2023-11-02 2024-02-02 绿城科技产业服务集团有限公司 基于微服务架构的灰度发布方法、装置及电子设备

Also Published As

Publication number Publication date
CN110071960A (zh) 2019-07-30

Similar Documents

Publication Publication Date Title
WO2020181684A1 (fr) Procédé, système, et dispositif de lancement nuancé et support d'informations
US11277306B2 (en) Sending information of a network repository function instance storing network function instance information
CN110061871B (zh) 基站开站方法、装置、计算机存储介质及设备
EP3373518B1 (fr) Procédé et dispositif de configuration de service pour service de réseau
CN110474794B (zh) 一种sdn架构的信息转换方法和系统
CN109429277A (zh) 网络切片的选择方法、装置及系统
CN109995588B (zh) 一种灵活以太网链路管理方法及系统
CN110290168B (zh) 数据发送方法、装置、服务器及存储介质
CN110768889A (zh) 一种vxlan隧道的构建方法及系统
WO2021136233A1 (fr) Procédé, dispositif et système de mise à niveau de service
CN106487538A (zh) 业务提速方法、策略控制平台以及系统
CN104427557B (zh) 用于控制QoS策略冲突的方法、设备和系统
US7254628B2 (en) Network management system with validation of policies
WO2021012588A1 (fr) Procédé et système d'établissement d'un canal de gestion ethernet flexible
CN110620811A (zh) 一种vOLT集群架构下ONU管理方法及系统
CN114422440B (zh) 灰度发布方法、装置、电子设备及存储介质
CN111464889B (zh) 一种通道带宽调整方法及系统
CN109951324A (zh) 一种网板隔离实现方法及装置
CN112256658B (zh) 日志记录的分流方法及装置、存储介质、电子装置
CN112492643B (zh) 基于多链路的数据转发方法、装置及终端设备
US9160811B2 (en) Client provisioning with enhanced linking
CN110753277B (zh) 一种在olt网络切片中配置管理的方法及系统
US10103897B2 (en) Method and apparatus for managing subscription to a policy counter
CN100401681C (zh) 一种配置业务框数据的实现方法
KR20170057770A (ko) 가상 스위치의 패킷 전송 제어 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19918893

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19918893

Country of ref document: EP

Kind code of ref document: A1