CN106202123B

CN106202123B - The method and apparatus of gray scale publication

Info

Publication number: CN106202123B
Application number: CN201510230777.1A
Authority: CN
Inventors: 朱曜鑫; 雷鹏涛; 秦天欢
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2015-05-07
Filing date: 2015-05-07
Publication date: 2019-07-05
Anticipated expiration: 2035-05-07
Also published as: CN106202123A

Abstract

Application provides a kind of method and apparatus of gray scale publication, include: the distribution batch of the implementation progress and each gray scale release tasks according to the gray scale release tasks of each server, optimal task execution path is selected to send as modified metadata to corresponding server from the task execution path of all candidates.The application can reach the effect that multiple tasks execution route can while concurrently carry out gray scale publication, when i.e. in the execution of one or more gray scale release tasks, new gray scale posting request can be added, optimal task execution path is selected by distribution batch, guarantee not interfereing with each other mutually between task and task simultaneously, greatly accelerates the speed of distribution configuration.

Description

The method and apparatus of gray scale publication

Technical field

This application involves the method and apparatus of communication and the publication of computer field more particularly to a kind of gray scale.

Background technique

Database administrator (DataBASE Administrator, abbreviation DBA) is when gray scale is issued, because of the business being related to Line is extensive, and not only the needing to distribute of the task is more, and managed service device substantial amounts, when each distributed tasks execute, because Gray scale publication needs to verify in batches, and the time is longer, if being at this moment unable to Multi-task Concurrency, usually there are also other distributed tasks It can only be issued using the serial ways of distribution of the following two kinds:

(1) etc. after a upper distributed tasks are completed and are verified, then to execute next distributed tasks；

(2) it needs to collect all posting requests before publication and merges, once merged completion and started publication, Other posting requests can not added again halfway, unless last task publication is completed and issues new request again after confirming, or Retract the supreme one gray scale task being carrying out, then issues after new request is reconsolidated.

But there is inefficiency in above-mentioned serial ways of distribution.

Summary of the invention

The purpose of the application is to provide a kind of method and apparatus of gray scale publication, and can be realized multiple tasks execution route can Concurrently to carry out gray scale publication simultaneously.

In view of this, the application provides a kind of method of gray scale publication,

The configuration item of new gray scale release tasks and old gray scale release tasks is deposited in catalogue, wherein described new Gray scale release tasks and old gray scale release tasks through conflict passed examination；

The task execution path of all candidates of new and old gray scale release tasks is generated according to catalogue and its configuration item；

According to the distribution batch of the implementation progress of the gray scale release tasks of each server and each gray scale release tasks, from Select optimal task execution path as modified metadata to corresponding server in the task execution path of all candidates It sends, wherein the metadata includes the volume of server address, the corresponding catalogue and corresponding configuration item used of the server Number.

Further, in the above method, optimal task execution path is selected from the task execution path of all candidates After being sent as modified metadata to corresponding server, further includes:

Each server completes configuration according to the metadata received.

Further, in the above method, when new and old gray scale release tasks are the configurations in the original catalogue of modification Xiang Shi deposits in the configuration item of new and old gray scale release tasks in catalogue, comprising:

Often there are a new gray scale release tasks, then replicates an original catalogue as new catalogue, according to each ash Degree release tasks modify to the configuration item to be modified in corresponding new catalogue, obtain modified configuration item；

Selected from the task execution path of all candidates optimal task execution path as modified metadata to During corresponding server is sent,

The metadata includes server address, corresponding in the corresponding new catalogue and the new catalogue used of the server Modified configuration item number.

Further, it in the above method, after each server completes configuration according to the metadata received, also wraps It includes:

The original catalogue and all new catalogues are deleted after backing up original catalogue and all new catalogues；

New original catalogue is incorporated as with all new catalogues；

Metadata is modified, the metadata includes server address, the corresponding new original catalogue used of the server With the number of modified configuration item corresponding in the original catalogue newly.

Further, in the above method, optimal task execution path is selected from the task execution path of all candidates While transmission as modified metadata to corresponding server, the method also includes:

Suspend to server and sends metadata；

After modifying metadata to the state for not including the gray scale release tasks wait retract, by modified metadata to correspondence Server is sent；

If some server has been completed to configure according to the metadata being originally received, the server is according to reception The modified metadata arrived completes the configuration that retracts.

Further, in the above method, when new and old gray scale release tasks are the configurations increased in original catalogue Xiang Shi deposits in the configuration item of new gray scale release tasks and old gray scale release tasks in catalogue, comprising:

Often there are a new old gray scale release tasks, is then added configuration item to be increased according to each gray scale release tasks Enter in the original catalogue；

The metadata includes corresponding in original catalogue and the original catalogue that server address, the server use Configuration item to be increased number.

Further, in the above method, often there are a new old gray scale release tasks, then appointed according to the publication of each gray scale Before configuration item to be increased is added in the original catalogue for business, further includes:

Back up original catalogue.

Suspend to server and sends metadata；

The anti-installation configuration item for corresponding to originally newly-increased configuration item, the anti-installation are added in original catalogue Configuration item is used to delete corresponding originally newly-increased configuration item in the catalogue；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server make The number of the anti-installation configuration item of originally newly-increased configuration number is replaced in original catalogue and the original catalogue；

Further, in the above method, after server completes rollback configuration according to the modified metadata received, Further include:

After backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, it is original new to delete this The configuration item of increasing and corresponding anti-installation configuration item delete the number of the anti-installation configuration item in metadata.

Further, in the above method, when new and old gray scale release tasks are the configurations deleted in original catalogue Xiang Shi deposits in the configuration item of new gray scale release tasks and old gray scale release tasks in catalogue, comprising:

Often there are a new and old gray scale release tasks, then it is right respectively in original catalogue according to each gray scale release tasks An anti-installation configuration item should be increased, the anti-installation configuration item is for deleting corresponding configuration item to be deleted in the catalogue；

The metadata includes replacing in original catalogue and the original catalogue that server address, the server use The number of the anti-installation configuration item of the number of configuration item to be deleted.

Further, in the above method, often there are a new and old gray scale release tasks, then according to each gray scale release tasks It is respectively corresponded in original catalogue before increasing an anti-installation configuration item, further includes:

Back up original catalogue.

Further, in the above method, the step of each server completes configuration according to the metadata that receives it Afterwards, further includes:

After backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue, by configuration to be deleted Item and corresponding anti-installation configuration item are deleted from original catalogue；

By the anti-correspondence configuration item for installing configuration item in the corresponding original catalogue used of each server in metadata Number delete.

Further, in the above method, optimal task execution path is selected from the task execution path of all candidates While transmission as modified metadata to corresponding server, further includes:

Suspend to server and sends metadata；

The newly-increased configuration item for corresponding to original anti-installation configuration item is added in original catalogue；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server make The volume of the newly-increased configuration item of the number of original anti-installation configuration item is replaced in original catalogue and the original catalogue Number；

Delete original anti-installation configuration item in the original catalogue.

A kind of equipment of gray scale publication is not provided according to the another side of the application, comprising:

First device, for the configuration item of new gray scale release tasks and old gray scale release tasks to be deposited in catalogue In, wherein the new gray scale release tasks and old gray scale release tasks are through the passed examination that conflicts；

Second device, for generating all candidate of new and old gray scale release tasks according to catalogue and its configuration item Task execution path；

3rd device, for the implementation progress and each gray scale release tasks according to the gray scale release tasks of each server Distribution batch, select optimal task execution path as modified metadata from the task execution path of all candidates It is sent to corresponding server, wherein the metadata includes server address, the corresponding catalogue used of the server and corresponding The number of configuration item.

Further, in above equipment, the equipment further include:

4th device, for controlling each server according to received described after 3rd device execution Metadata completes configuration.

Further, in above equipment, when new and old gray scale release tasks are the configurations in the original catalogue of modification Xiang Shi,

The first device then replicates an original catalogue as new for often there is a new gray scale release tasks Catalogue, modified according to each gray scale release tasks to the configuration item to be modified in corresponding new catalogue, after obtaining modification Configuration item；

The 3rd device to the metadata that corresponding server is sent include server address, the server correspondence use The number of corresponding modified configuration item in new catalogue and the new catalogue.

Further, in above equipment, the equipment further includes the 5th device, for executing it in the 4th device Afterwards,

New original catalogue is incorporated as with all new catalogues；

Further, in above equipment, the equipment further includes the 6th device, same for executing in the 3rd device When,

Suspend to server and sends metadata；

Further, in above equipment, when new and old gray scale release tasks are the configurations increased in original catalogue Xiang Shi,

