Extensible and elastic data management services engine external to a storage domain

Patent metadata

Field	Value
Publication number	US-12299052-B2
Application number	US-202318357277-A
Country	US
Kind code	B2
Filing date	Jul 24, 2023
Priority date	Jul 31, 2015
Publication date	May 13, 2025
Grant date	May 13, 2025

Abstract

A data management services architecture includes architectural components that run in both a storage and compute domains. The architectural components redirect storage requests from the storage domain to the compute domain, manage resources allocated from the compute domain, ensure compliance with a policy that governs resource consumption, deploy program code for data management services, dispatch service requests to deployed services, and monitor deployed services. The architectural components also include a service map to locate program code for data management services, and service instance information for monitoring deployed services and dispatching requests to deployed services. Since deployed services can be stateless or stateful, the services architecture also includes state data for the stateful services, with supporting resources that can expand or contract based on policy and/or service demand. The architectural components also include containers for the deployed services.

First claim

What is claimed is:

1. A method comprising:
identifying a message type of an operation targeting a destination;
evaluating the message type against a set of message types that are not to be routed to data management services for processing before being routed to the destination;
in response to the to the message type occurring within the set of message types, routing the operation to the destination and refraining from redirecting the operation to the data management services for processing;
evaluating service state information populated with service identifiers, service instance locations, service instance capacities for processing operations, and statuses periodically updated using timestamps from service instances; and
in response to the message type not occurring within the set of message types, redirecting the operation to a service instance of a data management service identified by a service identifier as being instantiated at a service instance location and having a service instance capacity and status indicating that the service instance is capable of processing the operation, wherein service state information is used to track deployment of the data management service processing the operation.

2. The method of claim 1 , comprising:
refraining from redirecting operations to the data management services based upon a transition to a state that suspends service availability.

3. The method of claim 1 , comprising:
in response to determining that a plurality of data management services can process the operation, selecting the data management service to process the operation based upon the data management service satisfying a criterion for processing the operation.

4. The method of claim 3 , wherein a service map and provisioned resources are used to determine the service instance capacities.

5. The method of claim 3 , wherein the criterion corresponds to at least one of a quality of service level of the operation or a capacity of the data management service for processing the operation.

6. The method of claim 1 , wherein the operation specifies the service identifier of the data management service, and the method comprising:
comparing the service identifier to a list of service identifiers of guaranteed services to determine whether the data management service is a guaranteed service, wherein resources are provisioned for the data management service from reserved resources in accordance with service attributes based upon the data management service being the guaranteed service.

7. The method of claim 1 , wherein the operation specifies the service identifier of the data management service, and the method comprising:
comparing the service identifier to a list of service identifiers of guaranteed services to determine whether the data management service is a guaranteed service, wherein a request is submitted to a cluster scheduler for compute resources for the data management service based upon the data management service not being the guaranteed service.

8. The method of claim 1 , comprising:
in response to redirecting the operation to the data management service, updating information indicating a change in consumption corresponding to resources being provisioned for the data management service to process the operation.

9. The method of claim 1 , comprising:
in response to the data management service processing the operation to create a processed operation, routing the processed operation to the destination.

10. A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
identify a message type of an operation targeting a destination;
evaluate the message type against a set of message types that are not to be routed to data management services for processing before being routed to the destination;
in response to the to the message type occurring within the set of message types, route the operation to the destination and refraining from redirecting the operation to the data management services for processing;
evaluate service state information populated with service identifiers, service instance locations, service instance capacities for processing operations, and statuses periodically updated using timestamps from service instances; and
in response to the message type not occurring within the set of message types, redirect the operation to a service instance of a data management service identified by a service identifier as being instantiated at a service instance location and having a service instance capacity and status indicating that the service instance is capable of processing the operation, wherein service state information is used to track deployment of the data management service processing the operation.

11. The non-transitory machine readable medium of claim 10 , wherein the instructions cause the machine to:
refrain from redirecting operations to the data management services based upon a transition to a state that suspends service availability.

12. The non-transitory machine readable medium of claim 10 , wherein the instructions cause the machine to:
in response to determining that a plurality of data management services can process the operation, select the data management service to process the operation based upon the data management service satisfying a criterion for processing the operation.

13. The non-transitory machine readable medium of claim 12 , wherein the criterion corresponds to a capacity of the data management service for processing the operation.

14. The non-transitory machine readable medium of claim 12 , wherein the criterion corresponds to quality of service level of the operation.

15. The non-transitory machine readable medium of claim 10 , wherein the operation specifies the service identifier of the data management service, and wherein the instructions cause the machine to:
compare the service identifier to a list of service identifiers of guaranteed services to determine whether the data management service is a guaranteed service, wherein resources are provisioned for the data management service from reserved resources in accordance with service attributes based upon the data management service being the guaranteed service.

16. A computing device comprising:
a memory comprising machine executable code for performing a method; and
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
identify a message type of an operation targeting a destination;
evaluate the message type against a set of message types that are not to be routed to data management services for processing before being routed to the destination;
in response to the to the message type occurring within the set of message types, route the operation to the destination and refraining from redirecting the operation to the data management services for processing;
evaluate service state information populated with service identifiers, service instance locations, service instance capacities for processing operations, and statuses periodically updated using timestamps from service instances; and
in response to the message type not occurring within the set of message types, redirect the operation to a service instance of a data management service identified by a service identifier as being instantiated at a service instance location and having a service instance capacity and status indicating that the service instance is capable of processing the operation, wherein service state information is used to track deployment of t

Assignees

• Netapp Inc

Inventors

• Kenchammana-Hosekote Deepak Raghu
• Chaitanya Shiva
• Ghanbari Saeed
• Benight Barry Patrick
• Slik David Anthony

Classifications

• H04L67/63

  Routing a service request depending on the request content or context · CPC title

• G06F16/10

  File systems; File servers · CPC title

• G06F16/20

  of structured data, e.g. relational data · CPC title

• H04L67/1097

  for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] · CPC title

• H04L67/142 Primary

  Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms · CPC title