DEPLOYING DATABASE UPGRADES TO MULTIPLE ENVIRONMENTS IN A DIFFERENT ORDER

• US 20140337282A1
• Filed: 05/07/2013
• Published: 11/13/2014
• Est. Priority Date: 05/07/2013
• Status: Active Grant

• Current Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Original Assignee: Red Hat Israel Ltd. (International Business Machines Corporation)
• Inventors: Zaslavsky, Yair, Mesika, Eli
• Granted Patent: US 9,569,468 B2
• Time in Patent Office: Days
• US Class Current: 707/609
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/45533 Hypervisors; Virtual machine monitors

Abstract

A virtualization manager receives a request to install a new feature in a first virtualization environment. The virtualization manager identifies a first database upgrade script corresponding to the new feature and compares a first identification number of the first database upgrade script to a second identification number of a second database upgrade script, the second database upgrade script previously run on a management database for the first virtualization environment. If the first identification number is less than the second identification number, the virtualization manager generates a copy of the first database upgrade script and names the copy of the first database upgrade script with a third identification number that is greater than the second identification number. The virtualization manager then runs the copy of the first database upgrade script on the management database.

Claims

1. A method comprising:

receiving a request to install a new feature in a first virtualization environment;

identifying a first database upgrade script corresponding to the new feature;

comparing a first identification number of the first database upgrade script to a second identification number of a second database upgrade script, the second database upgrade script previously run on a management database for the first virtualization environment;

if the first identification number is less than the second identification number, generating, by a processing device, a copy of the first database upgrade script and naming the copy of the first database upgrade script with a third identification number that is greater than the second identification number; and

running the copy of the first database upgrade script on the management database.

2. The method of claim 1, further comprising:

if the first identification number is greater than the second identification number, running the first database upgrade script on the management database.

3. The method of claim 1, further comprising:

prior to running the first database upgrade script, determining whether the copy of the first database upgrade script has been previously run on the management database.

4. The method of claim 3, wherein determining whether the copy of the first database upgrade script has been previously run comprises:

applying a hash function to the first database upgrade script to generate a first hash value;

applying the hash function to a schema version table in the management database to generate one or more second hash values, the schema version table storing one or more database upgrade scripts previously run on the management database; and

comparing the first hash value to the one or more second hash values to determine whether the first hash value matches one or more of the second hash values.

5. The method of claim 1, further comprising:

running the first database upgrade script on a management database in a second virtualization environment prior to running the second database upgrade script, wherein the second database upgrade script has not been previously run on the management database in the second virtualization environment.

6. The method of claim 1, wherein the first identification number and the second identification number increase sequentially in view of an order in which the first database upgrade script and the second database upgrade script were developed.

7. The method of claim 1, wherein:

the first virtualization environment comprises a plurality of host computers running a plurality of virtual machines associated with a plurality of virtual disks;

the processing device is part of a host controller coupled to the plurality of host computers; and

the management database comprises a plurality of entries pertaining to one or more of the plurality of host computers, the plurality of virtual machines or the plurality of virtual disks.

8. A system comprising:

a processing device;

a memory coupled to the processing device; and

a virtualization manager, executable by the processing device from the memory, to;

receive a request to install a new feature in a first virtualization environment;

identify a first database upgrade script corresponding to the new feature;

compare a first identification number of the first database upgrade script to a second identification number of a second database upgrade script, the second database upgrade script previously run on a management database for the first virtualization environment;

if the first identification number is less than the second identification number, generate a copy of the first database upgrade script and name the copy of the first database upgrade script with a third identification number that is greater than the second identification number; and

run the copy of the first database upgrade script on the management database.

9. The system of claim 8, the virtualization manager further to:

if the first identification number is greater than the second identification number, run the first database upgrade script on the management database.

10. The system of claim 8, the virtualization manager further to:

prior to running the first database upgrade script, determine whether the copy of the first database upgrade script has been previously run on the management database.

11. The system of claim 10, wherein to determine whether the copy of the first database upgrade script has been previously run, the virtualization manager further to:

apply a hash function to the first database upgrade script to generate a first hash value;

apply the hash function to a schema version table in the management database to generate one or more second hash values, the schema version table storing one or more database upgrade scripts previously run on the management database; and

compare the first hash value to the one or more second hash values to determine whether the first hash value matches one or more of the second hash values.

12. The system of claim 8, the virtualization manager further to:

run the first database upgrade script on a management database in a second virtualization environment prior to running the second database upgrade script, wherein the second database upgrade script has not been previously run on the management database in the second virtualization environment.

13. The system of claim 8, wherein the first identification number and the second identification number increase sequentially in view of an order in which the first database upgrade script and the second database upgrade script were developed.

14. The system of claim 8, wherein:

the first virtualization environment comprises a plurality of host computers running a plurality of virtual machines associated with a plurality of virtual disks;

the processing device is part of a host controller coupled to the plurality of host computers; and

the management database comprises a plurality of entries pertaining to one or more of the plurality of host computers, the plurality of virtual machines or the plurality of virtual disks.

15. A non-transitory machine-readable storage medium storing instructions which, when executed, cause a processing device to perform operations comprising:

receiving a request to install a new feature in a first virtualization environment;

identifying a first database upgrade script corresponding to the new feature;

comparing a first identification number of the first database upgrade script to a second identification number of a second database upgrade script, the second database upgrade script previously run on a management database for the first virtualization environment;

if the first identification number is less than the second identification number, generating, by the processing device, a copy of the first database upgrade script and naming the copy of the first database upgrade script with a third identification number that is greater than the second identification number; and

running the copy of the first database upgrade script on the management database.

16. The non-transitory machine-readable storage medium of claim 15, the operations further comprising:

if the first identification number is greater than the second identification number, running the first database upgrade script on the management database.

17. The non-transitory machine-readable storage medium of claim 15, the operations further comprising:

prior to running the first database upgrade script, determining whether the copy of the first database upgrade script has been previously run on the management database.

18. The non-transitory machine-readable storage medium of claim 16, wherein determining whether the copy of the first database upgrade script has been previously run comprises:

applying a hash function to the first database upgrade script to generate a first hash value;

applying the hash function to a schema version table in the management database to generate one or more second hash values, the schema version table storing one or more database upgrade scripts previously run on the management database; and

comparing the first hash value to the one or more second hash values to determine whether the first hash value matches one or more of the second hash values.

19. The non-transitory machine-readable storage medium of claim 15, the operations further comprising:

running the first database upgrade script on a management database in a second virtualization environment prior to running the second database upgrade script, wherein the second database upgrade script has not been previously run on the management database in the second virtualization environment.

20. The non-transitory machine-readable storage medium of claim 15, wherein the first identification number and the second identification number increase sequentially in view of an order in which the first database upgrade script and the second database upgrade script were developed.

21. The non-transitory machine-readable storage medium of claim 15, wherein:

the first virtualization environment comprises a plurality of host computers running a plurality of virtual machines associated with a plurality of virtual disks;

the processing device is part of a host controller coupled to the plurality of host computers; and

the management database comprises a plurality of entries pertaining to one or more of the plurality of host computers, the plurality of virtual machines or the plurality of virtual disks.