CSI driver for Ceph
Go to file
Serguei Bezverkhi 29ec9358d4 Starting README
2018-02-06 15:54:37 -05:00
deploy Starting README 2018-02-06 15:54:37 -05:00
pkg/rbd rbd plugin refactoring: remove k8s clientSet 2018-02-06 14:36:58 +00:00
rbd rbd plugin refactoring: remove k8s clientSet 2018-02-06 14:36:58 +00:00
vendor just code files 2018-01-15 11:50:50 -05:00
.gitignore add git ignore 2018-01-17 15:38:09 -05:00
.travis.yml rename travis 2018-01-10 18:27:56 +00:00
Gopkg.lock just code files 2018-01-15 11:50:50 -05:00
Gopkg.toml just code files 2018-01-15 11:50:50 -05:00
LICENSE add Apache License 2018-01-10 16:12:00 +00:00
Makefile tune Makefile: clean binary; make static binary 2018-01-18 14:01:24 +00:00
README.md Starting README 2018-02-06 15:54:37 -05:00

Ceph CSI

Overview

RBD CSI plugin implements an interface between CSI enabled Container Orchestrator and CEPH cluster. It allows dynamically provision CEPH volumes and attach it to workloads. Current implementation of CSI RBD plugin was tested in Kubernetes environment, but its code does not rely on any Kubernetes specific calls (WIP to make it k8s agnostic) and should be able to run with any CSI enabled CO (Containers Orchestration).

An RBD CSI plugin is available to help simplify storage management. Once user creates PVC with the reference to a RBD storage class, rbd image and corresponding PV object gets dynamically created and becomes ready to be used by workloads.

Container Storage Interface (CSI) driver, provisioner, and attacher for Ceph RBD and CephFS

RBD Plugin

Configuration Requirements

  • Secret object with the authentication key for ceph cluster
  • StorageClass with rbdplugin (default CSI RBD plugin name) as a provisioner name and information about ceph cluster (monitors, pool, etc)
  • Service Accounts with required RBAC permissions

Feature Status

1.9: Alpha

Important: CSIPersistentVolume and MountPropagation feature gates must be enabled starting in 1.9. Also API server must run with running config set to: storage.k8s.io/v1alpha1

Compiling

CSI RBD plugin can be compiled in a form of a binary file or in a form of a container. When compiled as a binary file, it gets stored in _output folder with the name rbdplugin. When compiled as a container, the resulting image is stored in a local docker's image store.

To compile just a binary file:

$ make rbdplugin

To build a container:

$ make container

By running:

$ docker images | grep rbdplugin

You should see the following line in the output:

csi_images/rbdplugin   latest  248ddba297fa        30 seconds ago    431 MB

Testing

Prerequisite

Enable Mount Propagation in Docker

Comment out MountFlags=slave in docker systemd service then restart docker service.

# systemctl daemon-reload
# systemctl restart docker
Enable Kubernetes Feature Gates

Enable features MountPropagation=true,CSIPersistentVolume=true and runtime config storage.k8s.io/v1alpha1=true

Step 1: Create Secret

$ kubectl create -f ./deploy/kubernetes/rbd-secrets.yaml 

Important: rbd-secrets.yaml, must be customized to match your ceph environment.

Step 2: Create StorageClass

$ kubectl create -f ./deploy/kubernetes/rbd-storage-class.yaml

Important: rbd-secrets.yaml, must be customized to match your ceph environment.

Step 3: Start CSI CEPH RBD plugin

$ kubectl create -f ./deploy/kubernetes/rbdplugin.yaml

Step 4: Start CSI External Attacher

$ kubectl create -f ./deploy/kubernetes/csi-attacher.yaml

Step 5: Start CSI External Provisioner

$ kubectl create -f ./deploy/kubernetes/csi-provisioner.yaml

Important: Deployment yaml files includes required Service Account definitions and required RBAC rules.

Step 6: Check status of CSI RBD plugin

$ kubectl get pods | grep csi 

The following output should be displayed:

NAMESPACE     NAME                                                READY     STATUS    RESTARTS   AGE          
default       csi-attacher-0                                      1/1       Running   0          1d           
default       csi-nodeplugin-rbdplugin-qxqtl                      2/2       Running   0          1d           
default       csi-provisioner-0                                   1/1       Running   0          1d           

Step 7: Create PVC

$ kubectl create -f ./deploy/kubernetes/pvc.yaml

Step 8: Check status of provisioner PV

$ kubectl get pv

The following output should be displayed:

NAME                                                          CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS    CLAIM             STORAGECLASS   REASON    AGE
kubernetes-dynamic-pvc-1b19ddf1-0047-11e8-85ab-760f2eed12ea   5Gi        RWO            Delete           Bound     default/csi-pvc   rbdv2                    10s
$ kubectl describe pv kubernetes-dynamic-pvc-1b19ddf1-0047-11e8-85ab-760f2eed12ea
Name:            kubernetes-dynamic-pvc-1b19ddf1-0047-11e8-85ab-760f2eed12ea
Annotations:     csi.volume.kubernetes.io/volume-attributes={"monitors":"192.168.80.233:6789","pool":"kubernetes"}
                 csiProvisionerIdentity=1516716490787-8081-rbdplugin  <------ !!!
                 pv.kubernetes.io/provisioned-by=rbdplugin
StorageClass:    rbdv2              <------ !!!
Status:          Bound              <------ !!!
Claim:           default/csi-pvc    <------ !!!
Reclaim Policy:  Delete
Access Modes:    RWO
VolumeMode:      Filesystem
Capacity:        5Gi
Message:         
Source:
    Type:    CSI <------ !!!

Step 9: Create a test pod

# kubectl create -f ./deploy/pod.yaml

CepgFS plugin

TODO

Troubleshooting

Please submit an issue at:Issues