These are the slides from a webinar I did today (Jan 26, 2012). It's all about where the GlusterFS project stands today and where it's going.

1. The Future of GlusterFS and Gluster.org John Mark Walker GlusterFS Community Guy Red Hat, Inc. January 25, 2012

3. Decided to write their own

4. No filesystem experts – Pro & Con

7. Not scalable, or…

8. Single purpose, or…

9. Don’t support legacy apps, or…

10. Don't support new apps, or...

11. Do some combo of the above, but not very well

13. Seamlessly integrated in the data center

15. POSIX-compliant

16. Stackable

17. User-space

19. No Centralized Metadata Client A Client B Client C Server X Files Extended Attr. Server Y Files Extended Attr. Server Z Files Extended Attr.

21. Reorder layers

22. Move layers between client and server

25. Global namespace

26. High availability

27. Geo-replication

28. Rebalancing

29. Remove or replace bricks

30. Self healing

31. volume profile and top metrics

32. No one ever expects the Red Hat acquisition

34. Cloud and virtualization are driving scale-out storage growth

35. Scale-out storage shipments to exceed 63,000 PB by 2015 (74% CAGR)

36. 40% of core cloud spend related to storage

37. GlusterFS-based solutions up to 50% less than other storage systems

45. The Immediate Future

49. Want to be more inclusive, more community-driven Goal: create global ecosystem that supports ISVs, service providers and more

54. No innovation outside of core engineering team

55. All open source features also in commercial product

56. Many features in Commercial product not in open source code Commercial Product Open Source Code

58. Engineering team from multiple sources

59. Project and product do not completely overlap

60. Commercial products are hardened, more secure and thoroughly tested Open Source Code Commercial Products

62. Engineering team from multiple sources

63. Open source project is “upstream” from commercial product

64. “ Downstream” products are hardened, more secure and thoroughly tested Fedora Linux RHEL

66. Engineering team from multiple sources

67. Open source project is “upstream” from commercial product

68. “ Downstream” products are hardened, more secure and thoroughly tested GlusterFS Red Hat Storage

69. Project Roadmaps

73. Granular locking – Much faster self-healing for large files

74. Proactive self-heal process starts without FS stat

75. Round-trip reduction for lower latency

76. Quorum enforcement - avoid split brain scenarios

78. New storage methodologies implement RESTful APIs over HTTP

79. Demand for unifying the storage infrastructure increasing

80. Treats files as objects and volumes as buckets

81. Available now in 3.3 betas

82. Soon to be backported to 3.2.x

85. HA and DR for VM’s

86. Faster VM deployment

88. CloudStack

89. OpenStack Goal: The standard for cloud storage OpenStack Imaging Services Unified File & Object Storage … Compute API Layer Mobile Apps. Web Clients. Enterprise Software Ecosystem

92. Provide users with file level access to data

95. HekaFS.org

96. ETA ~9 months

97. What else?

99. Jeff Darcy, Filesystem Engineer, Red Hat; Founder, HekaFS Project

100. AB Periasamy, Co-Founder, GlusterFS project

101. Ewan Mellor, Xen Engineer, Citrix; Member, OpenStack project

102. David Nalley, CloudStack Community Mgr; Fedora Advisory Board

103. Louis Zuckerman, Sr. System Administrator, Picture Marketing

104. Joe Julian, Sr. System Administrator, Ed Wyse Beauty Products

105. Greg DeKoenigsberg, Community VP, Eucalyptus; co-founder, Fedora

106. John Mark Walker, Gluster.org Community Guy (Chair)

108. Collaborative project hosting

111. HDFS compatibility

113. http://download.gluster.org/pub/gluster/glusterfs

117. @RedHatStorage & @GlusterOrg

119. Twitter & identi.ca: @johnmark