US 12,229,144 B2
Platform and service disruption avoidance using deployment metadata
Michael Philip Gugino, II, Raleigh, NC (US)
Assigned to Red Hat, Inc., Raleigh, NC (US)
Filed by Red Hat, Inc., Raleigh, NC (US)
Filed on Sep. 28, 2020, as Appl. No. 17/035,083.
Prior Publication US 2022/0100766 A1, Mar. 31, 2022
Int. Cl. G06F 16/245 (2019.01); G06F 8/60 (2018.01); G06F 8/61 (2018.01); G06F 9/50 (2006.01); G06F 9/54 (2006.01); G06F 16/2455 (2019.01); G06F 16/2457 (2019.01); G06F 16/28 (2019.01)
CPC G06F 16/24564 (2019.01) [G06F 8/61 (2013.01); G06F 9/541 (2013.01); G06F 16/24573 (2019.01); G06F 16/285 (2019.01)] 16 Claims
OG exemplary drawing
 
1. A system, comprising:
a cluster, including one or more nodes and an application programming interface (API) server;
a memory; and
one or more processors in communication with the memory, wherein the one or more processors are configured to, prior to performing a maintenance activity associated with a node of the one or more nodes in the cluster:
receive a request to determine a state of maintenance availability of the cluster, wherein a plurality of applications are installed on the cluster, and wherein the state of maintenance availability of the cluster indicates whether or not one or more applications of the plurality of applications or the cluster in its entirety is vulnerable to disruptions due to the maintenance activity; and
in response to receiving the request:
query the API server to retrieve deployment metadata to discover each of the plurality of applications installed on the cluster;
in response to retrieving the deployment metadata, parse the deployment metadata for each of the plurality of applications to retrieve one or more installation rules associated with each of the plurality of applications;
based on retrieving the one or more installation rules, correlate a first subset of the one or more installation rules associated with a first application of the plurality of applications with a second subset of the one or more installation rules of the plurality of applications to determine a set of conflicts for the first application, wherein determining the set of conflicts comprises determining whether a future downtime of a first node within the cluster would create an effect on the first application, wherein determining the set of conflicts further comprises determining whether a future downtime of each node within the cluster and associated with a second application of the plurality of applications would create an effect on the first application, wherein each conflict of the set of conflicts for the first application is associated with a potential disruption related to the first application caused by the maintenance activity associated with the node;
determine the state of maintenance availability based on the set of conflicts for the first application; and
based on determining the state of maintenance availability, output a notification to a user based on the state of maintenance availability, wherein the notification indicates whether the maintenance activity is unlikely to be successful based on the state of maintenance availability.