UNIFIED FILE AND OBJECT DATA STORAGE

• US 20140025713A1
• Filed: 11/27/2012
• Published: 01/23/2014
• 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
• Granted Patent: US 9,971,788 B2
• Time in Patent Office: Days
• US Class Current: 707/827
• 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 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 response indicating performance of the operation to the client computing device.

Claims

1. A method comprising:

receiving, from a client computing device, a request to perform an operation on an object in a first storage system, wherein the first storage system comprises an object storage system;

identifying, by a processing device, a file in a second storage system that corresponds to the object in the first storage system, wherein the second storage system comprises a network attached storage file system in the local area network;

mounting, by the processing device via a mount-point and the local area network, the network attached storage file system to perform the operation using the file in the second storage system that corresponds to the object in the first storage system; and

sending, to the client device, a response indicating performance of the operation.

2. The method of claim 1, further comprising:

receiving a file system request, from the client computing device using the mount-point via the local area network, to modify the file; and

modifying the file, wherein the modified file is accessible as an object using hypertext transfer protocol (HTTP).

3. The method of claim 1, wherein the operation is to retrieve the object, and sending the response comprises:

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

4. The method of claim 1, wherein the operation is to create the object, and mounting the network attached storage file system to perform the operation using the file comprises:

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

5. The method of claim 1, wherein identifying the file that corresponds to the object comprises:

identifying a volume, in the network attached storage file system, that corresponds to an account identifier in the request;

identifying a top-level directory, in the network attached storage file 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 network attached storage file 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 network attached storage file system comprises:

specifying a volume, in the network attached storage file system, that corresponds to an 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 the 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 storage medium including instructions that, when executed by a processing device, cause the processing device to perform operations comprising:

receiving, from a client computing device using a mount-point over a local area network, a file system command to perform an operation on a file in a first storage system, wherein the first storage system comprises a network attached storage file system in the local area network;

identifying, by the processing device, an object in the second storage system that corresponds to the file in the first storage system, wherein the second storage system comprises an object storage system;

accessing the object storage system to perform the operation using the object in the first storage system that corresponds to the file in the first storage system; and

sending, to the client computer device over the local area network, a file system response indicating performance of the operation.

10. The non-transitory computer-readable storage medium of claim 9, wherein the operation is to retrieve the file, and sending the file system response comprises:

sending the object in the object storage system to the client computing device in the file system response.

11. The non-transitory computer-readable storage medium of claim 9, wherein the operation is to create the file, and accessing the object storage system to perform the operation using the object comprises:

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

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

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

identifying an account identifier, in the object storage system, that corresponds to a volume label in the file system command;

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

identifying an object identifier, in the object 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 storage medium of claim 9, wherein accessing the object storage system comprises:

specifying an account identifier, in the object storage system, that corresponds to a volume label in the file system command; and

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

specifying 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 coupled to the memory to;

create a container and an object in a first storage system to store data in the first storage system, wherein the first storage system comprises an object storage system;

expose a file in a second storage system that corresponds to the object in the first storage system from a mount-point, wherein the second storage system comprises a network attached storage file system in a local area network; and

expose a top-level directory that corresponds to the container from the mount-point in the network attached storage file system.

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 network attached storage file system.

17. The system of claim 16, wherein the modification is visible by accessing the object 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 second top-level directory via the mount-point in the network attached file system to store second data in the network attached file system;

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

expose the second top-level directory as a second container in the object 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 object storage system using HTTP.

20. The system of claim 19, wherein the modification is visible from the mount-point in the network attached file system.