CN112905223B - Upgrade package generation method, device and equipment - Google Patents
Upgrade package generation method, device and equipment Download PDFInfo
- Publication number
- CN112905223B CN112905223B CN202110381640.1A CN202110381640A CN112905223B CN 112905223 B CN112905223 B CN 112905223B CN 202110381640 A CN202110381640 A CN 202110381640A CN 112905223 B CN112905223 B CN 112905223B
- Authority
- CN
- China
- Prior art keywords
- upgrade package
- upgrade
- version
- data packet
- package
- 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 67
- 238000005516 engineering process Methods 0.000 abstract description 5
- 238000010586 diagram Methods 0.000 description 7
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000004904 shortening Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 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
- G06F8/65—Updates
- G06F8/658—Incremental updates; Differential updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a generation method, a device and equipment of an upgrade package, wherein containers are distributed for generation flows of the upgrade packages, at least one generation flow of the upgrade package is operated in one container, and the upgrade package is preconfigured with a version unique version number which indicates a client which is upgraded by applying the upgrade package. The generation flow of the upgrade package in each container is executed in parallel, wherein in any one container, the following generation flow of the upgrade package is executed: generating a data packet according to the data packet of the historical version of the client and the differential data packet, wherein the data packet is used as a full-quantity data packet, the differential data packet is the differential data packet between the historical latest version and the latest version of the client, and extracting data from the full-quantity data packet according to the version number of the upgrading packet to generate the upgrading packet corresponding to the version number. Therefore, the generation flow of the upgrade package of each version is realized in parallel based on the container technology, so that the overall time of the generation flow can be shortened compared with a serial mode.
Description
Technical Field
The present invention relates to the field of electronic information, and in particular, to a method, an apparatus, and a device for generating an upgrade package.
Background
The upgrade of the client is an indispensable link in the operation of software. In general, a server generates an upgrade package corresponding to a version of each client, and issues a corresponding upgrade package to the client according to an actual version of the client, and after the electronic device operated by the client is operated, the upgrade of the client is realized.
The existing generation process of the upgrade package has the problem of excessively long time consumption, and therefore, how to shorten the time for generating the upgrade package becomes the problem to be solved at present.
Disclosure of Invention
The application provides a method and a device, and aims to solve the problem.
In order to achieve the above object, the present application provides the following technical solutions:
a generation method of an upgrade package comprises the following steps:
allocating containers for generating processes of all upgrade packages, wherein at least one generating process of the upgrade package is operated in one container, the upgrade package is pre-configured with a unique version number, and the version number represents the version of a client for upgrading by applying the upgrade package;
executing the generation flow of the upgrade package in each container in parallel, wherein in any one container, the following generation flow of the upgrade package is executed:
generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; the differential data packet is a differential data packet between a historical latest version and a latest version of the client;
and extracting data from the full data packet according to the version number of the upgrade packet, and generating an upgrade packet corresponding to the version number.
Optionally, the allocating a container for the generating process of each upgrade package includes:
determining an encryption mode adopted by the generation flow of each upgrade package;
and according to the rule that the fewer the containers are allocated as the execution speed of the encryption mode is higher, the number of the containers is allocated for the generation flow of each upgrade package under each encryption mode.
Optionally, the allocating a container for the generating process of each upgrade package further includes:
and under each encryption mode, if the number of the tasks divided in advance is greater than the number of the containers allocated for the encryption mode, allocating the tasks to the containers allocated for the encryption mode according to a load balancing principle, wherein one task is used for executing the generation flow of one upgrade package.
Optionally, the method further comprises:
if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, one of the tasks is allocated for each of the containers.
Optionally, the extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number includes:
acquiring index information according to the version number of the upgrade package, wherein the index information indicates the path of data corresponding to the version number in the full data package;
and extracting an upgrade package corresponding to the version number from the full data package according to the index information.
Optionally, the extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number includes:
under the condition that a plurality of generation flows of the upgrade packages are operated in one container, extracting data from the total data shared by the generation flows of the upgrade packages according to the version numbers of the upgrade packages, and generating the upgrade packages corresponding to the version numbers.
Alternatively, the container operates based on a k8s system.
An upgrade package generation apparatus, comprising:
the distribution module is used for distributing containers for the generation flow of each upgrade package, wherein at least one generation flow of the upgrade package is operated in one container, the upgrade package is pre-configured with a unique version number, and the version number represents the version of a client for upgrading by applying the upgrade package;
the execution module is used for executing the generation flow of the upgrade package in each container in parallel, wherein in any container, the following generation flow of the upgrade package is executed: generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; the differential data packet is a differential data packet between a historical latest version and a latest version of the client; and extracting data from the full data packet according to the version number of the upgrade packet, and generating an upgrade packet corresponding to the version number.
An electronic device, comprising:
a processor and a memory;
the memory is used for storing a program, and the processor is used for running the program so as to realize the generation method of the upgrade package.
A computer-readable storage medium having a program stored thereon, which when executed by a computer device, performs the above-described generation method of an upgrade package.
According to the method, the device and the equipment for generating the upgrade package, containers are distributed for the generation flow of each upgrade package, wherein at least one generation flow of the upgrade package is operated in one container, and the upgrade package is preconfigured with a unique version number of a version of a client for upgrading by applying the upgrade package. The generation flow of the upgrade package in each container is executed in parallel, wherein in any one container, the following generation flow of the upgrade package is executed: generating a data packet according to the data packet of the historical version of the client and the differential data packet, wherein the data packet is used as a full-quantity data packet, the differential data packet is the differential data packet between the historical latest version and the latest version of the client, and extracting data from the full-quantity data packet according to the version number of the upgrading packet to generate the upgrading packet corresponding to the version number. Therefore, compared with a serial mode, the execution speed of the generation flow can be improved, and the overall time of the generation flow is shortened.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a diagram of a method for generating an upgrade package according to an embodiment of the present application;
fig. 2 is an exemplary diagram of a result of allocation of a container in the method for generating an upgrade package according to the embodiment of the present application;
fig. 3 is an exemplary diagram of an allocation result of a further container in the generation method of an upgrade package disclosed in the embodiment of the present application;
FIG. 4 is a flowchart of a method for generating an upgrade package according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an upgrade package generating device according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The method and the device for generating the upgrade package can be applied to a server, and the server is used for generating the upgrade package for upgrading the client. The aim is to shorten the time for generating the upgrade package by using the container technology.
It can be understood that a server to which the upgrade package generation method disclosed in the following embodiments of the present application is applied is preconfigured with a system or environment for a container to run, for example, a k8s system.
The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Fig. 1 is a method for generating an upgrade package according to an embodiment of the present application, including the following steps:
s11, distributing containers for the generation flow of each upgrade package.
The upgrade package is a data package for upgrading the client from the current version to the latest version. It can be appreciated that different versions of clients are upgraded to different upgrade packages used by the latest version. For example, assuming that there are three versions 1, 2, and 3 of the client, after the latest version 4 is released, the upgrade package used to upgrade from versions 1, 2, and 3 to version 4 is different. Thus, an upgrade package needs to be generated for each version before the latest version.
In this embodiment, it is assumed that only one upgrade package is used for upgrading a client of any version, that is, one upgrade package is used for upgrading a client of one version, and further, one container runs at least one upgrade package generating process. In the embodiment of the present application, an upgrade package required by the client of the ith version (i is an integer greater than or equal to 0) is referred to as an upgrade package i, or an upgrade package of version i, where i or version i is a version number of the upgrade package.
Taking three versions 1, 2 and 3 existing at the client, the latest version to be upgraded is 4 as an example, as shown in fig. 2, three containers are configured and are respectively used for generating an upgrade package of version 1, an upgrade package of version 2 and an upgrade package of version 3. It is also possible, as shown in fig. 3, to configure two containers, the first container for generating the upgrade package of version 1 and the second container for generating the upgrade packages of versions 2 and 3.
The manner in which the container is configured for the upgrade package i will be described in detail in the following embodiments.
S12, executing the generation flow of the upgrade package in each container in parallel.
It will be appreciated that the flows in the various containers may be performed in parallel and isolated from each other based on the characteristics of the containers.
The steps of the generation flow of the upgrade package executed in any one container are as follows:
1. and generating the data packet according to the data packet of the historical version of the client and the differential data packet to serve as a full data packet.
The historical versions of the client are all versions that the client has released, such as the versions 1, 2 and 3. It will be appreciated that the historical version of the data packets are all published by the server, so the server can obtain the historical version of the data packets.
The differential data packet is a differential data packet between a historical latest version (i.e., a previous version of the latest version) of the client and the latest version.
It can be understood that after merging all the existing version and the latest version of the data packets of the client, all the version of the data packets of the client can be obtained, which is called a full-volume data packet in this embodiment.
2. And extracting data from the full data packet according to the version number of the upgrade packet, and generating an upgrade packet corresponding to the version number.
As described above, the upgrade packages used by the clients of different versions are different, and for any one version of client, the upgrade package required is a data package composed of data required for upgrading from the current version to the latest version.
And assuming that a generating flow of the upgrade package 3 is operated in one container, a data package formed by data required by upgrading the client version 3 to the latest version in the total data is the upgrade package corresponding to the version number 3.
And assuming that the generating flow of the upgrade package 2 and the upgrade package 3 is operated in one container, the data package formed by the data required by upgrading the client version 2 to the latest version in the total data is the upgrade package corresponding to the version number 2, and the data package formed by the data required by upgrading the client version 3 to the latest version is the upgrade package corresponding to the version number 3.
The specific execution flow of the step 2 may be: and acquiring index information according to the version number of the upgrade package, wherein the index information indicates the path of data corresponding to the version number in the full data package. And extracting the upgrade package corresponding to the version number from the full data package according to the index information. The specific implementation manner of obtaining the index information may refer to the prior art, and will not be described herein.
It is understood that in the case where the generation flows of the plurality of upgrade packages are run in one container, the full amount of data may be generated only once, and the generation flows of the plurality of upgrade packages share the full amount of data, so as to further shorten the generation time period of the upgrade package.
After the above 1 and 2 are performed for each container in fig. 2, upgrade packages 1, 2, and 3 may be generated.
In the present embodiment, the generation flow of the upgrade package is run using containers, and the generation flow of the upgrade package in each container is executed in parallel. Compared with the prior art that a main process is used for generating a full data packet and sub-processes are used for generating upgrade packets of all versions, the method can shorten the time.
It should be emphasized that the method described in this embodiment, in which the resources required for running the containers in parallel are higher than those required for starting the main process and then starting the sub-process, is a technical guide for adding more resources to shorten the duration. Moreover, although the container technology is relatively common, the flow described in this embodiment does not simply migrate the container technology to the generation scenario of the upgrade package based on the above-described technology guidance, but performs creative improvement based on the scenario: 1. because the flows running in different containers are isolated from each other, the prior art approach of first a main process and then a sub-process is not applicable, but instead generates a full amount of data in each container. 2. Based on the upgrade package generation scenario, the allocation manner of the container is designed (which will be described in detail in the following embodiments).
Although the time is exchanged for using resources, the entire time period of the upgrade package generation process is shortened, and therefore, the existing system does not require a long time to input more resources, and thus, the feasibility is high.
Fig. 4 is a schematic diagram of a method for generating an upgrade package according to an embodiment of the present application, and compared with the above embodiment, emphasis is placed on illustrating a configuration process of a container. In fig. 4, the following steps are included:
s41, determining an encryption mode adopted by the generation flow of each upgrade package.
In this embodiment, the encryption methods xxtea, jit32, and jit are taken as examples, that is, the upgrade package is generated by using the above three encryption methods.
S42, according to the rule that the execution speed of the encryption mode is higher, the fewer the allocated containers are, the quantity of the containers is allocated for the generation flow of each upgrade package under each encryption mode.
And the containers are distributed for different encryption modes according to the execution speed, so that the time length of the upgrade package generation process is further shortened.
For example, the process of generating the upgrade package by the xxtea encryption method has fewer steps and faster execution speed than the process of generating the upgrade package by the jit and jit encryption methods, so that the container with the least number is configured for the xxtea encryption method.
Further, in the case where the total number of containers is 64 (the maximum configurable number of containers), the ratio according to xxtea: jit32: jit64 is 2:3:3, configuring the number of containers for three encryption modes.
S43, under each encryption mode, if the number of tasks divided in advance is larger than the number of containers allocated for the encryption mode, the tasks are allocated to the containers according to the load balancing principle.
One task is used for executing a generation flow of an upgrade package. Generally, the generation flow of an upgrade package of one version is packaged as one task.
Taking the example of the number of containers allocated for the xxtea encryption method as 16, assuming that the number of tasks under the xxtea encryption method is 32, according to the principle of load balancing, for example, a group of the task with the longest time consumption and a group of the task with the shortest time consumption, a group of the task with the next longest time consumption and a group of the task with the next time consumption, and so on, the tasks are divided into groups, and the 16 groups are sequentially allocated to the 16 containers.
Load balancing allows the total time consumption of task operations in each container to be consistent, which is beneficial to shortening the total time consumption.
S44, if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, allocating a task for each container.
It is understood that S43 and S44 are performed for each encryption scheme.
S45, executing tasks in each container in parallel.
The flow described in this embodiment has the following beneficial effects:
1. and the generation speeds of the upgrade packages of different encryption modes are used as the basis, and corresponding numbers of containers are distributed for the different encryption modes, so that the overall time for executing tasks of all the containers is further shortened.
2. And taking the execution time of each task as a basis, distributing containers for each task according to a load balancing principle, and further shortening the overall time of executing the tasks by all the containers.
In summary, compared with the serial generation mode of the upgrade package in each encryption mode in the prior art, the concurrency capability of the method of the embodiment is enhanced, so that the speed of generating the upgrade package of all versions is effectively improved, and the generation time of the upgrade package can be effectively shortened.
Fig. 5 is a device for generating an upgrade package according to an embodiment of the present application, including: an allocation module, and an execution module.
The distribution module is used for distributing containers for the generation flow of each upgrade package, wherein at least one generation flow of the upgrade package is operated in one container, the upgrade package is preconfigured with a unique version number, and the version number represents the version of a client which applies the upgrade package to upgrade.
The execution module is used for executing the generation flow of the upgrade package in each container in parallel, wherein in any container, the following generation flow of the upgrade package is executed: generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; the differential data packet is a differential data packet between a historical latest version and a latest version of the client; and extracting data from the full data packet according to the version number of the upgrade packet, and generating an upgrade packet corresponding to the version number.
Optionally, the specific implementation manner of the allocation module for allocating containers to the generating processes of the upgrade packages includes: the distribution module is specifically used for determining an encryption mode adopted by the generation flow of each upgrade package; and according to the rule that the fewer the containers are allocated as the execution speed of the encryption mode is higher, the number of the containers is allocated for the generation flow of each upgrade package under each encryption mode.
Optionally, the specific implementation manner of the allocation module for allocating containers to the generating processes of the upgrade packages further includes: and under each encryption mode, if the number of the tasks divided in advance is greater than the number of the containers allocated for the encryption mode, allocating the tasks to the containers allocated for the encryption mode according to a load balancing principle, wherein one task is used for executing the generation flow of one upgrade package.
Optionally, the allocation module is further configured to: if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, one of the tasks is allocated for each of the containers.
Optionally, the specific implementation manner of the execution module for extracting data from the full data packet according to the version number of the upgrade packet to generate the upgrade packet corresponding to the version number includes: acquiring index information according to the version number of the upgrade package, wherein the index information indicates the path of data corresponding to the version number in the full data package; and extracting an upgrade package corresponding to the version number from the full data package according to the index information.
Optionally, the specific implementation manner of the execution module for extracting data from the full data packet according to the version number of the upgrade packet to generate the upgrade packet corresponding to the version number includes: under the condition that a plurality of generation flows of the upgrade packages are operated in one container, extracting data from the total data shared by the generation flows of the upgrade packages according to the version numbers of the upgrade packages, and generating the upgrade packages corresponding to the version numbers.
Alternatively, in this embodiment, the container operates based on a k8s system.
The upgrade package generation device of the embodiment can shorten the total generation time of the upgrade packages of a plurality of versions.
Fig. 6 is a schematic diagram of an electronic device according to an embodiment of the present application, including a processor and a memory. In the alternative, the processor and the storage may communicate via a communication bus. Wherein the memory is used for storing programs. The processor is configured to execute the program stored in the memory to implement the following procedures:
a generation method of an upgrade package comprises the following steps:
allocating containers for generating processes of all upgrade packages, wherein at least one generating process of the upgrade package is operated in one container, the upgrade package is pre-configured with a unique version number, and the version number represents the version of a client for upgrading by applying the upgrade package;
executing the generation flow of the upgrade package in each container in parallel, wherein in any one container, the following generation flow of the upgrade package is executed:
generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; the differential data packet is a differential data packet between a historical latest version and a latest version of the client;
and extracting data from the full data packet according to the version number of the upgrade packet, and generating an upgrade packet corresponding to the version number.
Optionally, the allocating a container for the generating process of each upgrade package includes:
determining an encryption mode adopted by the generation flow of each upgrade package;
and according to the rule that the fewer the containers are allocated as the execution speed of the encryption mode is higher, the number of the containers is allocated for the generation flow of each upgrade package under each encryption mode.
Optionally, the allocating a container for the generating process of each upgrade package further includes:
and under each encryption mode, if the number of the tasks divided in advance is greater than the number of the containers allocated for the encryption mode, allocating the tasks to the containers allocated for the encryption mode according to a load balancing principle, wherein one task is used for executing the generation flow of one upgrade package.
Optionally, the method further comprises:
if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, one of the tasks is allocated for each of the containers.
Optionally, the extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number includes:
acquiring index information according to the version number of the upgrade package, wherein the index information indicates the path of data corresponding to the version number in the full data package;
and extracting an upgrade package corresponding to the version number from the full data package according to the index information.
Optionally, the extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number includes:
under the condition that a plurality of generation flows of the upgrade packages are operated in one container, extracting data from the total data shared by the generation flows of the upgrade packages according to the version numbers of the upgrade packages, and generating the upgrade packages corresponding to the version numbers.
The embodiment of the application also discloses a computer readable storage medium, wherein a program is stored on the computer readable storage medium, and the generation method of the upgrade package described in the embodiment is executed when the computer device runs the program.
The functions described in the methods of the present application, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computing device readable storage medium. Based on such understanding, a portion of the embodiments of the present application that contributes to the prior art or a portion of the technical solution may be embodied in the form of a software product stored in a storage medium, comprising several instructions for causing a computing device (which may be a personal computer, a server, a mobile computing device or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different point from other embodiments, so that the same or similar parts between the embodiments are referred to each other.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (7)
1. The method for generating the upgrade package is characterized by comprising the following steps:
allocating containers for generating processes of all upgrade packages, wherein at least one generating process of the upgrade package is operated in one container, the upgrade package is pre-configured with a unique version number, and the version number represents the version of a client for upgrading by applying the upgrade package;
executing the generation flow of the upgrade package in each container in parallel, wherein in any one container, the following generation flow of the upgrade package is executed:
generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; the differential data packet is a differential data packet between a historical latest version and a latest version of the client; under the condition that the generation flow of a plurality of upgrade packages is operated in one container, the full data package is generated only once, and the generation flow of the plurality of upgrade packages shares the full data package;
extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number;
the allocating a container for the generating process of each upgrade package includes:
determining an encryption mode adopted by the generation flow of each upgrade package;
according to the rule that the fewer the containers are allocated as the execution speed of the encryption mode is higher, the number of the containers is allocated for the generation flow of each upgrade package under each encryption mode;
under each encryption mode, if the number of tasks divided in advance is greater than the number of containers allocated for the encryption mode, allocating the tasks to the containers allocated for the encryption mode according to a load balancing principle, wherein one task is used for executing the generation flow of one upgrade package;
if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, one of the tasks is allocated for each of the containers.
2. The method of claim 1, wherein the extracting data from the full data packet according to the version number of the upgrade package to generate the upgrade package corresponding to the version number comprises:
acquiring index information according to the version number of the upgrade package, wherein the index information indicates the path of data corresponding to the version number in the full data package;
and extracting an upgrade package corresponding to the version number from the full data package according to the index information.
3. The method of claim 1, wherein the extracting data from the full data packet according to the version number of the upgrade package to generate the upgrade package corresponding to the version number comprises:
under the condition that a plurality of generation flows of the upgrade packages are operated in one container, extracting data from the total data shared by the generation flows of the upgrade packages according to the version numbers of the upgrade packages, and generating the upgrade packages corresponding to the version numbers.
4. The method of claim 1, wherein the container operates based on a k8s system.
5. An upgrade package generation apparatus, comprising:
the distribution module is used for distributing containers for the generation flow of each upgrade package, wherein at least one generation flow of the upgrade package is operated in one container, the upgrade package is pre-configured with a unique version number, and the version number represents the version of a client for upgrading by applying the upgrade package;
the execution module is used for executing the generation flow of the upgrade package in each container in parallel, wherein in any container, the following generation flow of the upgrade package is executed: generating a data packet according to the historical version data packet and the differential data packet of the client, and taking the data packet as a full data packet; under the condition that the generation flow of a plurality of upgrade packages is operated in one container, the full data package is generated only once, and the generation flow of the plurality of upgrade packages shares the full data package; the differential data packet is a differential data packet between a historical latest version and a latest version of the client; extracting data from the full data packet according to the version number of the upgrade packet to generate an upgrade packet corresponding to the version number;
the allocating a container for the generating process of each upgrade package includes:
determining an encryption mode adopted by the generation flow of each upgrade package;
according to the rule that the fewer the containers are allocated as the execution speed of the encryption mode is higher, the number of the containers is allocated for the generation flow of each upgrade package under each encryption mode;
under each encryption mode, if the number of tasks divided in advance is greater than the number of containers allocated for the encryption mode, allocating the tasks to the containers allocated for the encryption mode according to a load balancing principle, wherein one task is used for executing the generation flow of one upgrade package;
if the number of tasks divided in advance is not greater than the number of containers allocated for the encryption mode, one of the tasks is allocated for each of the containers.
6. An electronic device, comprising:
a processor and a memory;
the memory is used for storing a program, and the processor is used for running the program to realize the generation method of the upgrade package according to any one of claims 1 to 4.
7. A computer-readable storage medium having a program stored thereon, characterized in that the upgrade package generation method according to any one of claims 1-4 is performed when the computer device runs the program.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110381640.1A CN112905223B (en) | 2021-04-09 | 2021-04-09 | Upgrade package generation method, device and equipment |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110381640.1A CN112905223B (en) | 2021-04-09 | 2021-04-09 | Upgrade package generation method, device and equipment |
Publications (2)
Publication Number | Publication Date |
---|---|
CN112905223A CN112905223A (en) | 2021-06-04 |
CN112905223B true CN112905223B (en) | 2024-03-19 |
Family
ID=76110305
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110381640.1A Active CN112905223B (en) | 2021-04-09 | 2021-04-09 | Upgrade package generation method, device and equipment |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112905223B (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113535203B (en) * | 2021-07-06 | 2024-06-07 | 海南视联通信技术有限公司 | Server upgrading method, device, equipment and storage medium |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007164290A (en) * | 2005-12-09 | 2007-06-28 | Dainippon Printing Co Ltd | Determination system, generation device, determination device, determination method, and the like |
CN103942107A (en) * | 2014-04-23 | 2014-07-23 | 杭州电子科技大学 | Distributed encryption system |
CN111158737A (en) * | 2019-12-30 | 2020-05-15 | 深圳云天励飞技术有限公司 | Increment upgrading method and related equipment |
CN112054899A (en) * | 2020-08-28 | 2020-12-08 | 航天科工网络信息发展有限公司 | Container mirror image encryption management method based on encryption machine |
-
2021
- 2021-04-09 CN CN202110381640.1A patent/CN112905223B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007164290A (en) * | 2005-12-09 | 2007-06-28 | Dainippon Printing Co Ltd | Determination system, generation device, determination device, determination method, and the like |
CN103942107A (en) * | 2014-04-23 | 2014-07-23 | 杭州电子科技大学 | Distributed encryption system |
CN111158737A (en) * | 2019-12-30 | 2020-05-15 | 深圳云天励飞技术有限公司 | Increment upgrading method and related equipment |
CN112054899A (en) * | 2020-08-28 | 2020-12-08 | 航天科工网络信息发展有限公司 | Container mirror image encryption management method based on encryption machine |
Also Published As
Publication number | Publication date |
---|---|
CN112905223A (en) | 2021-06-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3133771A1 (en) | Virtual machine resource changing method, device and virtual network function device | |
US11507419B2 (en) | Method,electronic device and computer program product for scheduling computer resources in a task processing environment | |
CN113641457A (en) | Container creation method, device, apparatus, medium, and program product | |
CN108399094A (en) | A kind of dispositions method of application, its dispose device and edge data center | |
US20200293361A1 (en) | Method and distributed database system for computer-aided execution of a program code | |
CN103902353A (en) | Virtual machine deployment method and device | |
CN109995814A (en) | Moving method and device, communication equipment, the storage medium of cloud host resource | |
CN107341054A (en) | Task executing method, device and computer-readable recording medium | |
CN108520077A (en) | A kind of method and apparatus avoiding repeated downloads | |
CN106528189A (en) | Backup task starting method and device and electronic equipment | |
CN112905223B (en) | Upgrade package generation method, device and equipment | |
CN113067866A (en) | Batch file transmission method and device between heterogeneous systems | |
CN111078353A (en) | Operation method of storage equipment and physical server | |
CN103581273B (en) | A kind of distributed system performs method, the apparatus and system of business | |
CN112506584A (en) | Resource file loading method, device, equipment, storage medium and product | |
CN106576068A (en) | Software security verification method, equipment and system | |
CN115794386A (en) | Resource calling method and device of virtual machine and storage medium | |
CN112306675B (en) | Data processing method, related device and computer readable storage medium | |
CN112130962B (en) | Continuous delivery platform and method for deploying application system by using same | |
CN112637201B (en) | Method, device, equipment and system for processing request of web server | |
CN114675954A (en) | Task scheduling method and device | |
CN113923257A (en) | Container group instance termination and creation method, device, electronic equipment and storage medium | |
CN111427691A (en) | Virtual resource allocation method, device, medium and electronic equipment | |
JP2017191485A (en) | Resource management device and resource management method | |
JP6339978B2 (en) | Resource allocation management device and resource allocation management method |
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 |