Managed database service like RDS

OpenEBS and MySQL

Introduction

MYSQL is most ubiquitous and commonly used database. RDS is a service that make deploying and making MYSQL easy. With OpenEBS CAS architecture each user is assigned an independent stack of storage that serves just one instance of MySQL database, making it easy to handle the provisioning and post deployment operations like capacity increase and upgrades.

Use OpenEBS and MySQL containers to quickly launch an RDS like service, where database launch is instantaneous, availability is provided across zones and increase in requested capacity can happen on the fly.

Deployment model

OpenEBS and Percona

As shown above, OpenEBS volumes need to be configured with three replicas for high availability. This configuration work fine when the nodes (hence the cStor pool) is deployed across Kubernetes zones.

Configuration workflow

  1. Install OpenEBS

    If OpenEBS is not installed in your K8s cluster, this can done from here. If OpenEBS is already installed, go to the next step.

  2. Configure cStor Pool : After OpenEBS installation, cStor pool has to be configured. As MySQL is a deployment, it need high availability at storage level. OpenEBS cStor volume has to be configured with 3 replica. During cStor Pool creation, make sure that the maxPools parameter is set to >=3. If cStor Pool is already configured as required go to Step 4 to create MySQL StorageClass.

  3. Create Storage Class

    You must configure a StorageClass to provision cStor volume on cStor pool. StorageClass is the interface through which most of the OpenEBS storage policies are defined. In this solution we are using a StorageClass to consume the cStor Pool which is created using external disks attached on the Nodes. Since MySQL is a deployments, it requires high availability of data at storage level. So cStor volume replicaCount is 3. Sample YAML named openebs-sc-disk.yamlto consume cStor pool with cStor volume replica count as 3 is provided in the configuration details below.

  4. Launch and test Mysql:

    Run MySQL database application using the stable helm chart. The following command will install MySQL database application in your cluster. This command will create a PVC of size 8Gi for running the database.

    1. helm install --name my-release --set persistence.storageClass=openebs-cstor-disk stable/mysql

    For more information about installation, see MySQL documentation.

Post deployment Operations

Monitor OpenEBS Volume size

It is not seamless to increase the cStor volume size (refer to the roadmap item). Hence, it is recommended that sufficient size is allocated during the initial configuration.

Monitor cStor Pool size

As in most cases, cStor pool may not be dedicated to just MySQL alone. It is recommended to watch the pool capacity and add more disks to the pool before it hits 80% threshold. See cStorPool metrics

Maintain volume replica quorum during node upgrades

cStor volume replicas need to be in quorum when MySQL application is deployed as deployment and cStor volume is configured to have 3 replicas. Node reboots may be common during Kubernetes upgrade. Maintain volume replica quorum in such instances. See here for more details.

Configuration Details

openebs-config.yaml

  2. #Use the following YAMLs to create a cStor Storage Pool.
  3. # and associated storage class.
  4. apiVersion: openebs.io/v1alpha1
  5. kind: StoragePoolClaim
  6. metadata:
  7.   name: cstor-disk
  8. spec:
  9.   name: cstor-disk
  10.   type: disk
  11.   poolSpec:
  12.     poolType: striped
  13.   # NOTE - Appropriate disks need to be fetched using `kubectl get bd -n openebs`
  14.   #
  15.   # `Block Devices` is a custom resource supported by OpenEBS with `node-disk-manager`
  16.   # as the disk operator
  17. # Replace the following with actual disk CRs from your cluster `kubectl get bd  -n openebs`
  18. # Uncomment the below lines after updating the actual disk names.
  19.   blockdevices:
  20.     blockDeviceList:
  21. # Replace the following with actual disk CRs from your cluster from `kubectl get bd  -n openebs`
  22. #   - blockdevice-69cdfd958dcce3025ed1ff02b936d9b4
  23. #   - blockdevice-891ad1b581591ae6b54a36b5526550a2
  24. #   - blockdevice-ceaab442d802ca6aae20c36d20859a0b
  26. ---

openebs-sc-disk.yaml

  2. apiVersion: storage.k8s.io/v1
  3. kind: StorageClass
  4. metadata:
  5.   name: openebs-cstor-disk
  6.   annotations:
  7.     openebs.io/cas-type: cstor
  8.     cas.openebs.io/config: |
  9.       - name: StoragePoolClaim
  10.         value: "cstor-disk"
  11.       - name: ReplicaCount
  12.         value: "3"
  13. provisioner: openebs.io/provisioner-iscsi
  14. reclaimPolicy: Delete
  15. ---

See Also:

OpenEBS architecture

OpenEBS use cases

cStor pools overview

Feedback

Was this page helpful?

YesNo

Thanks for the feedback. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement. Engage and get additional help on https://kubernetes.slack.com/messages/openebs/.