OpenShift + Container Native Storage (CNS)

Size: px

Start display at page:

Download "OpenShift + Container Native Storage (CNS)"

Charlotte Stanley
5 years ago
Views:

1 OpenShift + Container Native Storage (CNS) 31 May 2017 Michael Holzerland, Solution Architect

2 OpenShift supports Persistent Storage GlusterFS Amazon EBS Azure Disk AUTOMATED CONFIGURATION SINGLE CONTROL PANEL GCE Disk iscsi NFS Ceph RBD CHOICE OF PERSISTENT STORAGE

3 GlusterFS Support in OpenShift Scalable CONTAINER NODE 1 CONTAINER NODE 3 NGINX Container NGINX Container CONTAINER NODE 2 CONTAINER NODE 4 NGINX Container NGINX Container Highly-Available Automated Elastic

Launch Container-Native Storage July 2016 Red Hat Gluster Storage runs inside OpenShift in a container (in kubernetes pods) Application and storage containers can be co-located

4 Launch Container-Native Storage July 2016 Red Hat Gluster Storage runs inside OpenShift in a container (in kubernetes pods) Application and storage containers can be co-located There s exactly one RHGS container per host Uses host networking, not overlay Use OpenShift templates to deploy Use a dynamic volume allocator (heketi) to automate volume creation

5 RHGS is supported Everywhere!

6 RED HAT GLUSTER STORAGE concepts Red Hat Confidential - NDA Required

7 GLUSTER STORAGE CONCEPTS VOLUME A namespace presented as a POSIX mount point and is comprised of bricks. BRICK The basic unit of storage, represented by an export directory on a server SERVER/ NODES Contain the bricks

8 BRICKS A Brick is the combination of a node and file system (hostname:/dir) STORAGE NODE STORAGE NODE STORAGE NODE /export1 /export6 /export11 /export2 /export7 /export12 /export3 /export8 /export13 /export4 /export9 /export14 /export5 /export10 /export15 Each brick inherits limits of underlying file system (XFS) Red Hat Gluster Storage operates at the brick level, not the node level Ideally, each brick in a volume should be the same size GAJAH ANNUAL REPORT 2015

ELASTIC HASH ALGORITHM 0 1 1 0 1 0 1 0 No Central Metadata

of failure # BRICK BRICK Elastic Hashing Files assigned to

Volumes easily reassigned on-the-fly Location Hashed on

9 ELASTIC HASH ALGORITHM No Central Metadata Server Suitable for unstructured data storage No single point of failure # BRICK BRICK Elastic Hashing Files assigned to virtual volumes Virtual volumes assigned to multiple bricks Volumes easily reassigned on-the-fly Location Hashed on Filename No performance bottleneck Eliminates risk scenarios GAJAH ANNUAL REPORT 2015

as needed Load balanced data Managed by Gluster

10 VOLUMES CLIENTS Bricks taken from multiple hosts become one addressable unit VOLUMES High availability as needed Load balanced data Managed by Gluster SERVER BRICK BRICK SERVER BRICK BRICK GAJAH ANNUAL REPORT 2015

11 OpenShift + Storage - How it all works

12 What is Container native Storage and what is Heketi? CNS: providing dynamic persistent storage for openshift with GlusterFS in a hyper-converged fashion Heketi: the high-level service interface to gluster to manage the lifecycle of volumes in multiple Gluster clusters. Openshift Heketi Gluster

13 Components of CNS openshift/kubernetes dynamic glusterfs provisioner glusterfs plugin Heketi high-level service interface for gluster volume lifecycle management glusterfs: one or more glusterfs clusters running hyper-converged in openshift cns-deploy: tool to deploy gluster and heketi into an existing openshift cluster

14 Persistent Storage in OpenShift pod: group of one or more containers that form an entity persistent volume (PV): to be mounted by application pod provisioner: to provide PVs upon request plugin: mechanism to mount the PV, referenced in PV persistent volume claim (PVC): mechanism for a user to request a PV Access types for volumes: RWO - read write once (single node) RWX - read write many (multiple nodes) ROX - read only many (multiple nodes)

15 Dynamic Provisioning (OCP 3.4)

16 Details on Containerization

17 gluster cluster in openshift gluster running as pods aggregating host's disk devices into volumes gluster storage nodes tied to openshift nodes (disk devices...) gluster nodes on some, not necessarily on all openshift worker nodes application pods can be on the openshift nodes (need extra memory!)

18 about the gluster containers containerized systemd (running multiple processes: glusterd, brick servers,...) privileged container (systemd, access host /dev,...) startup script host /dev bind-mounted bind-mount config /etc/glusterfs, /var/lib/glsuterd, /var/log/glusterfs use host network: gluster ips need to be constant gluster config tied to the node performance

19 about heketi high-level service interface for managing the lifecycle of gluster volumes RESTful API and cli ("heketi-cli") manages one or several gluster clusters can create, expand, delete volumes (more coming) hides nitty gritty details of volume creation from caller just takes size and desired durability type (currently only replicate is supported in CNS) automatically finds cluster and disks to satisfy the request stores its state in a database (currently Bolt)

20 Wrap Up & Q/A

RED HAT GLUSTER TECHSESSION CONTAINER NATIVE STORAGE OPENSHIFT + RHGS. MARCEL HERGAARDEN SR. SOLUTION ARCHITECT, RED HAT BENELUX April 2017

RED HAT GLUSTER TECHSESSION CONTAINER NATIVE STORAGE OPENSHIFT + RHGS MARCEL HERGAARDEN SR. SOLUTION ARCHITECT, RED HAT BENELUX April 2017 AGENDA Why OpenShift? The Journey So Far for OpenShift Storage