Transition Manager System
AssigneeTransitional Data Services, Inc.
InventorsCraig MACFARLANE, Allison Layona MARTIN
Life of this patent
Estimating the term…
Abstract
Systems, software, and methods for evaluating the scope of computer system changes related to automatic migration from one set of computing hardware to another provide methods and techniques that include evaluations for compliance with one or more policies prior to implementation, and then sequence and automate the migration tasks. A domain-specific language describes activity specifications and asset metadata, which is then used to generate interdependent activities in a project workstream on the basis of stored expert knowledge embedded in knowledge templates. Disaster recovery and “what-if” migration scenarios are tested in order to test and compare options of one or more proposed infrastructure changes.
Claims30
Apparatus comprising:
- a source computer system comprising at least one source processor connected to source storage and to a source communication interface, the source storage configured to store an executable application and associated data, the source computer system having at least one source characteristic and at least one computing function provided by the source processor executing the executable application;
- a target computer system comprising at least one target processor connected to target storage and to a target communication interface, the target computer system having at least one target characteristic;
- and
- a migration computer system in communication with the source computer system and the target computer system via the source and target communication interfaces, respectively, the migration computer system comprising:
- at least one migration processor operating a transition manager application and storage operatively coupled to the at least one migration processor, and
- a migration communications interface operatively coupled to the migration processor, wherein the transition manager application is configured to use the migration communication interface to communicate with the source communication interface and a target communication interface,
- the migration processor being configured to perform migration operations comprising:
- identifying at least one type of transition to perform based upon the at least one source characteristic,
- selecting one or more transition templates based upon the identified type of transition, the source characteristic, and the target characteristic, the one or more transition templates specifying at least one operational requirement for the at least one computing function,
- converting the selected one or more transition templates to a sequence of ordered automated actions,
- executing the ordered actions to migrate the provision and execution of the at least one computing function from the source computer system to the target computer system, and
- automatically testing and verifying the operation of the target computer system with the migrated at least one computing function against the specified at least one operational requirement for the at least one computing function.
A method of operating a transition manager computer system including a processor operating a transition manager application, non-transitory storage, and a communications interface, wherein the transition manager application is in communication using the communication interface with a source computer system(s) and a target computer system(s), the processor performing operations comprising:
- identifying and characterizing an aspect(s) of a source computer system to be transitioned,
- storing the identified and characterized aspect(s) as a data structure in a data store,
- identifying at least one transition to perform based upon the identified and characterized aspect(s) of the source computer system(s),
- identifying the target computer system(s) of a transition,
- obtaining one or more transition templates selected based upon a type of the identified at least one transition, the identified and characterized aspect(s) of the source computer system, and the identified target computer system(s),
- associating the source computer system(s) and the target computer system(s) with the selected and obtained one or more transition templates,
- converting the one or more transition templates to a transition workstream comprising ordered actions,
- storing the ordered actions in a data store,
- executing the ordered actions in order to migrate aspects of the source computer system(s) to the target computer system(s), and
- after executing, verifying that the target computer system(s) is operational.
A transition manager system comprising:
- a processor operating a transition manager application,
- non-transitory storage, and
- a communications interface, wherein the transition manager application is in communication using the communication interface with a source computer system(s) and a target computer system(s), the processor being configured to perform operations comprising:
- identifying and characterizing an aspect(s) of a source computer system to be transitioned,
- storing the identified and characterized aspect(s) as a data structure in a data store,
- identifying at least one transition to perform based upon the identified and characterized aspect(s) of the source computer system(s),
- identifying one or more computer system to be the target computer system(s) of the transition,
- obtaining one or more transition templates selected based upon the type of transition identified, the identified and characterized aspect(s) of the source computer system, and identified target computer system(s),
- associating the source computer system(s) and the target computer system(s) with the obtained one or more transition templates,
- converting the one or more transition templates to a transition workstream comprising ordered actions,
- storing the transition workstream in a data store,
- executing the ordered actions of the transition workstream in order to migrate aspects of the source computer system(s) to the target computer system(s), and
- verifying that the target computer system(s) are operational.
Dependencies are inferred from the claim text.