Generating a customized set of tasks for migration of a deployed software solution

• US 9,600,264 B2
• Filed: 10/29/2014
• Issued: 03/21/2017
• Est. Priority Date: 11/30/2010
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Draper, Christine M., Manekar, Ashwin B., McMahon, Michael J., Sundararaman, Renganathan, Sweitzer, John W., Thomsen, Kaylee M.
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): KEPNANG, GILLES R
• Application Number:
  US14/526,817
• Publication Number:
  US 20150052510A1
• Time in Patent Office: 874 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A migration set list generator specifies a physical topology of a deployed software solution, wherein the software solution comprises software components and data associated with the software components, integrated into a single entity. The migration set list generator specifies at least one solution change to the deployed software solution to meet at least one business requirement and specifies at least one migration strategy for migrating the deployed software solution. The migration set list generator generates migration tasks for making the at least one solution change to the deployed software solution specified in the physical topology based on the at least one migration strategy and generates a recommended physical topology yielded for the software solution if the physical topology is updated according to the migration tasks.

Claims

1. A method for generating a set of tasks for performing a migration of a software solution comprising:

receiving, by at least one computer system, a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

receiving, by the at least one computer system, at least one solution change to the deployed software solution to meet at least one business requirement;

selecting, by the at least one computer system, a plurality of migration strategies for migrating the deployed software solution, wherein each of the plurality of migration strategies comprises at least one product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the plurality of migration strategies has a separate downtime effect for the deployed software solution during migration and a separate hardware requirement;

generating, by the at least one computer system, a first plurality of migration tasks for performing the at least one solution change to the deployed software solution of the current physical topology, wherein the plurality of migration tasks apply a first migration strategy with a first downtime effect and a first hardware requirement from among the plurality of migration strategies;

generating, by the at least one computer system, a recommendation of a first future physical topology for the received software solution, wherein the recommended first future physical topology is updated according to the first plurality of migration tasks, wherein one task of the plurality of migration tasks is associated with a machine;

outputting, by the at least one computer system, the first plurality of migration tasks and recommended first future physical topology, the outputting further illustrating a simulated plan for migrating the software solution according to the at least one migration strategy and meeting the at least one business requirement;

generating, by the at least one computer system, a second plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply a second migration strategy from among the plurality of migration strategies, the second migration strategy applied with a second downtime effect and a second hardware requirement from among the plurality of migration strategies;

generating, by the at least one computer system, a recommendation of a second future physical topology for the received software solution, wherein the recommended second future physical topology is updated according to the second plurality of migration tasks;

analyzing, by the at least one computer system, the first plurality of migration tasks, the recommended first future physical topology, the second plurality of migration tasks, and the recommended second future physical topology to identify at least one time difference between the first downtime effect and second downtime effect and to identify at least one hardware difference between the first hardware requirement and the second hardware requirement;

comparing, by the at least one computer system, a business cost between the first migration strategy and the second migration strategy, while taking into account the at least one time difference and the at least one hardware difference, thereby generating at least one business cost difference;

outputting, by the at least one computer system, the at least one business cost difference between the first migration strategy and the second migration strategy;

evaluating, by the at least one computer system, the business cost difference for the deployed software solution;

selecting, by the at least one computer system, based on the evaluated business cost difference, one of the first migration strategy and the second migration strategy, as a suitable migration strategy; and

executing, by the at least one computer system, a selection of migration tasks associated with the selected suitable migration strategy for the deployed software solution, the selection of migration tasks comprising one of the first plurality of migration tasks and the second plurality of migration tasks.

2. The method according to claim 1, further comprising:

selecting, by the at least one computer system, the plurality of migration strategies comprising the first migration strategy to migrate the software solution in place, wherein the first downtime effect is longer than the second downtime effect and the first hardware requirement is less than the second hardware requirement; and

generating, by the at least one computer system, the first plurality of migration tasks for performing the at least one solution change to the software solution on a same machine currently comprising the software solution, as specified for the software solution in the recommended first future physical topology, wherein the first downtime effect comprises bringing the same machine down, applying the solution change to the same machine, and restarting the same machine.

3. The method according to claim 1, further comprising:

selecting, by the at least one computer system, the plurality of migration strategies comprising the second migration strategy to install the upgraded version of the at least one software component of the plurality of software components on at least one new machine and migrate the data associated with the at least one software component to the at least one new machine, wherein the second downtime effect is less than the first downtime effect and the second hardware requirement of the at least one new machine is more than the first hardware requirement; and

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

performing, by the at least one computer system, the at least one solution change to the software solution on the at least one new machine; and

migrating, by the at least one computer system, the data associated with the at least one software component to the at least one new machine.

4. The method according to claim 1, further comprising:

specifying, by the at least one computer system, the second migration strategy to install the upgraded version of the at least one software component of the plurality of software components on at least one new machine and to keep the current version of the at least one software component on a current machine specified in the current physical topology, wherein the second downtime effect is less than the first downtime effect and the second hardware requirement of the at least one new machine is more than the first hardware requirement; and

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

performing, by the at least one computer system, the at least one solution change to the software solution on the at least one new machine; and

maintaining, by the at least one computer system, the current version of the at least one software component on the current machine.

5. The method according to claim 4, further comprising:

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

moving, by the at least one computer system, a copy of the data associated with the at least one software component to the at least one new machine;

keeping, by the at least one computer system, a current version of the data on the current machine; and

synchronizing, by the at least one computer system, the copy of the data with the current version of the data.

6. The method according to claim 4, further comprising:

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

maintaining, by the at least one computer system, the data associated with the at least one software component on the current machine; and

sharing, by the at least one computer system, the data between the upgraded version of the at least one software component and the current version of the at least one software component.

7. The method according to claim 4, further comprising:

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

moving, by the at least one computer system, a copy of the data associated with the at least one software component to the at least one new machine; and

keeping, by the at least one computer system, a current version of the data on the current machine.

8. The method according to claim 1, further comprising:

selecting, by the at least one computer system, the plurality of migration strategies comprising the second migration strategy with the product level strategy specified to migrate a particular software component and its associated data to another machine and with the solution level strategy specified to migrate the software solution in place;

applying, by the at least one computer system, the product level strategy to override the solution level strategy for the particular software component; and

generating, by the at least one computer system, the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

performing, by the at least one computer system, the at least one solution change to the particular software component on at least one new machine;

migrating, by the at least one computer system, the data associated with the particular software component to the at least one new machine, excluding the particular software component from at least one remaining change specified in the at least one solution change; and

performing, by the at least one computer system, the at least one remaining change on a same machine originally comprising the software solution, as specified for the software solution as originally specified in the current physical topology.

9. The method according to claim 1, further comprising:

accessing, by the at least one computer system, at least one recommended upgrade approach for at least one component of the software solution; and

generating, by the at least one computer system, the second plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the recommended second future physical topology, wherein the at least one solution change is based on the second migration strategy to perform in accordance with the at least one recommended upgrade approach.

10. The method according to claim 1, further comprising:

specifying, by the at least one computer system, the current physical topology of the deployed software solution for an enterprise client comprising at least one dependency between a first software component of the plurality of software components and a second software component of the plurality of software components;

receiving, by the at least one computer system, specifications for at least one solution change to the first software component of the deployed software solution to meet the at least one business requirement of the enterprise client;

generating, by the at least one computer system, the first plurality of migration tasks for performing the at least one solution change to the first software component of the deployed software solution comprising a first selection of tasks for migrating the first software component according to the first migration strategy and a second selection of tasks for migrating the second software component according to the first migration strategy; and

generating, by the at least one computer system, the recommended first future physical topology yielded for the software solution if the physical topology is updated according to the first plurality of migration tasks, wherein the recommended future physical topology comprises the dependency between an upgraded version of the first software component and the second software component, wherein the upgraded version of the first software component is based on the first selection of tasks.

11. A computer system for generating a set of tasks for performing a migration of a software solution, the system comprising:

a migration task list generator coupled to at least one processor and memory;

the migration task list generator programmed to;

receive a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

receive at least one solution change to the deployed software solution to meet at least one business requirement;

select a plurality of migration strategies for migrating the deployed software solution, wherein each of the plurality of migration strategies comprises at least one product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the plurality of migration strategies has a separate downtime effect for the deployed software solution during migration and a separate hardware requirement;

generate a first plurality of migration tasks for performing the at least one solution change to the deployed software solution of the current physical topology, wherein the plurality of migration tasks apply a first migration strategy with a first downtime effect and a first hardware requirement from among the plurality of migration strategies;

generate a recommendation of a first future physical topology for the received software solution, wherein the recommended first future physical topology is updated according to the first plurality of migration tasks, wherein one task of the plurality of migration tasks is associated with a machine;

output the first plurality of migration tasks and recommended first future physical topology, the outputting further illustrating a simulated plan for migrating the software solution according to the at least one migration strategy and meeting the at least one business requirement;

generate a second plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply a second migration strategy from among the plurality of migration strategies, the second migration strategy applied with a second downtime effect and a second hardware requirement from among the plurality of migration strategies;

generate a recommendation of a second future physical topology for the received software solution, wherein the recommended second future physical topology is updated according to the second plurality of migration tasks;

analyze the first plurality of migration tasks, the recommended first future physical topology, the second plurality of migration tasks, and the recommended second future physical topology to identify at least one time difference between the first downtime effect and second downtime effect and to identify at least one hardware difference between the first hardware requirement and the second hardware requirement;

compare a business cost between the first migration strategy and the second migration strategy, while taking into account the at least one time difference and the at least one hardware difference, thereby generating at least one business cost difference;

output at least one business cost difference between the first migration strategy and the second migration strategy;

evaluate the business cost difference for the deployed software solution;

select, based on the evaluated business cost difference, one of the first migration strategy and the second migration strategy, as a suitable migration strategy; and

execute a selection of migration tasks associated with the selected suitable migration strategy for the deployed software solution, the selection of migration tasks comprising one of the first plurality of migration tasks and the second plurality of migration tasks.

12. The system according to claim 11, the migration task list generator further programmed to:

select the plurality of migration strategies comprising the first migration strategy to migrate the software solution in place, wherein the first downtime effect is longer than the second downtime effect and the first hardware requirement is less than the second hardware requirement; and

generate the first plurality of migration tasks for performing the at least one solution change to the software solution on a same machine currently comprising the software solution, as specified for the software solution in the recommended first future physical topology, wherein the first downtime effect comprises bringing the same machine down, applying the solution change to the same machine, and restarting the same machine.

13. The system according to claim 11, the migration task list generator further programmed to:

select the plurality of migration strategies comprising the second migration strategy to install the upgraded version of the at least one software component of the plurality of software components on at least one new machine and migrate the data associated with the at least one software component to the at least one new machine, wherein the second downtime effect is less than the first downtime effect and the second hardware requirement of the at least one new machine is more than the first hardware requirement; and

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

perform the at least one solution change to the software solution on the at least one new machine; and

migrating the data associated with the at least one software component to the at least one new machine.

14. The system according to claim 11, the migration task list generator further programmed to:

specify the second migration strategy to install the upgraded version of the at least one software component of the plurality of software components on at least one new machine and to keep the current version of the at least one software component on a current machine specified in the current physical topology, wherein the second downtime effect is less than the first downtime effect and the second hardware requirement of the at least one new machine is more than the first hardware requirement; and

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

performing the at least one solution change to the software solution on the at least one new machine; and

maintaining the current version of the at least one software component on the current machine.

15. The system according to claim 14, the migration task list generator further programmed to:

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

moving a copy of the data associated with the at least one software component to the at least one new machine;

keeping a current version of the data on the current machine; and

synchronizing the copy of the data with the current version of the data.

16. The system according to claim 14, the migration task list generator further programmed to:

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

maintaining the data associated with the at least one software component on the current machine; and

sharing the data between the upgraded version of the at least one software component and the current version of the at least one software component.

17. The system according to claim 14, the migration task list generator further programmed to:

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one additional task for;

moving a copy of the data associated with the at least one software component to the at least one new machine; and

keeping a current version of the data on the current machine.

18. The system according to claim 11, the migration task list generator further programmed to:

select the plurality of migration strategies comprising the second migration strategy with the product level strategy specified to migrate a particular software component and its associated data to another machine and with the solution level strategy specified to migrate the software solution in place;

apply the product level strategy to override the solution level strategy for the particular software component; and

generate the second plurality of migration tasks, wherein the second plurality of migration tasks comprise at least one task for;

performing the at least one solution change to the particular software component on the at least one new machine;

migrating the data associated with the particular software component to the at least one new machine, excluding the particular software component from at least one remaining change specified in the at least one solution change; and

performing the at least one remaining change on a same machine originally comprising the software solution, as specified for the software solution as originally specified in the current physical topology.

19. The system according to claim 11, the migration task list generator further programmed to:

access at least one recommended upgrade approach for at least one component of the software solution; and

generate the second plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the recommended second future physical topology, wherein the at least one solution change is based on the second migration strategy to perform in accordance with the at least one recommended upgrade approach.

20. A computer program product for generating a set of tasks for performing a migration of a software solution, the computer program product comprising a non-transitory computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to:

receive, by the processor, a current physical topology of a deployed software solution, wherein the deployed software solution comprises a plurality of software components and data associated with the plurality of software components integrated into a single entity;

receive, by the processor, at least one solution change to the deployed software solution to meet at least one business requirement;

select, by the processor, a plurality of migration strategies for migrating the deployed software solution, wherein each of the plurality of migration strategies comprises at least one product level strategy applicable for a particular software component of the plurality of software components and at least one solution level strategy applicable for the plurality of software components, wherein the product level strategy overrides the solution level strategy for the particular software component, wherein each of the plurality of migration strategies has a separate downtime effect for the deployed software solution during migration and a separate hardware requirement;

generate, by the processor, a first plurality of migration tasks for performing the at least one solution change to the deployed software solution of the current physical topology, wherein the plurality of migration tasks apply a first migration strategy with a first downtime effect and a first hardware requirement from among the plurality of migration strategies;

generate, by the processor, a recommendation of a first future physical topology for the received software solution, wherein the recommended first future physical topology is updated according to the first plurality of migration tasks, wherein one task of the plurality of migration tasks is associated with a machine;

output, by the processor, the first plurality of migration tasks and recommended first future physical topology, the outputting further illustrating a simulated plan for migrating the software solution according to the at least one migration strategy and meeting the at least one business requirement;

generate, by the processor, a second plurality of migration tasks for performing the at least one solution change to the deployed software solution specified in the current physical topology, wherein the plurality of migration tasks apply a second migration strategy from among the plurality of migration strategies, wherein the plurality of migration tasks apply a second migration strategy with a second downtime effect and a second hardware requirement from among the plurality of migration strategies;

generate, by the processor, a recommendation of a second future physical topology for the received software solution, wherein the recommended second future physical topology is updated according to the second plurality of migration tasks;

analyze, by the processor, the first plurality of migration tasks, the recommended first future physical topology, the second plurality of migration tasks, and the recommended second future physical topology to identify at least one time difference between the first downtime effect and second downtime effect and to identify at least one hardware difference between the first hardware requirement and the second hardware requirement;

compare, by the processor, a business cost between the first migration strategy and the second migration strategy, while taking into account the at least one time difference and the at least one hardware difference, thereby generating at least one business cost difference;

output, by the processor, at least one business cost difference between the first migration strategy and the second migration strategy;

evaluate, by the processor, the business cost difference for the deployed software solution;

select, by the processor, based on the evaluated business cost difference, one of the first migration strategy and the second migration strategy, as a suitable migration strategy; and

execute, by the processor, a selection of migration tasks associated with the selected suitable migration strategy for the deployed software solution, the selection of migration tasks comprising one of the first plurality of migration tasks and the second plurality of migration tasks.