CN106815056B - Application heat deployment method and device based on JCL framework - Google Patents
Application heat deployment method and device based on JCL framework Download PDFInfo
- Publication number
- CN106815056B CN106815056B CN201710085628.XA CN201710085628A CN106815056B CN 106815056 B CN106815056 B CN 106815056B CN 201710085628 A CN201710085628 A CN 201710085628A CN 106815056 B CN106815056 B CN 106815056B
- Authority
- CN
- China
- Prior art keywords
- application
- module
- application module
- class
- catalog
- 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
Images
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/656—Updates while running
Abstract
The invention provides a JCL framework-based application heat deployment method and device, and belongs to the field of heat deployment of system application programs. The application heat deployment method comprises the following steps: modularly publishing the newly added first application module to an application directory of the container in a jar file form; discovering the first application module by monitoring the change of the application catalog and the configuration file and sending out a corresponding first calling instruction; and based on the first calling instruction, loading an execution method for operating the class corresponding to the interface of the first application module from the application catalog through a class loader, so that the application operating system can execute a new function corresponding to the first application module.
Description
Technical Field
The invention belongs to the field of heat deployment of system application programs, and particularly relates to a method and a device for deploying application heat based on a JCL framework.
Background
When a traditional Web application program based on an SSH (Struts + Spring + Hibernate) framework is on-line with a new function (for example, when a new version of the Web application is on-line), the application must be redeployed, which results in an unavailable state for a while for the system. However, the unavailable state caused by the redeployment of the application has a great influence on some business systems (such as part of business systems in the industries of finance, electricity, water conservancy and the like) which need to be connected or run continuously at any time. Thus, there is a current need to enable hot deployment of Web programs or applications in a business-like system, i.e., upgrading software while the application is running without restarting the application.
Meanwhile, the JCL (jakara common Logging or Apache common Logging) framework is a completely open-source log framework, and the JCL can provide a Class library for loading classes (i.e., files with the suffix name of Class) from JARs (i.e., multiple jar files), is particularly suitable for differentially loading the same Class (. Class) in multiple versions in an application program, and thus is also an excellent open-source java Class loader (Class loader), and can effectively manage the loaded Class (. Class), for example, perform isolation, reading, unloading, and the like on the classes.
Disclosure of Invention
To solve the above technical problems or other technical problems, the present invention provides the following technical solutions.
According to an aspect of the present invention, there is provided a method for deploying application heat based on a JCL framework, the method comprising:
the method comprises the steps that a newly added first application module is modularly issued to an application directory of a container in a jar file form, and a definition configuration file is updated in the corresponding container for the first application module, wherein the first application module comprises a class corresponding to an interface of the first application module, and the interface of the first application module at least comprises an initialization method and an execution method;
when other applications run in the application running system, the first application module is found by monitoring the change of the application catalog and the configuration file, and a corresponding first calling instruction is sent out; and
and based on the first calling instruction, loading an execution method for operating the class corresponding to the interface of the first application module from the application catalog through a class loader, so that the application operating system can execute a new function corresponding to the first application module.
According to an embodiment of the invention, the interface of the first application module further comprises a destruction method; the method further comprises the steps of:
and when the application running system does not need the new function corresponding to the first application module at all, loading and running a destruction method of the class corresponding to the interface of the first application module through a class loader, so as to uninstall the first application module, and deleting the content corresponding to the first application module in the application catalog and the configuration file respectively.
The method of thermal deployment according to an embodiment of the present invention, wherein the method further comprises the steps of: after the first application module is loaded, the first application module is recorded in the application catalog as belonging to an existing application module.
According to an embodiment of the invention, when the application running system is started, all existing application modules in the application catalog are detected and corresponding second call instructions are issued;
and loading and operating the execution method of the class corresponding to the interfaces of all the existing application modules from the application catalog through the class loader based on the second calling instruction.
According to another aspect of the present invention, a JCL framework-based application thermal deployment apparatus is characterized by comprising:
a container configured to: modularly publishing a newly added first application module to an application directory thereof in a jar file form, and updating a definition configuration file for the first application module, wherein the first application module comprises a class corresponding to an interface thereof, and the interface of the first application module at least comprises an initialization method and an execution method;
a monitoring module configured to: when other applications run in the application running system, the first application module is found by monitoring the change of the application catalog and the configuration file, and a corresponding first calling instruction is sent out; and
a load execution module configured to: and based on the first calling instruction, loading an execution method for operating the class corresponding to the interface of the first application module from the application catalog through a class loader, so that the application operating system can execute a new function corresponding to the first application module.
According to an embodiment of the invention, the thermal deployment device further comprises a destruction method, wherein the destruction method is used for destroying the first application module; the application thermal deployment apparatus further comprises:
an offload module configured to: and when the application running system does not need the new function corresponding to the first application module at all, loading and running a destruction method of the class corresponding to the interface of the first application module through a class loader, so as to uninstall the first application module, and deleting the content corresponding to the first application module in the application catalog and the configuration file respectively.
The thermal deployment device according to an embodiment of the invention, wherein the container is further configured to: after the first application module is loaded, the first application module is recorded in the application catalog as belonging to an existing application module.
The thermal deployment device according to an embodiment of the present invention further comprises:
an activation detection module configured to: when the application running system is started, detecting all existing application modules in the application catalog and sending out corresponding second calling instructions;
the load execution module is further configured to: based on the second call instruction, the execution method for loading and operating the classes corresponding to the interfaces of all the existing application modules from the application catalog through the class loader
The above features and operation of the present invention will become more apparent from the following description and the accompanying drawings.
Drawings
The above and other objects and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, in which like or similar elements are designated by like reference numerals.
Fig. 1 is a schematic block diagram of an application thermal deployment apparatus according to an embodiment of the present invention.
FIG. 2 is a flow chart illustrating a method for applying thermal deployment in accordance with an embodiment of the present invention.
Fig. 3 is a schematic diagram of an application offloading process of an application thermal deployment method according to an embodiment of the invention.
Fig. 4 is a schematic diagram of a starting process of an application running system to which the application hot-deployment apparatus belongs according to the embodiment shown in fig. 1.
Detailed Description
The present invention will now be described more fully with reference to the accompanying drawings, in which exemplary embodiments of the invention are shown. This invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. In the drawings, the same reference numerals denote the same elements or components, and thus, their description will be omitted.
Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
Herein, "class" refers to a file with the suffix name ". class".
Fig. 1 is a schematic block diagram of an application thermal deployment apparatus according to an embodiment of the present invention. The application hot-deployment apparatus according to the embodiment of the present invention is an application-level class management apparatus, which is capable of managing the docking, deployment and/or deletion of each newly-added application module (e.g., a new app), and is particularly used for newly-deploying an application (e.g., application module C) to the application execution system 400. In this embodiment, application module a and application module B are illustrated as applications that have been running continuously in the system, e.g., core applications, which may implement various core service functions. The main function of the application of the present invention is not restrictive, and for example, it is different according to the application execution system 400 to which the application hot deployment apparatus of the present invention corresponds. The application running system 400 may be a business system (e.g., a part of business systems in industries such as finance, power, water conservancy, etc.) that needs to be connected or run continuously, and therefore, the continuous running of the core application thereof is needed to provide support for the continuous running thereof, even when the application module C is newly deployed, the application running system 400 requires that an unavailable state does not exist.
As shown in fig. 1, the application thermal deployment apparatus mainly includes a container 100, a start detection module 200, a monitoring module 300, and a load operation module 410, and may further include an unload module 420.
Specifically, the core services or core applications (e.g., application modules B and C) of the application execution system 400 are deployed in a container 100 such as tomcat or jboss, where the container 100 has an application directory 110 (i.e., an application directory file) and an application configuration file 120, which are based on a JCL framework, and when an online new function or an update to a system application is needed, the application module C corresponding to the function modularly issues a newly added application module C to its application directory 110 in a jar file form, and defines the configuration file 120 for the application module C update, where the application module C includes a class corresponding to its interface, and the interface of the application module C includes at least an initialization method and an execution method. The application module "newly added" is defined relative to the existing application module of the container 100, and may need an application module corresponding to a new function of online or an application module corresponding to a system application when updating.
The JCL framework based container 100 itself also has a Java Virtual Machine (JVM) based operating system level Class loader 130, which can load all classes (classes) in the applications in the container 100 into memory.
Continuing with FIG. 1, monitoring module 300 is configured to: when other applications (for example, application module a or application module B run on the application running system, the application module C is discovered by monitoring the changes of the application catalog 110 and the configuration file 120 and issues a corresponding call instruction, and therefore, the monitoring module 300 is mainly used to monitor the newly added application module.
Continuing with FIG. 1, the load execution module 410 is configured to: based on the call instruction, the class loader 130 loads the execution method of the class corresponding to the interface of the application module C (i.e., runs the class file corresponding to the execution method) from the application directory 110, so that the application running system 400 can execute the new function corresponding to the application module C. It will be appreciated that the load-run module 410 may perform similar load-run processing for other application modules in the application catalog 100 when corresponding call instructions are present.
In an embodiment, the interface of the newly added application module C further includes a destruction method; the offload module 410 is configured to: when the application running system does not need the new function corresponding to the application module C at all, the class loader 130 loads the destruction method (i.e., class file for the operation destroy method) for operating the class corresponding to the interface of the application module C, so as to uninstall the application module C, and delete the content corresponding to the first application module in the application directory 110 and the configuration file 120, respectively. It should be noted that the uninstall module 410 can perform similar uninstall processing on other application modules in the application catalog 100.
The application hot deployment device of the embodiment has the advantages of the JCL open source framework, so that when jar files are loaded, class and lib loaded by each jar are independent of each other, and the classes in each jar are not conflicted with each other without additionally developing an isolation function.
In an embodiment, the container 100 is further configured to: after application module C is loaded, application module C is described in the application catalog 110 as belonging to an existing application module. At system startup, the application execution system 400 will correspondingly execute all existing application modules. As shown in fig. 1, a startup detection module 200 is further disposed in the application thermal deployment device, and is configured to: when the application running system is started, detecting all existing application modules (for example, detecting an application module a and an application module B) in the application directory 110 and sending out corresponding call instructions; the load execution module 410 is further configured to: based on the call instruction, loading an execution method for running a class corresponding to an interface of all existing application modules (for example, application module a and application module B are detected) from the application catalog 110 through the class loader 130; thus, the system has corresponding service function when starting operation.
Fig. 2 is a schematic flow chart of an application heat deployment method according to an embodiment of the present invention, fig. 3 is a schematic view of an application uninstallation process of the application heat deployment method according to an embodiment of the present invention, and fig. 4 is a schematic view of a start-up process of an application operating system to which the application heat deployment apparatus of the embodiment shown in fig. 1 belongs. The method for applying thermal deployment according to the embodiments of the present invention is described in detail below with reference to fig. 1 to 4.
First, in step S11, a newly added application module is released. The newly added, e.g., application module C is modularly published in jar files to the application directory 110 of the container 100 and the definition configuration files 120 are updated in the container 100 for the application module C.
In this embodiment, to achieve the full functionality of the JCL framework, the following detailed functions and objectives are achieved:
(1) before packaging into jar files, defining an interface, wherein each newly added module must contain a unique class for realizing the interface, and the interface comprises three methods of initialization, execution and destruction; after the interface is realized and the development is completed, a newly added application module C is packaged into a jar file and then is released to a directory specified by the application, i.e. the corresponding application directory 110, and the file name and the configuration item must conform to a certain format standard.
(2) A corresponding configuration file 120 is defined, where necessary information, for example, of the newly added application module C of the core application is configured, so that the core application can monitor as needed or load all the newly added application modules according to the content of this file at startup, and each entry of the configuration file must indicate the name of the newly added application module, the stored path, etc.
In step S21, the monitoring module 300 monitors the application catalog 110 and the configuration file 120 for changes. To obscure this, the monitoring module 300 may listen for changes to each application in the application distribution catalog. Thus, when an application is deployed (or re-deployed), step S22 is entered to find a newly added application module, and the monitoring module 300 can be notified to prepare for a thermal deployment process, and trigger a call instruction, i.e., step S31.
Step S32, the newly added application is loaded. Specifically, the application execution system 400 loads, through the load execution module 410, the execution method of the class (class) corresponding to the interface of the application module C from the application directory 110 through the class loader 130 based on the call instruction triggered by the monitoring module 300.
Step S41 executes a function corresponding to the newly added application, for example, enables the application execution system 400 to execute a new function corresponding to the application module C.
In an embodiment, when the application running system 400 receives that it is not required to execute a function corresponding to a certain application, as shown in fig. 3, that is, step S32, the method proceeds to step S33, and a destruction method corresponding to an interface of the application is loaded through the class loader 130; further to step S34, uninstall the application module, and delete the corresponding content of the application module in the application directory 110 and the configuration file 120, respectively, then the function will be permanently uninstalled from the system.
In one embodiment, during the system startup process, the added new application module and the existing application block are loaded by the method shown in fig. 4. As shown in fig. 4, the start detection module 200 detects all existing application modules, i.e., step S23, by detecting to the application catalog 110 and the configuration file 120 in the container 100; further, S24 returns the detection result, and may return all existing application modules (e.g., application modules A, B and C) in the application catalog 110; further, the start detection module 200 triggers a call instruction and sends the call instruction to the load operation module 410 of the application operation system 400; further step S36, specifically, the application execution system 400 loads, through the load execution module 410 and based on the call instruction triggered by the start detection module 200, the class loader 130 from the application directory 110 through an execution method for executing the class (class) corresponding to the interfaces of all the application modules; thus, the application execution system 400 performs the functions corresponding to all existing applications, i.e., step S41.
The application hot deployment device and method of the above embodiments have the following functions:
firstly, thanks to the advantages of the JCL open source framework, when jar files are loaded, the class and lib loaded by each jar can be independent from each other, and an isolation function is not required to be additionally developed to ensure that the classes in each jar file do not conflict with each other, namely, isolation is automatically established between each application, each application module operates independently, and the newly added application module is not possible to depend on jar file packages of different versions and does not cause class conflict.
Secondly, in the system, a corresponding jar loading method is developed, the jar files of the interface can be loaded, wherein class and dependent lib files in the jar files are loaded by using a class loader of a JCL framework.
Thirdly, a monitoring module is realized in the system, and a monitoring method is correspondingly arranged in the monitoring module; the method monitors the file directory and the configuration file which are appointed in the prior art, when the newly added jar file is copied to the target directory, the configuration file is modified, after an application module is newly added, the monitoring method is triggered, and the previously realized jar loading method is called to deploy the real-time heat of the newly added application module into the core system. Thus, the added functionality can be run by the system calling the execution method (defined in the interface) in the jar file.
Fourthly, when a certain function is not needed, a destroying method in jar files corresponding to the function can be called to unload the loaded application, and meanwhile, corresponding contents in the configuration files are deleted, so that the function is permanently unloaded from the system.
Therefore, the application heat deployment method based on the JCL framework can dynamically add system functions under the condition of not modifying the deployment version, the system does not have an unavailable state, the heat deployment of Web application is realized, the whole framework is completely open, and the method is suitable for being applied to systems which need to be online at any time and cannot be interrupted easily.
The above examples mainly illustrate the JCL-based thermal deployment method and apparatus of the present invention. Although only a few embodiments of the present invention have been described, those skilled in the art will appreciate that the present invention may be embodied in many other forms without departing from the spirit or scope thereof. Accordingly, the present examples and embodiments are to be considered as illustrative and not restrictive, and various modifications and substitutions may be made therein without departing from the spirit and scope of the present invention as defined by the appended claims.
Claims (6)
1. An application heat deployment method based on a JCL framework is characterized in that:
the method comprises the steps of releasing a first newly added application module (C) to an application directory (110) of a container (100) in a jar file mode in a modularized mode, and updating a definition configuration file (120) in the corresponding container (100) for the first application module (C), wherein the first application module (C) comprises a class corresponding to an interface of the first application module (C), the interface of the first application module (C) at least comprises an initialization method and an execution method, and the class refers to a file with a suffix name of ". class";
when other applications run the system, the first application module (C) is discovered and corresponding first call instructions are sent out by monitoring the change of the application catalog (110) and the configuration file (120);
based on the first calling instruction, loading an execution method for running a class corresponding to an interface of the first application module (C) from the application catalog (110) through a class loader (130), so that the application running system can execute a new function corresponding to the first application module (C); and
and when the application running system does not need the new function corresponding to the first application module at all, loading a destruction method for running the class corresponding to the interface of the first application module (C) through a class loader (130), so as to uninstall the first application module, and deleting the content corresponding to the first application module in the application catalog (110) and the configuration file (120) respectively.
2. The method of thermal deployment of claim 1, further comprising the steps of: after the first application module (C) is loaded, the first application module (C) is described in the application catalog (110) as belonging to an existing application module.
3. The method of thermal deployment according to claim 2, characterized in that, at the start of the application execution system, all existing application modules in the application catalog (110) are detected and corresponding second call instructions are issued;
and loading an execution method for running the class corresponding to the interfaces of all the existing application modules from the application catalog (110) through a class loader (130) based on the second calling instruction.
4. A JCL framework-based application thermal deployment apparatus, comprising:
a container (100) configured to: modularly publishing a newly added first application module (C) to an application directory (110) of the first application module (C) in a jar file form, and updating a definition configuration file (120) for the first application module (C), wherein the first application module (C) comprises a class corresponding to an interface of the first application module (C), the interface of the first application module (C) at least comprises an initialization method and an execution method, and the class refers to a file with a suffix name of ". class";
a monitoring module (300) configured to: when other applications run the system, the first application module (C) is discovered and corresponding first call instructions are sent out by monitoring the change of the application catalog (110) and the configuration file (120);
a load execution module (410) configured to: based on the first calling instruction, loading an execution method for running a class corresponding to an interface of the first application module (C) from the application catalog (110) through a class loader (130), so that the application running system can execute a new function corresponding to the first application module (C); and
an offload module (410) configured to: and when the application running system does not need the new function corresponding to the first application module at all, loading a destruction method for running the class corresponding to the interface of the first application module (C) through a class loader (130), so as to uninstall the first application module, and deleting the content corresponding to the first application module in the application catalog (110) and the configuration file (120) respectively.
5. The application heat deployment device of claim 4, wherein the container (100) is further configured to: after the first application module (C) is loaded, the first application module (C) is described in the application catalog (110) as belonging to an existing application module.
6. The application thermal deployment apparatus of claim 5, further comprising:
a launch detection module (200) configured to: when the application running system is started, detecting all existing application modules in the application catalog (110) and sending out corresponding second calling instructions;
the load execution module (410) is further configured to: and loading an execution method for running the class corresponding to the interfaces of all the existing application modules from the application catalog (110) through a class loader (130) based on the second calling instruction.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710085628.XA CN106815056B (en) | 2017-02-17 | 2017-02-17 | Application heat deployment method and device based on JCL framework |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710085628.XA CN106815056B (en) | 2017-02-17 | 2017-02-17 | Application heat deployment method and device based on JCL framework |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106815056A CN106815056A (en) | 2017-06-09 |
| CN106815056B true CN106815056B (en) | 2020-09-08 |
Family
ID=59112505
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710085628.XA Active CN106815056B (en) | 2017-02-17 | 2017-02-17 | Application heat deployment method and device based on JCL framework |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106815056B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109800013B (en) * | 2019-01-25 | 2022-04-19 | 上海创景信息科技有限公司 | Method and system for hot expansion of server application function and readable storage medium |
| CN115543546B (en) * | 2022-11-25 | 2023-06-23 | 金现代信息产业股份有限公司 | Spring-based module hot deployment method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102073520A (en) * | 2010-12-30 | 2011-05-25 | 中国民航信息网络股份有限公司 | Dynamic management system and method for C++ application program version |
| CN102200918A (en) * | 2010-03-23 | 2011-09-28 | 中兴通讯股份有限公司 | Method and device for deploying application program in server |
| CN105242948A (en) * | 2015-10-27 | 2016-01-13 | 江苏电力信息技术有限公司 | Java web project based hot deploy implementation method |
| CN105389186A (en) * | 2015-11-20 | 2016-03-09 | 福建亿榕信息技术有限公司 | Hot deployment method and system for Java application |
| CN105404524A (en) * | 2014-09-15 | 2016-03-16 | 阿里巴巴集团控股有限公司 | Class loading and isolating method and apparatus in Java application |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6886160B1 (en) * | 2000-11-29 | 2005-04-26 | Hyung Sup Lee | Distribution of mainframe data in the PC environment |
| US8914784B2 (en) * | 2011-06-10 | 2014-12-16 | International Business Machines Corporation | Method and system for checking the consistency of application jar files |
| US20130125092A1 (en) * | 2011-11-11 | 2013-05-16 | General Electric Company | Generating deployable code from simulation models |
-
2017
- 2017-02-17 CN CN201710085628.XA patent/CN106815056B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102200918A (en) * | 2010-03-23 | 2011-09-28 | 中兴通讯股份有限公司 | Method and device for deploying application program in server |
| CN102073520A (en) * | 2010-12-30 | 2011-05-25 | 中国民航信息网络股份有限公司 | Dynamic management system and method for C++ application program version |
| CN105404524A (en) * | 2014-09-15 | 2016-03-16 | 阿里巴巴集团控股有限公司 | Class loading and isolating method and apparatus in Java application |
| CN105242948A (en) * | 2015-10-27 | 2016-01-13 | 江苏电力信息技术有限公司 | Java web project based hot deploy implementation method |
| CN105389186A (en) * | 2015-11-20 | 2016-03-09 | 福建亿榕信息技术有限公司 | Hot deployment method and system for Java application |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106815056A (en) | 2017-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210349706A1 (en) | Release lifecycle management system for multi-node application | |
| US10740132B2 (en) | Systems and methods for updating containers | |
| US10908999B2 (en) | Network block device based continuous replication for Kubernetes container management systems | |
| US9519472B2 (en) | Automation of virtual machine installation by splitting an installation into a minimal installation and customization | |
| RU2495481C2 (en) | Software deployment in large-scale network systems | |
| US10248398B2 (en) | Method for virtualizing software applications | |
| US9280338B1 (en) | Dynamic application updates | |
| KR101574366B1 (en) | Synchronizing virtual machine and application life cycles | |
| US20120042195A1 (en) | Managing operating system deployment failure | |
| CN109614167B (en) | Method and system for managing plug-ins | |
| US20120110570A1 (en) | Stateful applications operating in a stateless cloud computing environment | |
| US20130007435A1 (en) | Server management with dynamic construction of pre-boot images | |
| Etchevers et al. | Self-configuration of distributed applications in the cloud | |
| US20150220308A1 (en) | Model-based development | |
| CN111610985B (en) | Kubernetes cluster rapid deployment method on domestic platform | |
| US20090249311A1 (en) | Sharing a native module of compiled code using an abstraction module of interpreted code in a virtual machine environment | |
| US10203976B2 (en) | Virtual appliance management in a virtualized computing environment based on operational modes associated with virtual appliance | |
| WO2020019993A1 (en) | Virtual machine container for applications | |
| CN106815056B (en) | Application heat deployment method and device based on JCL framework | |
| US20160378361A1 (en) | Methods and apparatus to apply a modularized virtualization topology using virtual hard disks | |
| CN112486938A (en) | Log collection method and system applied to kubernets cluster | |
| CN112214413B (en) | Application program testing method, device, equipment and storage medium | |
| US8949423B2 (en) | Autonomically co-locating first and second components on a select server | |
| CN113821220A (en) | Installation method and device of linux operating system | |
| US20220353341A1 (en) | Efficient deployment of cloud resources |
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 |