System and method for exposing cloud stored data to a content delivery network

• US 9,489,395 B2
• Filed: 04/17/2015
• Issued: 11/08/2016
• Est. Priority Date: 10/16/2012
• Status: Active Grant

• Current Assignee: Rackspace US Incorporated (Apollo Global Management, Inc.)
• Original Assignee: Rackspace US Incorporated (Apollo Global Management, Inc.)
• Inventors: Goetz, David Patrick, Holt, Gregory Lee
• Primary Examiner(s): Ly, Anh
• Application Number:
  US14/690,040
• Publication Number:
  US 20150220561A1
• Time in Patent Office: 571 Days
• Field of Search: 707/827, 707/E17.032, 707/620, 707/628, 707/652, 707/610, 707/638, 707/694, 707/654, 707/624, 707/E17.01, 707/E17.002, 707/E17.007, 707/792, 707/E17.014, 707/692, 711/163, 711/166, 711/156, 711/162, 711/170, 711/E12.001, 711/E12.108, 713/193, 713/161, 713/168, 713/176, 713/400, 713/503, 726/1, 726/4, 726/16, 709/217, 709/220, 709/224, 709/226, 709/206, 709/203, 709/230, 709/231, 709/218, 709/219
• US Class Current: 1/1
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/18 File system types
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 3/0611 in relation to response time
• CPC Class Codes: G06F 3/0644 Management of space entities, e.g. partitions, extents, pools
• CPC Class Codes: G06F 3/067 Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

A system for exposing data stored in a cloud computing system to a content delivery network provider includes a database configured to receive and store metadata about the data, the database being implemented in the cloud computing system to store configuration metadata for the data related to the content delivery network, and an origin server configured to receive requests for the data from the content delivery network provider, and configured to provide the data to the content delivery network provider based on the metadata.

Claims

1. A method for receiving content delivery network metadata for data stored in a cloud computing system, the method comprising:

receiving a request from a user to expose data stored in the cloud computing system to a content delivery network;

parsing the request to retrieve one or more metadata attributes and associated values, including an identification of an account and a container on which content delivery network metadata is to be updated;

generating a hash value from the identification of the account and the container;

storing the retrieved metadata attributes and associated values in a metadata container, the metadata container stored in the cloud computing system; and

sending an acknowledgement to the requesting user.

2. The method of claim 1, wherein receiving the request from a user includes receiving a request formatted according to the Hypertext Transfer Protocol (HTTP).

3. The method of claim 1, wherein the metadata attributes include one or more attributes selected from the group consisting of:

an account, a container, a time-to-live, a flag indicating whether the data is content delivery network enabled, a purge frequency, a list of geographic regions in which the content delivery network provider caches the data, a list of geographic regions in which the content delivery network provider does not cache the data, a priority, and an identifier indicating the associated data.

4. The method of claim 3, wherein the flag indicating whether the data is content delivery network enabled is a Boolean flag.

5. The method of claim 1, wherein the request from the user is a PUT request.

6. The method of claim 1, wherein parsing the request includes parsing a header of the request.

7. The method of claim 1, the method further comprising generating a hash container path from the hash value.

8. The method of claim 7, the method further comprising performing a mathematical operation on the hash value to determine the associated hash container.

9. The method of claim 7, the method further comprising creating an empty metadata container in the hash container specified by the hash container path.

10. The method of claim 1, further comprising creating a new metadata container, and wherein the storing further includes storing the retrieved metadata attributes and associated values in the created metadata container.

11. The method of claim 1, wherein the request from the user further includes authentication information for the user.

12. A system comprising:

a storage area configured to store data, the storage area being implemented in a cloud computing system;

a database configured to receive and store metadata corresponding to the data, the database being implemented in the cloud computing system; and

an origin server configured to;

receive a request to expose data stored in the storage area, the request including a configuration attribute associated with the data,

create a metadata container in the storage area, the metadata container including the configuration attribute,

generate a hash value corresponding to the metadata container based on the configuration attribute,

store the metadata container in the storage area in a hash container associated with the hash value, and

expose the data associated with the configuration attribute to the content delivery network provider, wherein exposing the data is based at least on a determination which includes;

checking a boolean flag for indicating that the content is to be exposed, and

determining, based on an indirection block, whether the data is configured to be exposed to the content delivery network.

13. The system of claim 12, wherein the step of receiving the request includes receiving the request formatted according to the Hypertext Transfer Protocol (HTTP).

14. The system of claim 12, wherein receiving the request to expose data including the configuration attribute associated with the data includes receiving an attribute selected from the group consisting of:

an account, a container, a time-to-live, a flag indicating whether the data is content delivery network enabled, a purge frequency, a list of geographic regions in which the content delivery network provider should cache the data, a list of geographic regions in which the content delivery network provider should not cache the data, a priority, and an identifier indicating the associated data.

15. The system of claim 12, the origin server further configured to:

perform a mathematical operation on the hash value to determine the associated hash container.

16. The system of claim 12, wherein the step of exposing the data associated with the configuration attribute to the content delivery network provider includes returning a response to the content delivery network provider including the data and a configuration attribute.

17. The system of claim 12, wherein the step of generating the hash value includes generating the hash value using an algorithm selected from the group consisting of:

message digest 5 (MD5), secure hash algorithm 1 (SHA-1), and secure hash algorithm 2 (SHA-2).

18. A system comprising:

a storage area configured to store data, the storage area being implemented in a cloud computing system;

a database configured to receive and store metadata corresponding to the data, the database being implemented in the cloud computing system; and

an origin server configured to;

receive a request from a user to expose data stored in the cloud computing system to a content delivery network;

parse the request to retrieve one or more metadata attributes and associated values including an identification of an account and a container on which content delivery network metadata is to be updated;

generate a hash value from the identification of the account and the container;

store the retrieved metadata attributes and associated values in a metadata container, the metadata container stored in the cloud computing system; and

send an acknowledgement to the requesting user.