Pluggable data resource management controller

Patent metadata

Field	Value
Publication number	US-11729111-B2
Application number	US-202017119600-A
Country	US
Kind code	B2
Filing date	Dec 11, 2020
Priority date	Dec 11, 2020
Publication date	Aug 15, 2023
Grant date	Aug 15, 2023

Abstract

Systems, methods, and machine-readable media for defining data formats, reflecting system states of managed systems, and managing aspects of those systems via a logically centralized proxy are disclosed. Resources may be represented within a resource provider definition, a package of data format and interaction methods used to instantiate a resource provider, which is a running instance of an executable from the resource provider definition. Users may submit new resource provider definitions, view a list of definitions, and delete definitions. A resource provider service may access the resource provider definition and instantiate a resource provider. The resource provider instance instantiated from the resource provider definition exposes an API, via the resource provider service, to manage data items defined for the resource(s) in the resource provider definition. When the resource is changed, information tracking the state may be updated to reflect the new state of the managed resource.

First claim

What is claimed is:

1. A method comprising:
instantiating, by a resource provider service, a resource provider instance that is based on a resource provider definition maintained by the resource provider service, the resource provider instance controlling access to an associated physical resource, and the resource provider definition comprising a data format, a resource provider application programming interface (API), and reference to an executable container for the resource provider instance;
exposing, by the resource provider service, the API for the resource provider instance for access from a client according to the resource provider definition;
proxying, by the resource provider service, a command from the client to the resource provider service for the resource provider instance, the command configured according to the resource provider API to manage the associated physical resource; and
updating, by the resource provider service, a state of the associated physical resource within an object model service associated with the resource provider service based on the command.

2. The method of claim 1 , further comprising:
accepting, prior to the instantiating, the resource provider definition in the object model service upon receipt of the resource provider definition.

3. The method of claim 1 , wherein the resource provider definition is formatted according to a common schema.

4. The method of claim 1 , further comprising:
exposing, by the resource provider service, a resource provider service API with one or more functions that facilitate at least one of the instantiating of the resource provider instance, accepting a new resource provider definition, making an accepted resource provider definition available, or managing what resource provider definition is running.

5. The method of claim 1 , further comprising:
receiving, by the resource provider service prior to the instantiating, an instruction to instantiate the resource provider instance, the instruction including an identification of the resource provider definition and a configuration parameter.

6. The method of claim 1 , wherein the resource provider service is configured to operate within a namespace for a tenant from among a plurality of namespaces, each comprising a respective instance of the resource provider service.

7. The method of claim 1 , further comprising:
deleting, by the resource provider service, the resource provider definition in response to a command according to a resource provide service API exposed by the resource provider service.

8. A computing device comprising:
a memory containing machine readable medium comprising machine executable code having stored thereon instructions for performing a method of providing proxied access to an associated physical resource in a container system by a resource provider service;
a processor coupled to the memory, the processor configured to execute the machine executable code to cause the processor to:
present, via a first resource provider service application programming interface (API) of the resource provider, a list of resource provider definitions to a client;
instantiate, via a second resource provider service API, a resource provider instance that is based on a resource provider definition selected from the list of resource provider definitions, the resource provider instance controlling access to the associated physical resource, the resource provider definition comprising s data format, a resource provider application programming interface (API), and reference to an executable container for the associated physical resource for the resource provider instance; and
proxy a command from the client to the resource provider service for the resource provider instance, the command configured according to a resource provider API for the resource provider instance exposed by the resource provider service to manage the associated physical resource.

9. The computing device of claim 8 , wherein the processor is further configured to:
update a state of the associated physical resource within an object model service associated with the resource provider service.

10. The computing device of claim 8 , wherein the processor is further configured to:
store, prior to presenting the list, the resource provider definition in an object model service via a third resource provider service API.

11. The computing device of claim 8 , wherein the resource provider definition is formatted according to a common schema.

12. The computing device of claim 8 , wherein the resource provider service is configured to operate within a namespace from among a plurality of namespaces, each comprising a respective instance of the resource provider service.

13. The computing device of claim 8 , wherein the processor is further configured to:
delete, via a fourth resource provider service API exposed by the resource provider service, the resource provider definition from the list of resource provider definitions in response to a command configured according to the fourth resource provider service API.

14. The computing device of claim 8 , wherein the processor is further configured to:
update metadata of the associated physical resource within an object model service associated with the resource provider service in response to an action by a second resource provider instance that is also based on the selected resource provider definition.

15. A non-transitory machine readable medium having stored thereon instructions for performing a method of providing proxied access to an associated physical resource by a resource provider service, comprising machine executable code which when executed by at least one machine, causes the machine to:
expose a resource provider application programming interface (API) for a resource provider instance for access from a client, the resource provider instance being based on a resource provider definition maintained by the resource provider service and controlling access to the associated physical resource, the resource provider definition comprising a data format, the resource provider API, and reference to an executable container for the resource provider instance;
proxy a command from the client to the resource provider service for the resource provider instance, the command configured according to the resource provider API to manage the associated physical resource; and
update a state of the associated physical resource within an object model service associated with the resource provider service based on the command.

16. The non-transitory machine readable medium of claim 15 , further comprising machine executable code that causes the machine to:
store, prior to exposing the resource provider API, the resource provider definition in the object model service upon receipt of the resource provider definition.

17. The non-transitory machine readable medium of claim 15 , further comprising machine executable code that causes the machine to:
create, prior to exposing the resource provider API, the resource provider instance based on the resource provider definition in response to the client selecting the resource provider definition from a list of resource provider definitions presented to the client.

18. The non-transitory machine readable medium of claim 15 , wherein the resource provider definition is formatted according to a common schema.

19. The non-transitory machine readable medium of claim 15 , wherein the resource provider service is configured to operate within a namespace from among a pl

Assignees

• Netapp Inc

Inventors

• Klosterman Andrew Joseph
• Nesbitt Richard
• Mueller Garrett
• Hrafnsson Eirikur Sveinn

Classifications

• H04L47/781 Primary

  Centralised allocation of resources · CPC title

• H04L47/762

  triggered by the network · CPC title

• H04L47/808

  User-type aware · CPC title

• H04L67/563

  Data redirection of data network streams · CPC title