Gray scale changing method and device, computer device and storage medium

Abstract

The application relates to a gray scale changing method and device, computer equipment and a storage medium. The method comprises the following steps: automatically grouping a plurality of to-be-changed objects based on a grouping label, sorting the plurality of to-be-changed objects in a grouping list according to a specified sorting label, determining an execution batch list to which the to-be-changed object belongs according to the sorting proportion of the to-be-changed object in the grouping list, and changing the gray scale of the to-be-changed objects in different execution batch lists in different execution orders, so that the plurality of to-be-changed objects are automatically batched and changed in gray scale, the diversity of object types in each execution batch list is ensured, the comprehensiveness of changing the gray scale of all to-be-changed objects in each execution batch list is ensured as much as possible, the method is more scientific and comprehensive compared with manual batching, and the object batching efficiency is improved, so that the gray scale changing efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a grayscale change method, apparatus, computer equipment, and storage medium. Background Technology

[0002] With the development of the Internet, software will also iterate and change according to user needs. Gray-scale change refers to gradually changing the new version of the software instead of changing it all at once. In this way, the development team can test the new features of the software, monitor the performance of the new version, and ensure that everything is running normally.

[0003] When software, services, or servers integrating multiple software need to undergo large-scale or even full-scale changes or upgrades, it is necessary to implement them in batches in order to control risks. However, currently, the process relies on manual batching of the objects to be changed, and then implementing them in batches, which results in low efficiency of gray-scale changes. Summary of the Invention

[0004] This application provides a grayscale change method, apparatus, computer equipment, and storage medium to solve the problem of low efficiency in grayscale change caused by manually performing grayscale changes in batches on objects to be changed.

[0005] In order to solve the above-mentioned technical problems, or at least partially solve the above-mentioned technical problems, this application provides a grayscale change method, apparatus, computer equipment and storage medium.

[0006] On the one hand, this application provides a grayscale change method, the method further comprising:

[0007] Obtain an object list, grouping tags, and batching information, wherein the object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list;

[0008] The multiple objects to be changed are grouped according to the grouping labels to obtain multiple group lists;

[0009] The objects to be changed in the group list are sorted according to the specified sorting labels to obtain the sorting list corresponding to the group list, and the sorting percentage of each object to be changed in the corresponding sorting list.

[0010] Based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, determine the execution batch list corresponding to the object to be changed, and add the object to be changed to the corresponding execution batch list;

[0011] According to the execution order corresponding to each execution batch list, the objects to be changed in each execution batch list are processed in a grayscale manner.

[0012] On the other hand, this application provides a grayscale changing device, the grayscale changing device comprising:

[0013] The acquisition module is used to acquire an object list, grouping tags, and batching information. The object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list.

[0014] The grouping module is used to group multiple objects to be changed according to the grouping labels to obtain multiple group lists;

[0015] The sorting module is used to sort each of the objects to be changed in the group list according to a specified sorting label, so as to obtain a sorting list corresponding to the group list and the sorting percentage of each object to be changed in the corresponding sorting list.

[0016] The batching module is used to determine the execution batch list corresponding to each object to be changed based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, and to add the object to be changed to the corresponding execution batch list.

[0017] The execution module is used to perform grayscale change processing on the objects to be changed in each of the execution batch lists in the order corresponding to each execution batch list.

[0018] On the other hand, a computer device is provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0019] Memory, used to store computer programs;

[0020] When a processor executes a program stored in memory, it implements the steps of the grayscale change method described in the first aspect.

[0021] On the other hand, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the grayscale change method as described in the first aspect.

[0022] On the other hand, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the grayscale change method as described in the first aspect.

