System module deployment optimization

Patent metadata

Field	Value
Publication number	US-10216502-B2
Application number	US-201715786844-A
Country	US
Kind code	B2
Filing date	Oct 18, 2017
Priority date	Sep 14, 2015
Publication date	Feb 26, 2019
Grant date	Feb 26, 2019

Abstract

Optimizing deployment of a modular application in a runtime environment is provided. The optimizing includes: deploying application modules of the modular application, each application module having a module manifest and at least one application module having parts for execution, one or more module manifests include one or more references to parts of another application module, and parts required for execution of the application, the deploying is according to the module manifest; executing the modular application; determining that at least one deployed application module has no parts executing in the runtime environment; and adapting the module manifest so that the determined at least one deployed application module will not be deployed as part of the modular application in future deployments.

First claim

What is claimed is:

1. A method for optimizing deployment of a modular application in a runtime environment, the method comprising:
deploying application modules of the modular application, each application module having a module manifest and at least one application module having parts for execution, one or more module manifests comprising one or more references to parts of another application module, and parts required for execution of the application, the deploying being according to the module manifest;
executing the modular application in a runtime environment on a representative workload;
based on the modular application operating on the representative workload, determining that at least one deployed application module has no parts executing in the runtime environment, the determining including checking a heap of the runtime environment to determine whether at least one deployed application module has no parts executing in the heap;
based on determining that at least one deployed application module has no parts executing in the heap, adapting the module manifests so that the determined at least one deployed application module with no parts executing in the heap will not be deployed as part of the modular application in future deployments; and
wherein adapting the module manifests comprises creating an overlay file that operates on the module manifests so that the determined at least one deployed application module will not be deployed in future deployments, wherein the overlay file is referenced in a module manifest and used during execution to selectively deploy listed parts required for execution in the module manifest rather than deploying all listed parts in the module manifest.

2. The method of claim 1 , wherein adapting the module manifests comprises physically changing at least one module manifest such that parts determined as not executing in the runtime environment are no longer listed in the at least one module manifest.

3. The method of claim 1 , further comprising providing a user option for each of the at least one determined application modules for confirming adaption of the module manifests or not.

4. The method of claim 1 , wherein the determining that the at least one deployed application module has no parts executing in the runtime environment comprises determining that the at least one deployed application module has no parts loaded in the heap of the runtime environment.

5. The method of claim 1 , wherein the module manifests for the modular application are collected and updated in a remote repository.

6. The method of claim 1 , further comprising providing an indication of a characteristic of the determined at least one deployed application module that would allow environment gains to be determined.

7. A system for optimizing deployment of a modular application in a runtime environment, the system comprising:
a memory; and
a processor in communications with the memory, wherein the system performs a method comprising:
deploying application modules of the modular application, each application module having a module manifest and at least one application module having parts for execution, one or more module manifests comprising one or more references to parts of another application module, and parts required for execution of the application, the deploying being according to the module manifest;
executing the modular application in a runtime environment on a representative workload;
based on the modular application operating on the representative workload, determining that at least one deployed application module has no parts executing in the runtime environment, the determining including checking a heap of the runtime environment to determine whether at least one deployed application module has no parts executing in the heap;
based on determining that at least one deployed application module has no parts executing in the heap, adapting the module manifests so that the determined at least one deployed application module with no parts executing in the heap will not be deployed as part of the modular application in future deployments; and
wherein adapting the module manifests comprises creating an overlay file that operates on the module manifests so that the determined at least one deployed application module will not be deployed in future deployments, wherein the overlay file is referenced in a module manifest and used during execution to selectively deploy listed parts required for execution in the module manifest rather than deploying all listed parts in the module manifest.

8. The system of claim 7 , wherein adapting the module manifests comprises physically changing at least one module manifest such that parts determined as not executing in the runtime environment are no longer listed in the at least one module manifest.

9. The system of claim 7 , wherein the method performed further comprises providing a user option for each of the at least one determined application modules for confirming adaption of the module manifests or not.

10. The system of claim 7 , wherein the determining that the at least one deployed application module has no parts executing in the runtime environment comprises determining that the at least one deployed application module has no parts loaded in the heap of the runtime environment.

11. The system of claim 7 , wherein the module manifests for the modular application are collected and updated in a remote repository.

12. The system of claim 7 , wherein the method performed further comprises providing an indication of a characteristic of the determined at least one deployed application module that would allow environment gains to be determined.

13. The system of claim 7 , wherein the system is a standalone system or a plugin for a tool, or a plugin for an integrated development environment.

14. A computer program product for optimizing deployment of a modular application in a runtime environment, the computer program product comprising:
a computer readable storage medium having program instructions embodied therewith, the program instructions being executable by a processor to cause the processor to perform a method comprising:
deploying application modules of the modular application, each application module having a module manifest and at least one application module having parts for execution, one or more module manifests comprising one or more references to parts of another application module, and parts required for execution of the application, the deploying being according to the module manifest;
executing the modular application in a runtime environment on a representative workload;
based on the modular application operating on the representative workload, determining that at least one deployed application module has no parts executing in the runtime environment, the determining including checking a heap of the runtime environment to determine whether at least one deployed application module has no parts executing in the heap;
based on determining that at least one deployed application module has no parts executing in the heap, adapting the module manifests so that the determined at least one deployed application module with no parts executing in the heap will not be deployed as part of the modular application in future deployments; and
wherein adapting the module manifests comprises creating an overlay file that operates on the module manifests so that the determined at least one deployed application module will not be deployed in future deployments, wherein the overlay file is referenced in a module manifest and used during execution to selectively deploy listed parts require

Assignees

• IBM
• Int Business Machines Corporations

Inventors

• Charters Graham C
• Evans Lewis
• Mitchell Timothy J
• Pilkington Adam J

Classifications

• G06F8/60 Primary

  Software deployment · CPC title

• G06F9/44505

  Configuring for program initiating, e.g. using registry, configuration files · CPC title