Kubernetes部署（十）：儲存之glusterfs和heketi部署

時間 2019-11-07

標籤 kubernetes 部署儲存 glusterfs heketi 简体版

原文原文鏈接

概觀

本指南支持在Kubernetes集羣中集成，部署和管理GlusterFS容器化存儲節點。這使Kubernetes管理員可以爲其用戶提供可靠的共享存儲。linux

包括設置指南、其中包含一個示例服務器pod，它使用動態配置的GlusterFS捲進行存儲。對於那些但願測試或瞭解有關此主題的更多信息的人，請按照主要自述文件中的快速入門說明瞭解gluster-kubernetesnginx

本指南旨在演示Heketi在Kubernetes環境中管理Gluster的最小示例。git

基礎設施要求

一個正在運行的Kubernetes集羣，至少有三個Kubernetes工做節點，每一個節點至少鏈接一個可用的原始塊設備（如EBS卷或本地磁盤）。

#使用file -s 查看硬盤若是顯示爲data則爲原始塊設備。若是不是data類型，可先用pvcreate，pvremove來變動。
[root@node-04 ~]# file -s /dev/sdc
/dev/sdc: x86 boot sector, code offset 0xb8
[root@node-04 ~]# pvcreate /dev/sdc
WARNING: dos signature detected on /dev/sdc at offset 510. Wipe it? [y/n]: y
Wiping dos signature on /dev/sdc.
Physical volume "/dev/sdc" successfully created.
[root@node-04 ~]# pvremove /dev/sdc
Labels on physical volume "/dev/sdc" successfully wiped.
[root@node-04 ~]# file -s /dev/sdc 
/dev/sdc: data

在glusterfs節點的宿主機須要安裝glusterfs-client、glusterfs-fuse包和socat包。
```
yum install -y glusterfs-client glusterfs-fuse socat
```
每一個kubetnetes節點的宿主機須要加載dm_thin_pool模塊modprobe dm_thin_pool

客戶端安裝

Heketi提供CLI，爲用戶提供管理Kubernetes中GlusterFS的部署和配置的方法。在您的客戶端計算機上下載並安裝下載並安裝heketi-cli，下載的heketi-cli版本最好是和heketi服務端版本一致，否則可能會出現報錯。github

Kubernetes部署

部署GlusterFS DaemonSet數據庫

{
"kind": "DaemonSet",
"apiVersion": "extensions/v1beta1",
"metadata": {
    "name": "glusterfs",
    "labels": {
        "glusterfs": "deployment"
    },
    "annotations": {
        "description": "GlusterFS Daemon Set",
        "tags": "glusterfs"
    }
},
"spec": {
    "template": {
        "metadata": {
            "name": "glusterfs",
            "labels": {
                "glusterfs-node": "daemonset"
            }
        },
        "spec": {
            "nodeSelector": {
                "storagenode" : "glusterfs"
            },
            "hostNetwork": true,
            "containers": [
                {
                    "image": "gluster/gluster-centos:latest",
                    "imagePullPolicy": "Always",
                    "name": "glusterfs",
                    "volumeMounts": [
                        {
                            "name": "glusterfs-heketi",
                            "mountPath": "/var/lib/heketi"
                        },
                        {
                            "name": "glusterfs-run",
                            "mountPath": "/run"
                        },
                        {
                            "name": "glusterfs-lvm",
                            "mountPath": "/run/lvm"
                        },
                        {
                            "name": "glusterfs-etc",
                            "mountPath": "/etc/glusterfs"
                        },
                        {
                            "name": "glusterfs-logs",
                            "mountPath": "/var/log/glusterfs"
                        },
                        {
                            "name": "glusterfs-config",
                            "mountPath": "/var/lib/glusterd"
                        },
                        {
                            "name": "glusterfs-dev",
                            "mountPath": "/dev"
                        },
                        {
                            "name": "glusterfs-cgroup",
                            "mountPath": "/sys/fs/cgroup"
                        }
                    ],
                    "securityContext": {
                        "capabilities": {},
                        "privileged": true
                    },
                    "readinessProbe": {
                        "timeoutSeconds": 3,
                        "initialDelaySeconds": 60,
                        "exec": {
                            "command": [
                                "/bin/bash",
                                "-c",
                                "systemctl status glusterd.service"
                            ]
                        }
                    },
                    "livenessProbe": {
                        "timeoutSeconds": 3,
                        "initialDelaySeconds": 60,
                        "exec": {
                            "command": [
                                "/bin/bash",
                                "-c",
                                "systemctl status glusterd.service"
                            ]
                        }
                    }
                }
            ],
            "volumes": [
                {
                    "name": "glusterfs-heketi",
                    "hostPath": {
                        "path": "/var/lib/heketi"
                    }
                },
                {
                    "name": "glusterfs-run"
                },
                {
                    "name": "glusterfs-lvm",
                    "hostPath": {
                        "path": "/run/lvm"
                    }
                },
                {
                    "name": "glusterfs-etc",
                    "hostPath": {
                        "path": "/etc/glusterfs"
                    }
                },
                {
                    "name": "glusterfs-logs",
                    "hostPath": {
                        "path": "/var/log/glusterfs"
                    }
                },
                {
                    "name": "glusterfs-config",
                    "hostPath": {
                        "path": "/var/lib/glusterd"
                    }
                },
                {
                    "name": "glusterfs-dev",
                    "hostPath": {
                        "path": "/dev"
                    }
                },
                {
                    "name": "glusterfs-cgroup",
                    "hostPath": {
                        "path": "/sys/fs/cgroup"
                    }
                }
            ]
        }
    }
}
}