[0023] The method provided in this application embodiment obtains an object list, grouping tags, and batching information. The object list includes multiple objects to be modified, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list. The method involves grouping the multiple objects to be modified according to the grouping tags to obtain multiple group lists; sorting each object to be modified within the group lists according to a specified sorting tag to obtain a sorting list corresponding to the group lists, and the sorting percentage of each object to be modified in the corresponding sorting list; determining the execution batch list corresponding to each object to be modified based on the percentage range of the sorting percentage of each object to be modified in the corresponding sorting list, and adding the object to be modified to the corresponding execution batch list; and performing grayscale modification processing on the objects to be modified in each execution batch list sequentially according to the execution order corresponding to each execution batch list.

[0024] Based on the above method, multiple objects to be modified are automatically grouped using grouping tags, and then sorted according to specified sorting tags within the group list. The execution batch list to which each object belongs is determined by its ranking proportion within the group list. Different execution batch lists correspond to different execution orders. Objects to be modified at different sorting positions in each group list will undergo gray-scale modification in different execution batch lists according to different execution orders. This achieves automatic batch gray-scale modification of multiple objects to be modified, while ensuring the diversity of object types in each execution batch list. This ensures the comprehensiveness of gray-scale modification of all objects to be modified in each execution batch list as much as possible. Compared with manual batching, this method is more scientific and comprehensive, and improves the efficiency of object batching, thereby improving the efficiency of gray-scale modification. This can solve the problem of low gray-scale modification efficiency caused by manual batching of objects to be modified. Attached Figure Description

[0025] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0026] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1A flowchart illustrating a grayscale change method provided in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram illustrating the effect of the grouping list provided in the embodiments of this application;

[0029] Figure 3 A schematic diagram of a grayscale changing device provided in an embodiment of this application.

[0030] Figure 4 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0031] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0032] In one embodiment, Figure 1 This is a flowchart illustrating a grayscale change method in one embodiment, referencing... Figure 1 This paper provides a method for grayscale changeover. This embodiment primarily illustrates the application of this method to a server, and the grayscale changeover method specifically includes the following steps:

[0033] Step S210: Obtain the object list, grouping tags, and batching information. The object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list.

[0034] Specifically, the objects to be changed are retrieved from the Configuration Management Database (CMDB). The CMDB stores information about all configuration items in the IT system. Objects stored in the CMDB include hardware, software, network devices, servers, applications, and documents. Objects in the CMDB can be tagged using at least one method, such as the operations and maintenance system, agent reporting, log analysis, or manual intervention. Tags are column key-value pairs, including a tag name and a tag value. Tag names include, but are not limited to, server type, operating system version, region, importance level, deployment method, application type, and programming language. A tag structure might be: Server Type: S1, Application Type: Front-end Service, Region: Guangzhou Zone 1, Programming Language: JAVA, Importance Level: Core, Module: Insurance. Tag names and values ​​with the same meaning are identical. Objects to be changed are those that have already been tagged and require gradual rollout. Grouping tags must include at least one tag, and grouping tags are used to group multiple tagged objects to be changed.

[0035] The batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, the percentage range corresponding to each execution batch list, and the grayscale ratio corresponding to each execution batch list. The number of batches in the execution batch list is the number of batches. The execution batch list is the execution list corresponding to the grayscale execution batches. Each grayscale execution batch corresponds to one execution list. The execution order of different grayscale execution batches is different, and the percentage range corresponding to different execution batch lists is different. The percentage range is determined by the grayscale ratio corresponding to the execution batch list. The sum of the grayscale ratios corresponding to all execution batch lists is 1, that is, the upper limit of the percentage range corresponding to the last batch of execution batch lists is 100%. The number of batches in the execution batch list and the percentage range corresponding to each execution batch list are pre-configured and can be customized and adjusted according to different application scenarios.

[0036] For example, a batch size of 6 indicates 6 grayscale execution batches, with each batch corresponding to a grayscale percentage of (5%, 15%, 20%, 20%, 20%, 20%). Therefore, the percentage range for the first grayscale execution batch is [0%-5%], the second batch is (5%-20%), the third batch is (20%-40%), the fourth batch is (40%-60%), the fifth batch is (60%-80%), and the sixth batch is (80%-100%). The execution order is from the first to the sixth batch, meaning the first batch is executed first and the sixth batch is executed last. Subsequently, the objects to be changed are added to the execution batch list corresponding to their respective percentage ranges, thus achieving batch processing of each object to be changed in different group lists.

