add rook
rootsongjc
parent
fa053d453a
commit
626bc95ea6
|
|
@ -140,6 +140,7 @@
|
|||
- [使用Ceph做持久化存储](practice/using-ceph-for-persistent-storage.md)
|
||||
- [OpenEBS](practice/openebs.md)
|
||||
- [使用OpenEBS做持久化存储](practice/using-openebs-for-persistent-storage.md)
|
||||
- [Rook](practice/rook.md)
|
||||
- [集群与应用监控](practice/monitoring.md)
|
||||
- [Heapster](practice//heapster.md)
|
||||
- [使用Heapster获取集群和对象的metric数据](practice/using-heapster-to-get-object-metrics.md)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,267 @@
|
|||
# Rook
|
||||
|
||||
[Rook](https://github.com/rook/rook)是一款云原生环境下的开源分布式存储编排系统，目前已进入CNCF孵化。Rook的官方网站是<https://rook.io>。
|
||||
|
||||
## Rook是什么？
|
||||
|
||||
Rook将分布式存储软件转变为自我管理，自我缩放和自我修复的存储服务。它通过自动化部署，引导、配置、供应、扩展、升级、迁移、灾难恢复、监控和资源管理来实现。 Rook使用基础的云原生容器管理、调度和编排平台提供的功能来履行其职责。
|
||||
|
||||
Rook利用扩展点深入融入云原生环境，为调度、生命周期管理、资源管理、安全性、监控和用户体验提供无缝体验。
|
||||
|
||||
Rook现在处于alpha状态，并且最初专注于在Kubernetes之上运行Ceph。Ceph是一个分布式存储系统，提供文件、数据块和对象存储，可以部署在大型生产集群中。Rook计划在未来的版本中增加对除Ceph之外的其他存储系统以及Kubernetes之外的其他云原生环境的支持。
|
||||
|
||||
## 部署
|
||||
|
||||
可以使用helm或直接用yaml文件两种方式来部署rook operator。
|
||||
|
||||
**使用helm部署**
|
||||
|
||||
```bash
|
||||
helm init -i jimmysong/kubernetes-helm-tiller:v2.8.1
|
||||
helm repo add rook-alpha https://charts.rook.io/alpha
|
||||
helm install rook-alpha/rook --name rook --namespace rook-system
|
||||
```
|
||||
|
||||
**直接使用yaml文件部署**
|
||||
|
||||
```bash
|
||||
kubectl apply -f rook-operator.yaml
|
||||
```
|
||||
|
||||
不论使用那种方式部署的rook operator，都会在rook-agent中看到rook-agent用户无法列出集群中某些资源的错误，可以通过为rook-agent的分配`cluster-admin`权限临时解决，详见[Issue 1472](https://github.com/rook/rook/issues/1472)。
|
||||
|
||||
使用如下yanl文件创建一个`ClusterRoleBinding`并应用到集群中。
|
||||
|
||||
```yaml
|
||||
kind: ClusterRoleBinding
|
||||
apiVersion: rbac.authorization.k8s.io/v1beta1
|
||||
metadata:
|
||||
name: rookagent-clusterrolebinding
|
||||
subjects:
|
||||
- kind: ServiceAccount
|
||||
name: rook-agent
|
||||
namespace: rook-system
|
||||
roleRef:
|
||||
kind: ClusterRole
|
||||
name: cluster-admin
|
||||
apiGroup: ""
|
||||
```
|
||||
|
||||
**部署rook cluster**
|
||||
|
||||
创建完rook operator后，我们再部署rook cluster。
|
||||
|
||||
`rook-cluster.yaml`配置如下：
|
||||
|
||||
```yaml
|
||||
apiVersion: v1
|
||||
kind: Namespace
|
||||
metadata:
|
||||
name: rook
|
||||
---
|
||||
apiVersion: rook.io/v1alpha1
|
||||
kind: Cluster
|
||||
metadata:
|
||||
name: rook
|
||||
namespace: rook
|
||||
spec:
|
||||
versionTag: v0.6.2
|
||||
dataDirHostPath: /var/lib/rook
|
||||
storage:
|
||||
useAllNodes: true
|
||||
useAllDevices: false
|
||||
storeConfig:
|
||||
storeType: bluestore
|
||||
databaseSizeMB: 1024
|
||||
journalSizeMB: 1024
|
||||
```
|
||||
|
||||
**注意**：需要手动指定`versionTag`，因为该镜像repo中没有`latest`标签，如不指定的话Pod将出现镜像拉取错误。
|
||||
|
||||
执行下面的命令部署rook集群。
|
||||
|
||||
```bash
|
||||
kubectl apply -f rook-cluster.yaml
|
||||
```
|
||||
|
||||
rook集群运行在`rook` namespace下，查看rook集群中的pod：
|
||||
|
||||
```bash
|
||||
$ kubectl -n rook get pod
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
rook-api-848df956bf-q6zf2 1/1 Running 0 4m
|
||||
rook-ceph-mgr0-cfccfd6b8-cpk5p 1/1 Running 0 4m
|
||||
rook-ceph-mon0-t496l 1/1 Running 0 6m
|
||||
rook-ceph-mon1-zcn7v 1/1 Running 0 5m
|
||||
rook-ceph-mon3-h97qx 1/1 Running 0 3m
|
||||
rook-ceph-osd-557tn 1/1 Running 0 4m
|
||||
rook-ceph-osd-74frb 1/1 Running 0 4m
|
||||
rook-ceph-osd-zf7rg 1/1 Running 1 4m
|
||||
rook-tools 1/1 Running 0 2m
|
||||
```
|
||||
|
||||
**部署StorageClass**
|
||||
|
||||
StorageClass rook-block的yaml文件（rook-storage.yaml）如下：
|
||||
|
||||
```yaml
|
||||
apiVersion: rook.io/v1alpha1
|
||||
kind: Pool
|
||||
metadata:
|
||||
name: replicapool
|
||||
namespace: rook
|
||||
spec:
|
||||
replicated:
|
||||
size: 1
|
||||
# For an erasure-coded pool, comment out the replication size above and uncomment the following settings.
|
||||
# Make sure you have enough OSDs to support the replica size or erasure code chunks.
|
||||
#erasureCoded:
|
||||
# dataChunks: 2
|
||||
# codingChunks: 1
|
||||
---
|
||||
apiVersion: storage.k8s.io/v1
|
||||
kind: StorageClass
|
||||
metadata:
|
||||
name: rook-block
|
||||
provisioner: rook.io/block
|
||||
parameters:
|
||||
pool: replicapool
|
||||
# Specify the Rook cluster from which to create volumes.
|
||||
# If not specified, it will use `rook` as the name of the cluster.
|
||||
# This is also the namespace where the cluster will be
|
||||
clusterName: rook
|
||||
# Specify the filesystem type of the volume. If not specified, it will use `ext4`.
|
||||
# fstype: ext4
|
||||
```
|
||||
|
||||
我们在下面的示例中将使用rook-block这个StorageClass来创建PV。
|
||||
|
||||
## 工具
|
||||
|
||||
部署rook操作工具pod，该工具pod的yaml文件（rook-tools.yaml）如下：
|
||||
|
||||
```yaml
|
||||
apiVersion: v1
|
||||
kind: Pod
|
||||
metadata:
|
||||
name: rook-tools
|
||||
namespace: rook-system
|
||||
spec:
|
||||
dnsPolicy: ClusterFirstWithHostNet
|
||||
serviceAccountName: rook-operator
|
||||
containers:
|
||||
- name: rook-tools
|
||||
image: rook/toolbox:master
|
||||
imagePullPolicy: IfNotPresent
|
||||
env:
|
||||
- name: ROOK_ADMIN_SECRET
|
||||
valueFrom:
|
||||
secretKeyRef:
|
||||
name: rook-ceph-mon
|
||||
key: admin-secret
|
||||
securityContext:
|
||||
privileged: true
|
||||
volumeMounts:
|
||||
- mountPath: /dev
|
||||
name: dev
|
||||
- mountPath: /sys/bus
|
||||
name: sysbus
|
||||
- mountPath: /lib/modules
|
||||
name: libmodules
|
||||
- name: mon-endpoint-volume
|
||||
mountPath: /etc/rook
|
||||
hostNetwork: false
|
||||
volumes:
|
||||
- name: dev
|
||||
hostPath:
|
||||
path: /dev
|
||||
- name: sysbus
|
||||
hostPath:
|
||||
path: /sys/bus
|
||||
- name: libmodules
|
||||
hostPath:
|
||||
path: /lib/modules
|
||||
- name: mon-endpoint-volume
|
||||
configMap:
|
||||
name: rook-ceph-mon-endpoints
|
||||
items:
|
||||
- key: endpoint
|
||||
path: mon-endpoints
|
||||
```
|
||||
|
||||
`ConfigMap`和`Secret`中的配置项内容是自定义的。
|
||||
|
||||
使用下面的命令部署工具pod：
|
||||
|
||||
```bash
|
||||
kubectl apply -f rook-tools.yaml
|
||||
```
|
||||
|
||||
这是一个独立的pod，没有使用其他高级的controller来管理，我们将它部署在`rook-system`的namespace下。
|
||||
|
||||
```bash
|
||||
kubectl -n rook exec -it rook-tools bash
|
||||
```
|
||||
|
||||
使用下面的命令查看rook集群状态。
|
||||
|
||||
```bash
|
||||
$ rookctl status
|
||||
OVERALL STATUS: OK
|
||||
|
||||
USAGE:
|
||||
TOTAL USED DATA AVAILABLE
|
||||
37.95 GiB 1.50 GiB 0 B 36.45 GiB
|
||||
|
||||
MONITORS:
|
||||
NAME ADDRESS IN QUORUM STATUS
|
||||
rook-ceph-mon0 10.254.162.99:6790/0 true UNKNOWN
|
||||
|
||||
MGRs:
|
||||
NAME STATUS
|
||||
rook-ceph-mgr0 Active
|
||||
|
||||
OSDs:
|
||||
TOTAL UP IN FULL NEAR FULL
|
||||
1 1 1 false false
|
||||
|
||||
PLACEMENT GROUPS (0 total):
|
||||
STATE COUNT
|
||||
none
|
||||
|
||||
$ ceph df
|
||||
GLOBAL:
|
||||
SIZE AVAIL RAW USED %RAW USED
|
||||
38861M 37323M 1537M 3.96
|
||||
POOLS:
|
||||
NAME ID USED %USED MAX AVAIL OBJECTS
|
||||
```
|
||||
|
||||
## 示例
|
||||
|
||||
官方提供了使用rook作为典型的LAMP（Linux + Apache + MySQL + PHP）应用Wordpress的存储后端的示例的yaml文件`mysql.yaml`和`wordpress.yaml`，使用下面的命令创建。
|
||||
|
||||
```bash
|
||||
kubectl apply -f mysql.yaml
|
||||
kubectl apply -f wordpress.yaml
|
||||
```
|
||||
|
||||
Wordpress要依赖于MySQL，所以要先创建MySQL。
|
||||
|
||||
在创建wordpress的时候可能遇到该错误[rook flexvolume failing to attach volumes #1147](https://github.com/rook/rook/issues/1147)，该问题尚未解决。
|
||||
|
||||
## 清理
|
||||
|
||||
如果使用helm部署，则执行下面的命令：
|
||||
|
||||
```bash
|
||||
helm delete --purge rook
|
||||
helm delete daemonset rook-agent
|
||||
```
|
||||
|
||||
如果使用yaml文件直接部署，则使用`kubectl delete -f `加当初使用的yaml文件即可删除集群。
|
||||
|
||||
## 参考
|
||||
|
||||
- [Operator Helm Chart](https://rook.io/docs/rook/master/helm-operator.html)
|
||||
- [Creating Rook Clusters](https://rook.io/docs/rook/v0.6/cluster-crd.html)
|
||||
Loading…
Reference in New Issue