1.
Open Cloud Campus - Japan
Comparing GlusterFS-SwiftAPI
with Original Swift
Etsuji Nakai / Red Hat K.K.
Twitter @enakai00

2.
Architecture of Swift Account Servers
Maintain mappings
between
Account Servers / Container Servers store accounts and containers
metadata in separate databases.
Authentication Server
DB
Container Servers
Maintain lists and ACLs
of objects
Proxy Servers in each container.
DB
Object Servers
Store object contents
in file system.
Handling REST
request from clients
File System
Open Cloud Campus

3.
Architecture of GlusterFS with Swift API
- You can add “all in one” servers for scalability.
Authentication Server
- In Red Hat Storage 2.0, “all in one” servers are
directly configured on GlusterFS storage nodes.
GlusterFS manages scalability, redundancy
TempAuth is the only and consistency.
supported method now.
GlusterFS Cluster
Account/Container/Object Server
modules retrieve required information
directly from locally mounted volumes.
Proxy / Account / Container / Object
“all in one” server & GlusterFS client
GlusterFS
Volume
Volume for each account is locally mounted at: One volume is used
/mnt/gluster-object/AUTH_<account name> for one account
Open Cloud Campus

4.
How GlusterFS's Swift API works.
 It's just a modified versions of Swift components.
– All metadata is stored in GlusterFS using extended attributes instead of
dedicated metadata store.
– For example, Container Server component works as below.
Original Swift
Requesting a list of objects
in a specific container.
Proxy Server Container Server
Returning it by referring to
the metadata in a local database.
GlusterFS with Swift API
Requesting a list of objects
in a specific container.
Proxy Server Container Server
Returning it by searching a list of files in locally mounted directory:
/mnt/gluster-object/AUTH_<account name>/<container name>
Open Cloud Campus

5.
Open Cloud Campus - Japan
Thank you!
Etsuji Nakai / Red Hat K.K.
Twitter @enakai00