server_quick_setup.md

Quick Start Guide to run Quobyte in Kubernetes

Prerequisites

Quobyte is designed to run on dedicated disk drives which are formatted with ext4 or xfs and are initialized as a Quobyte device. Quobyte 2.0 features the Device Inspector, which can detect unformatted devices on a node and format and mount them for use in Quobyte. The Device Inspector requires the feature gate "MountPropagation=true" to be set. This feature is in alpha State on Kubernetes 1.8 and requires manual interaction to enable. If it's not set, the Device Inspector is able to detect and format devices, but they will not be mounted.

If you plan to create the cluster with the help of the Device Inspector, you can start a directory based ephemeral registry, or prepare and mount a registry device.

Instead of creating any devices, just schedule an ephemeral bootstrap registry first, start registries, data, and metadata services on the target pods and let the device inspector create the devices. Afterwards, it is safe to delete the bootstrap registry again.

Quobyte setup requires bootstrap node. Update registry.bootstrap_node in deploy/config.yaml with bootstrap node.

Label your bootstrap node as registry.

kubectl label node <bootstrap-node> quobyte_registry="true"

Create the quobyte namespace, set up config and services.

kubectl create -f quobyte-ns.yaml
kubectl -n quobyte create -f config.yaml
kubectl -n quobyte create -f quobyte-services.yaml

kubectl -n quobyte create -f registry-ds.yaml
kubectl -n quobyte create -f data-ds.yaml
kubectl -n quobyte create -f metadata-ds.yaml

As soon as the registry is up, start the webconsole, api, and qmgmt pods:

kubectl create -f webconsole-deployment.yaml
kubectl create -f qmgmt-pod.yaml

When all pods are up, you should be able to log in to your initial cluster with your preferred browser:

kubectl port-forward <webconsole-pod> 8080:8080

To schedule other registries, data, and metadata servers, label the nodes accordingly. The services will show up in the webconsole and the Device Inspector will help to set up the devices.

kubectl label nodes <node> quobyte_data="true"
kubectl label nodes <node> quobyte_registry="true"
kubectl label nodes <node> quobyte_metadata="true"

Once you have three other registries set up on physical devices, it's safe to remove the quobyte_registry label, delete the registry pod on the bootstrap node and update registry.bootstrap_node in deploy/config.yaml with empty string"".