Activity 1.0: Download and Install

Here is a link to the instructions for downloading, installing, and setting up DBaaS in PMM within your hosted (or private cloud-hosted) environment. Please follow these instructions and perform the installation, including connecting to your own Kubernetes cluster.

https://www.percona.com/doc/percona-monitoring-and-management/2.x/setting-up/server/dbaas.html

After installation and deployment, begin playing around with DBaaS to create database clusters, edit configuration parameters, restart the cluster, etc. Let us know what issues and suggestions you have for us.

Feedback:

Please create a comment below providing feedback on:

  1. The set of instructions provided to help you download, install, and setup your DBaaS in PMM environment

  2. The actual install package and whether it was successful and what changes you would make to it

  3. The features/functionality of Percona’s DBaaS in PMM

2 Likes

For me it doesn’t work until the end.
The installation was ok so far, I had to figure out how minikube must be installed but this was no problem at all.
Additional I installed kubectl which was not available on my Debian 10 after all the installation steps, but was used in some config commands to run from here:
https://www.percona.com/doc/percona-monitoring-and-management/2.x/setting-up/server/dbaas.html#installing-percona-operators-in-aws-eks-kubernetes

Then I had to restart the pmm-server again, which was gone in the meantime, no idea why …
And then I was able to access the server and the dbaas dashboard (after searching for it) …

I then added the kubernetes cluster successful and tried to add a first mysql cluster and this failed.
Seems that the first and third node came up, but the second failed with some kind of “chrash”:

###FULL_PXC_CLUSTER_CRASH:mysqlcluster1-pxc-1.mysqlcluster1-pxc.default.svc.cluster.local###
You have the situation of a full PXC cluster crash. In order to restore your PXC cluster, please check the log
from all pods/nodes to find the node with the most recent data (the one with the highest sequence number (seqno).
It is mysqlcluster1-pxc-1.mysqlcluster1-pxc.default.svc.cluster.local node with sequence number (seqno): -1
If you want to recover from this node you need to execute the following command:
kubectl exec mysqlcluster1-pxc-1 -c pxc – sh -c ‘kill -s USR1 1’
###LAST_LINE:mysqlcluster1-pxc-1.mysqlcluster1-pxc.default.svc.cluster.local:-1:###