[0037] Step S220: Group the multiple objects to be changed according to the grouping labels to obtain multiple group lists.

[0038] Specifically, based on the tag values ​​corresponding to all tags in the group label, multiple objects to be changed with the same group are grouped into a group list. Objects to be changed with the same tag name and tag value as the group label are grouped into another group list. For example, refer to... Figure 2 The grouping tags include three tags: model, region, and module. Since each tag may have multiple tag values, it is necessary to group the objects to be changed that have the same tag values ​​for model, region, and module into a single group list. That is, multiple objects to be changed with the model S1, region Guangzhou Zone 1, and module insurance should be grouped into a single group list. Figure 2 Data objects with different background colors correspond to different group lists.

[0039] Step S230: Sort each of the objects to be changed in the group list according to the specified sorting label to obtain the sorting list corresponding to the group list, and the sorting percentage of each object to be changed in the corresponding sorting list.

[0040] Specifically, the specified sorting label can be any label name, which can be customized according to the actual application. Different sorting labels correspond to different sorting methods, which are either ascending or descending. Based on the sorting list, the sorting percentage of each object to be changed in the sorting list is determined. The sorting percentage is the ratio between the sorting position of the object to be changed in the sorting list and the total number of objects in the sorting list.

[0041] Step S240: Determine the execution batch list corresponding to the object to be changed based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, and add the object to be changed to the corresponding execution batch list.

[0042] Specifically, the execution batch list corresponding to the percentage range to which the sorting percentage belongs is determined as the execution batch list to which the corresponding object to be changed belongs. Objects to be changed that are in different sorting positions in the same sorting list belong to different gray-scale execution batches, while objects to be changed that correspond to the same sorting percentage in different sorting lists belong to the execution list corresponding to the same gray-scale execution batch. This can ensure that each execution batch list covers as many objects to be changed in different grouping labels as possible, and ensure that the gray-scale coverage of each execution batch list is relatively comprehensive.

[0043] Step S250: According to the execution order corresponding to each execution batch list, perform grayscale change processing on the objects to be changed in each execution batch list in turn.

[0044] Specifically, different execution batch lists correspond to different execution orders. That is, different execution batch lists correspond to different execution batches. The execution batch list with the first item in the execution order is the first batch execution batch list, and the execution batch list with the last item in the execution order is the last batch execution batch list. According to the execution order corresponding to each execution batch list, the objects to be changed in each execution batch list are processed in a gray-scale manner. This realizes the automatic batch gray-scale change of multiple objects to be changed, and ensures the diversity of object types in each execution batch list. This ensures the comprehensiveness of gray-scale change of all objects to be changed in each execution batch list as much as possible. Compared with manual batching, it is more scientific and more comprehensive, and improves the efficiency of object batching, thereby improving the efficiency of gray-scale change. This can solve the problem of low gray-scale change efficiency caused by manual batching of objects to be changed.

[0045] In one embodiment, obtaining the list of objects includes:

[0046] Select data objects in the configuration management database that meet the preset filtering criteria as objects to be changed;

[0047] The object list is composed of multiple objects to be changed.

[0048] Specifically, preset filtering conditions are used to filter within the configuration management database. These conditions can be flexibly defined by setting SQL query criteria or through the database's interface parameters. For example, setting `where zone = 'guangzhou'` in the SQL query as a preset filtering condition indicates that objects in the Guangzhou region will be selected as objects to be changed. If the preset filtering condition is empty, all objects in the configuration management database will be considered as objects to be changed. Based on these preset filtering conditions, partial or global grayscale processing can be performed on objects in the configuration management database, thereby improving the flexibility of grayscale processing.

[0049] In one embodiment, the step of sorting each of the objects to be changed in the grouping list according to a specified sorting label to obtain a sorted list corresponding to the grouping list, and the sorting percentage of each object to be changed in the corresponding sorted list, includes:

