SERVER CLUSTER PATCH TRACKING TO FACILITATE CODE LEVEL MATCHING OF ADDED SERVERS

• US 20170142228A1
• Filed: 11/12/2015
• Published: 05/18/2017
• Est. Priority Date: 11/12/2015
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Byrne, Alan, Gazda, Michael D., Lamb, Marshall A., Osenbach, Bryan D.
• Application Number:
  US14/938,920
• Publication Number:
  US 20170142228A1
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 67/1004 Server selection for load balancing
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• 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

One or more processors track one or more patch states of one or more servers in a server cluster. One or more processors select one or more patches to be applied to a first server based on a tracked patch state for the one or more servers in the server cluster to which the first server is to join. One or more processors apply the one or more patches to the first server before the first server is joined to the one or more servers in the server cluster.

Claims

1. A method comprising:

i) prior to a request to add a newly provisioned server to a first server cluster within a plurality of server clusters;

receiving, by one or more processors, one or more patch state updates to at least the first server cluster within the plurality of server clusters, wherein the first server cluster within the plurality of server clusters contains one or more servers with a first code level; and

generating, by the one or more processors, an updated patch history for the plurality of server clusters, wherein the updated patch history includes a server ID field, a server type field, a server cluster ID field, a server cluster type field, a server initial state field, a server cluster initial state field, and a patch sequence field; and

ii) subsequent to the request to add the newly provisioned server to the first server cluster within the plurality of server clusters;

based, at least in part, on the updated patch history, determining, by the one or more processors, one or more first patches and a first patch application sequence that will bring the newly provisioned server up to the first code level; and

applying, by the one or more processors, the one or more first patches to the newly provisioned server in a sequence dictated by the first patch application sequence.

4. The method of claim 1, wherein determining, by the one or more processors, the one or more first patches is dependent on:

a server type;

a server initial state; and

a target server cluster.

5. The method of claim 4, wherein the server type further comprises:

a web server, a file server, a print server, a database server, and a messaging server.

22. The method of claim 1, wherein the sequence dictated by the first patch application sequence is based, at least in part, on i) the one or more first patches to be applied to the newly provisioned server and ii) the order of applied patches for the at least one server of the first server cluster.

2-3. -3. (canceled)

6-7. -7. (canceled)

8. A computer program product comprising:

one or more computer-readable storage media and program instructions stored on at least one of the one or more computer-readable storage media, the program instructions comprising;

i) prior to a request to add a newly provisioned server to a first server cluster within a plurality of server clusters;

program instructions to receive one or more patch state updates to at least the first server cluster within the plurality of server clusters, wherein the first server cluster within the plurality of server clusters contains one or more servers with a first code level; and

program instructions to generate an updated patch history for the plurality of server clusters, wherein the updated patch history includes a server ID field, a server type field, a server cluster ID field, a server cluster type field, a server initial state field, a server cluster initial state field, and a patch sequence field; and

ii) subsequent to the request to add the newly provisioned server to the first server cluster within the plurality of server clusters;

based, at least in part, on the updated patch history, program instructions to determine one or more first patches and a first patch application sequence that will bring the newly provisioned server up to the first code level; and

program instructions to apply the one or more first patches to the newly provisioned server in a sequence dictated by the first patch application sequence.

11. The computer program product of claim 8, wherein program instructions to determine, by the one or more processors, the one or more first patches is dependent on:

a server type;

a server initial state; and

a target server cluster.

12. The computer program product of claim 11, wherein the server type further comprises:

a web server, a file server, a print server, a database server, and a messaging server.

23. The computer program product of claim 8, wherein the sequence dictated by the first patch application sequence is based, at least in part, on i) the one or more first patches to be applied to the newly provisioned server and ii) the order of applied patches for the at least one server of the first server cluster.

9-10. -10. (canceled)

13-14. -14. (canceled)

15. A computer system comprising:

one or more computer processors;

one or more computer-readable storage media; and

program instructions stored on at least one of the one or more computer-readable storage media for execution by at least one of the one or more processors, the program instructions comprising;

i) prior to a request to add a newly provisioned server to a first server cluster within a plurality of server clusters;

program instructions to receive one or more patch state updates to at least the first server cluster within the plurality of server clusters, wherein the first server cluster within the plurality of server clusters contains one or more servers with a first code level; and

program instructions to generate an updated patch history for the plurality of server clusters, wherein the updated patch history includes a server ID field, a server type field, a server cluster ID field, a server cluster type field, a server initial state field, a server cluster initial state field, and a patch sequence field; and

ii) subsequent to the request to add the newly provisioned server to the first server cluster within the plurality of server clusters;

based, at least in part, on the updated patch history, program instructions to determine one or more first patches and a first patch application sequence that will bring the newly provisioned server up to the first code level; and

program instructions to apply the one or more first patches to the newly provisioned server in a sequence dictated by the first patch application sequence.

18. The computer system of claim 15, wherein program instructions to determine, by the one or more processors, the one or more first patches is dependent on:

a server type;

a server initial state; and

a target server cluster.

19. The computer system of claim 18, wherein the server type further comprises:

a web server, a file server, a print server, a database server, and a messaging server.

24. The computer system of claim 15, wherein the sequence dictated by the first patch application sequence is based, at least in part, on i) the one or more first patches to be applied to the newly provisioned server and ii) the order of applied patches for the at least one server of the first server cluster.

16-17. -17. (canceled)

20-21. -21. (canceled)