Outdated resource handling and multiple-version upgrade of cloud software

• US 10,289,400 B2
• Filed: 09/07/2016
• Issued: 05/14/2019
• Est. Priority Date: 09/07/2016
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: Amplidata N.V. (Western Digital Corporation)
• Inventors: De Zaeytijd, Ruben, D'Halluin, Carl Rene, De Schrijver, Frederik Jacqueline Luc
• Primary Examiner(s): Zhen, Wei Y
• Assistant Examiner(s): Luu, Binh K
• Application Number:
  US15/258,642
• Publication Number:
  US 20180067736A1
• Time in Patent Office: 979 Days
• Field of Search: None
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416

Abstract

A system and method for seamlessly and automatically handling outdated resources in a cloud and/or performing a multiple-version upgrade within the cloud with little visibility of interim operations to end users are presented. Mechanisms ensure that outdated resources do not communicate with the rest of the cloud (for example, via distributed data models and Application Programming Interfaces (APIs) before they are upgraded to a target software level. A multiple-version upgrade is implemented in the cloud by a single upgrade operation, by which internal paths for upgrading through various interim versions of software are concealed from end users of the cloud.

Claims

1. A method comprising:

receiving, by a controller, a request to execute an upgrade of a resource at a particular cluster node in a cloud, wherein the upgrade is for a conversion of the resource from an initial version to a final version;

responsive to receiving the request, determining, by the controller, if the resource is in an outdated state; and

if the resource is determined to be in the outdated state;

flagging, by the controller, the resource;

executing an instruction, by the controller, to prevent communication from the resource to other cluster nodes in the cloud;

determining, by the controller, if a multiple-version upgrade is required to update the resource from the initial version to the final version;

using upgrade metadata of the resource to split up the multiple-version upgrade into previously defined and tested upgrade paths from the initial version to the final version;

designating the previously defined and tested upgrade paths within a conversion matrix;

determining one or more intermediate paths for the conversion using the conversion matrix;

selecting, using the conversion matrix, an intermediate path from the one or more intermediate paths for the multiple-version upgrade;

executing the multiple-version upgrade, by the controller, by first converting the initial version of the resource to one or more interim versions, via the selected intermediate path, and subsequently converting from the one or more interim versions to the final version; and

concealing, from an end user, conversions through the one or more interim versions to the final version.

2. The method of claim 1, wherein the controller is coupled to a central location for access to data provided by the particular cluster node to indicate states of multiple resources at the particular cluster node, wherein the particular cluster node provides data indicating the states of multiple resources to the central location.

3. The method of claim 2, wherein the multiple-version upgrade is executed responsive to determining an outdated state for a particular resource from the central location.

4. The method of claim 3, wherein the outdated state for the particular resource is determined from the central location at predetermined times.

5. The method of claim 1, wherein a number of the one or more interim versions and associated paths are tracked and placed in a queue for conversion.

6. The method of claim 1, wherein the controller accesses the particular cluster node to determine if a particular resource at the particular cluster node is outdated.

7. The method of claim 1, wherein in the event the controller cannot reach the particular cluster node, the particular cluster node has a mechanism to shut down services operated at the particular cluster node.

8. The method of claim 1, wherein the outdated state of a resource indicates if a particular resource in the particular cluster node is at least one of 1) improperly upgraded and 2) not upgraded.

9. A system comprising:

a processor; and

memory storing instructions that, when executed by the processor, cause the processor to;

receive a request to execute an upgrade of resources at a particular cluster node in a cloud, wherein the upgrade is for conversion of the resources from an initial version to a final version;

responsive to receiving the request, determine if any one of the resources is in an outdated state;

flag a particular resource that is determined to be in the outdated state;

execute instructions to prevent communications from the resource determined to be in the outdated state to other cluster nodes in the cloud;

determine if a multiple-version upgrade is required to update the resource determined to be in the outdated state from the initial version to the final version;

use upgrade metadata of the resource to split up the multiple-version upgrade into previously defined and tested upgrade paths from the initial version to the final version;

determine one or more paths for upgrading to the final version using a conversion matrix;

select an intermediate upgrade path from the one or more paths for upgrading to the final versions for the multiple-version upgrade; and

execute the multiple-version upgrade using the intermediate upgrade path for conversion from the initial version to the final version via at least one interim version, wherein the intermediate upgrade path is distinct from a displayed upgrade path visible to an end user.

