System and method for server migration synchronization

• US 9,495,283 B2
• Filed: 03/17/2014
• Issued: 11/15/2016
• Est. Priority Date: 09/30/2006
• Status: Expired due to Fees

• Current Assignee: Liberty Peak Ventures, LLC (Dominion Harbor Enterprises, LLC)
• Original Assignee: III Holdings 1, LLC
• Inventors: Wright, Lora L., Treger, Jerold R., Romanowski, Judy, Reza, Masood, Alger, James
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Smith, Cheneca
• Application Number:
  US14/216,187
• Publication Number:
  US 20140201716A1
• Time in Patent Office: 974 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 11/368 for test version control, e.g. updating test cases to a new software version
• CPC Class Codes: G06F 11/3684 for test design, e.g. generating new test cases
• CPC Class Codes: G06F 11/3688 for test execution, e.g. scheduling of test suites
• CPC Class Codes: G06F 11/3696 Methods or tools to render software testable
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

A system and method for managing the migration of software components among test servers that form a distributed software test environment to ensure that the software components in each of the test servers represent a production environment except for software components being tested. The system further ensures that component changes rolled out into production are not overridden when multiple update requests are made for the same component.

Claims

1. A method, comprising:

receiving, by a computer-based system configured to perform software component migration, information indicating a first software package is to be tested in a plurality of test environments, wherein the first software package includes a modified test version of a particular software component;

the computer-based system determining that a first computer system in the plurality of test environments is currently executing a process that uses the particular software component but that a second computer system in the plurality of test environments is not currently executing any processes that use the particular software component;

in response to the determining, the computer-based system deploying the first software package to the second computer system for testing and implementing a prohibition on deployment of the first software package to the first computer system;

the computer-based system lifting the prohibition based on received information indicating the process on the first computer system is no longer executing; and

replacing, by the computer-based system, the modified test version of the particular software component with a production component in each of a plurality of test environments.

2. The method of claim 1, wherein a test sequence for the first software package comprises an order in which the modified test version of the particular software component is to be tested in a plurality of computer systems corresponding to the plurality of test environments.

3. The method of claim 1, further comprising labeling, by the computer-based system and in response to completion of a test sequence, the particular software component as a production component.

4. The method of claim 1, further comprising testing, by the computer-based system, the modified test version of the particular software component in accordance with a test sequence, wherein the test sequence specifies testing the first software package on the first and second computer systems.

5. The method of claim 1, wherein the first software package and a second software package have respective priority levels, and wherein an order of testing the first and second software packages is based on the respective priority levels of the packages.

6. The method of claim 1, further comprising notifying, by the computer-based system, an owner of the modified test version of the particular software component that a different modification of the particular software component exists.

7. The method of claim 1, further comprising the computer-based system deploying the first software package to the first computer system in response to the prohibition being lifted;

wherein replacing the modified test version with a production component is performed subsequent to testing of the first software package on the first and second computer systems.

8. The method of claim 1, further comprising the computer-based system storing the first software package in a staging area based on the prohibition.

9. The method of claim 8, further comprising:

the computer-based system removing the first software package from the staging area to deploy it to the first computer system; and

subsequent to testing of the first software package being completed on the first computer system, the computer-based system returning the first software package to the staging area prior to deploying the first software package to a third computer system for testing.

10. A system configured to perform software component migration, comprising:

a processor; and

a non-transitory computer-readable medium having stored thereon instructions that are executable to cause the system to perform operations comprising;

receiving information indicating a first software package is to be tested in a plurality of test environments, wherein the first software package includes a modified test version of a particular software component;

determining that a task executing on a first computer system in the plurality of test environments prevents deployment of the modified test version of the particular software component to the first computer system, but that no tasks executing on a second computer system in the plurality of test environments prevent deployment of the modified test version of the particular software component to the second computer system;

based on the determining, deploying the first software package to the second computer system for testing and prohibiting deployment of the first software package to the first computer system until after the task is completed; and

subsequent to the task completing, deploying the first software package to the first computer system.

11. The system of claim 10, wherein the operations further comprise storing the first software package in a staging area until after the task is completed.

12. The system of claim 10, wherein the operations further comprise deploying the first software package to a third computer system in the plurality of test environments in response based on a testing schedule indicating the first software package is to be tested on the third computer system subsequent to testing the first software package on the first and second computer systems.

13. The system of claim 10, wherein the operations further comprise changing a status of the particular software version from a test status to a production status subsequent to deployment of the first software package to the first and second computer systems.

14. The system of claim 10, wherein deploying the first software package to the first computer system is performed in response to a command from an authorized user.

15. An article of manufacture comprising a non-transitory computer-readable medium having stored thereon instructions that are executable to cause a computer system to perform operations comprising:

receiving information indicating a first software package is to be tested in a plurality of test environments, wherein the first software package includes a modified test version of a particular software component;

determining that a first computer system in the plurality of test environments is currently executing a process that uses the particular software component but that a second computer system in the plurality of test environments is not currently executing any processes that use the particular software component;

in response to the determining, deploying the first software package to the second computer system for testing and implementing a prohibition on deployment of the first software package to the first computer system;

lifting the prohibition based on received information indicating the process on the first computer system is no longer executing; and

replacing the modified test version of the particular software component with a production component in each of a plurality of test environments.

16. The article of manufacture of claim 15, wherein the production component is a version of the particular software component that is earlier than the modified test version.

17. The article of manufacture of claim 15, wherein the operations further comprise storing the first software package in a staging area based on the prohibition.

18. The article of manufacture of claim 17, wherein the operations further comprise:

removing the first software package from the staging area to deploy it to the first computer system; and

subsequent to testing of the first software package being completed on the first computer system, returning the first software package to the staging area prior to deploying the first software package to a third computer system for testing.