diff options
author | Susant Palai <spalai@redhat.com> | 2017-11-26 11:49:48 +0530 |
---|---|---|
committer | Niels de Vos <ndevos@redhat.com> | 2018-01-18 08:50:30 +0000 |
commit | ee1c8b52721ce815bc98fd60a6b0e867848c8d79 (patch) | |
tree | d6c4bb262293292e399f5107d9dfa68099584f55 /design | |
parent | ee5fab234b0a9d317f7ec7cb7eb05c2d1172e94e (diff) |
cloudArchival: Added feature page and design document
Change-Id: Iff9025dc28ae1b12213b564903b03001251e8aff
Signed-off-by: Susant Palai <spalai@redhat.com>
Reviewed-on: https://review.gluster.org/18854
Reviewed-by: Ashish Pandey <aspandey@redhat.com>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
Tested-by: Amar Tumballi <amarts@redhat.com>
Reviewed-by: Niels de Vos <ndevos@redhat.com>
Diffstat (limited to 'design')
-rw-r--r-- | design/Cloud-Archival/CloudArchive.md | 60 |
1 files changed, 60 insertions, 0 deletions
diff --git a/design/Cloud-Archival/CloudArchive.md b/design/Cloud-Archival/CloudArchive.md new file mode 100644 index 0000000..9506429 --- /dev/null +++ b/design/Cloud-Archival/CloudArchive.md @@ -0,0 +1,60 @@ +# CloudArchival-Design.md + +This document gives a high level overview of CloudArchival. The design is being +refined as we go along, and this document will be updated along the way. + +## Introduction + +This design solves the usecase where data that requires high-speed access is +retained internally i.e. Glusterfs and lower-priority data is moved to a +low-cost cloud-based archive storage. This will allow reduction in storage cost +for usecases where a majority of data is cold and can be archived. + +## Architectural Overview + +CloudeArchival has two components. A scanner/uploader tool and a downloader +xlator in Glusterfs stack. + +### 1. Scanner/uploader + +This tool will scan the file system and based on a policy, will upload the data +to a predecided Cloud Storage. The policy can be user defined. A simple example +would be, upload any file that has not been accessed for one month. + +### 2. Downloader + +This xlator will download the file from Cloud-Storage when an access for +read/write (basically any data modification) request is made. This xlator will +be placed on the client side as AFR and EC xlators are client xlators. + +## Work Flow + + - Phase I - Post scanning, the uploader will filter out files to be archived + to Cloud. Once the data migration is complete to Cloud, the uploader will do +a setxattr operation on the file to inform the downloader xlator to truncate +the data. As part of this maintenance, downloader will store the size +information as an xattr on the file to serve lookup/stat etc and then will +truncate the data. + + +- Phase II - While the data resides on Cloud, all meta-data operation can be + performed locally on Glusterfs. The data will be downloaded only when a data +modification is requested. For read/write request, the downloader will stub the +request and start downloading the file from Cloud. Upon successful download, +the stubbed request will be resumed. + +## Cloud Information and Security + +Cloud information like which Cloud provider and it's access information can be +stored per volume basis through Glusterd. There can only one cloud storage be +attached to a volume. + +Since the communication channel to Cloud needs to be secured, the access +information for Cloud should and must reside on the trusted storage pool. +GF-proxy fits this requirement nicely as it runs on the trusted storage pool +(as for now). Hence, the downloader will be part of GF-proxy daemon on the +trusted storage pool. + +#### Note: Initial implementation will integrate with Amazon Web Service (AWS). +Integration with other Cloud Storage will be left open for development to the +community. |