Private cloud API

• US 10,127,317 B2
• Filed: 09/18/2014
• Issued: 11/13/2018
• Est. Priority Date: 09/18/2014
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Ve{hacek over (c)}e{hacek over (r)}a, Martin, Pechanec, Jiri
• Primary Examiner(s): King, John B
• Application Number:
  US14/489,933
• Publication Number:
  US 20160085861A1
• Time in Patent Office: 1,517 Days
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 2209/5015 Service provider selection
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0629 Configuration or reconfiguration of storage systems
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/126 the source of the received data

Abstract

Methods, systems, and computer program for implementing a private cloud are provided. A computer-implemented method may include registering a private cloud in a central registry; retrieving private cloud registration data from the central registry; sharing the private cloud registration data with other users; and allowing other users to connect to the private cloud using the shared private cloud registration data.

Claims

1. A system, comprising:

a central registry server structured with a memory and a processor, the processor in communication with the memory to perform operations comprising;

receiving, from a first client computing device, at least one private cloud descriptor corresponding to a first private cloud, the at least one private cloud descriptor comprising a location and a public key;

testing an ability of the first private cloud to respond to a function of a central registry server, wherein the testing includes sending, by the central registry server to the first private cloud, a function call to access data on the first private cloud;

determining, based on the testing, that the first private cloud implements a function in the function call by comparing a response from the first private cloud to an expected response;

registering, responsive to the determining, the first private cloud on the central registry server using the received private cloud descriptor;

receiving, from a second client computing device associated with a second registered private cloud on the central registry server, a request for the at least one private cloud descriptor;

locating, by the central registry server, the at least one private cloud descriptor, and sending the at least one private cloud descriptor to the second client computing device;

receiving, from the second client computing device, an encrypted access request at the location provided by the at least one private cloud descriptor to access the registered first private cloud, wherein the encrypted access request is encrypted by the second client computing device using the at least one private cloud descriptor, and wherein the encrypted access request includes an encrypted identifier that is encrypted using a private key of a user;

determining, based on the encrypted access request, that the second client computing device is configured with access privileges to access the first private cloud; and

granting access to the second client computing device to access the first private cloud based on the determining that the second client computing device is configured with access privileges.

2. The system of claim 1, wherein the comparing comprises determining whether at least one data type in the response of the first private cloud matches an expected data type.

3. The system of claim 1, wherein the location is an Internet Protocol (IP) address.

4. The system of claim 1, wherein communications between the central registry server and the first private cloud and the second private cloud are protected with cryptography.

5. The system of claim 1, wherein communications between the central registry server and the first client computing device and the second client computing device are protected with cryptography.

6. The system of claim 1, wherein the function call is for an amount of files shared by the first private cloud, and wherein the expected response is a positive integer.

7. The system of claim 1, wherein the function call is for a name of a file stored on the first private cloud.

8. The system of claim 1, wherein the function call is for a location of a file stored on the first private cloud.

9. The system of claim 1, wherein receiving the public key includes generating the public key, and wherein receiving the location includes detecting a location corresponding to a computing device that is accessing the central registry server.

10. A method comprising:

receiving, on a machine that includes a memory and a processor, at least one private cloud descriptor from a first client computing device corresponding to a first private cloud, the at least one private cloud descriptor comprising a location and a public key;

testing an ability of the first private cloud to respond to a function of a central registry server, wherein the testing includes sending, by the central registry server to the first private cloud, a function call to access data on the first private cloud;

determining, based on the testing, that the first private cloud implements a function in the function call by comparing a response from the first private cloud to an expected response;

registering, responsive to the determining, the first private cloud on the central registry server using the received private cloud descriptor;

receiving, from a second client computing device associated with a second registered private cloud on the central registry server, a request for the at least one private cloud descriptor;

locating, by the central registry server, the at least one private cloud descriptor, and sending the at least one private cloud descriptor to the second client computing device;

receiving, from the second client computing device, an encrypted access request at the location provided by the at least one private cloud descriptor to access the registered first private cloud, wherein the encrypted access request is encrypted by the second client computing device using the at least one private cloud descriptor, and wherein the encrypted access request includes an encrypted identifier that is encrypted using a private key of a user;

determining, based on the encrypted access request, that the second client computing device is configured with access privileges to access the first private cloud; and

granting access to the second client computing device to access the first private cloud based on the determining that the second client computing device is configured with the access privileges.

11. The method of claim 10, wherein the comparing comprises determining whether at least one data type in the response of the first private cloud matches an expected data type.

12. The method of claim 10, wherein the location is an Internet Protocol (IP) address.

13. The method of claim 10, wherein the function call is for an amount of files shared by the first private cloud, and wherein the expected response is a positive integer.

14. The method of claim 10, wherein the function call is for a name of a file stored on the first private cloud.

15. The method of claim 10, wherein the function call is for a location of a file stored on the first private cloud.

16. A non-transitory computer-readable medium storing instructions executable to cause one or more processors to perform operations comprising:

receiving, from a first client computing device, at least one private cloud descriptor corresponding to a first private cloud, the at least one private cloud descriptor comprising a location and a public key;

testing an ability of the first private cloud to respond to a function of a central registry server, wherein the testing includes sending, by the central registry server to the first private cloud, a function call to access data on the first private cloud;

determining, based on the testing, that the first private cloud implements a function in the function call by comparing a response from the first private cloud to an expected response;

registering, responsive to the determining, the first private cloud on the central registry server using the received private cloud descriptor;

receiving, from a second client computing device associated with a second registered private cloud on the central registry server, a request for the at least one private cloud descriptor;

locating, by the central registry server, the at least one private cloud descriptor, and sending the at least one private cloud descriptor to the second client computing device;

receiving, from the second client computing device, an encrypted access request at the location provided by the at least one private cloud descriptor to access the registered first private cloud, wherein the encrypted access request is encrypted by the second client computing device using the at least one private cloud descriptor, and wherein the encrypted access request includes an encrypted identifier that is encrypted using a private key of a user;

determining, based on the encrypted access request, that the second client computing device is configured with access privileges to access the first private cloud; and

granting access to the second client computing device to access the first private cloud based on the determining that the second client computing device is configured with the access privileges.

17. The non-transitory computer-readable medium of claim 16, wherein the location is an Internet Protocol (IP) address.

18. The non-transitory computer-readable medium of claim 16, wherein the function call is for an amount of files shared by the first private cloud, and wherein the expected response is a positive integer.

19. The non-transitory computer-readable medium of claim 16, wherein the function call is for a name of a file stored on the first private cloud.

20. The non-transitory computer-readable medium of claim 16, wherein the function call is for a location of a file stored on the first private cloud.