Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @bkoehn. I work for MayaData. I am trying to make a similar setup and trying out the use case. In general, if an old node is replaced with a new node, there are few manual steps to make the cStor pool and volume online. This can be done only when the unique id (BD name) of the underlying disk is not changed. So to understand about the attached block device information, could you give me the output of udevadm info <device_path> (For example,udevadm info /dev/sdb) of all attached blockdevices from all the worker nodes, please?
Hi @colinconstable … Yes, currently the manual steps need to perform to make the pools back online. We also documented the above steps with detailed information into our help center. Please have a look at it here.
I can tell you what happens when you click auto update and have OpenEBS on a Sunday morning all hell lets loose and the cluster is down.
Happened to me this morning … Stupid… Auto upgrade should not break anything… If an admin can fix this the system should manage it…