MAINTAINING DYNAMIC CONFIGURATION INFORMATION OF A MULTI-HOST OFF-CLUSTER SERVICE ON A CLUSTER

• US 20170257382A1
• Filed: 05/17/2017
• Published: 09/07/2017
• Est. Priority Date: 02/12/2015
• Status: Abandoned Application

• Current Assignee: NetApp, Inc.
• Original Assignee: NetApp, Inc.
• Inventors: Muhlestein, Mark, Jaiswal, Rajesh, Bhargo, Sunil, Singh, Mankawaldeep
• Application Number:
  US15/597,955
• Publication Number:
  US 20170257382A1
• Time in Patent Office: Days
• CPC Class Codes: G06F 21/57 Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
• CPC Class Codes: H04L 63/145 the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms

Abstract

Techniques for maintaining dynamic configuration information of a multi-host off-cluster service on a cluster are described. An apparatus may comprise a dynamic configuration validation service component to execute to execute a dynamic configuration validation service for scanning files in a cluster of nodes. The dynamic configuration validation service component operative to validate a scanner version for each one of multiple scanners for scanning a file in a cluster of nodes, maintain the scanner version in a list of valid scanner versions for the multiple scanners, and scan the file by one of the one of multiple scanners having the scanner version contained in the list of the valid scanner versions.

Claims

1-20. -20. (canceled)

21. A method, comprising:

retrieving, by a computing device, a scanner version identifier (ID) from a stored result of a file scan associated with a file in response to a received request to access the file;

determining, by the computing device, when a scanner corresponding to the scanner version ID is active; and

providing, by the computing device, access to the file in response to the request, without scanning the file, when the determining indicates that the scanner corresponding to the scanner version ID is active.

22. The method of claim 21, further comprising determining, by the computing device, when the scanner is valid based on a connection count associated with the scanner version ID in a scanner version list.

23. The method of claim 21, further comprising:

collating, by the computing device, connection information for multiple scanners actively performing scanning operations in a cluster of nodes, wherein the multiple scanners comprise the scanner;

maintaining, by the computing device, a connection count associated with a version of each of the multiple scanners based on the connection information;

determining, by the computing device, when a new version for one or more of the multiple scanner has been connected to one or more nodes in the cluster of nodes; and

updating, by the computing device, the connection information, when the determining indicated that a new version for one or more of the multiple scanners has been connected to one or more nodes in the cluster of nodes.

24. The method of claim 21, further comprising:

assigning, by the computing device, the scanner version ID based on a scanner version of the scanner; and

storing, by the computing device, the scanner version ID in a scanner version list.

25. The method of claim 21, further comprising scanning, by the computing device, the file with the scanner, when the determining indicates that the scanner corresponding to the scanner version ID is not active.

26. The method of claim 21, further comprising:

determining, by the computing device, when the scanner has disconnected and when the determining indicates that the scanner has disconnected;

resetting, by the computing device, a connection count associated with the scanner version ID in a scanner version list to indicate that the scanner is not currently connected;

delaying, by the computing device, a removal of the scanner version ID from the valid scanner version list; and

setting, by the computing device, a timeout period associated with the scanner version ID in the valid scanner version list.

27. A non-transitory machine readable medium having stored thereon instructions for maintaining dynamic configuration information for a cluster service comprising machine executable code which when executed by at least one machine, causes the machine to:

retrieve a scanner version identifier (ID) from a stored result of a file scan associated with a file in response to a received request to access the file;

determine when a scanner corresponding to the scanner version ID is active; and

provide access to the file in response to the request, without scanning the file, when the determining indicates that the scanner corresponding to the scanner version ID is active.

28. The non-transitory machine readable medium of claim 27, wherein the machine executable code when executed by the machine, further causes the machine to determine when the scanner is valid based on a connection count associated with the scanner version ID in a scanner version list.

29. The non-transitory machine readable medium of claim 27, wherein the machine executable code when executed by the machine, further causes the machine to:

collate connection information for multiple scanners actively performing scanning operations in a cluster of nodes, wherein the multiple scanners comprise the scanner;

maintain a connection count associated with a version of each of the multiple scanners based on the connection information;

determine when a new version for one or more of the multiple scanner has been connected to one or more nodes in the cluster of nodes; and

update the connection information, when the determining indicated that a new version for one or more of the multiple scanners has been connected to one or more nodes in the cluster of nodes.

30. The non-transitory machine readable medium of claim 27, wherein the machine executable code when executed by the machine, further causes the machine to:

assign the scanner version ID based on a scanner version of the scanner; and

store the scanner version ID in a scanner version list.

31. The non-transitory machine readable medium of claim 27, wherein the machine executable code when executed by the machine, further causes the machine to scan the file with the scanner, when the determining indicates that the scanner corresponding to the scanner version ID is not active.

32. The non-transitory machine readable medium of claim 27, wherein the machine executable code when executed by the machine, further causes the machine to:

determine when the scanner has disconnected and when the determining indicates that the scanner has disconnected;

reset a connection count associated with the scanner version ID in a scanner version list to indicate that the scanner is not currently connected;

delay a removal of the scanner version ID from the valid scanner version list; and

set a timeout period associated with the scanner version ID in the valid scanner version list.

33. A computing device, comprising:

a memory containing a machine readable medium comprising machine executable code having stored thereon instructions for maintaining dynamic configuration information for a cluster service; and

a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to;

retrieve a scanner version identifier (ID) from a stored result of a file scan associated with a file in response to a received request to access the file;

determine when a scanner corresponding to the scanner version ID is active; and

provide access to the file in response to the request, without scanning the file, when the determining indicates that the scanner corresponding to the scanner version ID is active.

34. The computing device of claim 33, wherein the processor is further configured to execute the machine executable code to cause the processor to determine when the scanner is valid based on a connection count associated with the scanner version ID in a scanner version list.

35. The computing device of claim 33, wherein the processor is further configured to execute the machine executable code to cause the processor to;

collate connection information for multiple scanners actively performing scanning operations in a cluster of nodes, wherein the multiple scanners comprise the scanner;

maintain a connection count associated with a version of each of the multiple scanners based on the connection information;

determine when a new version for one or more of the multiple scanner has been connected to one or more nodes in the cluster of nodes; and

update the connection information, when the determining indicated that a new version for one or more of the multiple scanners has been connected to one or more nodes in the cluster of nodes.

36. The computing device of claim 33, wherein the processor is further configured to execute the machine executable code to cause the processor to:

assign the scanner version ID based on a scanner version of the scanner; and

store the scanner version ID in a scanner version list.

37. The computing device of claim 33, wherein the processor is further configured to execute the machine executable code to cause the processor to scan the file with the scanner, when the determining indicates that the scanner corresponding to the scanner version ID is not active.

38. The computing device of claim 33, wherein the processor is further configured to execute the machine executable code to cause the processor to;

determine when the scanner has disconnected and when the determining indicates that the scanner has disconnected;

reset a connection count associated with the scanner version ID in a scanner version list to indicate that the scanner is not currently connected;

delay a removal of the scanner version ID from the valid scanner version list; and

set a timeout period associated with the scanner version ID in the valid scanner version list.