The first device, for often there is a new old gray scale release tasks, then according to each gray scale release tasks Configuration item to be increased is added in the original catalogue；

The 3rd device to the metadata that corresponding server is sent include server address, the server use it is original Catalogue and the original catalogue in corresponding configuration item to be increased number.

Further, in above equipment, the equipment further includes the 7th device, for executing it in the first device Before, back up original catalogue.

Further, in above equipment, the equipment further includes the 8th device, same for executing in the 3rd device When,

Suspend to server and sends metadata；

Further, in above equipment, the equipment further includes the 9th device, for executing it in the 8th device Afterwards, after backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, delete what this was originally increased newly Configuration item and corresponding anti-installation configuration item delete the number of the anti-installation configuration item in metadata.

Further, in above equipment, when new and old gray scale release tasks are the configurations deleted in original catalogue Xiang Shi,

The first device then exists according to each gray scale release tasks for often there is a new and old gray scale release tasks Increase by one anti-installation configuration item is respectively corresponded in original catalogue, the anti-installation configuration item is corresponding in the catalogue for deleting Configuration item to be deleted；

The 3rd device to the metadata that corresponding server is sent include server address, the server use it is original Catalogue and the original catalogue in replace configuration item to be deleted number anti-installation configuration item number.

Further, in above equipment, the equipment further includes the tenth device, for executing it in the first device Before, back up original catalogue.

Further, in above equipment, the equipment further includes the 11st device, for executing it in the 4th device Afterwards, after backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue, by configuration item to be deleted and Corresponding anti-installation configuration item is deleted from original catalogue；And each server correspondence in metadata is used original The number of the anti-correspondence configuration item for installing configuration item is deleted in catalogue.

Further, in above equipment, the equipment further includes the tenth two devices, for what is executed in the 3rd device Meanwhile

Suspend to server and sends metadata；

Further, in above equipment, the equipment further includes the 13rd device, for executing in the tenth two devices Later, original anti-installation configuration item in the original catalogue is deleted.

Compared with prior art, the application is according to the implementation progress and each gray scale of the gray scale release tasks of each server The distribution batch of release tasks, from selected in the task execution path of all candidates optimal task execution path as modification after Metadata to corresponding server send, achieve the effect that multiple tasks execution route can simultaneously concurrently progress gray scale publication, When i.e. in the execution of one or more gray scale release tasks, new gray scale posting request can be added, by distribution batch selection Optimal task execution path, while guaranteeing not interfereing with each other mutually between task and task, greatly accelerate the speed of distribution configuration.

Further, when new and old gray scale release tasks are the configuration items in the original catalogue of modification, often there is one A new gray scale release tasks then replicate an original catalogue as new catalogue, according to each gray scale release tasks to phase It answers the configuration item to be modified in new catalogue to modify, obtains modified configuration item, the metadata includes server The number of corresponding modified configuration item, is realized more in location, the corresponding new catalogue and the new catalogue used of the server The gray scale release tasks of configuration item in the original catalogue of a modification can carry out simultaneously.

Further, when new and old gray scale release tasks are the configuration items in the original catalogue of modification, by standby When part original catalogue and all new catalogues are to prevent there is rollback to require, can fast quick-recovery catalogue, and delete the original after backup The catalogue of beginning and all new catalogues avoid with the presence of multiple environment and generate interference；By with the conjunction of all new catalogues And as new original catalogue, resetted with facilitating, prepares the glitch-free environment of relative clean for gray scale release tasks next time.

Further, new and old gray scale release tasks are when increasing the configuration item in original catalogue, by often having One new old gray scale release tasks, then configuration item to be increased is added according to each gray scale release tasks described original In catalogue, the metadata includes corresponding in original catalogue and the original catalogue that server address, the server use Configuration item to be increased number, realize multiple gray scale release tasks for increasing the configuration item in original catalogue can simultaneously into Row.

Further, by the way that before the step in the original catalogue is added in configuration item to be increased, backup is former The catalogue of beginning, so as to it is subsequent need the case where retracting to occur when, can successfully return back to it is newly-increased before BASE environment.

Further, new and old gray scale release tasks are when deleting the configuration item in original catalogue, by often having One new and old gray scale release tasks then respectively corresponds increase by one instead according to each gray scale release tasks in original catalogue Configuration item is installed, the anti-installation configuration item is for deleting corresponding configuration item to be deleted in the catalogue, the metadata packet Include the number that configuration item to be deleted is replaced in server address, the original catalogue which uses and the original catalogue Anti- installation configuration item number, realize multiple gray scale release tasks for deleting the configuration item in original catalogue can simultaneously into Row.

Further, by the way that before respectively corresponding increase by one anti-installation configuration item in original catalogue, backup is former The catalogue of beginning, so as to it is subsequent need the case where retracting to occur when, can successfully return back to it is newly-increased before BASE environment；Pass through After the step of each server completes configuration according to the metadata received, back up to be deleted in original catalogue Configuration item and corresponding anti-installation configuration item, so as to the subsequent possible needs to retract, then by configuration item to be deleted and right Configuration item counter should be installed to delete from original catalogue, it will be in the corresponding original catalogue used of each server in metadata The number of the correspondence configuration item of anti-installation configuration item is deleted, and to remove unnecessary configuration item, is kept in the catalogue of end-state Configuration item is without conflicting situation.

Further, by selecting optimal task execution path as repairing in the task execution path from all candidates While metadata after changing is sent to corresponding server, to modification, increase, the new of configuration item in original catalogue is deleted And/or old gray scale release tasks retract, even if realizing that gray scale release tasks execute mistake, can carry out fast and accurately It retracts.

Detailed description of the invention

By reading a detailed description of non-restrictive embodiments in the light of the attached drawings below, the application's is other Feature, objects and advantages will become more apparent upon:

Fig. 1 shows the method flow diagram issued according to the gray scale of the application one aspect；

Fig. 2 shows the method flow diagrams of the preferred embodiment gray scale of the application publication；

Fig. 3 shows one gray scale release tasks execution route figure of method of the embodiment gray scale publication of the application；

Fig. 4 shows two tasks of method while gray scale release tasks execution route of the embodiment gray scale publication of the application Figure；

Fig. 5 shows three tasks of method while gray scale release tasks execution route of the embodiment gray scale publication of the application Figure；

Fig. 6 shows three tasks of method while gray scale release tasks execution route of the embodiment gray scale publication of the application Figure；

Fig. 7 shows the method flow diagram of the preferred embodiment gray scale publication of the application；

Fig. 8 shows the method flow diagram of another preferred embodiment gray scale publication of the application；

Fig. 9 shows the method flow diagram of the another preferred embodiment gray scale publication of the application；

Figure 10 shows the method flow diagram of another preferred embodiment gray scale publication of the application；

Figure 11 shows the method flow diagram of another preferred embodiment gray scale publication of the application；

Figure 12 shows the equipment schematic diagram issued according to the gray scale of the application other side；

Figure 13 shows the method equipment schematic diagram according to another preferred embodiment gray scale publication of the application；

Figure 14 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

Figure 15 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

Figure 16 shows the method equipment schematic diagram issued according to one preferred embodiment gray scale of the application；

Figure 17 shows the method equipment schematic diagram according to another preferred embodiment gray scale publication of the application；

Figure 18 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

Figure 19 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

Figure 20 shows the method equipment schematic diagram according to another preferred embodiment gray scale publication of the application；

Figure 21 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

Figure 22 shows the method equipment schematic diagram according to the another preferred embodiment gray scale publication of the application；

The same or similar appended drawing reference represents the same or similar component in attached drawing.

Specific embodiment

In a typical configuration of this application, terminal, the equipment of service network and trusted party include one or more Processor (CPU), input/output interface, network interface and memory.

Memory may include the non-volatile memory in computer-readable medium, random access memory (RAM) and/or The forms such as Nonvolatile memory, such as read-only memory (ROM) or flash memory (flash RAM).Memory is computer-readable medium Example.

Computer-readable medium includes permanent and non-permanent, removable and non-removable media can be by any method Or technology come realize information store.Information can be computer readable instructions, data structure, the module of program or other data. The example of the storage medium of computer includes, but are not limited to phase change memory (PRAM), static random access memory (SRAM), moves State random access memory (DRAM), other kinds of random access memory (RAM), read-only memory (ROM), electric erasable Programmable read only memory (EEPROM), flash memory or other memory techniques, read-only disc read only memory (CD-ROM) (CD-ROM), Digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or Any other non-transmission medium, can be used for storage can be accessed by a computing device information.As defined in this article, computer Readable medium does not include non-temporary computer readable media (transitory media), such as the data-signal and carrier wave of modulation.

