Native Clients, more the merrier with GFProxy!
0 likes272 views
The document discusses the current architecture and updates related to gfproxy, focusing on client-server protocols and challenges in client-driven distribution and replication. Key improvements and features implemented in gfproxy include daemon management, high availability protocols, and upcoming functionalities like volume multiplexing and integration with glusterd2. It highlights benefits for native clients across various operating systems, including enhanced performance and reduced resource consumption.
Native Clients, more the merrier with GFProxy!
- 1. Native Clients with GFProxy Poornima G Vijay Bellur
- 3. Cons of client driven distribution and replication ● Upgrade on all client machines is difficult ● In case of multiple clients on the same system, the resource consumption of client processes is duplicated. Eg: Samba, Containers native storage, Qemu etc. ● Bandwidth consumption on the client.
- 4. Hence GFProxy FUSE/gfapi Write-behind Protocol Client Protocol/Server DHT Protocol/Client AHA / Quiesce Protocol/Server Posix Performance xl AFR/EC Thin Client Gfproxyd Brick process
- 5. Current state of GFProxy ● Already done: ○ Glusterd changes - volfile generation, daemon management, port mapping. ○ AHA / Quiesce for High Availability. ○ Targeted for 3.13 as an experimental feature. ● To be done: ○ Dynamic graph switch ○ Volume multiplexing ○ Glusterd2 integration - volfile gen, daemon management, port mapping, gfproxy on subset of nodes etc. ○ Reduce the memory and thread consumption on thin clients. ○ Allow gfproxyd to be run on non-trusted storage pool nodes, for performance reasons. Issue #242 for details on each of these items
- 6. Native Clients with GFProxy ● GFProxy provides a thin client xlator stack ● Easy to have more native clients - for Mac, Windows and …! ● Fuse for Windows - https://github.com/billziss-gh/winfsp ● Fuse for Mac - https://osxfuse.github.io
- 7. Questions?