BlueSky_new(2013-10-22).pptxVIP

BlueSky: A Cloud-Backed File System for the Enterprise Michael Vrable Stefan Savage Geoffrey M. Voelker University of California, San Diego Computer Science and Engeneering Department (FAST 2012) Hongwei Li 2013-10-22 Background Many small/medium-sized organizations run a number of computing services, such as shared file systems. Often Brings significant cost: Purchasing and operating hardware and software Managing services Migrating file system to cloud storage is a better choice. Background Network file systems have potential benefits of their migration to cloud: High reliability Almost infinite capacity Dynamic scalability High availability Challenges Cloud storage (e.g., S3) brings new constraint: High latency Motivation The author puts forward a network file system named BlueSky which is backed by cloud storage to: Provide cloud storage services Reduce access latency Architecture Clients access local proxy by NFS/CIFS Local proxy acts as a role of cache between clients and cloud storage BlueSky encrypts part of data for confidentiality Cloud storage provides outsourcing services for local proxy File System Design BlueSky designs log-structured file system, it divides objects into 4 types: Data blocks Store file data,32KB Inodes Include basic metadata, such as ownership, timestamps,etc. Inode map Lists locations of the most recent version of each inode Checkpoint Determines the root of a file system snapshot File System Design Segment Multiple objects are aggregated into a segment with fixed size(4MB) Proxy log Manages data and metadata of the file system Cleaner Log For garbage collection of overwritten data Encryption Use AES for objects encryption, only part of data is encrypted Cleaner a) A file with 4 blocks, stored in two segments written by the proxy. b) The cleaner runs and relocates the data blocks. C) Concurrently, the proxy writes an update to the file, changing the contents of block 4 d) It accepts the relocated blocks