Edit

OpenEBS Storage Policies

---

Overview

This section explains storage policies, that every DevOps team can create and apply to their own storage systems. You can now define policies based on the type of application at the StorageClass (a Kubernetes Kind) level. This page explains when to add a storage policy to your OpenEBS cluster and how to use the same.

A storage policy states the desired behavior of an OpenEBS volume. For example, a set of storage policies can be set in a StorageClass that in turn will be referred to during OpenEBS volume provisioning.

Storage policies can be created, updated, and deleted in a running OpenEBS cluster through corresponding operations on StorageClass. Cluster administrators can update storage policies independent of the cluster. Once a storage policy is installed, users can create and access it’s objects with kubectl commands on StorageClass.

Adding a Custom Storage Policy to an OpenEBS Cluster

Storage policies are meant to be created per team, workload, storage controller, and so on that fits your requirement. Since OpenEBS storage controllers (i.e. jiva or cStor) run from within a container, a custom storage policy can be created and set against a particular storage controller instance that meets the demands of the application (which consumes the storage exposed from the storage controller instance). You can now define policies based on the type of application at the storageclass level. Following are some of the properties that can be customized at the default level in the openebs-storageclasses.yaml file.

Types of Storage Policies

OpenEBS supports several types of Storage Policies such as the following.

• openebs.io/jiva-replica-count
• openebs.io/jiva-replica-image
• openebs.io/jiva-controller-image
• openebs.io/storage-pool
• openebs.io/volume-monitor

Replica Count Policy

You can specify the jiva replica count using the openebs.io/jiva-replica-count property. In the following example, the jiva-replica-count is specified as 1. Hence, a single replica is created.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
    name: openebs-standalone
provisioner: openebs.io/provisioner-iscsi
parameters:
    openebs.io/jiva-replica-count: "1"

Replica Image Policy

You can specify the jiva replica image using the openebs.io/jiva-replica-image property.

Note:

Jiva replica image is a docker image. Following is a sample that makes use of replica image policy.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
    name: mysql
provisioner: openebs.io/provisioner-iscsi
parameters:
    openebs.io/jiva-replica-count: "1"
    openebs.io/capacity: "1G"
    openebs.io/jiva-replica-image: "openebs/jiva:0.5.0"

Controller Image Policy

You can specify the jiva controller image using the openebs.io/jiva-controller-image property.

Note:

Jiva controller image is a docker image. Following is a sample setting.

kind: StorageClass
metadata:
    name: mysql
provisioner: openebs.io/provisioner-iscsi
parameters:
    openebs.io/jiva-replica-count: "1"
    openebs.io/capacity: "1G"
    openebs.io/jiva-controller-image: "openebs/jiva:0.5.0"

Storage Pool Policy

A storage pool provides a persistent path for an OpenEBS volume. It can be a directory on any of the following.

• host-os or
• mounted disk

Note:

You must define the storage pool as a Kubernetes Custom Resource (CR) before using it as a Storage Pool policy. Following is a sample Kubernetes custom resource definition for a storage pool.

apiVersion: openebs.io/v1alpha1
kind: StoragePool
metadata:
    name: sp-mntdir
    type: hostdir
spec:
    path: "/mnt/openebs"

This storage pool custom resource can now be used as follows.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
    name: openebs-percona
provisioner: openebs.io/provisioner-iscsi
parameters:
    openebs.io/jiva-replica-count: "2"
    openebs.io/capacity: "2G"
    openebs.io/jiva-replica-image: "openebs/jiva:0.5.0"
    openebs.io/storage-pool: "sp-mntdir"

Storage Class Policy

You can specify a storage class policy where you can specify the capacity and file system type. By default, OpenEBS comes with ext4 file system. However, you can also use the xfs file system.

Following is a sample setting.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
   name: openebs-mongodb
provisioner: openebs.io/provisioner-iscsi
parameters:
  openebs.io/storage-pool: "test-mntdir"
  openebs.io/jiva-replica-count: "1"
  openebs.io/volume-monitor: "true"
  openebs.io/capacity: 5G
  openebs.io/fstype: "xfs"

Volume Monitoring Policy

You can specify the monitoring policy for a particular volume using openebs.io/volume-monitor property. The following Kubernetes storage class sample uses the Volume Monitoring policy.

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
    name: sc-percona-monitor
provisioner: openebs.io/provisioner-iscsi
parameters:
    openebs.io/jiva-replica-image: "openebs/jiva:0.5.0"
    openebs.io/volume-monitor: "true"