Granted Patent B2

US 12,388,826 · App. 18/544,399 · Granted Aug 12, 2025

Inventors: Naveen Reddy Gundlagutta (Bangalore, IN); Satyendra Singh Naruka (Pune, IN); Sirvisetti Venkat Sri Sai Ram (Kakinada, IN)

Assignee: Nutanix, Inc.

H04L63/10G06F16/9566

Abstract

Claims (35)

1. A system comprising:

one or more memories having computer-readable instructions stored thereon; and

one or more processors of an objects browser that executes the computer-readable instructions to:

receive a request through the objects browser of a first object store to perform an operation on either the first object store or a second object store, wherein the request comprises a uniform resource locator (URL), wherein the first object store and the second object store are part of a federated namespace comprising a plurality of object stores;

determine that the URL comprises a name of the federated namespace;

make an application programming interface (API) request comprising a header including the name of the federated namespace to an objects server to access the first object store or the second object store;

determine, by the objects server, whether the API request is to access the first object store or the second object store; and

provide access, by the objects server, to the first object store responsive to determining that the API request is to perform the operation on the first object store or route the API request to the second object store to perform the operation on the second object store responsive to determining that the API request is to perform the operation on the second object store.

2. The system of claim 1 , wherein the URL comprises a fully qualified domain name of the first object store or the second object store to be accessed and a name of the federated namespace.

3. The system of claim 1 , wherein the one or more processors further execute computer-readable instructions to determine, by the objects server, that the API request is to access the second object store responsive to identifying the name of the federated namespace in the header.

4. The system of claim 1 , wherein the one or more processors further execute computer-readable instructions to determine, by the objects server, that the API request is to access the first object store based on the API request not including a name of the federated namespace in the API request.

5. The system of claim 1 , wherein the one or more processors further execute computer-readable instructions to authenticate a user before making the API request.

6. The system of claim 1 , wherein the objects server comprises an objects server for a local member associated with the first object store, and wherein to route the API request to the second object store, the objects server for the local member sends the API request to an objects server for a remote member associated with the second object store.

7. A non-transitory computer-readable media comprising computer-readable instructions stored thereon that when executed by one or more processors of an object browser cause the one or more processors to:

receive a request through the objects browser of a first object store to perform an operation on either the first object store or a second object store, wherein the request comprises a uniform resource locator (URL), wherein the first object store and the second object store are part of a federated namespace comprising a plurality of object stores;

determine that the URL comprises a name of the federated namespace;

make an application programming interface (API) request comprising a header including the name of the federated namespace to an objects server to access the first object store or the second object store;

determine, by the objects server, whether the API request is to access the first object store or the second object store; and

provide access, by the objects server, to the first object store responsive to determining that the API request is to perform the operation on the first object store or route the API request to the second object store to perform the operation on the second object store responsive to determining that the API request is to perform the operation on the second object store.

8. The non-transitory computer-readable media of claim 7 , wherein the URL comprises a fully qualified domain name of the first object store or the second object store to be accessed and a name of the federated namespace.

9. The non-transitory computer-readable media of claim 7 , wherein the one or more processors further execute computer-readable instructions to determine, by the objects server, that the API request is to access the second object store responsive to identifying the name of the federated namespace in the header.

10. The non-transitory computer-readable media of claim 7 , wherein the one or more processors further execute computer-readable instructions to determine, by the objects server, that the API request is to access the first object store based on the API request not including a name of the federated namespace in the API request.

11. The non-transitory computer-readable media of claim 7 , wherein the one or more processors further execute computer-readable instructions to authenticate a user before making the API request.

12. The non-transitory computer-readable media of claim 7 , wherein the objects server comprises an objects server for a local member associated with the first object store, and wherein to route the API request to the second object store, the objects server for the local member sends the API request to an objects server for a remote member associated with the second object store.

13. A method comprising:

receiving, by one or more processors of an objects browser, a request through the objects browser of a first object store for performing an operation on either the first object store or a second object store, wherein the request comprises a uniform resource locator (URL), wherein the first object store and the second object store are part of a federated namespace comprising a plurality of object stores;

determining, by the one or more processors, that the URL comprises a name of the federated namespace;

making, by the one or more processors, an application programming interface (API) request comprising a header including the name of the federated namespace to an objects server to access the first object store or the second object store;

determining, by the objects server, whether the API request is to access the first object store or the second object store; and

providing access, by the objects server, to the first object store responsive to determining that the API request is to perform the operation on the first object store or route the API request to the second object store to perform the operation on the second object store responsive to determining that the API request is to perform the operation on the second object store.

14. The method of claim 13 , wherein the URL comprises a fully qualified domain name of the first object store or the second object store to be accessed and a name of the federated namespace.

15. The method of claim 13 , further comprising determining, by the objects server, that the API request is to access the second object store responsive to identifying the name of the federated namespace in the header.

16. The method of claim 13 , further comprising determining, by the objects server, that the API request is to access the first object store based on the API request not including a name of the federated namespace in the API request.

17. The method of claim 13 , further comprising authenticate a user before making the API request.

18. The method of claim 13 , wherein the objects server comprises an objects server for a local member associated with the first object store, and wherein routing the API request to the second object store comprises sensing, by the objects server for the local member, the API request to an objects server for a remote member associated with the second object store.

Assignments (2)

Priority Claims (1)

Continuity (1)

References Cited (42)