$ kubectl create -f glusterfs-daemonset.json

經過運行獲取節點名稱：

$ kubectl get nodes

經過storagenode=glusterfs在該節點上設置標籤，將gluster容器部署到指定節點上。

[root@node-01 heketi]# kubectl label node 10.31.90.204 storagenode=glusterfs
[root@node-01 heketi]# kubectl label node 10.31.90.205 storagenode=glusterfs
[root@node-01 heketi]# kubectl label node 10.31.90.206 storagenode=glusterfs

根據須要,驗證pod正在節點上運行，至少應運行三個pod。json

$ kubectl get pods

接下來咱們將爲Heketi建立一個ServiceAccount：bootstrap

{
"apiVersion": "v1",
"kind": "ServiceAccount",
"metadata": {
"name": "heketi-service-account"
}
}

$ kubectl create -f heketi-service-account.json

咱們如今必須創建該服務賬戶控制gluster pod的能力。咱們經過爲新建立的服務賬戶建立集羣角色綁定來實現此目的。centos
```
$ kubectl create clusterrolebinding heketi-gluster-admin --clusterrole=edit --serviceaccount=default:heketi-service-account
```
如今咱們須要建立一個Kubernetes secret，它將保存咱們的Heketi實例的配置。必須將配置文件設置爲使用 kubernetes執行程序，以便Heketi服務器控制gluster pod。除此以外，您能夠隨意嘗試配置選項。

{
  "_port_comment": "Heketi Server Port Number",
  "port": "8080",

  "_use_auth": "Enable JWT authorization. Please enable for deployment",
  "use_auth": false,

  "_jwt": "Private keys for access",
  "jwt": {
    "_admin": "Admin has access to all APIs",
    "admin": {
      "key": "My Secret"
    },
    "_user": "User only has access to /volumes endpoint",
    "user": {
      "key": "My Secret"
    }
  },

  "_glusterfs_comment": "GlusterFS Configuration",
  "glusterfs": {
    "_executor_comment": "Execute plugin. Possible choices: mock, kubernetes, ssh",
    "executor": "kubernetes",

    "_db_comment": "Database file name",
    "db": "/var/lib/heketi/heketi.db",

    "kubeexec": {
      "rebalance_on_expansion": true
    },

    "sshexec": {
      "rebalance_on_expansion": true,
      "keyfile": "/etc/heketi/private_key",
      "fstab": "/etc/fstab",
      "port": "22",
      "user": "root",
      "sudo": false
    }
  },

  "_backup_db_to_kube_secret": "Backup the heketi database to a Kubernetes secret when running in Kubernetes. Default is off.",
  "backup_db_to_kube_secret": false
}

$ kubectl create secret generic heketi-config-secret --from-file=./heketi.json

接下來，咱們須要部署一個初始Pod和一個服務來訪問該pod。以下會有一個heketi-bootstrap.json文件。
提交文件並驗證一切正常運行，以下所示：