As shown in Figure 1, the application provides a kind of method of gray scale publication, comprising:

The configuration item (state) of new gray scale release tasks and old gray scale release tasks is deposited in catalogue by step S1 (environment) in, wherein described old and new gray scale release tasks are gray scale publications times in time in contrast Business is new gray scale release tasks if newer in generation time, issues if older in generation time for old gray scale Task, the new gray scale publication engraved at one, if subsequent time has the gray scale release tasks of update, original new ash Degree release tasks then become old gray scale release tasks at the moment, in addition, the new gray scale release tasks and old ash Release tasks are spent through the passed examination that conflicts, to guarantee the subsequent gray scale release tasks executed parallel and old gray scale release tasks It clashes, if there is multiple new gray scale release tasks to generate simultaneously, is also required between new gray scale release tasks through conflicting Passed examination, new gray scale release tasks can be the change to original catalogue, such as to matching in original catalogue (BASE) Item is set to modify, increase and delete；

Step S2 is held according to the task that catalogue and its configuration item generate all candidates of new and old gray scale release tasks Walking along the street diameter carries out all candidates' of arbitrary arrangement combination producing to new gray scale release tasks and old gray scale release tasks Task execution path, wherein the execution completion of the gray scale release tasks in every Geju City or new gray scale release tasks is by its mesh Configuration item in record configures server, and each task execution path is used to execute old gray scale release tasks and/or new Gray scale release tasks；

Step S3, according to the distribution of the implementation progress of the gray scale release tasks of each server and each gray scale release tasks Batch selects optimal task execution path as modified metadata to correspondence from the task execution path of all candidates Server is sent, wherein the metadata includes server address such as IP address, the corresponding catalogue used of the server (environment) and corresponding configuration item (state) number, the number of a configuration item are corresponding with a configuration item.Specifically , for example need to update some configuration item A now with 10000 database servers, it needs to distribute to ensure to stablize on line Batch is divided into 10 batches of progress gray scale publications, every a collection of 1000, starts corresponding generation gray scale release tasks 1, it is assumed that now 5 batches are pushed, and wherein the server owner (owner) of 4 batches of gray scale release tasks 1 has confirmed that and pass through that the 5th batch is also confirming In, it is at this moment connected to second distributed tasks, needs to upgrade some software package B of 10000 database servers, is matched by checking After setting file A and software B Lothrus apterus, gray scale release tasks 2 are generated, it is same to distribute 10 batches of progress gray scale publications of batch point, it can be with According to the implementation progress of old gray scale release tasks (task 1), (old gray scale release tasks 1 may be on some servers Execute, it is also possible to be not carried out) and the distribution batch of each gray scale release tasks 1,2 held for the corresponding task of each server selection Walking along the street diameter executes task 2 again if part server has executed task 1, meanwhile, part server is also not carried out task 1 , the problem of task 1 and task 2 are performed simultaneously, or consider distribution batch, part server, which first carries out, makees task 2 again Execution task 1, or first carry out task 1 and execute task 2 again, to realize that task 1 and task 2 can be in asynchronous servers It is upper to be executed simultaneously, and if task 1 needs to retract, due between each task by the passed examination that conflicts, when rollback, It will not influence continuing to execute for task 2.And so on, if receiving task 3 again, task 4 ... task N can be held simultaneously Row, is mutually independent of each other, does not conflict.For another example, there are 10000 servers, distribution batch of the A mission requirements to this 10000 servers Secondary to divide 5 batches of execution, every batch of executes 2000 servers, then, and has B mission requirements to this same 10000 servers Distributing batch is point 20 batches of execution, 500 servers is only carried out every time, at this point, if having gay A (only carrying out task A), gay B (only carries out task B), gay AB (being performed simultaneously task AB) three candidate task execution path, 2000 a batch of A task, B 500 a batch of task, if that selecting 2000 machines for never executing the two tasks from the inside, that is by optimization Task execution path, that just has 1500 and goes to gay A, has 500 to go to gay AB.Here, can be by using such as General catalogue (environment) and configuration item (state) in the configuration management tool of saltstack, the metadata can To deposit in a file, can also deposit in one of lane database or multiple tables, such as can be used cooperatively The metadata of MySQL database service device, can while gray scale publication concurrently be carried out by reaching multiple tasks execution route Effect, i.e., one or more gray scale release tasks execution in when, new gray scale posting request can be added, by distribution batch Optimal task execution path is selected, while guaranteeing not interfereing with each other mutually between task and task, greatly accelerates distribution configuration Speed.The core concept of the present embodiment is to be held when there is multiple gray scale release tasks demands by generating all possible task Walking along the street diameter, that is, middle directory, then for state, that is, gray scale release tasks implementation progress of current different server and distribution batch It is secondary that an optimal step task execution path is selected to send as metadata to corresponding server from middle directory, thus maximum limit Realize multitask gray scale publication simultaneously in degree ground.The core concept of the present embodiment is led to when there is multiple gray scale release tasks demands It crosses and generates all possible task execution path i.e. middle directory, then for the state of current different server, that is, gray scale publication The implementation progress and distribution batch of task are made from the optimal step task execution path of all possible task execution Path selection For the transmission of metadata corresponding server, to realize multitask to the maximum extent, gray scale is issued simultaneously.

As shown in Fig. 2, further including after step S3 in one preferred embodiment of method that a kind of gray scale of the application is issued Step S4, each server complete configuration according to the metadata received, to complete gray scale hair on all servers Cloth.

In a kind of one preferred embodiment of method of gray scale publication of the application, when new and old gray scale release tasks are When modifying the configuration item in original catalogue (BASE in environment),

Step S1 deposits in the configuration item of new and old gray scale release tasks in catalogue, comprising:

