Red Hat Storage for Mere Mortals

115
RED HAT STORAGE FOR MERE MORTALS Thomas Cameron, RHCA, RHCSS, RHCDS, RHCVA, RHCX Chief Architect, Central US

Transcript of Red Hat Storage for Mere Mortals

Page 1: Red Hat Storage for Mere Mortals

RED HAT STORAGE FOR MERE MORTALS

Thomas Cameron, RHCA, RHCSS, RHCDS, RHCVA, RHCX

Chief Architect, Central US

Page 2: Red Hat Storage for Mere Mortals

AGENDA

Page 3: Red Hat Storage for Mere Mortals

AGENDA

● What is Red Hat Storage?● History● Community● Architecture● Node Installation● Installing RHS● Adding servers to the trusted pool● Distributed volumes● Replicated volumes● Distributed + replicated volumes

Page 4: Red Hat Storage for Mere Mortals

AGENDA

● Attaching to Red Hat Storage with NFS

Page 5: Red Hat Storage for Mere Mortals

WHAT IS RED HAT STORAGE?

Page 6: Red Hat Storage for Mere Mortals

WHAT IS RED HAT STORAGE

● Red Hat Storage is a commercially supported distribution of GlusterFS● GlusterFS is a scale-out network-attached storage filesystem which uses commodity

x86 hardware and inexpensive disks, JBODs, or (rarely) SAN● It can use ethernet or InfiniBand RDMA for transport

Page 7: Red Hat Storage for Mere Mortals

HISTORY

Page 8: Red Hat Storage for Mere Mortals

HISTORY

● The company Gluster was founded in 2005 by founder and CTO Anand Babu Periasamy (now an angel investor in Silicon Valley)

● In 2010, Ben Golub (now CEO of Docker) became the CEO● In 2011, Red Hat acquired Gluster● In 2012, Red Hat Storage was launched

Page 9: Red Hat Storage for Mere Mortals

COMMUNITY

Page 10: Red Hat Storage for Mere Mortals

COMMUNITY

● As Fedora is the upstream project from which Red Hat uses technologies to build Red Hat Enterprise Linux, the Gluster Project (www.gluster.org) is the upstream for Red Hat Storage.

● Documentation, IRC channels, development tools and docs, etc. are all there for the community.

● Community governance with Red Hat's sponsorship.

Page 11: Red Hat Storage for Mere Mortals

ARCHITECTURE

Page 12: Red Hat Storage for Mere Mortals

ARCHITECTURE

● Server component (glusterfsd) ● Client component (glusterfs)● The client runs in user space (FUSE)● File location determined by a hashing algorithm - no metadata services

– No SPOF● Global namespace

Page 13: Red Hat Storage for Mere Mortals
Page 14: Red Hat Storage for Mere Mortals

NODE INSTALLATION

Page 15: Red Hat Storage for Mere Mortals

NODE INSTALLATION

Page 16: Red Hat Storage for Mere Mortals
Page 17: Red Hat Storage for Mere Mortals
Page 18: Red Hat Storage for Mere Mortals
Page 19: Red Hat Storage for Mere Mortals
Page 20: Red Hat Storage for Mere Mortals

NODE INSTALLATION

● Note the inode option “size” is set to 512 bytes, not the default 256!

Page 21: Red Hat Storage for Mere Mortals
Page 22: Red Hat Storage for Mere Mortals
Page 23: Red Hat Storage for Mere Mortals
Page 24: Red Hat Storage for Mere Mortals
Page 25: Red Hat Storage for Mere Mortals
Page 26: Red Hat Storage for Mere Mortals
Page 27: Red Hat Storage for Mere Mortals

NODE INSTALLATION

● Once you've mounted the filesystem, you can “cheat” and get the correct syntax for /etc/fstab from /etc/mtab.

Page 28: Red Hat Storage for Mere Mortals
Page 29: Red Hat Storage for Mere Mortals
Page 30: Red Hat Storage for Mere Mortals

NODE INSTALLATION

● Register the systems to Red Hat

Page 31: Red Hat Storage for Mere Mortals
Page 32: Red Hat Storage for Mere Mortals
Page 33: Red Hat Storage for Mere Mortals
Page 34: Red Hat Storage for Mere Mortals
Page 35: Red Hat Storage for Mere Mortals
Page 36: Red Hat Storage for Mere Mortals
Page 37: Red Hat Storage for Mere Mortals
Page 38: Red Hat Storage for Mere Mortals
Page 39: Red Hat Storage for Mere Mortals
Page 40: Red Hat Storage for Mere Mortals
Page 41: Red Hat Storage for Mere Mortals
Page 42: Red Hat Storage for Mere Mortals
Page 43: Red Hat Storage for Mere Mortals
Page 44: Red Hat Storage for Mere Mortals
Page 45: Red Hat Storage for Mere Mortals
Page 46: Red Hat Storage for Mere Mortals

CLIENT INSTALLATION

