From 50dbfc7781f9978d62e7fd4be29f1b97dc1be15a Mon Sep 17 00:00:00 2001 From: TzZtzt Date: Tue, 1 Mar 2022 09:37:41 +0800 Subject: [PATCH] Update install document (#1475) * Update install document (zhCN) Signed-off-by: TrafalgarZZZ * Update install document (en) Signed-off-by: TrafalgarZZZ --- docs/en/userguide/install.md | 348 ++++++++++++++++------------------- docs/zh/userguide/install.md | 347 +++++++++++++++++----------------- 2 files changed, 329 insertions(+), 366 deletions(-) diff --git a/docs/en/userguide/install.md b/docs/en/userguide/install.md index ded51354bba..7bfcba97185 100644 --- a/docs/en/userguide/install.md +++ b/docs/en/userguide/install.md @@ -1,186 +1,164 @@ -# Deploy Fluid on Your Kubernetes Cluster - -## Prerequisites - -- Git -- Kubernetes cluster(version >= 1.14), and support CSI -- kubectl(version >= 1.14) -- [Helm](https://helm.sh/)(version >= 3.0) - -The following documents assume that you have installed all the above requirements. - -For the installation and configuration of kubectl, please refer to [here](https://kubernetes.io/docs/tasks/tools/install-kubectl/). - -For the installation and configuration of Helm 3, please refer to [here](https://v3.helm.sh/docs/intro/install/). - -## How to Deploy - -### Download Fluid Chart - -You can download the latest Fluid installation package from [Fluid Releases](https://github.com/fluid-cloudnative/fluid/releases). - -Untar the Fluid package you just downloaded: - -```shell -$ tar -zxf fluid.tgz -``` - -### Install Fluid with Helm - -Create namespace: - -```shell -$ kubectl create ns fluid-system -``` - -Install Fluid with: - -```shell -$ helm install fluid fluid -NAME: fluid -LAST DEPLOYED: Fri Jul 24 16:10:18 2020 -NAMESPACE: default -STATUS: deployed -REVISION: 1 -TEST SUITE: None -``` - -> The general format of the `helm install` command is like: `helm install `. In the above command, the first `fluid` means the release name, and the second `fluid` specified the path to the helm chart, i.e. the directory just unpacked. - - -### Upgrade Fluid to the latest version with Helm - -If you have installed an older version of Fluid before, you can use Helm to upgrade it. -Before upgrading, it is recommended to ensure that all components in the AlluxioRuntime resource object have been started completely, which is similar to the following state: - -```shell -$ kubectl get pod -NAME READY STATUS RESTARTS AGE -hbase-fuse-chscz 1/1 Running 0 9h -hbase-fuse-fmhr5 1/1 Running 0 9h -hbase-master-0 2/2 Running 0 9h -hbase-worker-bdbjg 2/2 Running 0 9h -hbase-worker-rznd5 2/2 Running 0 9h -``` - -The command "helm upgrade" will not upgrade CRDs,we need to upgrade them manually: - -```shell -$ tar zxvf fluid-0.5.0.tgz ./ -$ kubectl apply -f fluid/crds/. -``` - -upgrade fluid: -```shell -$ helm upgrade fluid fluid/ -Release "fluid" has been upgraded. Happy Helming! -NAME: fluid -LAST DEPLOYED: Fri Mar 12 09:22:32 2021 -NAMESPACE: default -STATUS: deployed -REVISION: 2 -TEST SUITE: None -``` - -The old version of controller will not terminate automatically, the new version will stay in the Pending status: -```shell -$ kubectl -n fluid-system get pods -NAME READY STATUS RESTARTS AGE -alluxioruntime-controller-56687869f6-g9l9n 0/1 Pending 0 96s -alluxioruntime-controller-5b64fdbbb-j9h6r 1/1 Running 0 3m55s -csi-nodeplugin-fluid-r6crn 2/2 Running 0 94s -csi-nodeplugin-fluid-wvhdn 2/2 Running 0 87s -dataset-controller-5b7848dbbb-rjkl9 1/1 Running 0 3m55s -dataset-controller-64bf45c497-w8ncb 0/1 Pending 0 96s -``` -delete them manually: -```shell -$ kubectl -n fluid-system delete pod alluxioruntime-controller-5b64fdbbb-j9h6r -$ kubectl -n fluid-system delete pod dataset-controller-5b7848dbbb-rjkl9 -``` - -> We recommend you to update from v0.3 and v0.4. If you have an older version, you'd better to reinstall it. - -### Check Status of Component - -**Check CRD used by Fluid:** - -```shell -$ kubectl get crd | grep data.fluid.io -alluxiodataloads.data.fluid.io 2020-07-24T06:54:50Z -alluxioruntimes.data.fluid.io 2020-07-24T06:54:50Z -datasets.data.fluid.io 2020-07-24T06:54:50Z -dataloads.data.fluid.io 2021-03-12T00:00:47Z -datasets.data.fluid.io 2021-03-12T00:00:47Z -jindoruntimes.data.fluid.io 2021-03-12T00:03:45Z -``` - -**Check the status of pods:** - -```shell -$ kubectl get pod -n fluid-system -NAME READY STATUS RESTARTS AGE -alluxioruntime-controller-5dfb5c7966-mkgzb 1/1 Running 0 2d1h -csi-nodeplugin-fluid-64h69 2/2 Running 0 2d1h -csi-nodeplugin-fluid-tc7fx 2/2 Running 0 2d1h -dataset-controller-7c4bc68b96-26mcb 1/1 Running 0 2d1h -``` - -If the Pod status is as shown above, then Fluid is installed on your Kubernetes cluster successfully! - -### Check version info of Component - -When csi-nodeplugin, alluxioruntime-controller and dataset-controller start,they will print their own version info into logs. -If you installed with the charts provided by us,their version info will be fully consistent. -If you installed manually, their version info may be not consistent. You can view in turn: -```bash -$ kubectl logs csi-nodeplugin-fluid-tc7fx -c plugins -n fluid-system | head -n 9 | tail -n 6 -$ kubectl logs alluxioruntime-controller-5dfb5c7966-mkgzb -n fluid-system | head -n 6 -$ kubectl logs dataset-controller-7c4bc68b96-26mcb -n fluid-system | head -n 6 -``` -The printed logs are in the following format: -```bash -2020/10/27 10:16:02 BuildDate: 2020-10-26_14:04:22 -2020/10/27 10:16:02 GitCommit: f2c3a3fa1335cb0384e565f17a4f3284a6507cef -2020/10/27 10:16:02 GitTreeState: dirty -2020/10/27 10:16:02 GoVersion: go1.14.2 -2020/10/27 10:16:02 Compiler: gc -2020/10/27 10:16:02 Platform: linux/amd64 -``` -If the logs printed by Pod have been cleaned up, you can run the following command to view the version: -```bash -$ kubectl exec csi-nodeplugin-fluid-tc7fx -c plugins fluid-csi version -n fluid-system -$ kubectl exec alluxioruntime-controller-5dfb5c7966-mkgzb alluxioruntime-controller version -n fluid-system -$ kubectl exec dataset-controller-7c4bc68b96-26mcb dataset-controller version -n fluid-system -``` - -### Fluid use cases -For more use cases about Fluid, please refer to our demos: -- [Speed Up Accessing Remote Files](../samples/accelerate_data_accessing.md) -- [Cache Co-locality for Workload Scheduling](../samples/data_co_locality.md) -- [Accelerate Machine Learning Training with Fluid](../samples/machinelearning.md) - -### Uninstall Fluid - -For uninstalling fluid safely, we should check weather Custom Resource Objects about fluid have been deleted completely first: -```shell -kubectl get crds -o custom-columns=NAME:.metadata.name | grep data.fluid.io | sed ':t;N;s/\n/,/;b t' | xargs kubectl get --all-namespaces -``` -If you confirm that all Custom resource objects about fluid have been deleted, you can safely uninstall fluid: - -```shell -$ helm delete fluid -$ kubectl delete -f fluid/crds -$ kubectl delete ns fluid-system -``` - -> The `fluid` in command `helm delete` means the during installation. - - -### Advanced Configuration - -In some cloud vendors, the default mount root directory `/runtime-mnt` is not writable, so you have to modify the directory location - -``` -helm install fluid --set runtime.mountRoot=/var/lib/docker/runtime-mnt fluid +# Deploy Fluid on Your Kubernetes Cluster + +## Prerequisites + +- Git +- Kubernetes cluster(version >= 1.16), and support CSI +- kubectl(version >= 1.16) +- [Helm](https://helm.sh/)(version >= 3.5) + +The following documents assume that you have installed all the above requirements. + +For the installation and configuration of kubectl, please refer to [here](https://kubernetes.io/docs/tasks/tools/install-kubectl/). + +For the installation and configuration of Helm 3, please refer to [here](https://v3.helm.sh/docs/intro/install/). + +## How to Deploy + +### Download Fluid Chart + +You can download the latest Fluid installation package from [Fluid Releases](https://github.com/fluid-cloudnative/fluid/releases). + +### Install Fluid with Helm + +Create namespace: + +```shell +$ kubectl create ns fluid-system +``` + +Install Fluid with: + +```shell +$ helm install fluid fluid.tgz +NAME: fluid +LAST DEPLOYED: Fri Jul 24 16:10:18 2020 +NAMESPACE: default +STATUS: deployed +REVISION: 1 +TEST SUITE: None +``` + +> For Kubernetes version lower than v1.17(included), please use `helm install --set runtime.criticalFusePod=false fluid fluid.tgz` + +> The general format of the `helm install` command is like: `helm install `. In the above command, the first `fluid` means the release name, and the second `fluid` specified the path to the helm chart, i.e. the directory just unpacked. + + +### Upgrade Fluid to the latest version(v0.7) with Helm + +If you have installed an older version of Fluid before, you can use Helm to upgrade it. +Before upgrading, it is recommended to ensure that all components in the AlluxioRuntime resource object have been started completely, which is similar to the following state: + +```shell +$ kubectl get pod +NAME READY STATUS RESTARTS AGE +hbase-fuse-chscz 1/1 Running 0 9h +hbase-fuse-fmhr5 1/1 Running 0 9h +hbase-master-0 2/2 Running 0 9h +hbase-worker-bdbjg 2/2 Running 0 9h +hbase-worker-rznd5 2/2 Running 0 9h +``` + +The command "helm upgrade" will not upgrade CRDs,we need to upgrade them manually: + +```shell +$ tar zxvf fluid-0.7.0.tgz ./ +$ kubectl apply -f fluid/crds/. +``` + +upgrade fluid: +```shell +$ helm upgrade fluid fluid/ +Release "fluid" has been upgraded. Happy Helming! +NAME: fluid +LAST DEPLOYED: Fri Mar 12 09:22:32 2021 +NAMESPACE: default +STATUS: deployed +REVISION: 2 +TEST SUITE: None +``` + +> For Kubernetes version lower than v1.17(included), please use `helm install --set runtime.criticalFusePod=false fluid fluid.tgz` + +> We recommend you to update Fluid v0.7 from v0.6. If you have an older version, our suggestion is to reinstall it to ensure everything works fine. + +### Check Status of Component + +**Check CRD used by Fluid:** + +```shell +$ kubectl get crd | grep data.fluid.io +alluxioruntimes.data.fluid.io 2022-02-28T08:14:45Z +databackups.data.fluid.io 2022-02-28T08:14:45Z +dataloads.data.fluid.io 2022-02-28T08:14:45Z +datasets.data.fluid.io 2022-02-28T08:14:45Z +goosefsruntimes.data.fluid.io 2022-02-28T08:14:45Z +jindoruntimes.data.fluid.io 2022-02-28T08:14:45Z +``` + +**Check the status of pods:** + +```shell +$ kubectl get pod -n fluid-system +NAME READY STATUS RESTARTS AGE +alluxioruntime-controller-66bf8cbdf4-k6cxt 1/1 Running 0 6m50s +csi-nodeplugin-fluid-pq2zd 2/2 Running 0 4m30s +csi-nodeplugin-fluid-rkv7h 2/2 Running 0 6m41s +dataset-controller-558c5c7785-mtgfh 1/1 Running 0 6m50s +fluid-webhook-7b6cbf558-lw6lq 1/1 Running 0 6m50s +``` + +If the Pod status is as shown above, then Fluid is installed on your Kubernetes cluster successfully! + +### Check version info of Component + +When csi-nodeplugin, alluxioruntime-controller and dataset-controller start,they will print their own version info into logs. +If you installed with the charts provided by us,their version info will be fully consistent. +If you installed manually, their version info may be not consistent. You can check it with the following command: + +```bash +$ kubectl exec csi-nodeplugin-fluid-pq2zd -n fluid-system -c plugins fluid-csi version +$ kubectl exec alluxioruntime-controller-66bf8cbdf4-k6cxt -n fluid-system -- alluxioruntime-controller version +$ kubectl exec dataset-controller-558c5c7785-mtgfh -n fluid-system -- dataset-controller version +``` + +The output should be like: +``` +BuildDate: 2022-02-20_09:43:43 +GitCommit: 808c72e3c5136152690599d187a76849d03ea448 +GitTreeState: dirty +GoVersion: go1.16.8 +Compiler: gc +Platform: linux/amd64 +``` + +### Fluid use cases +For more use cases about Fluid, please refer to our demos: +- [Speed Up Accessing Remote Files](../samples/accelerate_data_accessing.md) +- [Cache Co-locality for Workload Scheduling](../samples/data_co_locality.md) +- [Accelerate Machine Learning Training with Fluid](../samples/machinelearning.md) + +### Uninstall Fluid + +To uninstall fluid safely, we should check weather Custom Resource Objects about fluid have been deleted completely first: +```shell +kubectl get crds -o custom-columns=NAME:.metadata.name | grep data.fluid.io | sed ':t;N;s/\n/,/;b t' | xargs kubectl get --all-namespaces +``` +If you confirm that all Custom resource objects about fluid have been deleted, you can safely uninstall fluid: + +```shell +$ helm delete fluid +$ kubectl delete -f fluid/crds +$ kubectl delete ns fluid-system +``` + +> The `fluid` in command `helm delete` means the during installation. + + +### Advanced Configuration + +In some cloud vendors, the default mount root directory `/runtime-mnt` is not writable, so you have to modify the directory location + +``` +helm install fluid --set runtime.mountRoot=/var/lib/docker/runtime-mnt fluid ``` \ No newline at end of file diff --git a/docs/zh/userguide/install.md b/docs/zh/userguide/install.md index 68e69472524..9c6ee0b095a 100644 --- a/docs/zh/userguide/install.md +++ b/docs/zh/userguide/install.md @@ -1,181 +1,166 @@ -# 在Kubernetes集群上部署Fluid - -## 前提条件 - -- Git -- Kubernetes集群(version >= 1.14), 并且支持CSI功能 -- kubectl(version >= 1.14) -- Helm(version >= 3.0) - -接下来的文档假设您已经配置好上述所有环境。 - -对于`kubectl`的安装和配置,请参考[此处](https://kubernetes.io/docs/tasks/tools/install-kubectl/)。 - -对于Helm 3的安装和配置,请参考[此处](https://v3.helm.sh/docs/intro/install/)。 - -## Fluid安装步骤 - -### 获取Fluid Chart - -您可以从[Fluid Releases](https://github.com/fluid-cloudnative/fluid/releases)下载最新的Fluid安装包。 - - -### 使用Helm安装Fluid - -创建命名空间: - -```shell -$ kubectl create ns fluid-system -``` - -安装Fluid: - -```shell -$ helm install fluid fluid.tgz -NAME: fluid -LAST DEPLOYED: Fri Jul 24 16:10:18 2020 -NAMESPACE: default -STATUS: deployed -REVISION: 1 -TEST SUITE: None -``` - -> `helm install`命令的一般格式是`helm install `,在上面的命令中,第一个`fluid`指定了安装的release名字,这可以自行更改,第二个`fluid.tgz`指定了helm chart所在路径。 - -### 使用Helm将Fluid更新到最新版本 - -如果您此前已经安装过旧版本的Fluid,可以使用Helm进行更新。 -更新前,建议确保AlluxioRuntime资源对象中的各个组件已经顺利启动完成,也就是类似以下状态: - -```shell -$ kubectl get pod -NAME READY STATUS RESTARTS AGE -hbase-fuse-chscz 1/1 Running 0 9h -hbase-fuse-fmhr5 1/1 Running 0 9h -hbase-master-0 2/2 Running 0 9h -hbase-worker-bdbjg 2/2 Running 0 9h -hbase-worker-rznd5 2/2 Running 0 9h -``` - -由于helm upgrade不会更新CRD,需要先对其手动进行更新: - -```shell -$ tar zxvf fluid-0.5.0.tgz ./ -$ kubectl apply -f fluid/crds/. -``` - -更新: -```shell -$ helm upgrade fluid fluid/ -Release "fluid" has been upgraded. Happy Helming! -NAME: fluid -LAST DEPLOYED: Fri Mar 12 09:22:32 2021 -NAMESPACE: default -STATUS: deployed -REVISION: 2 -TEST SUITE: None -``` -此时,旧版本的controller不会自动结束,新版本的controller会停留在Pending状态: -```shell -$ kubectl -n fluid-system get pods -NAME READY STATUS RESTARTS AGE -alluxioruntime-controller-56687869f6-g9l9n 0/1 Pending 0 96s -alluxioruntime-controller-5b64fdbbb-j9h6r 1/1 Running 0 3m55s -csi-nodeplugin-fluid-r6crn 2/2 Running 0 94s -csi-nodeplugin-fluid-wvhdn 2/2 Running 0 87s -dataset-controller-5b7848dbbb-rjkl9 1/1 Running 0 3m55s -dataset-controller-64bf45c497-w8ncb 0/1 Pending 0 96s -``` -手动进行删除: -```shell -$ kubectl -n fluid-system delete pod alluxioruntime-controller-5b64fdbbb-j9h6r -$ kubectl -n fluid-system delete pod dataset-controller-5b7848dbbb-rjkl9 -``` - -> 建议您从v0.3和v0.4升级。如果您安装的是更旧版本的Fluid,建议重新进行安装。 - -### 检查各组件状态 - -**查看Fluid使用的CRD:** - -```shell -$ kubectl get crd | grep data.fluid.io -alluxiodataloads.data.fluid.io 2021-03-12T00:00:47Z -alluxioruntimes.data.fluid.io 2021-03-12T00:00:47Z -databackups.data.fluid.io 2021-03-12T00:03:45Z -dataloads.data.fluid.io 2021-03-12T00:00:47Z -datasets.data.fluid.io 2021-03-12T00:00:47Z -jindoruntimes.data.fluid.io 2021-03-12T00:03:45Z -``` - -**查看各Pod的状态:** - -```shell -$ kubectl get pod -n fluid-system -NAME READY STATUS RESTARTS AGE -alluxioruntime-controller-5dfb5c7966-mkgzb 1/1 Running 0 2d1h -csi-nodeplugin-fluid-64h69 2/2 Running 0 2d1h -csi-nodeplugin-fluid-tc7fx 2/2 Running 0 2d1h -dataset-controller-7c4bc68b96-26mcb 1/1 Running 0 2d1h -``` - -如果Pod状态如上所示,那么Fluid就可以正常使用了! - -**查看各Pod内程序的版本:** - -csi-nodeplugin、alluxioruntime-controller、dataset-controller在启动时,会将自身的版本信息打印到日志中。 -如果您使用我们提供的charts进行安装,它们的版本应该是完全一致的。 -如果您是手动安装部署,它们的版本可能不完全一致,可以分别依次查看: -```bash -$ kubectl logs csi-nodeplugin-fluid-tc7fx -c plugins -n fluid-system | head -n 9 | tail -n 6 -$ kubectl logs alluxioruntime-controller-5dfb5c7966-mkgzb -n fluid-system | head -n 6 -$ kubectl logs dataset-controller-7c4bc68b96-26mcb -n fluid-system | head -n 6 -``` -打印出的日志如下格式: -```bash -2020/10/27 10:16:02 BuildDate: 2020-10-26_14:04:22 -2020/10/27 10:16:02 GitCommit: f2c3a3fa1335cb0384e565f17a4f3284a6507cef -2020/10/27 10:16:02 GitTreeState: dirty -2020/10/27 10:16:02 GoVersion: go1.14.2 -2020/10/27 10:16:02 Compiler: gc -2020/10/27 10:16:02 Platform: linux/amd64 -``` -若Pod打印的日志已经被清理掉,可以执行下列命令查看版本: -```bash -$ kubectl exec csi-nodeplugin-fluid-tc7fx -c plugins fluid-csi version -n fluid-system -$ kubectl exec alluxioruntime-controller-5dfb5c7966-mkgzb alluxioruntime-controller version -n fluid-system -$ kubectl exec dataset-controller-7c4bc68b96-26mcb dataset-controller version -n fluid-system -``` - -### Fluid使用示例 - -有关Fluid的使用示例,可以参考我们提供的示例文档: -- [远程文件访问加速](../samples/accelerate_data_accessing.md) -- [数据缓存亲和性调度](../samples/data_co_locality.md) -- [用Fluid加速机器学习训练](../samples/machinelearning.md) - -### 卸载Fluid - -为了安全的卸载fluid,在卸载前,首先需要检查fluid相关的自定义资源对象是否已被清除: -```shell -kubectl get crds -o custom-columns=NAME:.metadata.name | grep data.fluid.io | sed ':t;N;s/\n/,/;b t' | xargs kubectl get --all-namespaces -``` -如果确认已经删除所有资源对象,则可以安全卸载fluid: - -```shell -$ helm delete fluid -$ kubectl delete -f fluid/crds -$ kubectl delete ns fluid-system -``` - -> `helm delete`命令中的`fluid`对应安装时指定的。 - - -### 高级配置 - -在一些特定的云厂商实现下, 默认mount根目录`/runtime-mnt`是不可写的,因此需要修改目录位置 - -``` -helm install fluid --set runtime.mountRoot=/var/lib/docker/runtime-mnt fluid -``` - +# 在Kubernetes集群上部署Fluid + +## 前提条件 + +- Git +- Kubernetes集群(version >= 1.16), 并且支持CSI功能 +- kubectl(version >= 1.16) +- Helm(version >= 3.5) + +接下来的文档假设您已经配置好上述所有环境。 + +对于`kubectl`的安装和配置,请参考[此处](https://kubernetes.io/docs/tasks/tools/install-kubectl/)。 + +对于Helm 3的安装和配置,请参考[此处](https://v3.helm.sh/docs/intro/install/)。 + +## Fluid安装步骤 + +### 获取Fluid Chart + +您可以从[Fluid Releases](https://github.com/fluid-cloudnative/fluid/releases)下载最新的Fluid安装包。 + + +### 使用Helm安装Fluid + +创建命名空间: + +```shell +$ kubectl create ns fluid-system +``` + +安装Fluid: + +```shell +$ helm install fluid fluid.tgz +NAME: fluid +LAST DEPLOYED: Fri Jul 24 16:10:18 2020 +NAMESPACE: default +STATUS: deployed +REVISION: 1 +TEST SUITE: None +``` + +> 对于Kubernetes v1.17及以下环境,清使用`helm install --set runtime.criticalFusePod=false fluid fluid.tgz` + +> `helm install`命令的一般格式是`helm install `,在上面的命令中,第一个`fluid`指定了安装的release名字,这可以自行更改,第二个`fluid.tgz`指定了helm chart所在路径。 + +### 使用Helm将Fluid更新到最新版本(v0.7) + +如果您此前已经安装过旧版本的Fluid,可以使用Helm进行更新。 +更新前,建议确保各Runtime资源对象中的各个组件已经顺利启动完成,也就是类似以下状态: + +```shell +$ kubectl get pod +NAME READY STATUS RESTARTS AGE +hbase-fuse-chscz 1/1 Running 0 9h +hbase-fuse-fmhr5 1/1 Running 0 9h +hbase-master-0 2/2 Running 0 9h +hbase-worker-bdbjg 2/2 Running 0 9h +hbase-worker-rznd5 2/2 Running 0 9h +``` + +由于helm upgrade不会更新CRD,需要先对其手动进行更新: + +```shell +$ tar zxvf fluid-0.7.0.tgz ./ +$ kubectl apply -f fluid/crds/. +``` + +更新: +```shell +$ helm upgrade fluid fluid/ +Release "fluid" has been upgraded. Happy Helming! +NAME: fluid +LAST DEPLOYED: Fri Mar 12 09:22:32 2021 +NAMESPACE: default +STATUS: deployed +REVISION: 2 +TEST SUITE: None +``` + +> 对于Kubernetes v1.17及以下环境,清使用`helm upgrade --set runtime.criticalFusePod=false fluid fluid/` + +> 建议您从v0.6升级到最新版本v0.7。如果您安装的是更旧版本的Fluid,建议重新进行安装。 + +### 检查各组件状态 + +**查看Fluid使用的CRD:** + +```shell +$ kubectl get crd | grep data.fluid.io +alluxioruntimes.data.fluid.io 2022-02-28T08:14:45Z +databackups.data.fluid.io 2022-02-28T08:14:45Z +dataloads.data.fluid.io 2022-02-28T08:14:45Z +datasets.data.fluid.io 2022-02-28T08:14:45Z +goosefsruntimes.data.fluid.io 2022-02-28T08:14:45Z +jindoruntimes.data.fluid.io 2022-02-28T08:14:45Z +``` + +**查看各Pod的状态:** + +```shell +$ kubectl get pod -n fluid-system +NAME READY STATUS RESTARTS AGE +alluxioruntime-controller-66bf8cbdf4-k6cxt 1/1 Running 0 6m50s +csi-nodeplugin-fluid-pq2zd 2/2 Running 0 4m30s +csi-nodeplugin-fluid-rkv7h 2/2 Running 0 6m41s +dataset-controller-558c5c7785-mtgfh 1/1 Running 0 6m50s +fluid-webhook-7b6cbf558-lw6lq 1/1 Running 0 6m50s +``` + +如果Pod状态如上所示,那么Fluid就可以正常使用了! + +**查看各Pod内程序的版本:** + +csi-nodeplugin、alluxioruntime-controller、dataset-controller在启动时,会将自身的版本信息打印到日志中。 +如果您使用我们提供的charts进行安装,它们的版本应该是完全一致的。 + +可以执行下列命令查看版本: +```bash +$ kubectl exec csi-nodeplugin-fluid-pq2zd -n fluid-system -c plugins fluid-csi version +$ kubectl exec alluxioruntime-controller-66bf8cbdf4-k6cxt -n fluid-system -- alluxioruntime-controller version +$ kubectl exec dataset-controller-558c5c7785-mtgfh -n fluid-system -- dataset-controller version +``` + +如果版本一致,您将看到如下信息: +``` +BuildDate: 2022-02-20_09:43:43 +GitCommit: 808c72e3c5136152690599d187a76849d03ea448 +GitTreeState: dirty +GoVersion: go1.16.8 +Compiler: gc +Platform: linux/amd64 +``` + +### Fluid使用示例 + +有关Fluid的使用示例,可以参考我们提供的示例文档: +- [远程文件访问加速](../samples/accelerate_data_accessing.md) +- [数据缓存亲和性调度](../samples/data_co_locality.md) +- [用Fluid加速机器学习训练](../samples/machinelearning.md) + +### 卸载Fluid + +为了安全的卸载fluid,在卸载前,首先需要检查fluid相关的自定义资源对象是否已被清除: +```shell +kubectl get crds -o custom-columns=NAME:.metadata.name | grep data.fluid.io | sed ':t;N;s/\n/,/;b t' | xargs kubectl get --all-namespaces +``` +如果确认已经删除所有资源对象,则可以安全卸载fluid: + +```shell +$ helm delete fluid +$ kubectl delete -f fluid/crds +$ kubectl delete ns fluid-system +``` + +> `helm delete`命令中的`fluid`对应安装时指定的。 + + +### 高级配置 + +在一些特定的云厂商实现下, 默认mount根目录`/runtime-mnt`是不可写的,因此需要修改目录位置 + +``` +helm install fluid --set runtime.mountRoot=/var/lib/docker/runtime-mnt fluid +``` +