The added features include in 0.7 includes Management of local nodes Many NoSQL and other users do not need the resilience features of OpenEBS however they do want management of these nodes. OpenEBS users can now designate local node via their storage classes and have the benefits of metrics and fault management. Node Disk Management support (NDM). One capability that has been added by MayaData to Kubernetes itself is improvements in the management of storage media in local nodes. OpenEBS 0.7 now uses NDM to improve the resilience and flexibility of Kubernetes for storage. Data operations automation As OpenEBS was adopted users increasingly encountered a number of storage and data management tasks such as data clean up, data back-up, copy data operations, auto-scaling and cross availability zone deployment specification and much more. All of these use cases and others have been made simpler to deliver in OpenEBS, to test and validate via Litmus integration in MayaOnline, and to observe and operate in MayaOnline. Resilience and supportability The fundamental task of any storage is to keep the data safe. With that in mind, OpenEBS adds resilience and supportability capabilities in each release, such as improved retry logic, improved resilience to network outages, cross availability zone recovery, initial snapshot-based replication, and backup options, and ongoing integrations with emerging Kubernetes capabilities to further increase control and availability. A new user interface for MayaOnline MayaOnline has been redesigned to be more intuitive for use in understanding, controlling and troubleshooting stateful environments on Kubernetes.

1. Quick Intro - Sept 14 2018
Volume Policies with
Release 0.7

2. ● Volume Policies in 0.7
○ As StorageClass Annotations
○ cas-type: jiva
● Number of Replicas
● Format Type
● NodeSelector
● Resource Requests
● Advanced
○ Volume Software Version
○ Volume Deployments
Agenda

3. Volume Policies
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: openebs-standalone
annotations:
openebs.io/cas-type: jiva
cas.openebs.io/config: |
- name: ReplicaCount
value: "1"
- name: StoragePool
value: default
provisioner: openebs.io/provisioner-iscsi
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: openebs-standalone
provisioner: openebs.io/provisioner-iscsi
parameters:
openebs.io/storage-pool: "default"
openebs.io/jiva-replica-count: "1"

4. - name: ReplicaCount
value: "3"
- name: StoragePool
value: "default"
- name: FSType
value: "ext4"
- name: TargetNodeSelector
value: "none"
- name: ReplicaNodeSelector
value: "none"
- name: ReplicaAntiAffinityTopoKey
value: "kubernetes.io/hostname"
Default Policies
https://github.com/openebs/maya/blob/master/pkg/install/v1alpha1/jiva_volume_0.7.0.go
- name: TargetResourceRequests
value: "none"
- name: TargetResourceLimits
value: "none"
- name: ReplicaResourceRequests
value: "none"
- name: ReplicaResourceLimits
value: "none"

5. - name: ControllerImage
value: {{env "OPENEBS_IO_JIVA_CONTROLLER_IMAGE" | default "openebs/jiva:latest"}}
- name: ReplicaImage
value: {{env "OPENEBS_IO_JIVA_REPLICA_IMAGE" | default "openebs/jiva:latest"}}
- name: VolumeMonitorImage
value: {{env "OPENEBS_IO_VOLUME_MONITOR_IMAGE" | default "openebs/m-exporter:latest"}}
Default Policies
https://github.com/openebs/openebs/blob/master/k8s/openebs-operator.yaml
- name: OPENEBS_IO_JIVA_CONTROLLER_IMAGE
value: "openebs/jiva:0.7.0"
- name: OPENEBS_IO_JIVA_REPLICA_IMAGE
value: "openebs/jiva:0.7.0"
- name: OPENEBS_IO_VOLUME_MONITOR_IMAGE
value: "openebs/m-exporter:0.7.0"

6. Usecase: Mongo STS
us-central-1a us-central-1b us-central-1c
v1 v2 v3
● MongoDB deployed as STS
with 3 instances => 3 PVs
● Format type xfs is preferred
● Single Replica is sufficient
since application takes care of
high availability and rebuild.
s2 s3s1

7. apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: mongo-pv-az
annotations:
cas.openebs.io/config: |
- name: ReplicaCount
value: "1"
- name: StoragePool
value: default
- name: FSType
value: "xfs"
provisioner: openebs.io/provisioner-iscsi
Volume Policy - Replicas and Format
https://github.com/openebs/openebs/blob/master/k8s/demo/mongodb/mongo-statefulset.yml

8. apiVersion: apps/v1beta1
kind: StatefulSet
metadata:
name: mongo
spec:
serviceName: "mongo"
replicas: 3
template:
metadata:
labels:
#This label will be used by openebs to place in replica
# pod anti-affinity to make sure data of different mongo
# instances are not co-located on the same node
openebs.io/replica-anti-affinity: vehicle-db
Volume Policy - Anti Affinity Label
https://github.com/openebs/openebs/blob/master/k8s/demo/mongodb/mongo-statefulset.yml

9. apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: mongo-pv-az
annotations:
cas.openebs.io/config: |
- name: ReplicaCount
value: "1"
- name: StoragePool
value: default
- name: FSType
value: "xfs"
- name: ReplicaAntiAffinityTopoKey
value: failure-domain.beta.kubernetes.io/zone
provisioner: openebs.io/provisioner-iscsi
Volume Policy - AZ Anit Affinity
https://github.com/openebs/openebs/blob/master/k8s/demo/mongodb/mongo-statefulset.yml

10. Usecase: Mongo STS
us-central-1a us-central-1b us-central-1c
v1 v2 v3
● MongoDB deployed as STS
with 3 instances => 3 PVs
● Format type xfs is preferred
● Single Replica is sufficient
since application takes care of
high availability and rebuild.
● Replicas should be pinned to
subset of nodes
s2 s3s1

11. - name: ReplicaNodeSelector
value: |-
nodetype: storage
- name: TargetNodeSelector
value: |-
nodetype: app
Volume Policy - Replica NodeSelector
https://github.com/openebs/openebs/blob/master/k8s/sample-pv-yamls/pvc-jiva-sc-nodeselector.yaml
kubectl label nodes <node-name> nodetype=storage
kubectl label nodes <node-name> nodetype=app

12. Usecase: Mongo STS
us-central-1a us-central-1b us-central-1c
v1 v2 v3
● MongoDB deployed as STS
with 3 instances => 3 PVs
● Format type xfs is preferred
● Single Replica is sufficient
since application takes care of
high availability and rebuild.
● Replicas should be pinned to
subset of nodes
● Limit the resources used
s2 s3s1

13. - name: TargetResourceLimits
value: |-
memory: 1Gi
cpu: 100m
- name: ReplicaResourceLimits
value: |-
memory: 2Gi
cpu: 200m
- name: AuxResourceLimits
value: |-
memory: 0.5Gi
cpu: 50m
Volume Policy - CPU/RAM limits
https://github.com/openebs/openebs/blob/master/k8s/sample-pv-yamls/pvc-jiva-sc-standard-limit-resources.yaml
- Use Default Kubernetes limits/requests
- Use limits/requests associated with PVC
namespace
- Customize per Target or Replica
resources

14. cas.openebs.io/config: |
- name: ControllerImage
value: openebs/jiva:0.7.0-hotfix
- name: ReplicaImage
value: openebs/jiva:0.7.0-hotfix
- name: VolumeMonitorImage
value: openebs/m-exporter:0.7.0-hotfix
Advanced Volume Policy - Version!

15. apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: openebs-standard
annotations:
cas.openebs.io/create-volume-template: jiva-volume-create-default-0.7.0
cas.openebs.io/delete-volume-template: jiva-volume-delete-default-0.7.0
cas.openebs.io/read-volume-template: jiva-volume-read-default-0.7.0
Advanced Volume Policy - DIY!
https://github.com/openebs/charts/blob/master/store/openebs-pre-release-features-0.7.0-RC1.yaml

16. Thank you!