Application to container conversion and migration
A method and system is disclosed for migrating an application on a source computer system, which may be a legacy application running on an out-of-date operating system, to a container host running on a target computer system. The system includes software products which analyse the source system to identify application components, and which provision containers corresponding to the identified components.
1. A method of migrating an application, the method comprising the steps of:
a) providing a source computer system that is a server computer system and a target computer system that is a virtual machine, the source computer system having the application to be migrated to the target computer system, and the application being installed on the source computer system and running on the source computer system;
b) the source computer system identifying a primary entry point provided by the application on the source computer system, the primary entry point being an interface to an external system or another application;
c) the source computer system examining the application on the source computer system when the application is running on the source computer system to determine an executable program which provides the primary entry point;
d) the source computer system defining an application component by identifying internal and external entry points used and provided by the executable program, an internal entry point being an interface to another component in the application and an external entry point being an interface to an external system or another application;
e) recursively carrying out steps c) and d) for each of the internal entry points identified as used in step (d), until there are no internal entry points associated with any components which are not provided by another component; and
f) subsequent to steps (a) to (e), migrating the application to the target computer system by provisioning a container on the target computer system for each application component.
2. The method as claimed in claim 1 , wherein for each application component identified, a list of dependencies associated with the executable program is identified.
3. The method as claimed in claim 2 , wherein the list of dependencies include packages and libraries required by the executable program.
4. The method as claimed in claim 2 , wherein the list of dependencies include persistent storage required by the executable program.
5. The method as claimed in claim 2 , wherein the list of dependencies are identified during step (ed).
6. The method as claimed in claim 2 , wherein determining the list of dependencies includes recursively building a dependency tree.
7. The method as claimed in claim 1 , in which redundant entry points are identified, and the application components having the redundant entry points are redefined to omit the redundant entry points.
8. The method as claimed in claim 1 , in which identifying the primary entry point includes scanning the source computer system for known types of service files.
9. The method as claimed in claim 1 , in which identifying entry points used and provided by the application components includes examining the application when it is running on the source computer system.
10. The method as claimed in claim 1 , further including provisioning network connections between the containers on the target computer system.
11. The method as claimed in claim 1 , further including provisioning volumes for persistent storage on the target computer system.
12. The method as claimed in claim 1 , further including creating a startup script associated with at least one of the containers.
13. A computer program product comprising a non-transitory computer readable storage media storing computer executable instructions which when executed are adapted to carry out the method of claim 1 .