[0050] The objects to be changed in the group list are sorted in ascending order according to their importance level to obtain a sorted list corresponding to the group list, wherein the specified sorting label is the importance level;

[0051] When the number of objects to be changed in the target sorting list is greater than or equal to the batch quantity, the sorting proportion of the target object to be changed in the target sorting list is determined based on the ratio between the sorting position of the target object to be changed in the target sorting list and the number of objects to be changed in the target sorting list. The target sorting list is any sorting list, and the target object to be changed is any object to be changed in the target sorting list.

[0052] Specifically, in this embodiment, the specified sorting label is designated as the importance level, meaning each object to be modified has a corresponding importance level. The importance levels are categorized in ascending order of importance: ordinary, important, and core. Multiple objects to be modified within the group list are sorted in ascending order of importance level, that is, each object to be modified within the group list is sorted sequentially from lowest to highest importance level, thus obtaining the sorted list. (Refer to...) Figure 2Multiple objects to be modified that are the same model, region, and module are grouped into the same list. For example, the first group might include multiple objects with model S1, region Guangzhou 1, and module "insurance". These objects are then sorted in ascending order of importance, from lowest to highest. For objects of equal importance, a random sort is applied. For example, objects with the same level of importance within the same group are randomly sorted. This process is repeated to create a sorted list for each group. Figure 2 The first row of the table is the header row. Figure 2 The table contains a sorted list for rows 2 to 10, rows 11 to 19, rows 20 to 27, and rows 28 to 30.

[0053] The target sorting list is a sorted list obtained by sorting any grouped list. The number of objects to be changed in the target sorting list is denoted as n, and the number of batches in the total execution batch list is denoted as N. If n≥N, it means that the number of objects to be changed in the target sorting list is sufficient to be distributed in each execution batch list. In other words, the number of objects to be changed in the target sorting list is large enough. Therefore, the sorting ratio of the target object to be changed in the target sorting list can be used as the sorting ratio of the target object to be changed in the target sorting list. For example, if the sorting position of the target object to be changed in the target sorting list is r, then the sorting ratio of the target object to be changed is p = 100*r / n. Then, the target object to be changed is added to the execution batch list corresponding to the ratio range of p, thus ensuring that the target sorting list with a sufficient number of objects can achieve batch processing.

[0054] In one embodiment, after sorting each of the objects to be changed in the grouping list according to a specified sorting label to obtain a sorted list corresponding to the grouping list, the method further includes:

[0055] When the number of objects to be changed in the target sorting list is less than the number of batches in the entire execution batch list, determine whether the target object to be changed is the first in the target sorting list;

[0056] When the target object to be changed is ranked first in the target sorting list, zero percentage is taken as the sorting percentage of the target object to be changed; or,

[0057] When the sorting position of the target object to be changed in the target sorted list is not the first position, based on the ratio between the sorting position of the target object to be changed in the target sorted list and the number of objects in the target sorted list that are objects to be changed, determine the sorting proportion of the target object to be changed in the target sorted list.

[0058] Specifically, if n < N, it means that the number of objects to be changed in the target sorted list is not enough to be distributed to each list of the first execution batch. The sorting proportion of the first object to be changed in the target sorted list is relatively large and cannot meet the proportion range corresponding to the first execution batch list. That is, there is no object to be changed in the target sorted list that can be assigned to the first execution batch list. Therefore, when determining the sorting proportion of the target object to be changed, it is necessary to judge whether the target object to be changed is located at the first position in the target sorted list. If the target object to be changed is the first object in the target sorted list, its sorting proportion cannot be determined according to the ratio between its sorting position and the number of objects in the target sorted list, because the sorting proportion calculated by this method cannot meet the proportion range corresponding to the first execution batch list. In order to move the target object to be changed at the first position to the first execution batch list, a zero proportion (0%) is used as the sorting proportion of the target object to be changed. 0% meets the proportion range corresponding to the first execution batch list, and the target object to be changed can be added to the first execution batch list to solve the problem that there is no object meeting the proportion range in the first batch due to the small number of objects in the sorted list, so as to ensure that each sorted list can provide objects to be changed to the first execution batch list.

