Mrunal Patel 8e5b17cf13 Switch to github.com/golang/dep for vendoring

Signed-off-by: Mrunal Patel <mrunalp@gmail.com>

2017-01-31 16:45:59 -08:00

3.6 KiB

Raw Blame History

Quobyte Volume
- Quobyte
  - Prerequisites
  - Fixed user Mounts
- Creating a pod

Quobyte Volume

Quobyte

Quobyte is software that turns commodity servers into a reliable and highly automated multi-data center file system.

The example assumes that you already have a running Kubernetes cluster and you already have setup Quobyte-Client (1.3+) on each Kubernetes node.

Prerequisites

Running Quobyte storage cluster
Quobyte client (1.3+) installed on the Kubernetes nodes more information how you can install Quobyte on your Kubernetes nodes, can be found in the documentation of Quobyte.
To get access to Quobyte and the documentation please contact us
Already created Quobyte Volume
Added the line allow-usermapping-in-volumename in /etc/quobyte/client.cfg to allow the fixed user mounts

Fixed user Mounts

Quobyte supports since 1.3 fixed user mounts. The fixed-user mounts simply allow to mount all Quobyte Volumes inside one directory and use them as different users. All access to the Quobyte Volume will be rewritten to the specified user and group – both are optional, independent of the user inside the container. You can read more about it here under the section "Quobyte Mount and Docker — what’s special"

Creating a pod

See example:

apiVersion: v1
kind: Pod
metadata:
  name: quobyte
spec:
  containers:
  - name: quobyte
    image: kubernetes/pause
    volumeMounts:
    - mountPath: /mnt
      name: quobytevolume
  volumes:
  - name: quobytevolume
    quobyte:
      registry: registry:7861
      volume: testVolume
      readOnly: false
      user: root
      group: root

Download example

Parameters:

registry Quobyte registry to use to mount the volume. You can specifiy the registry as : pair or if you want to specify multiple registries you just have to put a comma between them e.q. :,:,:. The host can be an IP address or if you have a working DNS you can also provide the DNS names.
volume volume represents a Quobyte volume which must be created before usage.
readOnly is the boolean that sets the mountpoint readOnly or readWrite.
user maps all access to this user. Default is root.
group maps all access to this group. Default is nfsnobody.

Creating the pod:

$ kubectl create -f examples/volumes/quobyte/quobyte-pod.yaml

Verify that the pod is running:

$ kubectl get pods quobyte
NAME      READY     STATUS    RESTARTS   AGE
quobyte   1/1       Running   0          48m

$ kubectl get pods quobyte --template '{{.status.hostIP}}{{"\n"}}'
10.245.1.3

SSH onto the Machine and validate that quobyte is mounted:

$ mount | grep quobyte
quobyte@10.239.10.21:7861/ on /var/lib/kubelet/plugins/kubernetes.io~quobyte type fuse (rw,nosuid,nodev,noatime,user_id=0,group_id=0,default_permissions,allow_other)

$ docker inspect --format '{{ range .Mounts }}{{ if eq .Destination "/mnt"}}{{ .Source }}{{ end }}{{ end }}' 55ab97593cd3
/var/lib/kubelet/plugins/kubernetes.io~quobyte/root#root@testVolume

3.6 KiB Raw Blame History Unescape Escape