Determination of node and cluster compliance with known good states
AssigneeDell Products L.P.
InventorsXueqiang Zhou, Qin Ding
Life of this patent
Estimating the term…
Abstract
Disclosed systems and methods determine a runtime resource state (RRS) of a multi-node cluster running on an information handling system. The RRS may include data tuples referred to as component version pairs (CVP) including a component identifier and version information for each managed component in each of the cluster's multiple nodes. Disclosed systems and methods may compare the RRS information with certified node state information to determine whether a cluster, node, or component is non-compliant. Beneficially, the determination of non-compliant nodes may accommodate nodes and/or clusters that have been partially upgraded.
Claims12
A method, comprising:
- determining a runtime resource state (RRS) for each particular node of a plurality of nodes in a cluster associated with an information handling system, wherein the RRS for each particular node indicates a respective component version pair (CVP) for each component in such particular node, wherein each CVP includes a component identifier and version information;
- determining, based on a comparison of the RRS for each particular node of the plurality of nodes and at least one certified node state (CNS) indicating an approved combination of CVPs for such particular node, whether the cluster includes any non-compliant nodes, wherein the at least one CNS includes:
- a source CNS indicative of approved baseline CVPs;
- and
- a target CNS indicative of approved update CVPS;
- wherein determining whether the cluster includes any non-compliant nodes comprises, for each particular node of the plurality of nodes:
- comparing the RRS of such particular node against the target CNS to identify a target non-compliant component set comprising any CVPs of the RRS of such particular node that are not found within the target CNS;
- comparing the RRS of such particular node against the source CNS to identify a source non-compliant component set comprising any CVPs of the RRS of such particular node that are not found within the source CNS;
- and
- calculating an intersection of the target non-compliant component set and the source non-compliant component set, wherein such particular node is identified as non-compliant responsive to the intersection being non-null;
- responsive to detecting one or more non-compliant nodes, identifying the cluster as a non-compliant cluster;
- responsive to detecting no non-compliant nodes, identifying the cluster as a compliant cluster;
- responsive to detecting a request to upgrade the cluster, a node of the plurality of nodes, or a component of a node of the plurality of nodes, authorizing the request responsive to the cluster being identified as compliant, and denying the request responsive to the cluster being identified as non-compliant;
- and
- responsive to the request being authorized, executing the upgrade on the information handling system.
An information handling system, comprising:
- a central processing unit (CPU);
- and
- a memory accessible to the CPU including processor executable instructions that, when executed by the CPU cause the system to perform operations including:
- determining a runtime resource state (RRS) for each particular node of a plurality of nodes in a cluster associated with an information handling system, wherein the RRS for each particular node indicates a respective component version pair (CVP) including a component identifier and version information for each component in such particular node;
- determining, based on a comparison of the RRS for each particular node of the plurality of nodes and at least one certified node state (CNS) indicating an approved combination of CVPs for such particular node, whether the cluster includes any non-compliant nodes, wherein the at least one CNS includes:
- a source CNS indicative of approved baseline CVPs;
- and
- a target CNS indicative of approved update CVPS;
- wherein determining whether the cluster includes any non-compliant nodes comprises, for each particular node of the plurality of nodes:
- comparing the RRS of such particular node against the target CNS to identify a target non-compliant component set comprising any CVPs of the RRS of such particular node that are not found within the target CNS;
- comparing the RRS of such particular node against the source CNS to identify a source non-compliant component set comprising any CVPs of the RRS of such particular node that are not found within the source CNS;
- and
- calculating an intersection of the target non-compliant component set and the source non-compliant component set, wherein such particular node is identified as non-compliant responsive to the intersection being non-null;
- responsive to detecting one or more non-compliant nodes, identifying the cluster as a non-compliant cluster;
- responsive to detecting no non-compliant nodes, identifying the cluster as a compliant cluster;
- responsive to detecting a request to upgrade the cluster, a node of the plurality of nodes, or a component of a node of the plurality of nodes, authorizing the request responsive to the cluster being identified as compliant, and denying the request responsive to the cluster being identified as non-compliant;
- and
- responsive to the request being authorized, executing the upgrade on the information handling system.
Dependencies are inferred from the claim text.