[0059] Generally, the number of objects in the previous execution batch lists is relatively small, but a small number may lead to incomplete gray coverage and easy risks. Therefore, based on the above method, it can be ensured that each sorted list can provide objects to be changed to the first execution batch list, so as to improve the gray coverage of the first gray execution batch and effectively control the gray change risk.

[0060] If the target object to be changed is not the object to be changed at the first position in the target sorted list, its sorting proportion can be normally determined according to the ratio between its sorting position and the number of objects in the target sorted list. The objects to be changed after the first position can be batch-processed based on the actual sorting proportion, mainly to ensure that when the number of objects in the target sorted list is small, there are objects to be changed assigned to the first execution batch list, so as to follow the gray change principle that the previous gray execution batches should cover as many scenarios as possible and effectively control the gray change risk.

[0061] In one embodiment, after grouping and processing multiple objects to be changed according to the grouping label and obtaining multiple grouped lists, the method further includes:

[0062] When at least one ungrouped object exists, the ungrouped object is added to the execution batch list that is last in the execution order, wherein the ungrouped object is the object to be changed that does not belong to any of the group lists.

[0063] Specifically, ungrouped objects are objects that do not belong to any group list, i.e., objects with empty group labels that are to be changed. If there are ungrouped objects that failed to be grouped, they will be added to the last batch of execution list to reduce the risk of gray-scale changes.

[0064] In one embodiment, after determining the execution batch list corresponding to each object to be changed based on the percentage range of the ranking percentage of each object to be changed in the corresponding ranking list, and adding the object to be changed to the corresponding execution batch list, the method further includes:

[0065] If there is a target of interest in the execution batch list that is first in the execution order, the target of interest is transferred from the execution batch list that is first in the execution order to the execution batch list that is last in the execution order. The target of interest is the target to be changed that meets the preset tag requirements.

[0066] Specifically, the first batch of executions is the first batch, and the last batch is the last batch. Objects of interest meeting the preset tag requirements are those whose preset tag values ​​are specified content and are to be changed. These preset tags can be customized based on different application scenarios; for example, machine type, region, module, and importance level can be selected. In this embodiment, importance level is used as the preset tag for illustration. Objects of interest meeting the preset tag requirements are those whose importance level tag value is important or core and whose specified content is important or core. If manual batch processing is relied upon, since humans cannot accurately identify the importance level of data objects, important objects may be placed in inappropriate batches, leading to change risks. Therefore, if important or core objects of interest exist in the first batch, based on risk principles, these objects need to be automatically moved to the last batch to delay the gray-scale change of these objects. This avoids premature gray-scale changes of important or core objects and prevents anomalies, adhering to the principle of gray-scale changes starting with ordinary objects and then moving to core objects, effectively controlling the risk of gray-scale changes.

[0067] In one embodiment, after performing grayscale change processing on the objects to be changed in each of the execution batch lists according to the execution order corresponding to each execution batch list, the method further includes:

[0068] When a new object is detected, the number of the new object is determined;

[0069] When the number of newly added objects is less than the preset number, multiple newly added objects are added to the execution batch list that is last in the execution order;

[0070] When the number of newly added objects is greater than or equal to a preset number, after determining that multiple objects to be changed have completed the grayscale change process, the newly added objects are used as new objects to be changed to execute the steps of obtaining the object list, grouping tags, and batch information. The object list includes multiple objects to be changed, and the batch information includes the batch number of the execution batch list, the execution order of each execution batch list, and the proportion range corresponding to each execution batch list. The steps are to perform grayscale change processing on the objects to be changed in each execution batch list in the order corresponding to each execution batch list.

