IP Library › Granted Patent US 10,785,029
Granted Patent B2
US 10,785,029 · App. 16/177,310 · Granted Sep 22, 2020

Systems and methods for pairing on-premise clusters to clouds using identity service providers

Inventors: Vinod Gupta (San Jose, CA); Abhijit Khinvasara (San Jose, CA); Ranjan Parthasarathy (San Jose, CA); Pritesh Lahoti (Bangalore, IN); Akanksha Deswal (Bangalore, IN); Vaishali Gupta (Bangalore, IN); Ramesh Chandra (San Jose, CA)
Assignee: NUTANIX, INC.
H04L9/3213G06F9/45558G06F9/5077H04L41/12H04L63/102H04L63/12H04L67/32G06F2009/45562H04L67/10
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,785,029
App. No.
16/177,310
Filed
Oct 31, 2018
Granted
Sep 22, 2020
Kind
B2
Art Unit
2438
USPC
726/4
Abstract

A method includes receiving, by a host server on a public cloud including one or more physical data centers associated with one or more logical zones, a pairing request by a client device associated with a private cloud, allocating, by the host server, access to resources on the one or more physical data centers to the client device, and pairing, by the host server, the private cloud to the public cloud based on receiving an identity provider token from an identity provider.

Claims (59)

1. A method comprising:

receiving, at a server on a public cloud comprising a first data center in the public cloud, a pairing request by a client device associated with a private cloud;

responsive to determining that a first logical zone is not mapped to the first data center, mapping the first data center to the first logical zone;

allocating access to resources on the first data center to the client device;

pairing the private cloud to the first logical zone of the public cloud based on receiving an identity token from an identity provider;

receiving a second pairing request from the client device to pair with a second data center in a second logical zone, wherein the first logical zone and the second logical zone are different; and

pairing the private cloud to the second logical zone without re-pairing the first logical zone to the private cloud.

2. The method of claim 1 , further comprising:

validating a signature of the identity token; and

generating an access token based on validating the signature of the identity token.

3. The method of claim 1 , further comprises mapping each of a plurality of data centers to, at most, one of the plurality of logical zones.

4. The method of claim 1 , further comprising forwarding a resource request to a first server associated with the one of the plurality of physical data centers.

5. The method of claim 1 , further comprises:

receiving a container request to create a container from a plurality of first resources of the public cloud; and

receiving a second request to copy an object from a plurality of second resources of the private cloud to the container, wherein the object is one of a user virtual machine, an image, a volume, a disk, a snapshot.

6. The method of claim 1 , wherein allocating the access to the resources on the first data center to the client device comprises allocating the access to the resources on the first data center of a plurality of physical data centers exclusively to the private cloud associated with the client device.

7. The method of claim 1 , wherein the identity token includes a plurality of identity tokens for each service offered by the public cloud.

8. The method of claim 1 , wherein the pairing request includes one of a request to login to the public cloud or a remote application programming interface (API) call to the public cloud.

9. A system comprising:

a private cloud comprising a client device;

an identity provider; and

a public cloud comprising a first data center in the public cloud, the first data center comprising a server having programmed instructions to:

receive a pairing request by the client device;

responsive to determining that a first logical zone is not mapped to the first data center, map the first data center to the first logical zone;

allocate access to resources on the first data center to the client device;

pair the private cloud to the first logical zone of the public cloud based on receiving an identity token from the identity provider;

receive a second pairing request from the client device to pair with a second data center in a second logical zone, wherein the first logical zone and the second logical zone are different; and

pair the private cloud to the second logical zone without re-pairing the first logical zone to the private cloud.

10. The system of claim 9 , wherein the server further includes programmed instructions to:

validate a signature of the identity token; and

generate an access token based on validating the signature of the identity token.

11. The system of claim 9 , wherein the server further includes programmed instructions to map the first data center to the first logical zone such that each of a plurality of data centers is mapped to, at most, one of a plurality of logical zones.

12. The system of claim 9 , wherein the server further includes programmed instructions to forward a resource request to a first server associated with the one of a plurality of data centers.

13. The system of claim 9 , wherein the server further includes programmed instructions to:

receive a container request to create a container from a plurality of first resources of the public cloud; and

receive a second request to copy an object from a plurality of second resources of the private cloud to the container, wherein the object is one of a user virtual machine, an image, a volume, a disk, a snapshot.

14. The system of claim 9 , wherein the server further includes programmed instructions to allocate the access to the resources on a first physical data center of a plurality of data centers exclusively to the private cloud associated with the client device.

15. The system of claim 9 , wherein the identity token includes a plurality of identity tokens for each service offered by the public cloud.

16. The system of claim 9 , wherein the pairing request includes one of a request to login to the public cloud or a remote application programming interface (API) call to the public cloud.

17. The method of claim 2 , further comprising:

generating, by the server, a data entry including the access token, an identifier of the public cloud, and a plurality of identifiers of a plurality of logical zones; and

sharing, by the server, contents of the data entry with the client device.

18. The system of claim 10 , further comprising:

generating a data entry including the access token, an identifier of the public cloud, and a plurality of identifiers of the plurality of logical zones; and

sharing contents of the data entry with the client device.

19. A non-transitory computer-readable media comprising computer-executable instructions embodied thereon that, when executed by a processor, cause the processor to perform a process comprising:

receiving, at a server on a public cloud comprising a first data center in the public cloud, a pairing request by a client device associated with a private cloud;

responsive to determining that a first logical zone is not mapped to the first data center, mapping the first data center to the first logical zone;

allocating access to resources on the first data center to the client device;

pairing the private cloud to the first logical zone of the public cloud based on receiving an identity token from an identity provider;

receiving a second pairing request from the client device to pair with a second data center in a second logical zone, wherein the first logical zone and the second logical zone are different; and

pairing the private cloud to the second logical zone without re-pairing the first logical zone to the private cloud.

20. The non-transitory computer-readable media of claim 19 , wherein the pairing operation includes disaster recovery from the public cloud to the private cloud.

21. The non-transitory computer-readable media of claim 19 , wherein the process further comprises:

forwarding, by the server, a resource request to a first server associated with the one of the plurality of data centers.

22. The non-transitory computer-readable media of claim 19 , further comprises:

receiving a first request to create a container from a plurality of first resources of the public cloud; and

receiving a second request to copy an object from a plurality of second resources of the private cloud to the container, wherein the object is one of a user virtual machine, an image, a volume, a disk, a snapshot.

23. The method of claim 1 , wherein the pairing operation includes disaster recovery from the public cloud to the private cloud.

Assignments (2)
SECURITY INTEREST Recorded Feb 13, 2025
From: NUTANIX, INC.
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 070206/0463 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 10, 2020
From: GUPTA, VINOD; KHINVASARA, ABHIJIT; PARTHASARATHY, RANJAN; LAHOTI, PRITESH; DESWAL, AKANKSHA; GUPTA, VAISHALI; CHANDRA, RAMESH
To: NUTANIX, INC.
Reel/Frame 053450/0343 →
Continuity (1)
Related Publication 20200136825A1 · Apr 30, 2020
Cited By (8)
US 12,306,819 US 12,477,034 US 12,481,638 US 12,613,857 US 12,657,097 US 12,693,999 US 12,699,685 US 12,730,914