CN117591132B - Service release method and release system - Google Patents
Service release method and release system Download PDFInfo
- Publication number
- CN117591132B CN117591132B CN202410043938.5A CN202410043938A CN117591132B CN 117591132 B CN117591132 B CN 117591132B CN 202410043938 A CN202410043938 A CN 202410043938A CN 117591132 B CN117591132 B CN 117591132B
- Authority
- CN
- China
- Prior art keywords
- deployment
- unit
- task
- tasks
- sub
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 238000009826 distribution Methods 0.000 claims description 7
- 230000007613 environmental effect Effects 0.000 claims description 3
- 238000012545 processing Methods 0.000 abstract description 2
- 238000007726 management method Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 6
- 238000004519 manufacturing process Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012800 visualization Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
- G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5061—Partitioning or combining of resources
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Hardware Redundancy (AREA)
Abstract
The invention discloses a service release method and a service release system, which belong to the technical field of electric digital data processing, wherein the service release method comprises the following steps: according to the dependency of each unit of the subsystem, a stage of subsystem release is obtained; dividing the units in the same stage into one or more sub-stages according to the deployment environment of the units, wherein the task set of the sub-stages comprises the deployment tasks of one or more units; and sequentially issuing corresponding task sets according to the sequence of the stages and the sub-stages. The dependency does not exist among different units in the same sub-stage, the deployment environments are different, and the steps can be performed in parallel; when the parallel steps are sent, mutual interference among units can not be caused, the unit deployment efficiency can be improved, the intermediate operation steps from the machine list to the release are reduced, and the release safety is enhanced.
Description
Technical Field
The invention relates to the technical field of electric digital data processing, in particular to a service release method and a service release system.
Background
With the deep development of informatization technology and the wide use of micro-service architecture, great challenges are brought to service release. There may be tens or more subsystems for a complete customer service product, and a subsystem typically contains multiple modular units. There are dependencies between subsystems of the same cluster, while the tens of subsystems are deployed to multiple units in the cluster because of the high availability of the subsystems.
In more complex deployment, the subsystems can be deployed to different clusters at the same time, and the whole deployment process is very complicated.
The traditional production and release modes are as follows: the operation and maintenance personnel manually create a release pipeline, manually modify the environment and parameters required by release or online according to the version and the environment of the service product, and then complete deployment according to the sub-units of the subsystem in a cluster-by-cluster and environment-by-environment deployment pipeline. This way of publishing has more problems: firstly, the configured artificial operation is excessive, more artificial participation introduces uncertainty, and the requirements of certainty and stability of production deployment are not met; the service release process has low efficiency and timeliness, so that the production requirement cannot be met; moreover, the whole deployment state of the assembly line can be only checked, the deployment condition of each cluster environment in the multi-subsystem, multi-unit and multi-environment deployment can not be accurately mastered, the configuration file is associated with the on-line unit based on the branches, the risk of manually falsifying the on-line configuration exists, and the deployment tracing and archiving are inconvenient.
With the popularity of agile development, the cloud frequency of application update is faster and faster, and a flexible, rapid and safe service release method is urgently needed.
Disclosure of Invention
Aiming at the technical problems in the prior art, the invention provides a service release method and a service release system, which can release the service rapidly and safely.
The invention discloses a service release method, which comprises one or more subsystems, wherein the subsystems comprise a plurality of units, and the release method comprises the following steps: according to the dependency of each unit of the subsystem, a stage of releasing the subsystem is obtained; dividing the units in the same stage into one or more sub-stages according to the deployment environment of the units, and obtaining a task set of the sub-stages; and sequentially issuing the task sets according to the sequence of the stages and the sub-stages.
Preferably, a plurality of deployment tasks in the task set are issued in parallel; the deployment environment includes a target cluster or target node.
Preferably, the method of dividing the sub-stages comprises:
Obtaining a deployment environment of each unit in the stage, wherein the deployment environment comprises a target deployment cluster;
classifying the deployment tasks of the units according to the target deployment cluster or the target node to obtain a plurality of unit sets;
Giving priorities to the deployment tasks of the unit sets respectively, wherein the priorities of the deployment tasks of the same unit set are different;
and dividing the unit deployment task of the stage into one or more sub-stages according to the priority.
Preferably, the priorities are assigned according to the order of the target clusters or the locations of the target nodes.
Preferably, the release tasks of the stage are represented by father task TP, the release tasks of the sub-stage are represented by child tasks Tpsub, the task set is represented by system task Tsys, and the unit deployment task is represented by Tsysdeploy; and performing serial execution among the parent tasks, performing serial execution among the child tasks, and performing parallel execution of the system tasks.
Preferably, the method for publishing the corresponding task set comprises the following steps:
step 301: generating an execution record table according to the release sequence of the task set;
step 302: judging whether a parent task to be executed exists in the execution record table;
If yes, go to step 303: executing the father task according to the release sequence of the stages, entering a subtask list, and executing step 305;
if not, step 304: ending the service release;
step 305: sequentially reading a system task queue from the subtask list according to the priority;
Step 306: consuming the system task queue, executing the unit deployment task in the system task queue, generating a deployment record of the system task and the unit deployment task, executing step 305 until the subtask list is consumed, and executing step 302.
Preferably, the method of deployment is skipped:
judging whether the first unit of the first subsystem fails to be deployed or not;
If yes, marking the first subsystem;
Judging whether a second unit to be issued belongs to the first subsystem or not;
if the second unit belongs to the first subsystem, skipping the release of the second unit;
the service comprises a first version and a second version, and a version rollback method comprises the following steps:
determining if the second version has a logic problem,
If so, acquiring the deployed units of the second version and a deployment environment from the deployment record;
and rolling back the deployed units to the corresponding units of the first version according to the deployment environment.
Preferably, configuration management information is set for the unit, and the configuration management information includes: the subsystem issues a version, a version submission record, a deployment package address and a deployment cluster;
and performing unit deployment tasks of the task set according to the environmental configuration of the units.
The invention also provides a system for realizing the release method, which comprises a stage arrangement module, a sub-stage arrangement module and a release module, wherein the stage arrangement module is used for obtaining the release stage of the subsystem according to the dependence of each unit of the subsystem; the sub-stage arrangement module is used for dividing the units in the same stage into one or more sub-stages according to the deployment environment of the units, and obtaining a task set of the sub-stages; the issuing module is used for issuing corresponding task sets in sequence according to the sequence of the stage and the sub-stage.
Preferably, the release system further comprises a version control module for service version and configuration management of subsystems and units.
Compared with the prior art, the invention has the beneficial effects that: the dependency does not exist among different units in the same sub-stage, the deployment environments are different, and the steps can be performed in parallel; when the parallel steps are performed, the mutual interference among the units is not caused, and the unit deployment efficiency can be improved; supporting service release of multiple systems, multiple units and multiple environments and release of multiple services through the release list; the problems of low efficiency and high error caused by a single release task are avoided, the intermediate operation steps from the operation of loading the machine list to release are reduced, and the release safety is enhanced.
Drawings
FIG. 1 is a flow chart of a service distribution method of the present invention;
FIG. 2 is a logical block diagram of a service publishing phase;
FIG. 3 is a flow chart of a method of publishing a task set;
fig. 4 is a logic block diagram of the service distribution system of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The invention is described in further detail below with reference to the attached drawing figures:
A method of publishing a service, the service comprising one or more subsystems, the subsystems comprising a plurality of units, as shown in fig. 1, the method of publishing comprising:
Step 101: and obtaining the release stage of the subsystem according to the dependency of each unit of the subsystem.
Step 102: units of the same stage are divided into one or more sub-stages according to the deployment environment of the units, and a task set of the sub-stages comprises deployment tasks of one or more units.
Wherein the deployment environment comprises a target cluster or target node. Separate configuration management information may be set for the unit, the configuration management information including: subsystem release version, version commit record, deployment package address, deployment cluster, etc. And performing unit deployment tasks of the task set according to the environmental configuration of the units.
Step 103: and generating a release list according to the sequence of the stages and the sub-stages, and sequentially releasing the corresponding task sets.
The dependency does not exist among different units in the same sub-stage, the deployment environments are different, and the steps can be performed in parallel; in the parallel step, the mutual interference among the units is not caused, and the unit deployment efficiency can be improved; supporting service release of multiple systems, multiple units and multiple environments and release of multiple services through the release list; the problems of low efficiency and high error caused by a single release task are avoided, the intermediate operation steps from the operation of loading the machine list to release are reduced, and the release safety is enhanced.
In step 102, the method for dividing sub-phases includes:
Step 201: a deployment environment of each unit in the phase is obtained, wherein the deployment environment comprises a target deployment cluster.
Step 202: and classifying the unit deployment tasks according to the target deployment cluster or the target node to obtain a plurality of unit sets.
Step 203: and giving priorities to the deployment tasks of the unit sets respectively, wherein the priorities of the deployment tasks of the same unit set are different.
The order of priority may be empirically set; the setting may also be performed according to the order of the target clusters and the order of the target nodes.
Step 204: and dividing the unit deployment task of the stage into one or more sub-stages according to the priority. I.e. unit deployment tasks of the same priority are in the same sub-phase.
The target deployment clusters or deployment target nodes of the units are ensured to be different in the same priority, so that the units in the same sub-stage are prevented from interfering or competing for resources during release, and the parallel release efficiency is improved.
FIG. 2 shows a specifically orchestrated service delivery task set, including subsystems A, B and C, divided into phase A, phase B, and phase N. In the sub-phase with the priority of 1 in the phase a, the sub-phase comprises deployment tasks of the units a1 to the cluster a, deployment tasks of the units a1 to the cluster B and the like, when the same unit a2 is released to different environments, the release tasks of the units a1 and B1 released to the cluster a are in different priorities as two deployment tasks, and the release tasks are not released at the same time, so that interference or resource competing does not occur. The cell a2 is integrated with the cell a1, and the stage of the cell a1 precedes the stage of the cell a 2.
In one embodiment, subsystem-related information that does not need to be online may be filtered prior to task orchestration. The release tasks of the stage are represented by parent tasks (PARENT TASK, TP), the release tasks of the sub-stage are represented by child tasks (parent subtask) Tpsub, the task set of the sub-stage is represented by system tasks (SYSTEM TASK) Tsys, and the unit deployment tasks are represented by Tsysdeploy. Tsysdeploy is the minimum deployment unit combined according to the cluster and unit information, and is the deployment task actually executed. The units are divided according to a high availability deployment architecture, for example, services need to achieve different available domains (AZ) or different data centers to be highly available, and each available domain or data center is a unit; the stages can be manually divided and recorded in the phone bill.
Tp, tpsub, tsys are all scheduled tasks. The parent tasks Tp are executed serially, the child tasks Tpsub are executed serially, and the system tasks Tsys are executed in parallel.
The following codes show a specific definition format:
{ "id": "3132123299652071424",
"jobName": "XXX",
"Tplist": [
{ "id": "3132123299937284096",
"stageName": null,
"description": "",
"currentFlag": 0,
"sort": 1,
"Tpsubslist": [
{ "id": "3132123299954061312",
"stepName": "1-1",
"sort": 1,
"TsysList": [
{ "id": "3132123299954061313",
"name": ""
"TsysdeployList": [{"id": "3132123299954061313",
"unitdeployname": "co-city cluster _ subsystem _ unit 1",
"executeID":"xxx" } ] }]}] }] }
If executed serially, the sort attribute may be incremented.
When executing the release task, the related scheduling task can be deployed through the message queue coupling, the task execution is controlled through the task state machine, and the deployment is elasticized through the deployment execution engine link kubernetes. As shown in fig. 3, the method for publishing a task set includes:
Step 301: and generating an execution record table according to the release sequence of the task set.
Step 302: and judging whether the parent task to be executed exists in the execution record table.
If yes, go to step 303: the parent task is executed in the order of the phases, the child task list is entered, and step 305 is executed.
If not, step 304: and ending the service release.
Step 305: and sequentially reading the system task queues from the subtask list according to the order of the priorities.
Step 306: consuming the system task queue, executing the unit deployment task in the system task queue, generating a deployment record of the system task and the unit deployment task, executing step 305 until the subtask list is consumed, and executing step 302.
In the deployment task of the execution unit, after the execution engine finishes executing, the callback task scheduling engine updates the state. If Tdeploy completes simultaneously Tsys completes and Tpsub completes, determine if Tp is to be executed Tpsub, then generate Tpsub task into the queue.
For faults encountered in service delivery, the deployment method may be skipped:
Step 401: whether the first unit of the first subsystem fails to be deployed is judged.
If yes, step 402: the first subsystem is marked.
If not, go to step 403: the next unit is published until all units are published.
Step 404: judging whether a second unit to be issued belongs to the first subsystem or not;
If the first subsystem is owned, step 405 is executed: skipping the publication of the second unit.
If not, go to step 406: the second unit is issued.
When the deployment task of a certain environment fails, the release task of the subsystem can be skipped in the rest of the parent deployment tasks for execution. The execution engine supports filtering of tasks and is ignored during execution.
If the service comprises a first version and a second version, the method for version rollback comprises the following steps:
Step 411 is performed: determining if the second version has a logic problem,
If so, step 412 is performed: from the deployment record, the deployed units of the second version and the deployment environment are obtained, and step 413 is performed.
If not, the second version is continuously monitored.
Step 413: the deployed units are rolled back to the corresponding units of the first version according to the deployment environment.
Rollback of the unitized and deployed environments involved with the version of any subsystem in any stage may roll back to the last successful version. The execution engine needs to record the execution information in the execution process, and can select part of task execution history tasks to realize rollback when executing. In a specific design, the full rollback of a plurality of subsystems of a single release task can be supported, and the overall failure of the service possibly caused by the failure of a subsystem in a special scene is met.
The present invention also provides a publication system for implementing the above publication method, as shown in fig. 4, including a stage arrangement module 1, a sub-stage arrangement module 2 and a publication module 3,
The stage arrangement module 1 is used for obtaining the stage issued by the subsystem according to the dependency of each unit of the subsystem; the sub-stage arrangement module 2 is used for dividing the units in the same stage into one or more sub-stages according to the deployment environment of the units, and obtaining a task set of the sub-stages, wherein the task set of the sub-stages comprises deployment tasks of one or more units; the issuing module 3 is configured to issue corresponding task sets sequentially according to the sequence of the stages and the sub-stages. In the release process, synchronization of corresponding version information and synchronization of unit configuration information can be realized.
The release system further comprises a version control module 4, wherein the version control module is used for service version and configuration management of subsystems and units.
The invention can effectively control the issuing scope authority (limit the issuing subsystem, environment and version), simplify the operation and ensure the standardization and stability of the service issuing flow. Creating a multi-subsystem, multi-unit and multi-environment publishing task based on the version of the subsystem, and arranging the publishing order. In a specific design, a one-key release task can be realized, the state visualization of the subsystem and the environment granularity can be realized, and the configuration files are stored in a configuration library, so that the problem deployment tracing and the history version archiving are facilitated; error versions and version rollbacks may be skipped according to different scenarios.
The automatic circulation is realized from the system configuration to the production environment configuration without manual intervention in the deployment process, and the service release and circulation from the development environment to the test environment and then to the production environment can be realized. In the running process, the deployment state of the subsystem units is updated in real time, visualization of release tasks is realized, and high-concurrency release and deployment of multiple units are realized.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (9)
1. A method of publishing a service, the service comprising one or more subsystems, the subsystems comprising a plurality of units, the method comprising:
according to the dependency of each unit of the subsystem, a stage of releasing the subsystem is obtained;
Dividing unit deployment tasks of the same stage into one or more sub-stages according to the deployment environment of the units, and obtaining task sets of the sub-stages;
sequentially issuing the task sets according to the sequence of the stages and the sub-stages;
the method for dividing the sub-stages comprises the following steps:
Obtaining a deployment environment of each unit in the stage, wherein the deployment environment comprises a target deployment cluster;
classifying the deployment tasks of the units according to the target deployment cluster or the target node to obtain a plurality of unit sets;
Giving priorities to the deployment tasks of the unit sets respectively, wherein the priorities of the deployment tasks of the same unit set are different;
and dividing the unit deployment task of the stage into one or more sub-stages according to the priority.
2. The publishing method of claim 1, wherein a plurality of deployment tasks in the set of tasks are published in parallel;
The deployment environment includes a target cluster or target node.
3. The publishing method of claim 1, wherein the priorities are assigned according to an order of target clusters or a location of target nodes.
4. The publishing method of claim 1, wherein the publishing tasks of the phases are represented by parent tasks, the publishing tasks of the sub-phases are represented by sub-tasks, and the task sets of the sub-phases are represented by system tasks;
and performing serial execution among the parent tasks, performing serial execution among the child tasks, and performing parallel execution of unit deployment tasks in the system tasks.
5. The publishing method of claim 4, wherein the method of publishing the corresponding task set comprises:
step 301: generating an execution record table according to the release sequence of the task set;
step 302: judging whether a parent task to be executed exists in the execution record table;
If yes, go to step 303: executing the father task according to the release sequence of the stages, entering a subtask list, and executing step 305;
if not, step 304: ending the service release;
step 305: sequentially reading a system task queue from the subtask list according to the priority;
Step 306: consuming the system task queue, executing the unit deployment task in the system task queue, generating a deployment record of the system task and the unit deployment task, executing step 305 until the subtask list is consumed, and executing step 302.
6. The publishing method of claim 4, further comprising skipping deployment methods of:
judging whether the first unit of the first subsystem fails to be deployed or not;
If yes, marking the first subsystem;
Judging whether a second unit to be issued belongs to the first subsystem or not;
if the second unit belongs to the first subsystem, skipping the release of the second unit;
the service comprises a first version and a second version, and a version rollback method comprises the following steps:
determining if the second version has a logic problem,
If so, acquiring the deployed units of the second version and a deployment environment from the deployment record;
The deployed units are rolled back to the corresponding units of the first version according to the deployment environment.
7. The distribution method according to claim 1, wherein configuration management information is set for the unit, the configuration management information including: the subsystem issues a version, a version submission record, a deployment package address and a deployment cluster;
and performing unit deployment tasks of the task set according to the environmental configuration of the units.
8. A service distribution system for implementing a distribution method according to any one of claims 1-7, said distribution system comprising a phase orchestration module, a sub-phase orchestration module and a distribution module,
The stage arrangement module is used for obtaining the stage issued by the subsystem according to the dependency of each unit of the subsystem;
The sub-stage arrangement module is used for dividing the units in the same stage into one or more sub-stages according to the deployment environment of the units, and obtaining a task set of the sub-stages;
The issuing module is used for issuing the task sets in sequence according to the sequence of the stage and the sub-stage.
9. The publication system of claim 8, further comprising a version control module for service version and configuration management of subsystems and units.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410043938.5A CN117591132B (en) | 2024-01-12 | 2024-01-12 | Service release method and release system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410043938.5A CN117591132B (en) | 2024-01-12 | 2024-01-12 | Service release method and release system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117591132A CN117591132A (en) | 2024-02-23 |
| CN117591132B true CN117591132B (en) | 2024-04-26 |
Family
ID=89910223
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410043938.5A Active CN117591132B (en) | 2024-01-12 | 2024-01-12 | Service release method and release system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117591132B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| WO2021051623A1 (en) * | 2019-09-18 | 2021-03-25 | 平安科技（深圳）有限公司 | Grayscale release method and apparatus based on microservice framework, and computer device |
| WO2021088437A1 (en) * | 2019-11-06 | 2021-05-14 | 苏宁云计算有限公司 | Version releasing method and device based on multi-environment offline task |
| CN114371881A (en) * | 2021-12-20 | 2022-04-19 | 浪潮软件股份有限公司 | Flexible and safe CI/CD service deployment system and method based on gitlab-CI |
| CN115202670A (en) * | 2022-06-17 | 2022-10-18 | 平安银行股份有限公司 | Application batch release method and device, electronic equipment and storage medium |
| CN115757552A (en) * | 2022-11-29 | 2023-03-07 | 广发银行股份有限公司 | Bank historical data management system based on distributed micro-service |
| CN115794307A (en) * | 2022-11-18 | 2023-03-14 | 杭州谐云科技有限公司 | Cross-cloud application release method and system based on cloud originality |
| CN116466959A (en) * | 2023-04-07 | 2023-07-21 | 中国邮政储蓄银行股份有限公司 | Deployment method and device of micro-service system, readable storage medium and electronic equipment |
-
2024
- 2024-01-12 CN CN202410043938.5A patent/CN117591132B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110572436A (en) * | 2019-08-12 | 2019-12-13 | 浙江讯盟科技有限公司 | Multi-place cross-cluster server deployment method and system |
| WO2021051623A1 (en) * | 2019-09-18 | 2021-03-25 | 平安科技（深圳）有限公司 | Grayscale release method and apparatus based on microservice framework, and computer device |
| WO2021088437A1 (en) * | 2019-11-06 | 2021-05-14 | 苏宁云计算有限公司 | Version releasing method and device based on multi-environment offline task |
| CN114371881A (en) * | 2021-12-20 | 2022-04-19 | 浪潮软件股份有限公司 | Flexible and safe CI/CD service deployment system and method based on gitlab-CI |
| CN115202670A (en) * | 2022-06-17 | 2022-10-18 | 平安银行股份有限公司 | Application batch release method and device, electronic equipment and storage medium |
| CN115794307A (en) * | 2022-11-18 | 2023-03-14 | 杭州谐云科技有限公司 | Cross-cloud application release method and system based on cloud originality |
| CN115757552A (en) * | 2022-11-29 | 2023-03-07 | 广发银行股份有限公司 | Bank historical data management system based on distributed micro-service |
| CN116466959A (en) * | 2023-04-07 | 2023-07-21 | 中国邮政储蓄银行股份有限公司 | Deployment method and device of micro-service system, readable storage medium and electronic equipment |
Non-Patent Citations (2)
| Title |
|---|
| Constraint-aware and multi-objective optimization for micro-service composition in mobile edge computing;Wu, JT等;Software-Practice&Experience;20230530;全文 * |
| 数字图书馆网格服务发布和发现机制研究;张自然;董慧;;现代图书情报技术;20090525(第05期) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117591132A (en) | 2024-02-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9846594B2 (en) | Workflow control apparatus and method therefor | |
| EP2482192B1 (en) | Testing lifecycle | |
| CN113569987A (en) | Model training method and device | |
| CN111400011B (en) | Real-time task scheduling method, system, equipment and readable storage medium | |
| CN108491254A (en) | A kind of dispatching method and device of data warehouse | |
| CN114461357B (en) | Remote sensing satellite original data real-time processing flow scheduling system | |
| CN114637511A (en) | Code testing system, method, device, electronic equipment and readable storage medium | |
| CN110619014A (en) | ETL-based data extraction method | |
| CN114416703A (en) | Method, device, equipment and medium for automatically monitoring data integrity | |
| CN116661978B (en) | Distributed flow processing method and device and distributed business flow engine | |
| CN117591132B (en) | Service release method and release system | |
| US11995587B2 (en) | Method and device for managing project by using data merging | |
| JP5387083B2 (en) | Job management system and method | |
| Weyns et al. | Codifying architecture knowledge to support online evolution of software product lines | |
| CN115437766A (en) | Task processing method and device | |
| CN112860334A (en) | Parallel simulation method and storage medium | |
| CN112418796A (en) | Sub-process node activation method and device, electronic equipment and storage medium | |
| CN112817808B (en) | Computer cluster maintenance task management method and system | |
| US11797291B2 (en) | Software update management device and software update management method | |
| EP4109367A1 (en) | Method and device for managing project by using data filtering | |
| CN117971412A (en) | Task dependency scheduling method supporting dependency arrangement | |
| CN117632359A (en) | Task scheduling management method based on kubernetes, electronic equipment and storage medium | |
| CN115185561A (en) | CICD system based on service Jenkins and implementation method | |
| CN114896054A (en) | Cross-heterogeneous computing engine big data task scheduling method, device and medium | |
| CN117667362A (en) | Method, system, equipment and readable medium for scheduling process engine |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |