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

Patent metadata

Field	Value
Publication number	US-9600264-B2
Application number	US-201414526817-A
Country	US
Kind code	B2
Filing date	Oct 29, 2014
Priority date	Nov 30, 2010
Publication date	Mar 21, 2017
Grant date	Mar 21, 2017

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.

First claim

What is claimed is:

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 leas

Assignees

• IBM

Inventors

• Draper Christine M
• Manekar Ashwin B
• Mcmahon Michael J
• Sundararaman Renganathan
• Sweitzer John W
• Thomsen Kaylee M

Classifications

• G06F8/71

  Version control (security arrangements therefor G06F21/57); Configuration management · CPC title

• G06F8/10

  Requirements analysis; Specification techniques · CPC title

• G06F8/65 Primary

  Updates (security arrangements therefor G06F21/57) · CPC title