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

Patent metadata

Field	Value
Publication number	US-11232160-B2
Application number	US-201916375942-A
Country	US
Kind code	B2
Filing date	Apr 5, 2019
Priority date	Jul 31, 2015
Publication date	Jan 25, 2022
Grant date	Jan 25, 2022

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:
evaluating a service policy to determine that a set of data management services are to process storage operations within a service request, wherein a service redirector identifies a counterpart service that is to reverse a transformation of a service execution result output by a first data management service of the set of data management services;
utilizing the service policy to construct a service sequence defining an order with which each data management service of the set of data management services is to sequentially process the service request, wherein the service sequence specifies that the first data management service is to process a first storage operation of the service request to create the service execution result whose transformation by the first data management service will be reserved by the counterpart service; and
sequentially processing the storage operations of the service request using the set of data management services according to the service sequence, wherein an ingest service attaches a service identifier of the counterpart service to the service execution result, and wherein the counterpart service is deployed, for processing the service execution result based upon the service identifier, when the first data management service is deployed.

2. The method of claim 1 , comprising:
maintaining state information to track service execution results by the data management services across the service sequence.

3. The method of claim 2 , wherein a data management service can use the state information to access service execution results of a prior executed data management service.

4. The method of claim 2 , comprising:
utilizing the state information to route the service execution results to internal destinations within a data management services architecture hosting the set of data management services.

5. The method of claim 4 , wherein the service execution results are routed before a final data management service is executed to process the service request.

6. The method of claim 1 , comprising:
utilizing the service redirector to track progress of the data management services processing the service request.

7. The method of claim 6 , wherein the service redirector generates a new service request to include the service execution result from the first data management service, wherein the new service request is transmitted by the service redirector to a second data management service specified by the service sequence to process the service request after the first data management service.

8. The method of claim 1 , comprising:
removing the service identifier from the service execution result before routing the service execution result to the counterpart service.

9. The method of claim 1 , comprising:
removing the service identifier from an output resulting from the counterpart service processing the service execution result.

10. The method of claim 1 , comprising:
redirecting, by the service redirector, the service execution result to the counterpart service based upon the service execution result being tagged with the service identifier.

11. The method of claim 1 , wherein multiple instances of the service request are processed by data management services specified by a set of service sequences.

12. The method of claim 11 , comprising:
evaluating service execution results generated from execution of the data management services according to the set of service sequences to select a target service sequence from the set of service sequences for subsequently processing instances of the service request.

13. The method of claim 1 , wherein a data management service comprises a deduplication service, and wherein service execution results of the deduplication service are evaluated to identify a storage efficiency of deduplication.

14. The method of claim 1 , wherein a data management service comprises a compression service, and wherein service execution results of the compression service are evaluated to identify a storage efficiency of compression.

15. The method of claim 1 , wherein a service redirector routes data relating to the processing of the service request between the data management services.

16. A non-transitory machine readable medium comprising instructions for performing a method, which when executed by a machine, causes the machine to:
evaluate a service policy to determine that a set of data management services are to process storage operations within a service request, wherein a service redirector identifies a counterpart service that is to reverse a transformation of a service execution result output by a first data management service of the set of data management services
utilize the service policy to construct a service sequence defining an order with which each data management service of the set of data management services is to sequentially process the service request, wherein the service sequence specifies that the first data management service is to process a first storage operation of the service request to create the service execution result whose transformation by the first data management service will be reserved by the counterpart service; and
sequentially process the storage operations of the service request using the set of data management services according to the service sequence, wherein an ingest service attaches a service identifier of the counterpart service to the service execution result, and wherein the counterpart service is deployed, for processing the service execution result based upon the service identifier, when the first data management service is deployed.

17. The non-transitory machine readable medium of claim 16 , wherein the instructions cause the machine to:
maintain state information to track service execution results by the data management services across the service sequence.

18. The non-transitory machine readable medium of claim 17 , wherein a data management service can use the state information to access service execution results of a prior executed data management service.

19. The non-transitory machine readable medium of claim 18 , wherein the instructions cause the machine to:
utilize the state information to route the service execution results to internal destinations within a data management services architecture hosting the set of data management services.

20. 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:
evaluate a service policy to determine that a set of data management services are to process storage operations within a service request, wherein a service redirector identifies a counterpart service that is to reverse a transformation of a service execution result output by a first data management service of the set of data management services
utilize the service policy to construct a service sequence defining an order with which each data management service of the set of data management services is to sequentially process the service request, wherein the service sequence specifies that the first data management service is to process a first storage operation of the service request to create the service execution result whose transformation by the first data management service will be reserved by the counterpart service; and

sequentially process the storage operations of the service request using 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

• 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

• G06F16/20

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

• H04L67/142 Primary

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

• G06F16/93 Primary

  Document management systems · CPC title