Unified file and object data storage

• US 9,971,787 B2
• Filed: 07/23/2012
• Issued: 05/15/2018
• Est. Priority Date: 07/23/2012
• Status: Active Grant

• Current Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Original Assignee: Red Hat, Inc. (International Business Machines Corporation)
• Inventors: Avati, Anand Vishweswaran, Ahmed, Mohammed Junaid
• Primary Examiner(s): Brooks, David T
• Application Number:
  US13/555,718
• Publication Number:
  US 20140025711A1
• Time in Patent Office: 2,122 Days
• Field of Search: None
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 16/196 Specific adaptations of the file system to access devices and non-file objects via standard file system access operations, e.g. pseudo file systems dedicated interfaces to storage systems G06F3/0601
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking

Abstract

A server computing device receives, from a client computing device, a hypertext transfer protocol (HTTP) request to perform an operation on an object. The server computing device identifies a file, that corresponds to the object, in a network attached storage file system in a local area network. The server computing device mounts, via the local area network, the network attached storage file system to perform the operation using the file that corresponds to the object. The computer device sends a HTTP response indicating performance of the operation to the client computing device.

Claims

1. A method comprising:

receiving, from a client computing device by a processing device via a wide area network, a request to perform an operation on an object in a first storage system;

determining a hash value associated with an identifier of the object from the request;

identifying an object server of a plurality of object servers of the first storage system to forward the request to perform the operation on the object by using a hash value associated with the identifier of the object;

receiving mapping data that associates an account identifier from the request to perform the operation on the object in the first storage system to a volume of a file system of a second storage system;

identifying, by the processing device, a file in the second storage system that corresponds to the object at the object server in the first storage system in view of the identifier of the object and the volume that is associated with the account identifier from the mapping data; and

mounting, by the processing device via a local area network and in response to receiving the request via the wide area network from the client computing device, the second storage system to perform the operation using the file in the second storage system that corresponds to the object in the first storage system, wherein the second storage system is mounted by using the account identifier from the mapping data, and wherein the account identifier is received via the wide area network.

2. The method of claim 1, further comprising:

receiving a file system request, from the client computing device using a mount-point via a local area network, to modify the file, wherein the modified file is accessible as an object using hypertext transfer protocol (HTTP).

3. The method of claim 1, further comprising:

sending a file in the second storage system to the client computing device in a hypertext transfer protocol (HTTP) response in response to the request.

4. The method of claim 1, further comprising:

creating the file and one or more directories for the file in the second storage system via a mount-point, wherein the file and the one or more directories are accessible to a second client computing device as an object and a container using hypertext transfer protocol (HTTP).

5. The method of claim 1, wherein identifying the file in the second storage system that corresponds to the object in the first storage system comprises:

identifying a top-level directory, in the second storage system, that corresponds to a container identifier in the request;

identifying at least one of a file name or one or more sub-directories, in the second storage system, that correspond to an object identifier in the request; and

identifying a file path for the file using the top-level directory and at least one of the one or more sub-directories or the file name.

6. The method of claim 1, wherein mounting the second storage system comprises:

specifying the volume, in the second storage system, that corresponds to the account identifier in the request; and

specifying a file path for the file, the file path comprising a top-level directory that corresponds to a container identifier in the request, and at least one of one or more sub-directories or a file name that correspond to an object identifier in the request.

7. The method of claim 1, wherein receiving the request comprises:

correlating a plurality of object server computing devices in a local area network to one of the plurality of object server computing devices to create a non-distributed object storage system; and

receiving, by a proxy server computing device, the request from a client computing device, wherein the proxy server computing device sends the request to the one of the plurality of object server computing devices in the non-distributed object storage system.

8. The method of claim 7, wherein correlating the plurality of object server computing devices comprises:

mapping a plurality of object identifiers to the one of the plurality of object server computing devices.

9. A non-transitory computer-readable medium having instructions that, when executed by a processing device, cause the processing device to:

receive, by the processing device from a client computing device over a wide area network, a request associated with a file system command to perform an operation on an object in a first storage system;

determine a hash value associated with an identifier of the object from the file system command;

identify an object server of a plurality of object servers of the first storage system to forward the request to perform the operation on the object by using a hash value associated with the identifier of the object

receive mapping data that associates an account identifier from the request to perform the operation on the object in the first storage system to a volume of a file system of a second storage system;

identify, by the processing device, a file in the second storage system that corresponds to the object at the object server in the first storage system in view of the identifier of the object and the volume that is associated with the account identifier from the mapping data; and

access the second storage system by using the account identifier from the mapping data to perform the operation using the file in the second storage system that corresponds to the object in the first storage system.

10. The non-transitory computer-readable medium of claim 9, the instructions further causing the processing device to:

send, via the wide area network, a file system response to the client computing device, the file system response comprising the file in the second storage system.

11. The non-transitory computer-readable medium of claim 9, the instructions further causing the processing device to:

create the file and a container in the second storage system, wherein the file and the container are accessible to a second client computing device in the local area network as the object and a directory from the mount-point.

12. The non-transitory computer-readable medium of claim 11, wherein the second client computing device modifies the file using the object and the mount-point over the local area network and the modification is accessible in the file using hypertext transfer protocol (HTTP).

13. The non-transitory computer-readable medium of claim 9, wherein to identify the file in the second storage system that corresponds to the object in the first storage system, the processing device is to:

identify a container identifier, in the second storage system, that corresponds to a top-level directory in the file system command; and

identify an object identifier, in the second storage system, that corresponds to at least one of a file name or one or more sub-directories in the file system command.

14. The non-transitory computer-readable medium of claim 9, wherein to access the second storage system, the processing device is to:

specify the account identifier, in the second storage system, that corresponds to volume label of the volume in the file system command;

specify a container identifier in the second storage system that correspond to a top-level directory in the file system command; and

specify an object identifier that corresponds to at least one of one or more sub-directories or a file name in the file system command.

15. A system comprising:

a memory; and

a processing device, operatively coupled with the memory, to;

create an object in a first storage system to store data in the first storage system;

create correlation data that identifies an object server of a plurality of object servers of the first storage system to forward a request to perform an operation on the object by using a hash value associated with an identifier of the object;

create mapping data that associates an account identifier from the request to perform the operation on the object in the first storage system to a volume of a file system of a second storage system;

create distribution data that identifies the second storage system that stores a file corresponding to the object in view of the identifier of the object and the volume that is associated with the account identifier from the mapping data;

expose, to a client computing device via a wide area network, the file in the second storage system that corresponds to the object in the first storage system from a mount-point in the second storage system, wherein the mount point is selected by using the account identifier from the mapping data received over the wide area network and the distribution data.

16. The system of claim 15, wherein a second processing device modifies the object using the file in the second storage system that corresponds to the object in the first storage system from the mount-point in the second storage system.

17. The system of claim 16, wherein the modification is visible by accessing the first storage system using hypertext transfer protocol.

18. The system of claim 15, wherein the processing device is further to:

create a second file and a top-level directory via the mount-point in the second storage system to store second data in the second storage system;

expose the second file as a second object in the first storage system using hypertext transfer protocol (HTTP); and

expose the top-level directory as a container in the first storage system using HTTP.

19. The system of claim 18, wherein a second processing device modifies the second file using the second object from the first storage system using HTTP.

20. The system of claim 19, wherein the modification is visible from the mount-point in the second storage system.