Software version management for executing replacement actions

• US 9,411,576 B2
• Filed: 12/02/2013
• Issued: 08/09/2016
• Est. Priority Date: 12/04/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Hocker, Michael D., Jordan, Michael J., Visegrady, Tamas, Werner, Klaus
• Primary Examiner(s): Aponte, Francisco
• Application Number:
  US14/093,661
• Publication Number:
  US 20140157251A1
• Time in Patent Office: 981 Days
• Field of Search: 717168-174, 717/120
• US Class Current: 1/1
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/654 using techniques specially adapted for alterable solid state memories, e.g. for EEPROM or flash memories
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06F 9/44536 Selecting among different versions

Abstract

A software version management system comprising a host driver and at least one software module. The host driver comprises migration means to start, stop and replace the software modules on a computer system in response to replacement actions. The system is characterized by the software module being a downgradable software module comprising a compatibility database specifying dependencies between different versions of the software module; the migration means further comprising i) at least a status means to retrieve temporal information from the downgradable software module; ii) at least a downgrading means responsive to a replacement action to downgrade the downgradable software module to a particular downgrade version and to the status means, the downgrading means identifying an intermediate version of the downgradable software module; the host driver comprising restarting means responsive to the report of the completion of the intermediate version to load and start the downgrade version of the software module.

Claims

1. A software version management system to start, stop and replace one or more software modules on a computer system based on replacement actions, said software version management system comprising:

a memory; and

a processor in communications with the memory, wherein the software version management system is configured to perform a method, said method comprising;

retrieving temporal information from a downgradable software module, the downgradable software module comprising a compatibility database specifying dependencies between different versions of the software module, wherein the compatibility database comprises one or more revision identifiers and one or more attributes thereof for the different versions, and wherein the attributes describe properties of a migration from a first version of the different versions to a second version of the different versions, the properties comprising a concurrent update capability if the first version is replaced by the second version;

downgrading, based on a replacement action to downgrade, the downgradable software module to a particular downgrade version, the downgrading identifying an intermediate version of the downgradable software module, wherein the intermediate version comprises logic to convert the compatibility database to the downgrade version of the downgradable software module and based on execution and completion of the logic, the processor updates the software module to a version of the software module that recognizes the downgraded compatibility database; and

restarting, based on a report of completion of the intermediate version, loading and starting the downgrade version of the software module.

2. The software version management system according to claim 1, wherein the compatibility database specifies temporal dependencies between persistent data of the particular version of the software module and other versions of the software module,

wherein the intermediate version of the downgradable software module is identified from the retrieved temporal dependencies and the downgrade version and is reported to the downgradable software module, and

wherein the downgrading of the software modules is performable without service interruption based on the retrieved temporal dependencies, whether the particular downgrade version of the software module is compatible or incompatible with a current version of the software module before the downgrading.

3. The software version management system according to claim 2, wherein the downgrading stops activities of the downgradable software module and subsequently loads and executes the intermediate version and reports the completion of the intermediate version to a host driver.

4. The software version management system according to claim 1, wherein the downgradable software module is started after completion of the conversion of the compatibility database to the downgrade version of the downgradable software module.

5. The software version management system according to claim 1, wherein the system is extendable to combine multiple databases describing compatibilities between software modules from multiple sources.

6. A computer program product to start, stop and replace one or more software modules on a computer system based on replacement actions, said computer program product comprising:

a non-transitory computer readable storage medium readable by a processing circuit and storing instructions for execution by the processing circuit for performing a method comprising;

retrieving temporal information from a downgradable software module, the downgradable software module comprising a compatibility database specifying dependencies between different versions of the software module, wherein the compatibility database comprises one or more revision identifiers and one or more attributes thereof for the different versions, and wherein the attributes describe properties of a migration from a first version of the different versions to a second version of the different versions, the properties comprising a concurrent update capability if the first version is replaced by the second version;

downgrading, based on a replacement action to downgrade, the downgradable software module to a particular downgrade version, the downgrading identifying an intermediate version of the downgradable software module, wherein the intermediate version comprises logic to convert the compatibility database to the downgrade version of the downgradable software module and based on execution and completion of the logic, the processor updates the software module to a version of the software module that recognizes the downgraded compatibility database; and

restarting, based on a report of completion of the intermediate version, loading and starting the downgrade version of the software module.

7. The computer program product according to claim 6, wherein the compatibility database specifies temporal dependencies between persistent data of the particular version of the software module and other versions of the software module,

wherein the intermediate version of the downgradable software module is identified from the retrieved temporal dependencies and the downgrade version and is reported to the downgradable software module, and

wherein the downgrading of the software modules is performable without service interruption based on the retrieved temporal dependencies, whether the particular downgrade version of the software module is compatible or incompatible with a current version of the software module before the downgrading.

8. The computer program product according to claim 7, wherein the downgrading stops activities of the downgradable software module and subsequently loads and executes the intermediate version and reports the completion of the intermediate version to a host driver.

9. The computer program product according to claim 6, wherein the downgradable software module is started after completion of the conversion of the compatibility database to the downgrade version of the downgradable software module.

10. The computer program product according to claim 6, wherein the system is extendable to combine multiple databases describing compatibilities between software modules from multiple sources.

11. A method for starting, stopping and replacing one or more software modules on a computer system based on replacement actions, said method comprising:

retrieving temporal information from a downgradable software module, the downgradable software module comprising a compatibility database specifying dependencies between different versions of the software module, wherein the compatibility database comprises one or more revision identifiers and one or more attributes thereof for the different versions, and wherein the attributes describe properties of a migration from a first version of the different versions to a second version of the different versions, the properties comprising a concurrent update capability if the first version is replaced by the second version;

downgrading, based on a replacement action to downgrade, the downgradable software module to a particular downgrade version, the downgrading identifying an intermediate version of the downgradable software module, wherein the intermediate version comprises logic to convert the compatibility database to the downgrade version of the downgradable software module and based on execution and completion of the logic, the processor updates the software module to a version of the software module that recognizes the downgraded compatibility database; and

restarting, based on a report of completion of the intermediate version, loading and starting the downgrade version of the software module.

12. The method according to claim 11, wherein the compatibility database specifies temporal dependencies between persistent data of the particular version of the software module and other versions of the software module,

wherein the intermediate version of the downgradable software module is identified from the retrieved temporal dependencies and the downgrade version and is reported to the downgradable software module, and

wherein the downgrading of the software modules is performable without service interruption based on the retrieved temporal dependencies, whether the particular downgrade version of the software module is compatible or incompatible with a current version of the software module before the downgrading.

13. The method according to claim 12, wherein the downgrading stops activities of the downgradable software module and subsequently loads and executes the intermediate version and reports the completion of the intermediate version to a host driver.

14. The method according to claim 11, wherein the downgradable software module is started after completion of the conversion of the compatibility database to the downgrade version of the downgradable software module.