Often there are a new gray scale release tasks, then replicates an original catalogue (BASE) as new catalogue (GAY A, GAY B, GAY C ...), the configuration item to be modified in corresponding new catalogue is repaired according to each gray scale release tasks Change, obtains modified configuration item；Here, the catalogue (environment) of most original state is called BASE (a b c), when When receiving new gray scale release tasks gay A (a'b c), i.e., modify to a configuration item in catalogue, then it can be first from original BASE (a b c) duplication to generate new environmentg be gay A (a b c), and the configuration item inside gay A A goes modification to generate gay A (a'b c) by newest requirement, when new gray scale release tasks gay A (a'b c) is executed, if receiving The gray scale release tasks gay B (a b'c) new to another requires modification configuration item b, at this moment again can be in original BASE (a b C) it is gay B (a b'c) that a new environment is regenerated on the basis of；

Correspondingly, step S2, according to catalogue and base configuration item to new gray scale release tasks and old gray scale release tasks The all possible task execution path of carry out arbitrary arrangement combination producing (distribution catalogue) in, as shown in figure 3, if original point Sending out catalogue is (BASE (1 2 3)), and when increasing new gray scale release tasks gay A, distribution catalogue is revised as (BASE (1 2 3), gay A (1'2 3)), similarly, when receiving new gray scale release tasks again when gay B, as shown in figure 4, distribution catalogue It is revised as (BASE (1 2 3), gay A (1'2 3), gay B (1 2'3), gay AB (1'2'3)), three tasks while gray scale The distribution catalogue of publication is as shown in figure 5, the distribution catalogue of four tasks gray scale publication simultaneously is as shown in Figure 6, and so on, pass through Duplication BASE catalogue and the task execution for generating the i.e. all candidates of intermediate state environment combined to different task Path, and modify when new distributed tasks are added to execution route and generate the task execution path of new all candidates, It is finally reached the consistent state of all tasks, the gray scale publication of all distributed tasks is completed, even if carrying out more tasks simultaneously Gray scale publication, can complete that is certain through this embodiment, as being performed simultaneously for task is more, intermediate environment The generation of (gay A, gay B ...) can be more, and execution route can be more complicated；

Correspondingly, step S3, according to the implementation progress of each server gray scale release tasks and each gray scale release tasks Distribution batch, select optimal task execution path as modified metadata from the task execution path of all candidates In the step of being sent to corresponding server,

The metadata includes server address, corresponding in the corresponding new catalogue and the new catalogue used of the server Modified configuration item number.Here, new catalogue is for original catalogue, every generation one is new to be repaired Change the configuration gray scale hair of original catalogue and task, then correspondence can generate a new catalogue, the generation of each new catalogue when Between on may have precedence relationship, but the concept of the new and old relationship is not present between each new catalogue, may be new gray scale publication The new catalogue of task, it is also possible to the new catalogue of old gray scale release tasks, but the catalogue that each new catalogue is relatively primitive For be all new catalogue.For example, metadata original before receiving gay A is machine X-- > BASE-- > [1], [2], [3], after receiving gay A, metadata is revised as machine X-- > gay A-- > [1], [2], [3], similarly, when again When receiving new gray scale release tasks when gay B, the server for having executed gay A also needs to be distributed task gay B, the machine for having not carried out any task needs to carry out gay AB publication by batch, for example, the server of gay A can will be not carried out The metadata of X is further by machine X-- > gay A-- > [1], [2], [3] be revised as machine X-- > gay AB-- > [1], [2], [3], simultaneously, it is contemplated that the problem of batch, while by the metadata of server Y by original metadata machine AB-- > [1] machine Y-- > gay a/gay b/gay, [2], [3], i.e. m are revised as in Y-- > BASE-- > [1], [2], [3] AB-- > [1] achine Y-- > gay A--gay, [2], [3] or AB-- > [1] machine Y-- > gay B--gay, [2], [3] or machine Y-- > gay AB-- > [1], [2], [3].

As shown in fig. 7, in one preferred embodiment of method that a kind of gray scale of the application is issued, when new and old gray scale When release tasks are the configuration items in the original catalogue (BASE in environment) of modification, step S4, each server root After the step of completing configuration according to the metadata received, further includes:

Step S411 deletes the original catalogue and all new mesh after backing up original catalogue and all new catalogues Record；Here, need to back up the i.e. original catalogue of all intermediate state environment and all new catalogues, when to prevent there is rollback to require, Can fast quick-recovery catalogue, can be deleted after backup, avoid interfering with the presence of multiple environment and generating；

Step S412 is incorporated as new original catalogue with all new catalogues, here, needing to replicate end-state Catalogue as original catalogue (BASE), resetted with facilitating, it is noiseless to prepare relative clean for gray scale release tasks next time Environment, for example, first gray scale release tasks gay A (a'b c) be modification configuration item a, second gray scale release tasks gay A (a b'c) is modification configuration item b, and first gray scale release tasks gay A (a b c') is modification configuration item c, then all new Catalogue merges into gay A (a'b'c')；

Step S413, modifies metadata, and the metadata includes server address, the corresponding new original used of the server The number of corresponding modified configuration item in the catalogue of beginning and the new original catalogue.Step S411 to step S413 be It is carried out after the completion of whole gray scale tasks.

In a kind of one preferred embodiment of method of gray scale publication of the application, when new and old gray scale release tasks are When increasing the configuration item in original catalogue,

Step S1 deposits in the configuration item of new gray scale release tasks and old gray scale release tasks in catalogue, comprising:

Often there are a new old gray scale release tasks, is then added configuration item to be increased according to each gray scale release tasks Enter in the original catalogue；Here, not needing picture when gray scale release tasks are to increase configuration item newly in original catalogue It is completed in previous embodiment by duplication BASE, because repairing for the existing configuration item in catalogue will not be caused by increasing configuration item Change, so only needing to be directly added into a new configuration item in former BASE；

The metadata includes corresponding in original catalogue and the original catalogue that server address, the server use Configuration item to be increased number.Here, modification metadata in configuration item (state) content, i.e., plus new state again into Row push, if such as when (1 2 3) BASE, corresponding metadata is machine X (server X) -- > BASE-- > [1], [2], [3], when will the increased configuration item A in BASE when, BASE is changed to BASE (1 23 A) in step S121, then, step It is corresponding that metadata is revised as metadata machine X-- > BASE-- > [1] in rapid S321, [2], [3], [A], here [1], [2], [3], [A] is respectively the number of the configuration item corresponding to 123 A of configuration item, if existing simultaneously multiple newly-increased configuration items Task, and metadata is generated using same method, for example, to increase there are two configuration item A and B, according to batch and each Server implementation progress can increase A and B metadata simultaneously, can also increase the metadata of A or B step by step, then carry out metadata Push to server.

In a kind of one preferred embodiment of method of gray scale publication of the application, when new and old gray scale release tasks are When increasing the configuration item in original catalogue (BASE in environment), in step S1, often there is a new old gray scale Release tasks, then according to each gray scale release tasks by configuration item to be increased be added the step in the original catalogue it Before, further includes:

Back up original catalogue.It is for subsequent needs here, backing up current BASE environment before newly-increased configuration item When the case where rollback, occurs, can successfully return back to it is newly-increased before BASE environment.

In a kind of one preferred embodiment of method of gray scale publication of the application, when new and old gray scale release tasks are When deleting the configuration item in original catalogue,

The metadata includes replacing in original catalogue and the original catalogue that server address, the server use The number of the anti-installation configuration item of the number of configuration item to be deleted.Here, replacing configuration to be deleted in the original catalogue Number anti-installation configuration item number that is, removing institute in the original catalogue that each server in the metadata uses The number of the correspondence configuration item of configuration item to be deleted is stated, and adds the number of the correspondence configuration item of the anti-installation configuration item. Here the deletion of configuration item is modified to s tate information in BASE, but is not directly to delete, but in intermediate shape Newly-built one anti-installation configuration item (uninstall state) of state, and will be in original metadata before pushing metadata Fall the state for needing to delete, uninstall state is added.

In a kind of one preferred embodiment of method of gray scale publication of the application, when new old gray scale release tasks are to delete When except configuration item in original catalogue, in step S1, often there are a new and old gray scale release tasks, is then sent out according to each gray scale Cloth task was respectively corresponded in original catalogue before the step of increase by one anti-installation configuration item, further includes:

Original catalogue is backed up, is for subsequent needs here, backing up current BASE environment before deleting configuration item When the case where rollback, occurs, can successfully return back to it is newly-increased before BASE environment.

As shown in figure 8, in one preferred embodiment of method that a kind of gray scale of the application is issued, when new old gray scale hair Cloth task is step S4 when deleting the configuration item in original catalogue, and each server is complete according to the metadata received After the step of configuration, further includes:

Step S431 will be to after backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue The configuration item of deletion and corresponding anti-installation configuration item are deleted from original catalogue, here, in the original catalogue of backup wait delete The configuration item and corresponding anti-installation configuration item removed by configuration item to be deleted and is corresponded to anti-for the subsequent possible needs to retract Installation configuration item is to keep in the catalogue of end-state configuration item without conflicting situation from deleting in original catalogue；

Step S432, by counter pair for installing configuration item in the corresponding original catalogue used of each server in metadata It answers the number of configuration item to delete, to remove unnecessary configuration item, keeps configuration item without conflicting situation, for example, originally The number of configuration item in metadata is (2, -1), wherein -1 is the number of the correspondence configuration item of anti-installation configuration item, then deletes The number of the configuration item in metadata afterwards is revised as (2), and step S431 to step S432 is after the completion of whole gray scale tasks It carries out.

As shown in figure 9, step S3 is executed same in one preferred embodiment of method that a kind of gray scale of the application is issued When, further include step S31, the new and/or old gray scale release tasks for the configuration item modified in original catalogue are returned It moves back, specifically includes:

Step S311 suspends to server and sends metadata；

Step S312, after modifying metadata to the state for not including the gray scale release tasks wait retract, by modified member Data are sent to corresponding server；Multitask simultaneously carry out gray scale publication when, if receive request need to some task into When row retracts, suspend the push of metadata first, and all current metadata comprising rollback task are return back to upper one without being somebody's turn to do The state of gray scale release tasks to be retracted, by taking the case that four tasks of aforementioned modifications configuration item are modified simultaneously as an example, The current distributed tasks carried out simultaneously have A, B, C, D, now need to retract to A task, then can suspend push first, avoid Further expansion is influenced, while modifying metadata, i.e., is retracted to the metadata for the intermediate environment for having included A, and The optimization level of rollback task is improved, i.e., return back to BASE current for the metadata of GAY A, GAY A, B return back to GAY B, GAY A, C return back to GAY C, GAY A, D, return back to GAY D, GAY A, B, C return back to GAY B, C ... and so on, due to aforementioned The original catalogue and all new catalogues are deleted after having backed up original catalogue and all new catalogues in step S411, i.e., The i.e. original catalogue of all intermediate state environment and all new catalogues have been had backed up, so when thering is rollback to require here, it can With fast quick-recovery metadata to the state for not including gray scale release tasks to be retracted；

Step S313, if some server has been completed to configure according to the metadata being originally received, the service Device completes the configuration that retracts according to the modified metadata received.Here, can be according to the flag bit being arranged in configuration item Judge whether some server has been completed to configure, if so, needing to be returned according to the modified metadata received Configuration is moved back, if it is not, not needing then to carry out rollback configuration.

As shown in Figure 10, in a kind of one preferred embodiment of method of gray scale publication of the application, step S3 is executed same When, further include step S32, the new and/or old gray scale release tasks of the configuration item increased newly in original catalogue are returned It moves back, specifically includes:

Step S321 suspends to server and sends metadata；

Step S322 adds the anti-installation configuration item for corresponding to originally newly-increased configuration item in original catalogue, The anti-installation configuration item is used to delete corresponding originally newly-increased configuration item in the catalogue；

Step S323 modifies metadata and sends to corresponding server, and modified metadata includes server address, is somebody's turn to do Originally newly-increased configuration number (configuration item i.e. to be deleted is replaced in the original catalogue and the original catalogue that server uses Number) anti-installation configuration item number；

Step S324, if some server has been completed to configure according to the metadata being originally received, the service Device completes the configuration that retracts according to the modified metadata received.It is to delete here, corresponding for the rollback for increasing configuration item newly Except configuration item, it can judge whether some server has been completed to configure according to the flag bit being arranged in configuration item, if so, It then needs to carry out rollback configuration according to the modified metadata received, if it is not, not needing then to carry out rollback configuration.

In a kind of one preferred embodiment of method of gray scale publication of the application, after step S324, further includes:

After backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, it is original new to delete this The configuration item of increasing and corresponding anti-installation configuration item, delete metadata in anti-installation configuration item number, with facilitate it is subsequent with When can retract or re-execute the needs of gray scale release tasks.

As shown in figure 11, in a kind of one preferred embodiment of method of gray scale publication of the application, step S3 is executed same When, further include step S33, the new and/or old gray scale release tasks for the configuration item deleted in original catalogue are returned It moves back, specifically includes:

Step S331 suspends to server and sends metadata；

Step S332 adds the newly-increased configuration for corresponding to original anti-installation configuration item in original catalogue ?；Here, not needing to add if the newly-increased configuration item has existed in original catalogue；

Step S333 modifies metadata and sends to corresponding server, and modified metadata includes server address, is somebody's turn to do The number that original anti-installation configuration item is replaced in the original catalogue and the original catalogue that server uses is (i.e. to be deleted The number of configuration item) newly-increased configuration item number；

Step S334, if some server has been completed to configure according to the metadata being originally received, the service Device completes the configuration that retracts according to the modified metadata received.Here, being to rejoin for the rollback for deleting configuration item Configuration item originally, can judge whether some server has been completed to configure according to the flag bit being arranged in configuration item, If so, needing to carry out rollback configuration according to the modified metadata received, if it is not, not needing then to carry out rollback configuration.

In a kind of one preferred embodiment of method of gray scale publication of the application, after step S334, further includes:

Delete original anti-installation configuration item in original catalogue, configuration item in the catalogue to keep end-state Without conflicting.

In addition, for the offline situation of server, as long as directly deleting the metadata of the server, and to new clothes The online situation of business device, as long as increasing the metadata of the server.

As shown in figure 12, a kind of equipment 100 of gray scale publication is also provided according to the another side of the application, comprising:

First device 1, for the configuration item of new gray scale release tasks and old gray scale release tasks to be deposited in catalogue In, wherein the new gray scale release tasks and old gray scale release tasks are through the passed examination that conflicts；Here, the old sum New gray scale release tasks are gray scale release tasks in time in contrast, are new ash if newer in generation time Release tasks are spent, are old gray scale release tasks if older in generation time, the new gray scale publication engraved at one, If subsequent time has the gray scale release tasks of update, originally new gray scale release tasks then become old ash at the moment Release tasks are spent, in addition, the new gray scale release tasks and old gray scale release tasks are through the passed examination that conflicts, to guarantee The subsequent gray scale release tasks executed parallel and old gray scale release tasks clash, if there is multiple new gray scale publications simultaneously Task generates, then is also required between new gray scale release tasks through the passed examination that conflicts, and new gray scale release tasks can be pair The change of original catalogue is such as modified, increases and is deleted to the configuration item in original catalogue (BASE)；

Second device 2, for generating all candidates of new and old gray scale release tasks according to catalogue and its configuration item Task execution path, i.e. the carry out arbitrary arrangement combination producing to new gray scale release tasks and old gray scale release tasks The task execution path of all candidates, wherein the gray scale release tasks in every Geju City or new gray scale release tasks execute completion It is to be configured by the configuration item in its catalogue to server, each task execution path is used to execute old gray scale publication and appoints Business and/or new gray scale release tasks；

3rd device, for the implementation progress and each gray scale release tasks according to the gray scale release tasks of each server Distribution batch, select optimal task execution path as modified metadata from the task execution path of all candidates It is sent to corresponding server, wherein the metadata includes server address, the corresponding catalogue used of the server (environment) and the number of corresponding configuration item (state), the number of a configuration item are corresponding with a configuration item.Tool Body, for example need to update some configuration item A now with 10000 database servers, it needs to divide to ensure to stablize on line Hair batch is divided into 10 batches of progress gray scale publications, every a collection of 1000, starts corresponding generation gray scale release tasks 1, it is assumed that now 5 batches are pushed, and wherein the server owner (owner) of 4 batches of gray scale release tasks 1 has confirmed that and pass through that the 5th batch also true In recognizing, it is at this moment connected to second distributed tasks, needs to upgrade some software package B of 10000 database servers, passes through inspection After configuration file A and software B Lothrus apterus, gray scale release tasks 2 are generated, it is same to distribute 10 batches of progress gray scale publications of batch point, it can With according to the implementation progress of old gray scale release tasks (task 1), (old gray scale release tasks 1 may be on some servers Through executing, it is also possible to be not carried out) it with the distribution batch of each gray scale release tasks 1,2 is the corresponding task of each server selection Execution route executes task 2 again if part server has executed task 1, meanwhile, part server is also not carried out task 1, the problem of task 1 and task 2 are performed simultaneously, or consider distribution batch, part server, which first carries out, makees task 2 again Execution task 1, or first carry out task 1 and execute task 2 again, to realize that task 1 and task 2 can be in asynchronous servers It is upper to be executed simultaneously, and if task 1 needs to retract, due between each task by the passed examination that conflicts, when rollback, It will not influence continuing to execute for task 2.And so on, if receiving task 3 again, task 4 ... task N can be held simultaneously Row, is mutually independent of each other, does not conflict.For another example, there are 10000 servers, distribution batch of the A mission requirements to this 10000 servers Secondary to divide 5 batches of execution, every batch of executes 2000 servers, then, and has B mission requirements to this same 10000 servers Distributing batch is point 20 batches of execution, 500 servers is only carried out every time, at this point, if having gay A (only carrying out task A), gay B (only carries out task B), gay AB (being performed simultaneously task AB) three candidate task execution path, 2000 a batch of A task, B 500 a batch of task, if that selecting 2000 machines for never executing the two tasks from the inside, that is by optimization Task execution path, that just has 1500 and goes to gay A, has 500 to go to gay AB.Here, can be by using such as General catalogue (environment) and configuration item (state) in the configuration management tool of saltstack, the metadata can To deposit in a file, can also deposit in one of lane database or multiple tables, such as can be used cooperatively The metadata of MySQL database service device, can while gray scale publication concurrently be carried out by reaching multiple tasks execution route Effect, i.e., one or more gray scale release tasks execution in when, new gray scale posting request can be added, by distribution batch Optimal task execution path is selected, while guaranteeing not interfereing with each other mutually between task and task, greatly accelerates distribution configuration Speed.The core concept of the present embodiment is to be held when there is multiple gray scale release tasks demands by generating all possible task Walking along the street diameter, that is, middle directory, then for state, that is, gray scale release tasks implementation progress of current different server and distribution batch It is secondary that an optimal step task execution path is selected to send as metadata to corresponding server from middle directory, thus maximum limit Realize multitask gray scale publication simultaneously in degree ground.The core concept of the present embodiment is led to when there is multiple gray scale release tasks demands It crosses and generates all possible task execution path i.e. middle directory, then for the state of current different server, that is, gray scale publication The implementation progress and distribution batch of task are made from the optimal step task execution path of all possible task execution Path selection For the transmission of metadata corresponding server, to realize multitask to the maximum extent, gray scale is issued simultaneously.

As shown in figure 13, in a kind of one preferred embodiment of equipment of gray scale publication of the application, the equipment 100 is also wrapped It includes:

4th device 4 is used for after the 3rd device 3 execution, i.e., in the task execution path from all candidates After selecting optimal task execution path to send as modified metadata to corresponding server, each server root is controlled Configuration is completed according to the received metadata.

In a kind of one preferred embodiment of equipment of gray scale publication of the application, when new and old gray scale release tasks are When modifying the configuration item in original catalogue (BASE in environment),

The first device 1 then replicates an original catalogue (BASE) for often there is a new gray scale release tasks As new catalogue (GAY A, GAY B, GAY C ...), according to each gray scale release tasks in corresponding new catalogue to Modification configuration item is modified, and modified configuration item is obtained；Here, the catalogue (environment) of most original state is claimed The a configuration item in catalogue is carried out when receiving new gray scale release tasks gay A (a'b c) for BASE (a b c) Modification then first can generate a new environmentg from original BASE (a b c) duplication as gay A (a b c), and handle Configuration item a inside gay A goes modification to generate gay A (a'b c) by newest requirement, new gray scale release tasks gay A (a' B c) when executing, if receiving another new gray scale release tasks gay B (a b'c) requires modification configuration item b, at this moment meeting again One new environment of regeneration is gay B (a b'c) on the basis of original BASE (a b c)；

Correspondingly, the second device, sends out new gray scale release tasks and old gray scale according to catalogue and base configuration item In all possible task execution path of carry out arbitrary arrangement combination producing (distribution catalogue) of cloth task, as shown in figure 3, if former The distribution catalogue come is (BASE (1 2 3)), and when increasing new gray scale release tasks gay A, distribution catalogue is revised as (BASE (1 2 3), gay A (1'2 3)), similarly, when receiving new gray scale release tasks again when gay B, as shown in figure 4, distribution Catalogue is revised as (BASE (1 2 3), gay A (1'2 3), gay B (1 2'3), gay AB (1'2'3)), and three tasks are simultaneously The distribution catalogue of gray scale publication is as shown in figure 5, the distribution catalogue of four tasks gray scale publication simultaneously is as shown in Figure 6, and so on, Pass through the task for i.e. all candidates of intermediate state environment that different task was combined in duplication BASE catalogue and generation Execution route, and modify when new distributed tasks are added to execution route and generate the task execution road of new all candidates Diameter is finally reached the consistent state of all tasks, the gray scale publication of all distributed tasks is completed, even if more being appointed simultaneously Gray scale of being engaged in publication, can complete that is certain through this embodiment, as being performed simultaneously for task is more, intermediate environment The generation of (gay A, gay B ...) can be more, and execution route can be more complicated；

Correspondingly, the 3rd device 3 to the metadata that corresponding server is sent include server address, the server pair The number of corresponding modified configuration item in the new catalogue and the new catalogue that should be used.Here, new catalogue is opposite For original catalogue, every configuration gray scale for generating an original catalogue of new modification is sent out and task, then correspondence can give birth to At a new catalogue, the generation of each new catalogue may have precedence relationship in time, but be not present between each new catalogue The concept of the new and old relationship may be the new catalogue of new gray scale release tasks, it is also possible to old gray scale release tasks New catalogue, but the new catalogue for being all for the relatively primitive catalogue of each new catalogue.For example, original before receiving gay A Metadata be machine X-- > BASE-- > [1], [2], [3], after receiving gay A, metadata is revised as machine X-- > gay A-- > [1], [2], [3] similarly when receiving new gray scale release tasks again when gay B, have executed The server of gay A also needs to be distributed task gay B, and the machine for having not carried out any task needs to carry out gay by batch AB publication, for example, can will be not carried out the metadata of the server X of gay A further by machine X-- > gay A-- > [1], machine X-- > gay AB-- > [1] is revised as in [2], [3], [2], [3], simultaneously, it is contemplated that the problem of batch, simultaneously By the metadata of server Y by original metadata machine Y-- > BASE-- > [1], [2], [3] are revised as machine AB-- > [1] Y-- > gay a/gay b/gay, [2], [3], i.e. m achine Y-- > gay A--gay AB-- > [1], [2], [3] or AB-- > [1] machine Y-- > gay B--gay, [2], [3] or machine Y-- > gay AB-- > [1], 【2】,【3】。

As shown in figure 14, in a kind of one preferred embodiment of equipment of gray scale publication of the application, the equipment further includes 5th device 5 is matched for after the 4th device 4 execution being each server according to the metadata completion received After setting,

The original catalogue and all new catalogues are deleted after backing up original catalogue and all new catalogues；Here, needing The i.e. original catalogue of all intermediate state environment and all new catalogues are backed up, it, can be quickly extensive when to prevent there is rollback to require Multiple catalogue, can delete after backup, avoid with the presence of multiple environment and generate interference；

New original catalogue is incorporated as with all new catalogues；Here, the catalogue for needing to replicate end-state is made It for original catalogue (BASE), is resetted with facilitating, prepares the glitch-free environment of relative clean, example for gray scale release tasks next time Such as, first gray scale release tasks gay A (a'b c) is modification configuration item a, second gray scale release tasks gay A (a b'c) It is modification configuration item b, first gray scale release tasks gay A (a b c') is modification configuration item c, the then conjunction of all new catalogues It and is gay A (a'b'c')；

As shown in figure 15, in a kind of one preferred embodiment of equipment of gray scale publication of the application, the equipment 100 is also wrapped Include the 6th device 6, for while the 3rd device 3 executes, to the new of the configuration item modified in original catalogue and/ Or old gray scale release tasks retract, and specifically include:

Suspend to server and sends metadata；

After modifying metadata to the state for not including the gray scale release tasks wait retract, by modified metadata to correspondence Server is sent；It is first if receive request and need to retract to some task when multitask carries out gray scale publication simultaneously First suspend the push of metadata, and all current metadata comprising rollback task are return back to the gray scale that a upper nothing should be to be retracted The state of release tasks currently carries out simultaneously by taking the case that four tasks of aforementioned modifications configuration item are modified simultaneously as an example Distributed tasks have A, B, C, D, now need to retract to A task, then push can be suspended first, avoid influencing further expanding Greatly, while metadata is modified, i.e., retracted to the metadata for the intermediate environment for having included A, and improve rollback task Optimization level, i.e., the current metadata for GAY A is return back to BASE, GAY A, B return back to GAY B, GAY A, and C is return back to GAY C, GAY A, D return back to GAY D, and GAY A, B, C return back to GAY B, C ... and so on, due to aforementioned 5th device 5, In have backed up original catalogue and all new catalogues after delete the original catalogue and all new catalogues, that is, have backed up The catalogue and all new catalogues of all intermediate state environment, that is, original, so when thering is rollback to require here, it can be quickly extensive Data are recovered to the state for not including gray scale release tasks to be retracted；

If some server has been completed to configure according to the metadata being originally received, the server is according to reception The modified metadata arrived completes the configuration that retracts.Here, can judge some according to the flag bit being arranged in configuration item Whether server, which has been completed, configures, if so, need to carry out rollback configuration according to the modified metadata received, if It is no, then it does not need to carry out rollback configuration.

In a kind of one preferred embodiment of equipment of gray scale publication of the application, when new and old gray scale release tasks are When increasing the configuration item in original catalogue,

The first device 1, for often there is a new old gray scale release tasks, then according to each gray scale release tasks Configuration item to be increased is added in the original catalogue；Here, when gray scale release tasks are increased newly in original catalogue When configuration item, it may not be necessary to as being completed in previous embodiment by duplication BASE, because catalogue will not be caused by increasing configuration item In existing configuration item modification, so only needing to be directly added into a new configuration item in former BASE；

Correspondingly, the 3rd device 3 includes that server address, the server make to the metadata that corresponding server is sent The number of corresponding configuration item to be increased in original catalogue and the original catalogue.Here, matching in modification metadata Set item (state) content, i.e., pushed again plus new state, if such as when (1 2 3) BASE, corresponding member number According to for machine X (server X) -- > BASE-- > [1], [2], [3], when will the increased configuration item A in BASE when, step BASE is changed to BASE (1 2 3A) in S121, it is then, corresponding that metadata is revised as metadata machine in step S321 X-- > BASE-- > [1], [2], [3], [A], here [1], [2], [3], [A] is respectively the configuration corresponding to 123 A of configuration item The number of item if existing simultaneously multiple newly-increased configuration item tasks, and generates metadata using same method, for example, having Two configuration items A and B will increase, and according to batch and each server implementation progress, can increase A and B metadata simultaneously, can also divide Step increases the metadata of A or B, then metadata is carried out to the push to server.

As shown in figure 16, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 It further include the 7th device 7, for before the first device 1 execution, i.e., often having a new old gray scale release tasks, Before then configuration item to be increased is added in the original catalogue according to each gray scale release tasks, original mesh is backed up Record.Here, back up current BASE environment before newly-increased configuration item, be in order to it is subsequent need the case where retracting to occur when, energy It is enough successfully return back to it is newly-increased before BASE environment.

As shown in figure 17, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 Further include the 8th device 8, is used for while the 3rd device 3 executes, to the new of the configuration item increased newly in original catalogue And/or old gray scale release tasks retract, specifically include:

Suspend to server and sends metadata；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server make The anti-of originally newly-increased configuration number (configuration item No. i.e. to be deleted) is replaced in original catalogue and the original catalogue The number of configuration item is installed；

If some server has been completed to configure according to the metadata being originally received, the server is according to reception The modified metadata arrived completes the configuration that retracts.Here, corresponding for the rollback for increasing configuration item newly is to delete configuration item, it can To judge whether some server has been completed to configure according to the flag bit being arranged in configuration item, if so, needing basis The modified metadata received carries out rollback configuration, if it is not, not needing then to carry out rollback configuration.

As shown in figure 18, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 It further include the 9th device 9, for after the 8th device 8 execution, i.e., server to be according to the modified first number received After completing rollback configuration, after backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, The configuration item originally increased newly and corresponding anti-installation configuration item are deleted, the number of the anti-installation configuration item in metadata is deleted, To facilitate the subsequent needs that can retract or re-execute at any time gray scale release tasks.

In a kind of one preferred embodiment of equipment of gray scale publication of such as figure the application, when new and old gray scale publication is appointed When business is the configuration item in the original catalogue of deletion,

The first device 1 then exists according to each gray scale release tasks for often there is a new and old gray scale release tasks Increase by one anti-installation configuration item is respectively corresponded in original catalogue, the anti-installation configuration item is corresponding in the catalogue for deleting Configuration item to be deleted；

Correspondingly, the 3rd device 3 includes that server address, the server make to the metadata that corresponding server is sent The number of the anti-installation configuration item of the number of configuration item to be deleted is replaced in original catalogue and the original catalogue.? This, replaces the number of the anti-installation configuration item of the number of configuration item to be deleted that is, in the metadata in the original catalogue The number of the correspondence configuration item of the configuration item to be deleted is removed in the original catalogue that each server uses, and adds institute State the number of the correspondence configuration item of anti-installation configuration item.Here the deletion of configuration item is carried out to state information in BASE Modification, but be not directly delete, but create anti-installation configuration item (uninstall state) in intermediate state, and The state for needing to delete will be removed in original metadata before push metadata, uninstall state is added.

As shown in figure 19, in a kind of one preferred embodiment of equipment of gray scale publication of the application, the equipment further includes Tenth device 10, for before the first device 1 execution, i.e., often having a new and old gray scale release tasks, then basis Before each gray scale release tasks respectively correspond increase by one anti-installation configuration item in original catalogue, original mesh is backed up Record.Here, back up current BASE environment before deleting configuration item, be in order to it is subsequent need the case where retracting to occur when, energy It is enough successfully return back to it is newly-increased before BASE environment.

As shown in figure 20, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 Further include the 11st device 11, is used for after the 4th device 4 execution, i.e., in each server according to receiving It, will after backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue after metadata completes configuration Configuration item to be deleted and corresponding anti-installation configuration item are deleted from original catalogue, here, in the original catalogue of backup to The configuration item of deletion and corresponding anti-installation configuration item are for the subsequent possible needs to retract, by configuration item and correspondence to be deleted Anti- installation configuration item is to keep in the catalogue of end-state configuration item without conflicting feelings from deleting in original catalogue Condition；And each server in metadata is corresponded into the anti-correspondence configuration item for installing configuration item in the original catalogue used Number is deleted, and to remove unnecessary configuration item, keeps configuration item without conflicting situation, for example, in original metadata The number of configuration item is (2, -1), wherein -1 is the number of the correspondence configuration item of anti-installation configuration item, the then metadata after deleting In the number of configuration item be revised as (2),

As shown in figure 21, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 Further include the tenth two devices 12, be used for while the 3rd device 3 executes,

Suspend to server and sends metadata；

The newly-increased configuration item for corresponding to original anti-installation configuration item is added in original catalogue；Here, if The newly-increased configuration item has existed in original catalogue, then does not need to add；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server make Replaced in original catalogue and the original catalogue original anti-installation configuration item number (configuration item i.e. to be deleted Number) newly-increased configuration item number；

If some server has been completed to configure according to the metadata being originally received, the server is according to reception The modified metadata arrived completes the configuration that retracts.Here, being to rejoin original configuration for the rollback for deleting configuration item , it can judge whether some server has been completed to configure according to the flag bit being arranged in configuration item, if so, needing Rollback configuration is carried out according to the modified metadata received, if it is not, not needing then to carry out rollback configuration.

As shown in figure 22, as figure the application a kind of gray scale issue one preferred embodiment of equipment in, the equipment 100 Further include the 13rd device 13, is used for after the tenth two devices 12 execution, i.e., in server according to the modification received After metadata afterwards completes rollback configuration, original anti-installation configuration item in the original catalogue is deleted, to keep most Configuration item is without conflicting in the catalogue of whole state.

In conclusion the application appoints according to the implementation progress of the gray scale release tasks of each server and the publication of each gray scale The distribution batch of business selects optimal task execution path as modified first number from the task execution path of all candidates It is sent according to corresponding server, achievees the effect that multiple tasks execution route can while concurrently carry out gray scale publication, i.e., one When in a or multiple gray scale release tasks execution, new gray scale posting request can be added, is selected by distribution batch optimal Task execution path, while guaranteeing not interfereing with each other mutually between task and task, greatly accelerate the speed of distribution configuration.

Obviously, those skilled in the art can carry out various modification and variations without departing from the essence of the application to the application Mind and range.In this way, if these modifications and variations of the application belong to the range of the claim of this application and its equivalent technologies Within, then the application is also intended to include these modifications and variations.

It should be noted that the application can be carried out in the assembly of software and/or software and hardware, for example, can adopt With specific integrated circuit (ASIC), general purpose computer or any other realized similar to hardware device.In one embodiment In, the software program of the application can be executed to implement the above steps or functions by processor.Similarly, the application Software program (including relevant data structure) can be stored in computer readable recording medium, for example, RAM memory, Magnetic or optical driver or floppy disc and similar devices.In addition, hardware can be used to realize in some steps or function of the application, example Such as, as the circuit cooperated with processor thereby executing each step or function.

In addition, a part of the application can be applied to computer program product, such as computer program instructions, when its quilt When computer executes, by the operation of the computer, it can call or provide according to the present processes and/or technical solution. And the program instruction of the present processes is called, it is possibly stored in fixed or moveable recording medium, and/or pass through Broadcast or the data flow in other signal-bearing mediums and transmitted, and/or be stored according to described program instruction operation In the working storage of computer equipment.Here, including a device according to one embodiment of the application, which includes using Memory in storage computer program instructions and processor for executing program instructions, wherein when the computer program refers to When enabling by processor execution, method and/or skill of the device operation based on aforementioned multiple embodiments according to the application are triggered Art scheme.

It is obvious to a person skilled in the art that the application is not limited to the details of above-mentioned exemplary embodiment, Er Qie In the case where without departing substantially from spirit herein or essential characteristic, the application can be realized in other specific forms.Therefore, no matter From the point of view of which point, the present embodiments are to be considered as illustrative and not restrictive, and scope of the present application is by appended power Benefit requires rather than above description limits, it is intended that all by what is fallen within the meaning and scope of the equivalent elements of the claims Variation is included in the application.Any reference signs in the claims should not be construed as limiting the involved claims.This Outside, it is clear that one word of " comprising " does not exclude other units or steps, and odd number is not excluded for plural number.That states in device claim is multiple Unit or device can also be implemented through software or hardware by a unit or device.The first, the second equal words are used to table Show title, and does not indicate any particular order.

Claims

1. a kind of method of gray scale publication, wherein include:

The configuration item of new gray scale release tasks and old gray scale release tasks is deposited in catalogue, wherein the new ash Release tasks and old gray scale release tasks are spent through the passed examination that conflicts；

The task execution path of all candidates of new and old gray scale release tasks is generated according to catalogue and its configuration item, it is described The task execution path of all candidates includes: the task execution path and old gray scale release tasks to new gray scale release tasks Task execution path carry out arbitrary arrangement and combine task execution path generated；

According to the distribution batch of the implementation progress of the gray scale release tasks of each server and each gray scale release tasks, from all Optimal task execution path is selected to send as modified metadata to corresponding server in candidate task execution path, Wherein, the metadata is for configuring corresponding server, including server address, the corresponding catalogue used of the server With the number of corresponding configuration item.

2. the method for claim 1, wherein selecting optimal task execution from the task execution path of all candidates After path is sent as modified metadata to corresponding server, further includes:

Each server completes configuration according to the metadata received.

3. method according to claim 2, wherein when new and old gray scale release tasks are in the original catalogue of modification When configuration item, the configuration item of new and old gray scale release tasks is deposited in catalogue, comprising:

Often there are a new gray scale release tasks, then replicates an original catalogue as new catalogue, sent out according to each gray scale Cloth task modifies to the configuration item to be modified in corresponding new catalogue, obtains modified configuration item；

Select optimal task execution path as modified metadata to correspondence from the task execution path of all candidates During server is sent,

The metadata includes server address, repairs in the corresponding new catalogue and the new catalogue used of the server accordingly The number of configuration item after changing.

4. method as claimed in claim 3, wherein each server completes configuration according to the metadata received Afterwards, further includes:

New original catalogue is incorporated as with all new catalogues；

Metadata is modified, the metadata includes server address, the corresponding new original catalogue used of the server and is somebody's turn to do The number of corresponding modified configuration item in new original catalogue.

5. method as claimed in claim 3, wherein select optimal task execution from the task execution path of all candidates While path is sent as modified metadata to corresponding server, the method also includes:

Suspend to server and sends metadata；

After modifying metadata to the state for not including the gray scale release tasks wait retract, by modified metadata to corresponding with service Device is sent；

If some server has been completed to configure according to the metadata being originally received, the server is according to receiving Modified metadata completes the configuration that retracts.

6. method according to claim 2, wherein when new and old gray scale release tasks are increased in original catalogue When configuration item, the configuration item of new gray scale release tasks and old gray scale release tasks is deposited in catalogue, comprising:

Often there are a new old gray scale release tasks, then institute is added in configuration item to be increased according to each gray scale release tasks It states in original catalogue；

The metadata include in original catalogue and the original catalogue that server address, the server use accordingly to Increase the number of configuration item.

7. method as claimed in claim 6, wherein often have a new old gray scale release tasks, then according to each gray scale Before configuration item to be increased is added in the original catalogue release tasks, further includes:

Back up original catalogue.

8. method as claimed in claim 6, wherein select optimal task execution from the task execution path of all candidates While path is sent as modified metadata to corresponding server, the method also includes:

Suspend to server and sends metadata；

The anti-installation configuration item for corresponding to originally newly-increased configuration item, the anti-installation configuration are added in original catalogue Item is for deleting corresponding originally newly-increased configuration item in the catalogue；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server use The number of the anti-installation configuration item of originally newly-increased configuration number is replaced in original catalogue and the original catalogue；

9. method according to claim 8, wherein server completes the configuration that retracts according to the modified metadata received Later, further includes:

After backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, delete what this was originally increased newly Configuration item and corresponding anti-installation configuration item delete the number of the anti-installation configuration item in metadata.

10. method according to claim 2, wherein when new and old gray scale release tasks are deleted in original catalogue Configuration item when, the configuration item of new gray scale release tasks and old gray scale release tasks is deposited in catalogue, comprising:

Often there are a new and old gray scale release tasks, then respectively corresponds increasing in original catalogue according to each gray scale release tasks Add an anti-installation configuration item, the anti-installation configuration item is for deleting corresponding configuration item to be deleted in the catalogue；

The metadata includes replacing in original catalogue and the original catalogue that server address, the server use wait delete The number of the anti-installation configuration item of the number of the configuration item removed.

11. method as claimed in claim 10, wherein often have a new and old gray scale release tasks, then according to each gray scale Release tasks are respectively corresponded in original catalogue before increase by one anti-installation configuration item, further includes:

Back up original catalogue.

12. method as claimed in claim 10, wherein each server completes configuration according to the metadata received After step, further includes:

After backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue, by configuration item to be deleted and Corresponding anti-installation configuration item is deleted from original catalogue；

By the volume of the anti-correspondence configuration item for installing configuration item in the corresponding original catalogue used of each server in metadata Number delete.

13. method as claimed in claim 10, wherein select optimal task to hold from the task execution path of all candidates While walking along the street diameter is sent as modified metadata to corresponding server, further includes:

Suspend to server and sends metadata；

It modifies metadata simultaneously to send to corresponding server, modified metadata includes that server address, the server use The number of the newly-increased configuration item of the number of original anti-installation configuration item is replaced in original catalogue and the original catalogue；

14. method as claimed in claim 13, wherein server is completed to retract according to the modified metadata received matches After setting, further includes:

Delete original anti-installation configuration item in the original catalogue.

15. a kind of equipment of gray scale publication, wherein include:

First device, for the configuration item of new gray scale release tasks and old gray scale release tasks to be deposited in catalogue, In, the new gray scale release tasks and old gray scale release tasks are through the passed examination that conflicts；

Second device, the task of all candidates for generating new and old gray scale release tasks according to catalogue and its configuration item Execution route, the task execution path of all candidates include: to the task execution path of new gray scale release tasks and old The task execution paths of gray scale release tasks carry out arbitrary arrangement and combine task execution path generated；

3rd device, for the implementation progress of gray scale release tasks and dividing for each gray scale release tasks according to each server Batch is sent out, selects optimal task execution path as modified metadata to right from the task execution path of all candidates Server is answered to send, wherein the metadata is used to configure corresponding server, including server address, the server The number of the corresponding catalogue and corresponding configuration item used.

16. equipment as claimed in claim 15, wherein the equipment further include:

4th device, for after 3rd device execution, controlling each server according to received first number It is configured according to completion.

17. equipment as claimed in claim 16, wherein when new and old gray scale release tasks are in the original catalogue of modification Configuration item when,

The first device then replicates an original catalogue as new mesh for often there is a new gray scale release tasks Record modifies to the configuration item to be modified in corresponding new catalogue according to each gray scale release tasks, obtains modified match Set item；

The 3rd device to the metadata that corresponding server is sent include server address, the server it is corresponding use it is new The number of corresponding modified configuration item in catalogue and the new catalogue.

18. equipment as claimed in claim 17, wherein the equipment further includes the 5th device, in the 4th device After execution,

New original catalogue is incorporated as with all new catalogues；

19. equipment as claimed in claim 17, wherein the equipment further includes the 6th device, in the 3rd device While execution,

Suspend to server and sends metadata；

20. equipment as claimed in claim 16, wherein when new and old gray scale release tasks are increased in original catalogue Configuration item when,

The first device then will be to according to each gray scale release tasks for often there is a new old gray scale release tasks Increased configuration item is added in the original catalogue；

The 3rd device is to the original mesh that the metadata that corresponding server is sent includes that server address, the server use The number of corresponding configuration item to be increased in record and the original catalogue.

21. equipment as claimed in claim 20, wherein the equipment further includes the 7th device, in the first device Before execution, original catalogue is backed up.

22. equipment as claimed in claim 20, wherein the equipment further includes the 8th device, in the 3rd device While execution,

Suspend to server and sends metadata；

23. equipment as claimed in claim 22, wherein the equipment further includes the 9th device, in the 8th device After execution, after backing up the originally newly-increased configuration item and corresponding anti-installation configuration item in original catalogue, it is original to delete this Newly-increased configuration item and corresponding anti-installation configuration item deletes the number of the anti-installation configuration item in metadata.

24. equipment as claimed in claim 16, wherein when new and old gray scale release tasks are deleted in original catalogue Configuration item when,

The first device, for often there is a new and old gray scale release tasks, then according to each gray scale release tasks original Catalogue in respectively correspond the anti-installation configuration item of increase by one, the anti-installation configuration item be used to delete in the catalogue it is corresponding to The configuration item of deletion；

The 3rd device is to the original mesh that the metadata that corresponding server is sent includes that server address, the server use The number of the anti-installation configuration item of the number of configuration item to be deleted is replaced in record and the original catalogue.

25. equipment as claimed in claim 24, wherein the equipment further includes the tenth device, in the first device Before execution, original catalogue is backed up.

26. equipment as claimed in claim 24, wherein the equipment further includes the 11st device, in the 4th dress It, will be to be deleted after backing up the configuration item to be deleted and corresponding anti-installation configuration item in original catalogue after setting execution Configuration item and corresponding anti-installation configuration item are deleted from original catalogue；And each server in metadata is corresponded to and is used Original catalogue in the anti-correspondence configuration item for installing configuration item number delete.

27. equipment as claimed in claim 24, wherein the equipment further includes the tenth two devices, for filling in the third While setting execution,

Suspend to server and sends metadata；

28. equipment as claimed in claim 27, wherein the equipment further includes the 13rd device, for the described 12nd After device executes, original anti-installation configuration item in the original catalogue is deleted.