Page 47: Red Hat Storage for Mere Mortals
Page 48: Red Hat Storage for Mere Mortals
Page 49: Red Hat Storage for Mere Mortals
Page 50: Red Hat Storage for Mere Mortals
Page 51: Red Hat Storage for Mere Mortals
Page 52: Red Hat Storage for Mere Mortals
Page 53: Red Hat Storage for Mere Mortals

ADDING SERVERS TO THE TRUSTED POOL

Page 54: Red Hat Storage for Mere Mortals
Page 55: Red Hat Storage for Mere Mortals
Page 56: Red Hat Storage for Mere Mortals
Page 57: Red Hat Storage for Mere Mortals

DISTRIBUTED VOLUMES

Page 58: Red Hat Storage for Mere Mortals
Page 59: Red Hat Storage for Mere Mortals
Page 60: Red Hat Storage for Mere Mortals
Page 61: Red Hat Storage for Mere Mortals
Page 62: Red Hat Storage for Mere Mortals
Page 63: Red Hat Storage for Mere Mortals
Page 64: Red Hat Storage for Mere Mortals
Page 65: Red Hat Storage for Mere Mortals
Page 66: Red Hat Storage for Mere Mortals
Page 67: Red Hat Storage for Mere Mortals

ACCESSING DISTRIBUTED VOLUMES

Page 68: Red Hat Storage for Mere Mortals
Page 69: Red Hat Storage for Mere Mortals

TEST FILE CREATION

● Note that on the client, creating 1000 files indicates that there are 1000 files in one mount point

Page 70: Red Hat Storage for Mere Mortals
Page 71: Red Hat Storage for Mere Mortals

TEST FILE CREATION

● But when you look at the bricks, the files are roughly distributed with about a quarter of them on each of the 4 machines.

Page 72: Red Hat Storage for Mere Mortals
Page 73: Red Hat Storage for Mere Mortals
Page 74: Red Hat Storage for Mere Mortals
Page 75: Red Hat Storage for Mere Mortals
Page 76: Red Hat Storage for Mere Mortals
Page 77: Red Hat Storage for Mere Mortals

REPLICATED VOLUMES

Page 78: Red Hat Storage for Mere Mortals
Page 79: Red Hat Storage for Mere Mortals
Page 80: Red Hat Storage for Mere Mortals
Page 81: Red Hat Storage for Mere Mortals
Page 82: Red Hat Storage for Mere Mortals
Page 83: Red Hat Storage for Mere Mortals
Page 84: Red Hat Storage for Mere Mortals

ACCESSING REPLICATED VOLUMES

Page 85: Red Hat Storage for Mere Mortals
Page 86: Red Hat Storage for Mere Mortals

ACCESSING REPLICATED VOLUMES

● This time, creating 1000 files from the client creates 1000 files on each of the replicas.

Page 87: Red Hat Storage for Mere Mortals
Page 88: Red Hat Storage for Mere Mortals
Page 89: Red Hat Storage for Mere Mortals
Page 90: Red Hat Storage for Mere Mortals
Page 91: Red Hat Storage for Mere Mortals
Page 92: Red Hat Storage for Mere Mortals

DISTRIBUTED + REPLICATED VOLUMES

Page 93: Red Hat Storage for Mere Mortals
Page 94: Red Hat Storage for Mere Mortals
Page 95: Red Hat Storage for Mere Mortals
Page 96: Red Hat Storage for Mere Mortals
Page 97: Red Hat Storage for Mere Mortals
Page 98: Red Hat Storage for Mere Mortals
Page 99: Red Hat Storage for Mere Mortals

ACCESSING DISTRIBUTED + REPLICATED VOLUMES

Page 100: Red Hat Storage for Mere Mortals
Page 101: Red Hat Storage for Mere Mortals

ACCESSING DISTRIBUTED+REPLICATED VOLUMES

● This time, since it's a distributed set of replicated (in this case, two way, or mirrored) volumes, creating 1000 files on the clients results in approximately half of the files getting created on each of the distributed nodes, then it is replicated. So 500-ish files on each node.

Page 102: Red Hat Storage for Mere Mortals
Page 103: Red Hat Storage for Mere Mortals
Page 104: Red Hat Storage for Mere Mortals
Page 105: Red Hat Storage for Mere Mortals
Page 106: Red Hat Storage for Mere Mortals

CONNECTING VIA NFS

Page 107: Red Hat Storage for Mere Mortals

CONNECTING VIA NFS

● On the client, install the utilities necessary for NFS

Page 108: Red Hat Storage for Mere Mortals
Page 109: Red Hat Storage for Mere Mortals
Page 110: Red Hat Storage for Mere Mortals
Page 111: Red Hat Storage for Mere Mortals
Page 112: Red Hat Storage for Mere Mortals
Page 113: Red Hat Storage for Mere Mortals

QUESTIONS?

Page 114: Red Hat Storage for Mere Mortals

THANKS! DO THE SURVEY!

Page 115: Red Hat Storage for Mere Mortals