[0071] Specifically, the scan results obtained by rescanning the configuration management database can be compared with the object list. Data objects that only exist in the scan results but not in the object list can be added as new objects. When the number of new objects is less than the preset number, it means that the number of new objects is small. In this case, multiple new objects can be added directly to the last batch of execution list. When the last batch of execution list is subjected to gray-scale change processing, the new objects can be gray-scale changed together. This can detect new objects in a timely and accurate manner during the change cycle and perform gray-scale changes on a small number of new objects to avoid missing new objects.

[0072] When the number of newly added objects is greater than or equal to the preset number, it means that there are too many newly added objects to be added to the current change cycle for gray-scale change. In this case, it is necessary to wait until the current change cycle ends and then re-process the grouping, batching, and gray-scale change of the newly added objects as new objects to be changed.

[0073] Based on the above grayscale change method, scientific grouping can be performed according to grouping tags. Following the principles of starting with ordinary and then core, starting with small batches and then expanding the scope, and ensuring that the initial batches cover as many scenarios as possible, the automated batch processing of objects to be changed can be achieved. This batching method can achieve batching in seconds even for a total of hundreds of thousands of objects. Compared with manual batching, it is more scientific, more comprehensive, more efficient, and less risky.

[0074] Figure 1 This is a flowchart illustrating a grayscale change method in one embodiment. It should be understood that, although... Figure 1The steps in the flowchart are shown sequentially as indicated by the arrows, but these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order in which these steps are executed, and they can be performed in other orders. Figure 1 At least some of the steps in the process may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least some of the sub-steps or stages of other steps.

[0075] In one embodiment, such as Figure 3 As shown, a grayscale changing device is provided, comprising:

[0076] The acquisition module 310 is used to acquire an object list, grouping tags, and batching information. The object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list.

[0077] Grouping module 320 is used to group multiple objects to be changed according to the grouping labels to obtain multiple group lists;

[0078] The sorting module 330 is used to sort each of the objects to be changed in the group list according to a specified sorting label, so as to obtain a sorting list corresponding to the group list and the sorting percentage of each object to be changed in the corresponding sorting list.

[0079] The batching module 340 is used to determine the execution batch list corresponding to the object to be changed based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, and to add the object to be changed to the corresponding execution batch list.

[0080] The execution module 350 is used to perform grayscale change processing on the objects to be changed in each of the execution batch lists in the order corresponding to each execution batch list.

[0081] In one embodiment, the acquisition module 310 is further configured to:

[0082] Select data objects in the configuration management database that meet the preset filtering criteria as objects to be changed;

[0083] The object list is composed of multiple objects to be changed.

[0084] In one embodiment, the sorting module 330 is further configured to:

[0085] The objects to be changed in the group list are sorted in ascending order according to their importance level to obtain a sorted list corresponding to the group list, wherein the specified sorting label is the importance level;

[0086] When the number of objects to be changed in the target sorting list is greater than or equal to the batch quantity, the sorting proportion of the target object to be changed in the target sorting list is determined based on the ratio between the sorting position of the target object to be changed in the target sorting list and the number of objects to be changed in the target sorting list. The target sorting list is any sorting list, and the target object to be changed is any object to be changed in the target sorting list.

[0087] In one embodiment, the sorting module 330 is further configured to:

[0088] When the number of objects to be changed in the target sorting list is less than the number of batches in the entire execution batch list, determine whether the target object to be changed is the first in the target sorting list;

[0089] When the target object to be changed is ranked first in the target sorting list, zero percentage is taken as the sorting percentage of the target object to be changed; or,

[0090] When the target object to be changed is not ranked first in the target sorting list, the ranking proportion of the target object to be changed in the target sorting list is determined based on the ratio between the ranking of the target object to be changed in the target sorting list and the number of objects to be changed in the target sorting list.

[0091] In one embodiment, the batching module 340 is further configured to:

[0092] When at least one ungrouped object exists, the ungrouped object is added to the execution batch list that is last in the execution order, wherein the ungrouped object is the object to be changed that does not belong to any of the group lists.

