CN116737201A - Open source container upgrading method and device - Google Patents
Open source container upgrading method and device Download PDFInfo
- Publication number
- CN116737201A CN116737201A CN202310686262.7A CN202310686262A CN116737201A CN 116737201 A CN116737201 A CN 116737201A CN 202310686262 A CN202310686262 A CN 202310686262A CN 116737201 A CN116737201 A CN 116737201A
- Authority
- CN
- China
- Prior art keywords
- open source
- layer
- container
- component
- upgraded
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004806 packaging method and process Methods 0.000 claims abstract description 44
- 238000012360 testing method Methods 0.000 claims abstract description 25
- 238000003860 storage Methods 0.000 claims abstract description 16
- 230000008569 process Effects 0.000 claims description 7
- 238000005096 rolling process Methods 0.000 claims description 7
- 230000004044 response Effects 0.000 claims description 4
- 238000005538 encapsulation Methods 0.000 claims 1
- 238000004519 manufacturing process Methods 0.000 abstract description 15
- 239000002699 waste material Substances 0.000 abstract description 8
- 230000008878 coupling Effects 0.000 abstract description 5
- 238000010168 coupling process Methods 0.000 abstract description 5
- 238000005859 coupling reaction Methods 0.000 abstract description 5
- 238000011161 development Methods 0.000 description 6
- 238000012856 packing Methods 0.000 description 6
- 230000008859 change Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 244000035744 Hura crepitans Species 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
- H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
The application provides a method and a device for upgrading an open source container, comprising the following steps: the application program is packaged in layers in a main program operation layer, an open source component container layer and a private component container layer of the open source container; acquiring an open source component to be upgraded; and upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container. Therefore, the coupling degree of the application program and the bottom layer platform is further reduced by layering the container base layer, frequent packaging and production due to open source holes are avoided, invalid container storage is also reduced, waste of cloud computing resources is reduced, and follow-up rapid testing and production are facilitated.
Description
Technical Field
The application relates to the technical field of software development, in particular to an open source container upgrading method and device.
Background
JAVA development can use open source components on a large scale to speed development. However, the open source assembly often generates open source loopholes, and the system is required to carry out rectification and regression testing to upgrade the open source assembly. However, with the increase of open source components, the frequency of rectification and regression testing is gradually increased, and the manpower and material resources are wasted.
In the prior art, a basic assembly is placed on a basic layer by providing a basic editing container, a developer compiles codes and stores the container mirror images in a layered manner in an application layer and the like, a user packages the custom-written codes on the next layer of the basic layer by referring to the container when carrying out subsequent packaging of the container, and the decoupling of the basic layer is realized through the inside of the container so as to accelerate the downloading of the container (only downloading the changed container layer) by means of a pipeline, thereby reducing the storage space and relieving the compiling and production pressure. However, the decoupling scheme belongs to an invasive scheme, the two parts are not completely decoupled, each time of production is required to recompile codes and images, only the downloading cost of a user end is reduced, the storage cost of a container image warehouse is slightly reduced, and a great deal of manpower and energy are required to manage and control the projects. Meanwhile, frequent open source upgrades can also cause frequent container packaging and compiling, occupying a large amount of cloud computing resources. Particularly, in a large container cloud operation platform, tens of millions of containers can be operated simultaneously, and the repeated packing and compiling of the tens of millions of containers can be faced in the mode, so that system resources are wasted greatly.
Therefore, how to reduce the resource waste caused by the open source upgrade is a technical problem that needs to be solved by those skilled in the art.
Disclosure of Invention
In view of this, the embodiment of the application provides a method and a device for upgrading an open source container, which aims to reduce resource waste caused by open source upgrading.
In a first aspect, an embodiment of the present application provides an open source container upgrade method, where an open source container includes a main program running layer, an open source component container layer, and a private component container layer, and the method includes:
the application program is packaged in layers in a main program operation layer, an open source component container layer and a private component container layer of the open source container;
acquiring an open source component to be upgraded;
and upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container.
Optionally, the layering packaging the application program in a main program running layer, an open source component container layer and a private component container layer of the open source container includes:
encapsulating the running codes in the application program in the main program running layer;
packaging an open source component in the application program in the open source component container layer;
and packaging the private programming language library in the application program in the private component container layer.
Optionally, the obtaining the open source component to be upgraded includes:
acquiring a first to-be-upgraded open source assembly and a second to-be-upgraded open source assembly;
the upgrading of the open source component container layer based on the open source component to be upgraded comprises the following steps:
and upgrading the open source component container layer based on the first open source component to be upgraded and the second open source component to be upgraded.
Optionally, after the step of upgrading the container layer of the open source component based on the open source component to be upgraded, the method further includes:
copying the programs of the open source component container layer and the private component container layer to a shared directory, wherein the shared directory is shared by the main program operation layer, the open source component container layer and the private component container layer;
copying the program of the main program operation layer to the shared directory to generate a combined program.
Optionally, after the copying the program of the main program operation layer to the shared directory, the method further includes:
the merging procedure was subjected to a full-scale regression test.
Optionally, after the performing a full-scale regression test on the merged program in the shared directory, the method further includes:
and in response to the result of the full-scale regression testing meeting a preset condition, rolling and upgrading the multiple copies of the application program.
In a second aspect, an embodiment of the present application provides an apparatus for upgrading an open source container, where the open source container includes a main program running layer, an open source component container layer, and a private component container layer, and the apparatus includes:
the packaging module is used for packaging the application program in layers in a main program running layer, an open source component container layer and a private component container layer of the open source container;
the upgrade component acquisition module is used for acquiring an open source component to be upgraded;
and the upgrading module is used for upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container.
Optionally, the packaging module includes:
the first packaging component is used for packaging the running codes in the application program in the main program running layer;
the second packaging component is used for packaging the open source component in the application program in the open source component container layer;
and the third packaging component is used for packaging the private programming language library in the application program in the private component container layer.
In a third aspect, an embodiment of the present application provides an apparatus, where the apparatus includes a memory for storing instructions or code, and a processor for executing the instructions or code, so that the apparatus performs the open source container upgrade method according to any one of the first aspect.
In a fourth aspect, an embodiment of the present application provides a computer storage medium having code stored therein, where when the code is executed, a device executing the code implements the open source container upgrade method of any one of the foregoing first aspects.
The embodiment of the application provides an open source container upgrading method and device, when the method is executed, an application program is firstly packaged in layers in a main program running layer, an open source component container layer and a private component container layer of the open source container; acquiring an open source component to be upgraded; and finally, upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container. Therefore, the coupling degree of the application program and the bottom layer platform is further reduced by layering the container base layer, frequent packaging and production due to open source holes are avoided, invalid container storage is also reduced, waste of cloud computing resources is reduced, and follow-up rapid testing and production are facilitated.
Drawings
In order to more clearly illustrate this embodiment or the technical solutions of the prior art, the drawings that are required for the description of the embodiment or the prior art will be briefly described, 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 flow chart of a method for upgrading an open source container according to an embodiment of the present application;
FIG. 2 is a flowchart of another method of the open source container upgrading method according to the embodiment of the present application;
fig. 3 is a schematic structural diagram of an upgrade apparatus for an open source container according to an embodiment of the present application.
Detailed Description
In the prior art, a basic assembly is placed on a basic layer by providing a basic editing container, a developer compiles codes and stores the container mirror images in a layered manner in an application layer and the like, a user packages the custom-written codes on the next layer of the basic layer by referring to the container when carrying out subsequent packaging of the container, and the decoupling of the basic layer is realized through the inside of the container so as to accelerate the downloading of the container (only downloading the changed container layer) by means of a pipeline, thereby reducing the storage space and relieving the compiling and production pressure. However, the decoupling scheme belongs to an invasive scheme, the two parts are not completely decoupled, each time of production is required to recompile codes and images, only the downloading cost of a user end is reduced, the storage cost of a container image warehouse is slightly reduced, and a great deal of manpower and energy are required to manage and control the projects. Meanwhile, frequent open source upgrades can also cause frequent container packaging and compiling, occupying a large amount of cloud computing resources. Particularly, in a large container cloud operation platform, tens of millions of containers can be operated simultaneously, and the repeated packing and compiling of the tens of millions of containers can be faced in the mode, so that system resources are wasted greatly.
The method provided by the embodiment of the application is executed by the computer equipment and is used for reducing the resource waste caused by open source upgrading.
It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, fig. 1 is a flowchart of a method for upgrading an open source container according to an embodiment of the present application, including:
step S101: and packaging the application program in layers in a main program running layer, an open source component container layer and a private component container layer of the open source container.
The application program may be a program developed by using a development language, which is required to be applied to an open source component in the development process in the present application. The container (including but not limited to Docker) is an open-source application container engine that allows developers to package their applications and rely on packages into a portable image and then release them to any popular Linux or Windows operating system machine, as well as to implement virtualization. The containers are completely using a sandbox mechanism without any interface to each other.
And packaging the application program in layers on a main program operation layer, an open source component container layer and a private component container layer of the open source container, wherein the essence of the application program is based on the container layering technology, packaging all open source components to a sidecar container layer of the sidecar, and packaging program operation codes to the main container operation layer to realize basic component level decoupling. In subsequent upgrades, a container layer of a new version of the sidecar open source base component can be released based on a container operation platform (such as Kubernetes), so that quick and noninductive upgrade is realized, and the continuous rectifying burden caused by open source holes is reduced.
The sidecar refers to an operation scheme supported by the container cloud platform. The functionality of the application is divided into separate processes, namely the sidocar mode. The Sidecar is originally intended as a Sidecar for a motorcycle and is used in a software architecture, i.e., the Sidecar application is connected to and extends or enhances functionality for a parent application. Sidecar applies to the loose coupling of the host application. For the present embodiment, the open source component container layer and the private component container layer are the Sidecar companion containers of the main program run container.
Using the Sidecar schema, the complexity of the micro-service code can be reduced by abstracting the common infrastructure associated with the functionality to a different layer. Meanwhile, the application does not need to write the same third party component configuration file and code, so that the complexity of the code in the micro-service architecture is reduced, and the coupling degree of the application program and the bottom layer platform is also reduced.
As a possible implementation manner, the running code in the application program may be encapsulated in the main program running layer; packaging an open source component in the application program in the open source component container layer; and packaging the private programming language library in the application program in the private component container layer.
Step S102: and obtaining the open source component to be upgraded.
When the superior security center finds that one or more of the issued components have an open source vulnerability, the superior security center reissues an alternative version of the open source component to be upgraded, namely the open source component to be upgraded. Since the modification of the open source bug does not require a change in the code in most cases, the present embodiment is only directed to the case where there is no code change. Before the upper security center issues the open source assembly to be upgraded, it will analyze whether the upgrade needs to change the code. If the code needs to be changed, other upgrading methods are changed.
Step S103: and upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container.
Based on the open source component to be upgraded, the open source component container layer is upgraded, and the original container image is divided into 3 container images, wherein only the open source component container layer is changed, and the main program operation layer and the private component container layer hardly change every time the upgrade is performed. Therefore, the versions of the internal system scaffolds are unified, and only one version of the open source component container is provided, so that the storage and downloading cost is greatly reduced. Meanwhile, each time of open source upgrading only upgrades the open source component container, and a developer is not required to put into production again, so that the upgrading cost is reduced.
It should be noted that, when the open source container needs to be upgraded, the steps S101-S103 may be executed in the test environment first, and after the test is passed, the open source component container is automatically updated, so as to reduce the labor cost of the upgrade work.
In summary, according to the embodiment, the container base layer is layered, so that the coupling degree of the application program and the bottom layer platform is further reduced, frequent packaging and production due to open source holes are avoided, invalid container storage is reduced, waste of cloud computing resources is reduced, and subsequent rapid testing and production are facilitated.
In the embodiment of the present application, there are a plurality of possible implementations of the steps described in fig. 1, and the following descriptions are provided separately. It should be noted that the implementations presented in the following description are only exemplary and not representative of all implementations of the embodiments of the present application.
Referring to fig. 2, the flowchart of another method of the open source container upgrading method provided by the embodiment of the present application includes:
step S201: and packaging the application program in layers in a main program running layer, an open source component container layer and a private component container layer of the open source container.
Step S202: and acquiring a first to-be-upgraded open source component and a second to-be-upgraded open source component.
JAVA development can use open source components on a large scale to speed development. Open source components can often generate open source vulnerabilities, and the open source components are upgraded by requiring system rectification and regression testing. When the number of the open source components to be upgraded is multiple, different open source components can be obtained at the same time, and the multiple components are updated at the same time in one upgrade, namely, the first open source component to be upgraded and the second open source component to be upgraded are obtained. And 3, frequent packing and production due to a large number of open source holes are avoided, and invalid container storage is reduced (invalid containers refer to containers with open source holes in which recompilation and packing are caused by layered packing only through a container internal layering technology, and a large number of abandoned old containers with open source holes exist in a system).
Step S203: and upgrading the open source component container layer based on the first open source component to be upgraded and the second open source component to be upgraded.
Because the first open source component to be upgraded and the second open source component to be upgraded are both packaged in the open source component container layer, different components in the open source component container layer can be upgraded at the same time, so that the upgrading efficiency is improved, and the problem of cloud computing resource waste is solved.
Step S204: copying the programs of the open source component container layer and the private component container layer to a shared directory.
In practical application, after the upgrade of the container layer of the open source component is completed, the container management platform needs to combine the upgraded container layer of the open source component with the container layer of the private component and the running layer of the main program to form a complete program for subsequent use. Implementations require that programs at different container layers be copied into the same directory, which may be a shared directory shared by the main program run layer, the open source component container layer, and the private component container layer. Specifically, the sidecar associated container, namely the open source component container layer and the private component container layer, may be started first to copy the programs of the open source component container layer and the private component container layer to the shared directory, so as to perform the first step of program merging.
Step S205: copying the program of the main program operation layer to the shared directory to generate a combined program.
After the sidecar associated container finishes copying, a main program operation container layer is informed to start, and the programs of the main program operation layer are copied to the shared directory to generate a combined program for subsequent testing or use.
Step S206: the merging procedure was subjected to a full-scale regression test.
Regression testing is to re-perform functional and nonfunctional testing on the original state of a program to ensure that software that has been developed and tested before will still perform satisfactorily after such changes as bug fixes, configuration changes, software updates, etc. (i.e., the functional and nonfunctional of those parts of the current state of the software that have not been modified remain identical to the original state). The full-scale regression test is to verify all functions, and ensure that the program has no problem to the greatest extent possible.
Step S207: and in response to the result of the full-scale regression testing meeting a preset condition, rolling and upgrading the multiple copies of the application program.
When the steps are the primary upgrade, the method can be carried out in a test environment, and then the production upgrade is carried out. Since the system needs to deploy 3 or 6 copies (without limitation in number here) for deploying a set of programs, for improving stability and overall performance of the programs, all simultaneous upgrades affect service continuity. The whole process of rolling upgrade is a smooth transition upgrade, and in the upgrade process, the service is still available. The service continuity can be maintained in the upgrading process, so that the outside is not perceived in the upgrading process.
Thus, multiple copies of the application program may be scroll-upgraded, with steps S201-S207 above being performed each time a copy is upgraded, until all copies are upgraded.
In summary, in this embodiment, by updating a plurality of open source components at the same time through one-time updating, the efficiency of updating the open source container is further improved; at the same time, utilizing rolling upgrades reduces the impact of the upgrades on the overall service. The whole embodiment avoids frequent packing and production due to open source loopholes, reduces invalid container storage, reduces waste of cloud computing resources, and is convenient for subsequent rapid testing and production.
The embodiments of the present application provide some specific implementations of an open source container upgrading method, and based on this, the present application also provides a corresponding apparatus. The apparatus provided by the embodiment of the present application will be described in terms of functional modularization.
Referring to the schematic structural diagram of the open source container upgrade apparatus shown in fig. 3, the open source container includes a main program running layer, an open source component container layer, and a private component container layer, and the apparatus includes a packaging module 301, an upgrade component obtaining module 302, and an upgrade module 303.
The packaging module 301 is configured to package an application program in layers on a main program running layer, an open source component container layer and a private component container layer of the open source container;
an upgrade component acquisition module 302, configured to acquire an open source component to be upgraded;
and the upgrading module 303 is configured to upgrade the container layer of the open source component based on the open source component to be upgraded, so as to complete upgrading of the open source container.
As a possible implementation manner, the packaging module 301 includes:
the first packaging component is used for packaging the running codes in the application program in the main program running layer;
the second packaging component is used for packaging the open source component in the application program in the open source component container layer;
and the third packaging component is used for packaging the private programming language library in the application program in the private component container layer.
As a possible implementation manner, the upgrade component obtaining module 302 includes:
the multi-component acquisition component is used for acquiring a first to-be-upgraded open source component and a second to-be-upgraded open source component;
the upgrade module 303 includes:
and the multi-component upgrading component is used for upgrading the container layer of the open source component based on the first open source component to be upgraded and the second open source component to be upgraded.
As a possible implementation manner, the device further comprises:
the first copying module is used for copying the programs of the open source component container layer and the private component container layer to a shared directory, and the shared directory is shared by the main program running layer, the open source component container layer and the private component container layer;
and the second copying module is used for copying the program of the main program operation layer to the shared directory to generate a combined program.
As a possible implementation manner, the device further comprises:
and the test module is used for carrying out full-scale regression test on the merging program.
As a possible implementation manner, the device further comprises:
and the rolling upgrading module is used for rolling upgrading the multiple copies of the application program in response to the result of the full-scale regression test meeting a preset condition.
The embodiment of the application also provides corresponding equipment and a computer storage medium, which are used for realizing the scheme provided by the embodiment of the application.
The device comprises a memory and a processor, wherein the memory is used for storing instructions or codes, and the processor is used for executing the instructions or codes so as to enable the device to execute the open source container upgrading method according to any embodiment of the application.
The computer storage medium stores codes, and when the codes are executed, equipment for executing the codes realizes the open source container upgrading method according to any embodiment of the application.
The "first" and "second" in the names of "first", "second" (where present) and the like in the embodiments of the present application are used for name identification only, and do not represent the first and second in sequence.
From the above description of embodiments, it will be apparent to those skilled in the art that all or part of the steps of the above described example methods may be implemented in software plus general hardware platforms. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network communication device such as a router) to perform the method according to the embodiments or some parts of the embodiments of the present application.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present application without undue burden.
The foregoing description of the exemplary embodiments of the application is merely illustrative of the application and is not intended to limit the scope of the application.
Claims (10)
1. An open source container upgrade method, wherein the open source container includes a main program operation layer, an open source component container layer and a private component container layer, the method comprising:
the application program is packaged in layers in a main program operation layer, an open source component container layer and a private component container layer of the open source container;
acquiring an open source component to be upgraded;
and upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container.
2. The method of claim 1, wherein hierarchically encapsulating the application in a main program run layer, an open source component container layer, and a private component container layer of the open source container comprises:
encapsulating the running codes in the application program in the main program running layer;
packaging an open source component in the application program in the open source component container layer;
and packaging the private programming language library in the application program in the private component container layer.
3. The method of claim 1, wherein the obtaining an open source component to be upgraded comprises:
acquiring a first to-be-upgraded open source assembly and a second to-be-upgraded open source assembly;
the upgrading of the open source component container layer based on the open source component to be upgraded comprises the following steps:
and upgrading the open source component container layer based on the first open source component to be upgraded and the second open source component to be upgraded.
4. The method of claim 1, wherein after the upgrading the open source component container layer based on the open source component to be upgraded, the method further comprises:
copying the programs of the open source component container layer and the private component container layer to a shared directory, wherein the shared directory is shared by the main program operation layer, the open source component container layer and the private component container layer;
copying the program of the main program operation layer to the shared directory to generate a combined program.
5. The method of claim 4, wherein after said copying the program of the main program runtime layer to the shared directory, the method further comprises:
the merging procedure was subjected to a full-scale regression test.
6. The method of claim 5, wherein after said performing a full-scale regression test on the merge process in the shared directory, the method further comprises:
and in response to the result of the full-scale regression testing meeting a preset condition, rolling and upgrading the multiple copies of the application program.
7. An open source container upgrade apparatus, wherein the open source container comprises a main program run layer, an open source component container layer, and a private component container layer, the apparatus comprising:
the packaging module is used for packaging the application program in layers in a main program running layer, an open source component container layer and a private component container layer of the open source container;
the upgrade component acquisition module is used for acquiring an open source component to be upgraded;
and the upgrading module is used for upgrading the container layer of the open source assembly based on the open source assembly to be upgraded so as to finish the upgrading of the open source container.
8. The apparatus of claim 7, wherein the encapsulation module comprises:
the first packaging component is used for packaging the running codes in the application program in the main program running layer;
the second packaging component is used for packaging the open source component in the application program in the open source component container layer;
and the third packaging component is used for packaging the private programming language library in the application program in the private component container layer.
9. An apparatus comprising a memory for storing instructions or code and a processor for executing the instructions or code to cause the apparatus to perform the open source container upgrade method of any one of claims 1 to 6.
10. A computer storage medium having code stored therein, which when executed, causes a computer storage device executing the code to implement the open source container upgrade method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310686262.7A CN116737201A (en) | 2023-06-08 | 2023-06-08 | Open source container upgrading method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310686262.7A CN116737201A (en) | 2023-06-08 | 2023-06-08 | Open source container upgrading method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116737201A true CN116737201A (en) | 2023-09-12 |
Family
ID=87903961
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310686262.7A Pending CN116737201A (en) | 2023-06-08 | 2023-06-08 | Open source container upgrading method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116737201A (en) |
-
2023
- 2023-06-08 CN CN202310686262.7A patent/CN116737201A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210349706A1 (en) | Release lifecycle management system for multi-node application | |
| US11698781B2 (en) | System and method for upgrading kernels in cloud computing environments | |
| US10146515B1 (en) | Live code updates | |
| Dearle | Software deployment, past, present and future | |
| CN105657191B (en) | Application increment upgrading method and system based on Android system | |
| CN109491695A (en) | A kind of increment updating method of integrated Android application | |
| US8924930B2 (en) | Virtual machine image lineage | |
| US20150220308A1 (en) | Model-based development | |
| US10514898B2 (en) | Method and system to develop, deploy, test, and manage platform-independent software | |
| CN111966396A (en) | Data processing method and device, computer system and computer readable storage medium | |
| CN115629971A (en) | Application development system and method | |
| US9110758B2 (en) | Cross-platform software framework for embedded systems on data storage device | |
| Van Der Burg et al. | Disnix: A toolset for distributed deployment | |
| US20170322792A1 (en) | Updating of operating system images | |
| CN113900704A (en) | Method and device for issuing application program installation package, readable medium and electronic equipment | |
| CN111522623B (en) | Modularized software multi-process running system | |
| CN111273960A (en) | Method for realizing cloud native MIPS architecture container cloud | |
| CN115756424A (en) | Method, device and equipment for generating MVP (multifunction vehicle platform) code | |
| CN115857999A (en) | Method and system for obtaining micro front-end system architecture based on vue system architecture transformation | |
| CN116737201A (en) | Open source container upgrading method and device | |
| Sethi et al. | Rapid deployment of SOA solutions via automated image replication and reconfiguration | |
| US20220027263A1 (en) | Disk image selection in virtualized network environments | |
| CN113360156B (en) | IOS compiling method and related equipment | |
| Siebra et al. | Empowering continuous delivery in software development: the DevOps strategy | |
| CN115543486B (en) | Server-free computing oriented cold start delay optimization method, device and equipment |
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 |