{
"kind": "List",
"apiVersion": "v1",
"items": [
{
  "kind": "Service",
  "apiVersion": "v1",
  "metadata": {
    "name": "deploy-heketi",
    "labels": {
      "glusterfs": "heketi-service",
      "deploy-heketi": "support"
    },
    "annotations": {
      "description": "Exposes Heketi Service"
    }
  },
  "spec": {
    "selector": {
      "name": "deploy-heketi"
    },
    "ports": [
      {
        "name": "deploy-heketi",
        "port": 8080,
        "targetPort": 8080
      }
    ]
  }
},
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "deploy-heketi",
    "labels": {
      "glusterfs": "heketi-deployment",
      "deploy-heketi": "deployment"
    },
    "annotations": {
      "description": "Defines how to deploy Heketi"
    }
  },
  "spec": {
    "replicas": 1,
    "template": {
      "metadata": {
        "name": "deploy-heketi",
        "labels": {
          "name": "deploy-heketi",
          "glusterfs": "heketi-pod",
          "deploy-heketi": "pod"
        }
      },
      "spec": {
        "serviceAccountName": "heketi-service-account",
        "containers": [
          {
            "image": "heketi/heketi:8",
            "imagePullPolicy": "Always",
            "name": "deploy-heketi",
            "env": [
              {
                "name": "HEKETI_EXECUTOR",
                "value": "kubernetes"
              },
              {
                "name": "HEKETI_DB_PATH",
                "value": "/var/lib/heketi/heketi.db"
              },
              {
                "name": "HEKETI_FSTAB",
                "value": "/var/lib/heketi/fstab"
              },
              {
                "name": "HEKETI_SNAPSHOT_LIMIT",
                "value": "14"
              },
              {
                "name": "HEKETI_KUBE_GLUSTER_DAEMONSET",
                "value": "y"
              }
            ],
            "ports": [
              {
                "containerPort": 8080
              }
            ],
            "volumeMounts": [
              {
                "name": "db",
                "mountPath": "/var/lib/heketi"
              },
              {
                "name": "config",
                "mountPath": "/etc/heketi"
              }
            ],
            "readinessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 3,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            },
            "livenessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 30,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            }
          }
        ],
        "volumes": [
          {
            "name": "db"
          },
          {
            "name": "config",
            "secret": {
              "secretName": "heketi-config-secret"
            }
          }
        ]
      }
    }
  }
}
]
}

# kubectl create -f heketi-bootstrap.json
service "deploy-heketi" created
deployment "deploy-heketi" created

[root@node-01 heketi]# kubectl get pod
NAME                            READY     STATUS    RESTARTS   AGE
deploy-heketi-8888799fd-cmfp6   1/1       Running   0          6m
glusterfs-7t5ls                 1/1       Running   0          8m
glusterfs-drsx9                 1/1       Running   0          8m
glusterfs-pnnn8                 1/1       Running   0          8m

如今Bootstrap Heketi服務正在運行，咱們將配置端口轉發，以便咱們可使用Heketi CLI與服務進行通訊。使用Heketi pod的名稱，運行如下命令：

kubectl port-forward deploy-heketi-8888799fd-cmfp6 :8080

若是在運行命令的系統上本地端口8080空閒，則能夠運行port-forward命令，以便它爲了方便而綁定到8080：api

kubectl port-forward deploy-heketi-8888799fd-cmfp6 18080:8080

如今經過對Heketi服務運行示例查詢來驗證端口轉發是否正常工做。該命令應該打印將要轉發的本地端口。將其合併到URL中以測試服務，以下所示：

curl http://localhost:18080/hello
Handling connection for 18080
Hello from Heketi

最後，爲Heketi CLI客戶端設置環境變量，以便它知道如何到達Heketi Server。

export HEKETI_CLI_SERVER=http://localhost:18080

接下來，咱們將向Heketi提供有關要管理的GlusterFS集羣的信息。咱們經過拓撲文件提供此信息。您克隆的repo中有一個示例拓撲文件，名爲topology-sample.json。拓撲指定運行GlusterFS容器的Kubernetes節點以及每一個節點的相應原始塊設備。
確保hostnames/manage指向下面顯示的確切名稱kubectl get nodes，而且hostnames/storage是存儲網絡的IP地址。
重要信息：此時，必須使用與服務器版本匹配的heketi-cli版本加載拓撲文件。做爲最後的手段，Heketi容器附帶了一份能夠經過的方式訪問的heketi-cli kubectl exec ...。

修改拓撲文件以反映您所作的選擇，而後部署它，以下所示：

{
  "clusters": [
    {
      "nodes": [
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.204"
              ],
              "storage":[
                "10.31.90.204"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.205"
              ],
              "storage":[
                "10.31.90.205"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        },
        {
          "node": {
            "hostnames": {
              "manage": [
                "10.31.90.206"
              ],
              "storage":[
                "10.31.90.206"
              ]
            },
            "zone": 1
          },
          "devices": [
            "/dev/sdc"
          ]
        }
      ]
    }
  ]
}