10. The system of claim 9, wherein the processor is coupled to a central location for access to data provided by the particular cluster node to indicate states of multiple resources at the particular cluster node, wherein the particular cluster node provides data indicating the states of multiple resources to the central location.

11. The system of claim 10, wherein the multiple-version upgrade is executed responsive to determining an outdated state for a particular resource from the central location.

12. The system of claim 11, wherein the outdated state for the particular resource is determined from the central location at predetermined times.

13. The system of claim 9, wherein a number of the at least one interim version and associated paths are tracked and placed in a queue for conversion.

14. The system of claim 9, wherein the processor accesses the particular cluster node to determine if a particular resource at the particular cluster node is outdated.

15. The system of claim 9, wherein in the event the processor cannot reach the particular cluster node, the particular cluster node has a mechanism to shut down services operated at the particular cluster node.

16. The system of claim 9, wherein the outdated state of a resource indicates if a particular resource in the particular cluster node is at least one of 1) improperly upgraded and 2) not upgraded.

17. A computer program product comprising a non-transitory computer useable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

receive a request to execute an upgrade of resources at a particular cluster node in a cloud, wherein the upgrade is for conversion of the resources from an initial version to a final version;

responsive to receiving the request, determine if any one of the resources is in an outdated state;

flag a particular resource that is determined to be in the outdated state;

execute instructions to prevent communications from the particular resource determined to be in the outdated state to other cluster nodes in the cloud;

determine if a multiple-version upgrade is required to update the particular resource determined to be in the outdated state from the initial version to the final version;

use upgrade metadata of the particular resource determined to be in the outdated state to split up the multiple-version upgrade into previously defined and tested upgrade paths from the initial version to the final version;

designate the previously defined and tested upgrade paths within a conversion matrix;

determine one or more paths for upgrading to the final version, including identifying one or more intermediate upgrade paths for the conversion using the conversion matrix;

select an intermediate upgrade path from the one or more intermediate upgrade paths for the multiple-version upgrade; and

execute the multiple-version upgrade using the intermediate upgrade path for conversion from the initial version to the final version via at least one interim version, wherein the intermediate upgrade path is distinct from a displayed upgrade path visible to an end user.

18. The computer program product of claim 17, wherein the computer readable program, when executed on a computer further causes the computer to:

access data provided by the particular cluster node to indicate states of multiple resources at the particular cluster node, wherein the particular cluster node provides data indicating states of the multiple resources to a central location.

19. The computer program product of claim 18, wherein the computer readable program, when executed on a computer further causes the computer to:

execute the multiple-version upgrade, responsive to determining an outdated state for a particular resource from the central location.

20. The computer program product of claim 18, wherein the computer readable program, when executed on a computer further causes the computer to:

determine if a particular state is in an outdated state at predetermined times.

21. The computer program product of claim 17, wherein the computer readable program, when executed on a computer further causes the computer to:

track a number of the at least one interim version and associated paths and place them in queue for conversion.

22. The computer program product of claim 18, wherein the computer readable program, when executed on a computer further causes the computer to:

access the particular cluster node to determine if a particular resource at the particular cluster node is outdated.

23. The computer program product of claim 18, wherein the computer readable program, when executed on a computer further causes the computer to:

shut down services operating at the particular cluster node by a mechanism at the particular cluster node, in the event the computer cannot reach the particular cluster node.

24. A system comprising:

means for receiving a request to execute an upgrade of a resource at a particular cluster node in a cloud, the upgrade for conversion of the resource from an initial version to a final version;

means for determining, responsive to receiving the request, if the resource is in an outdated state;

responsive to determining that the resource is in the outdated state;

means for flagging the resource;

means for executing an instruction to prevent communication from the resource to other cluster nodes in the cloud;

means for determining if a multiple-version upgrade is required to update the resource from the initial version to the final version;

means for designating previously defined and tested upgrade paths within a conversion matrix;

means for using upgrade metadata of the resource to split up the multiple-version upgrade into the previously defined and tested upgrade paths from the initial version to the final version;

means for determining one or more intermediate paths for the conversion using a conversion matrix based on previously defined and tested upgrade paths from the initial version to the final version;

means for selecting an intermediate path from the one or more intermediate paths for the multiple-version upgrade;

means for executing the multiple-version upgrade by first converting the initial version of the resource to one or more interim versions, via the intermediate path, and subsequently converting from the one or more interim versions to the final version; and

means for concealing, from an end user, conversions through the one or more interim versions to the final version.