[0093] In one embodiment, the batching module 340 is further configured to:

[0094] If there is a target of interest in the execution batch list that is first in the execution order, the target of interest is transferred from the execution batch list that is first in the execution order to the execution batch list that is last in the execution order. The target of interest is the target to be changed that meets the preset tag requirements.

[0095] In one embodiment, the batching module 340 is further configured to:

[0096] When a new object is detected, the number of the new object is determined;

[0097] When the number of newly added objects is less than the preset number, multiple newly added objects are added to the execution batch list that is last in the execution order;

[0098] When the number of newly added objects is greater than or equal to a preset number, after determining that multiple objects to be changed have completed the grayscale change process, the newly added objects are used as new objects to be changed to execute the steps of obtaining the object list, grouping tags, and batch information. The object list includes multiple objects to be changed, and the batch information includes the batch number of the execution batch list, the execution order of each execution batch list, and the proportion range corresponding to each execution batch list. The steps are to perform grayscale change processing on the objects to be changed in each execution batch list in the order corresponding to each execution batch list.

[0099] like Figure 4 As shown, this application provides a computer device including a processor 711, a communication interface 712, a memory 713, and a communication bus 714, wherein the processor 711, the communication interface 712, and the memory 713 communicate with each other through the communication bus 714.

[0100] Memory 713 is used to store computer programs;

[0101] When the processor 711 executes the program stored in the memory 713, it implements the grayscale change control method provided in any of the aforementioned method embodiments.

[0102] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0103] In one embodiment, the grayscale changing device provided in this application can be implemented as a computer program, and the computer program can be implemented as follows: Figure 4 It runs on the computer device shown. The computer device's memory can store the various program modules that make up the grayscale changing device, for example, Figure 3The diagram shows an acquisition module 310, a grouping module 320, a sorting module 330, a batching module 340, and an execution module 350. The computer program comprised of these modules causes the processor to execute the steps in the grayscale changing methods of the various embodiments of this application described in this specification.

[0104] Figure 4 The computer device shown can be used as follows Figure 3 The acquisition module 310 in the grayscale change device shown acquires an object list, grouping labels, and batching information. The object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list. The computer device can use the grouping module 320 to group the multiple objects to be changed according to the grouping labels, obtaining multiple group lists. The computer device can use the sorting module 330 to sort each object to be changed in the group lists according to a specified sorting label, obtaining a sorting list corresponding to the group lists, and the percentage of each object to be changed in the corresponding sorting list. The computer device can use the batching module 340 to determine the execution batch list corresponding to each object to be changed based on the percentage range of each object's percentage in the corresponding sorting list, and add the object to be changed to the corresponding execution batch list. The computer device can use the execution module 350 to perform grayscale change processing on the objects to be changed in each execution batch list sequentially according to the execution order corresponding to each execution batch list.

[0105] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the grayscale change method provided in any of the foregoing method embodiments.

[0106] This application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the grayscale change method provided in any of the foregoing method embodiments.

[0107] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0108] The above description is merely a specific embodiment of this application, enabling those skilled in the art to understand or implement this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A grayscale change method, characterized in that, The method further includes: Obtain an object list, grouping tags, and batching information, wherein the object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list; The multiple objects to be changed are grouped according to the grouping labels to obtain multiple group lists; The objects to be changed in the group list are sorted according to the specified sorting labels to obtain the sorting list corresponding to the group list, and the sorting percentage of each object to be changed in the corresponding sorting list. Based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, determine the execution batch list corresponding to the object to be changed, and add the object to be changed to the corresponding execution batch list; According to the execution order corresponding to each execution batch list, the objects to be changed in each execution batch list are processed in a grayscale manner.

2. The method according to claim 1, characterized in that, Get a list of objects, including: Select data objects in the configuration management database that meet the preset filtering criteria as objects to be changed; The object list is composed of multiple objects to be changed.