[root@node-01 ~]# heketi-cli topology load --json=top.json
Creating cluster ... ID: e758afb77ee26d5f969d7efee1516e64
        Allowing file volumes on cluster.
        Allowing block volumes on cluster.
        Creating node 10.31.90.204 ... ID: a6eedd58c118dcfe44a0db2af1a4f863
                Adding device /dev/sdc ... OK
        Creating node 10.31.90.205 ... ID: 4066962c14bcdebd28aca193b5690792
                Adding device /dev/sdc ... OK
        Creating node 10.31.90.206 ... ID: 91e42a2361f0266ae334354e5c34ce11
                Adding device /dev/sdc ... OK

接下來咱們將使用Heketi爲它配置一個捲來存儲其數據庫：

執行此命令後會生成一個heketi-storage.json的文件，咱們最好是將此文件裏的
"image": "heketi/heketi:dev"
改成
"image": "heketi/heketi:8"

# heketi-client/bin/heketi-cli setup-openshift-heketi-storage

而後在建立heketi相關服務

# kubectl create -f heketi-storage.json

陷阱：若是heketi-cli在運行setup-openshift-heketi-storage子命令時報告「無空間」錯誤，則可能無心中運行topology load了服務器和heketi-cli的不匹配版本。中止正在運行的Heketi pod（kubectl scale deployment deploy-heketi --replicas=0），手動從存儲塊設備中刪除任何簽名，而後繼續運行Heketi pod（kubectl scale deployment deploy-heketi --replicas=1）。而後使用匹配版本的heketi-cli從新加載拓撲並重試該步驟。

等到做業完成而後刪除引導程序Heketi：

# kubectl delete all,service,jobs,deployment,secret --selector="deploy-heketi"

建立長期Heketi實例：

{
"kind": "List",
"apiVersion": "v1",
"items": [
{
  "kind": "Secret",
  "apiVersion": "v1",
  "metadata": {
    "name": "heketi-db-backup",
    "labels": {
      "glusterfs": "heketi-db",
      "heketi": "db"
    }
  },
  "data": {
  },
  "type": "Opaque"
},
{
  "kind": "Service",
  "apiVersion": "v1",
  "metadata": {
    "name": "heketi",
    "labels": {
      "glusterfs": "heketi-service",
      "deploy-heketi": "support"
    },
    "annotations": {
      "description": "Exposes Heketi Service"
    }
  },
  "spec": {
    "selector": {
      "name": "heketi"
    },
    "ports": [
      {
        "name": "heketi",
        "port": 8080,
        "targetPort": 8080
      }
    ]
  }
},
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "heketi",
    "labels": {
      "glusterfs": "heketi-deployment"
    },
    "annotations": {
      "description": "Defines how to deploy Heketi"
    }
  },
  "spec": {
    "replicas": 1,
    "template": {
      "metadata": {
        "name": "heketi",
        "labels": {
          "name": "heketi",
          "glusterfs": "heketi-pod"
        }
      },
      "spec": {
        "serviceAccountName": "heketi-service-account",
        "containers": [
          {
            "image": "heketi/heketi:8",
            "imagePullPolicy": "Always",
            "name": "heketi",
            "env": [
              {
                "name": "HEKETI_EXECUTOR",
                "value": "kubernetes"
              },
              {
                "name": "HEKETI_DB_PATH",
                "value": "/var/lib/heketi/heketi.db"
              },
              {
                "name": "HEKETI_FSTAB",
                "value": "/var/lib/heketi/fstab"
              },
              {
                "name": "HEKETI_SNAPSHOT_LIMIT",
                "value": "14"
              },
              {
                "name": "HEKETI_KUBE_GLUSTER_DAEMONSET",
                "value": "y"
              }
            ],
            "ports": [
              {
                "containerPort": 8080
              }
            ],
            "volumeMounts": [
              {
                "mountPath": "/backupdb",
                "name": "heketi-db-secret"
              },
              {
                "name": "db",
                "mountPath": "/var/lib/heketi"
              },
              {
                "name": "config",
                "mountPath": "/etc/heketi"
              }
            ],
            "readinessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 3,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            },
            "livenessProbe": {
              "timeoutSeconds": 3,
              "initialDelaySeconds": 30,
              "httpGet": {
                "path": "/hello",
                "port": 8080
              }
            }
          }
        ],
        "volumes": [
          {
            "name": "db",
            "glusterfs": {
              "endpoints": "heketi-storage-endpoints",
              "path": "heketidbstorage"
            }
          },
          {
            "name": "heketi-db-secret",
            "secret": {
              "secretName": "heketi-db-backup"
            }
          },
          {
            "name": "config",
            "secret": {
              "secretName": "heketi-config-secret"
            }
          }
        ]
      }
    }
  }
}
]
}

# kubectl create -f heketi-deployment.json
service "heketi" created
deployment "heketi" created

如今這樣作了，Heketi數據庫將保留在GlusterFS卷中，而且每次重啓Heketi pod時都不會重置。

使用諸如heketi-cli cluster list和之類的命令heketi-cli volume list 來確認先前創建的集羣是否存在，以及Heketi是否知道在引導階段建立的db存儲卷。

演示測試

接下來就是創建存儲卷，而後掛載測試。
在測試以前咱們須要先將heketi服務經過Ingress對外發布，將heketi.cnlinux.club的A記錄解析爲10.31.90.200。

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: ingress-heketi
annotations:
nginx.ingress.kubernetes.io/rewrite-target: /
kubernetes.io/ingress.class: nginx
spec:
rules:
- host: heketi.cnlinux.club
  http:
    paths:
      - path: 
        backend:
          serviceName: heketi
          servicePort: 8080

[root@node-01 heketi]# kubectl create -f ingress-heketi.yaml

在瀏覽器訪問http://heketi.cnlinux.club/hello

建立StorageClass

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: gluster-heketi
provisioner: kubernetes.io/glusterfs
parameters:
  resturl: "http://heketi.cnlinux.club"
  restauthenabled: "false" 
  volumetype: "replicate:2"

[root@node-01 heketi]# kubectl create -f storageclass-gluster-heketi.yaml
[root@node-01 heketi]# kubectl get sc
NAME             PROVISIONER               AGE
gluster-heketi   kubernetes.io/glusterfs   10s

建立pvc

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: pvc-gluster-heketi
spec:
storageClassName: gluster-heketi
accessModes:
- ReadWriteOnce
resources:
requests:
  storage: 1Gi

[root@node-01 heketi]# kubectl create -f pvc-gluster-heketi.yaml 
[root@node-01 heketi]# kubectl get pvc
NAME                 STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS     AGE
pvc-gluster-heketi   Bound     pvc-d978f524-0b74-11e9-875c-005056826470   1Gi        RWO            gluster-heketi   30s

在pod裏掛載pvc

apiVersion: v1
kind: Pod
metadata:
name: pod-pvc
spec:
containers:
- name: pod-pvc
image: busybox:latest
command:
- sleep
- "3600"
volumeMounts:
- name: gluster-volume
  mountPath: "/pv-data"
volumes:
- name: gluster-volume
  persistentVolumeClaim:
    claimName: pvc-gluster-heketi

[root@node-01 heketi]# kubectl create -f pod-pvc.yaml

進入容器查看是否已經掛載成功

[root@node-01 heketi]# kubectl exec pod-pvc -it /bin/sh
/ # df -h
Filesystem                Size      Used Available Use% Mounted on
overlay                  47.8G      4.3G     43.5G   9% /
tmpfs                    64.0M         0     64.0M   0% /dev
tmpfs                     1.9G         0      1.9G   0% /sys/fs/cgroup
10.31.90.204:vol_675cc9fe0e959157919c886ea7786d33
                   1014.0M     42.7M    971.3M   4% /pv-data
/dev/sda3                47.8G      4.3G     43.5G   9% /dev/termination-log
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/resolv.conf
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/hostname
/dev/sda3                47.8G      4.3G     43.5G   9% /etc/hosts

#往/pv-data寫文件，當容量超過1G時就自動退出了，證實容量限制是生效的。

/ # cd /pv-data/
/pv-data # dd if=/dev/zero of=/pv-data/test.img bs=8M count=300
123+0 records in
122+0 records out
1030225920 bytes (982.5MB) copied, 24.255925 seconds, 40.5MB/s

在宿主機磁盤裏查看是否建立了test.img文件

[root@node-04 cfg]# mount /dev/vg_2631413b8b87bbd6cb526568ab697d37/brick_1691ef862dd504e12e8384af76e5a9f2 /mnt
[root@node-04 cfg]# ll -h /mnt/brick/
total 982M
-rw-r--r-- 2 root 2001 982M Jan  2 15:14 test.img

至此，全部的操做都已完成。