3. The method according to claim 1, characterized in that, The step of sorting each of the objects to be changed in the group list according to a specified sorting label to obtain a sorted list corresponding to the group list, and the sorting percentage of each object to be changed in the corresponding sorted list, includes: The objects to be changed in the group list are sorted in ascending order according to their importance level to obtain a sorted list corresponding to the group list, wherein the specified sorting label is the importance level; When the number of objects to be changed in the target sorting list is greater than or equal to the batch quantity, the sorting proportion of the target object to be changed in the target sorting list is determined based on the ratio between the sorting position of the target object to be changed in the target sorting list and the number of objects to be changed in the target sorting list. The target sorting list is any sorting list, and the target object to be changed is any object to be changed in the target sorting list.

4. The method according to claim 3, characterized in that, After sorting each of the objects to be changed in the grouping list according to a specified sorting label to obtain the sorted list corresponding to the grouping list, the method further includes: When the number of objects to be changed in the target sorting list is less than the number of batches in the entire execution batch list, determine whether the target object to be changed is the first in the target sorting list; When the target object to be changed is ranked first in the target sorting list, zero percentage is taken as the sorting percentage of the target object to be changed; or, When the target object to be changed is not ranked first in the target sorting list, the ranking proportion of the target object to be changed in the target sorting list is determined based on the ratio between the ranking of the target object to be changed in the target sorting list and the number of objects to be changed in the target sorting list.

5. The method according to claim 1, characterized in that, After grouping the multiple objects to be changed according to the grouping labels to obtain multiple group lists, the method further includes: When at least one ungrouped object exists, the ungrouped object is added to the execution batch list that is last in the execution order, wherein the ungrouped object is the object to be changed that does not belong to any of the group lists.

6. The method according to claim 1, characterized in that, Based on the percentage range of each object to be changed in the corresponding sorting list, the method further includes determining the execution batch list corresponding to each object to be changed, and adding the object to be changed to the corresponding execution batch list. If there is a target of interest in the execution batch list that is first in the execution order, the target of interest is transferred from the execution batch list that is first in the execution order to the execution batch list that is last in the execution order. The target of interest is the target to be changed that meets the preset tag requirements.

7. The method according to claim 1, characterized in that, After performing grayscale change processing on the objects to be changed in each of the execution batch lists according to the execution order corresponding to each execution batch list, the method further includes: When a new object is detected, the number of the new object is determined; When the number of newly added objects is less than the preset number, multiple newly added objects are added to the execution batch list that is last in the execution order; When the number of newly added objects is greater than or equal to a preset number, after determining that multiple objects to be changed have completed the grayscale change process, the newly added objects are used as new objects to be changed to execute the steps of obtaining the object list, grouping tags, and batch information. The object list includes multiple objects to be changed, and the batch information includes the batch number of the execution batch list, the execution order of each execution batch list, and the proportion range corresponding to each execution batch list. The steps are to perform grayscale change processing on the objects to be changed in each execution batch list in the order corresponding to each execution batch list.

8. A grayscale changing device, characterized in that, The grayscale changing device includes: The acquisition module is used to acquire an object list, grouping tags, and batching information. The object list includes multiple objects to be changed, and the batching information includes the number of batches in the execution batch list, the execution order of each execution batch list, and the percentage range corresponding to each execution batch list. The grouping module is used to group multiple objects to be changed according to the grouping labels to obtain multiple group lists; The sorting module is used to sort each of the objects to be changed in the group list according to a specified sorting label, so as to obtain a sorting list corresponding to the group list and the sorting percentage of each object to be changed in the corresponding sorting list. The batching module is used to determine the execution batch list corresponding to each object to be changed based on the percentage range of the sorting percentage of each object to be changed in the corresponding sorting list, and to add the object to be changed to the corresponding execution batch list. The execution module is used to perform grayscale change processing on the objects to be changed in each of the execution batch lists in the order corresponding to each execution batch list.

9. A computer device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the steps of the grayscale change method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the grayscale change method as described in any one of claims 1-7.

11. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1-7.

Images