Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 3 additions & 13 deletions docs/installation/webui-installation.md
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,8 @@ When troubleshooting, check the HAMi WebUI component logs.
Run:

```bash
kubectl logs --namespace=hami deploy/my-hami-webui -c hami-webui-fe-oss
kubectl logs --namespace=hami deploy/my-hami-webui -c hami-webui-be-oss
kubectl logs --namespace=kube-system deploy/my-hami-webui -c hami-webui-fe-oss
kubectl logs --namespace=kube-system deploy/my-hami-webui -c hami-webui-be-oss
```

For more information, see [Pods](https://kubernetes.io/docs/reference/kubectl/cheatsheet/#interacting-with-running-pods) and [Deployments](https://kubernetes.io/docs/reference/kubectl/cheatsheet/#interacting-with-deployments-and-services).
Expand All @@ -91,18 +91,8 @@ For more information, see [Pods](https://kubernetes.io/docs/reference/kubectl/ch

To remove the Helm release, use:

`helm uninstall <RELEASE-NAME> <NAMESPACE-NAME>`

```bash
helm uninstall my-hami-webui -n hami
```

This removes the resources associated with that release in the `hami` namespace.

To delete the `hami` namespace (if you no longer need it):

```bash
kubectl delete namespace hami
helm uninstall my-hami-webui -n kube-system
```

## Related documentation
Expand Down
4 changes: 2 additions & 2 deletions docs/userguide/ascend-device/enable-ascend-sharing.md
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ spec:

1. Ascend-sharing in init container is not supported.

1. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend91B0=1`.
`huawe.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
1. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend910B=1`.
`huawei.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2 changes: 1 addition & 1 deletion docs/userguide/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can update these configurations using one of the following methods:
| `nvidia.resourceCountName` | String | vGPU number resource name. | `"nvidia.com/gpu"` |
| `nvidia.resourceMemoryName` | String | vGPU memory size resource name. | `"nvidia.com/gpumem"` |
| `nvidia.resourceMemoryPercentageName` | String | vGPU memory fraction resource name. | `"nvidia.com/gpumem-percentage"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/cores"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/gpucores"` |
| `nvidia.resourcePriorityName` | String | vGPU job priority name. | `"nvidia.com/priority"` |

## Node Configs: ConfigMap
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ When running `Kubernetes` with `Docker`, edit the configuration file, typically
And then restart `Docker`:

```
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -105,4 +105,4 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend91B0=1`, `huawe.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend910B=1`, `huawei.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ When running `Kubernetes` with `Docker`, edit the configuration file, typically
And then restart `Docker`:

```
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -105,4 +105,4 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend91B0=1`, `huawe.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend910B=1`, `huawei.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ When running `Kubernetes` with `Docker`, edit the configuration file, typically
And then restart `Docker`:

```
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -105,4 +105,4 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend91B0=1`, `huawe.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
2. `huawei.com/Ascend910B-memory` only work when `huawei.com/Ascend910B=1`, `huawei.com/Ascend310P-memory` only work when `huawei.com/Ascend310P=1`,etc..
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ When running `Kubernetes` with `Docker`, edit the configuration file, typically
And then restart `Docker`:

```
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend91B0=1`.
`huawe.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend910B=1`.
`huawei.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2 changes: 1 addition & 1 deletion versioned_docs/version-v2.5.1/userguide/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can update these configurations using one of the following methods:
| `nvidia.resourceCountName` | String | vGPU number resource name. | `"nvidia.com/gpu"` |
| `nvidia.resourceMemoryName` | String | vGPU memory size resource name. | `"nvidia.com/gpumem"` |
| `nvidia.resourceMemoryPercentageName` | String | vGPU memory fraction resource name. | `"nvidia.com/gpumem-percentage"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/cores"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/gpucores"` |
| `nvidia.resourcePriorityName` | String | vGPU job priority name. | `"nvidia.com/priority"` |

## Chart Configs: arguments
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ sudo nvidia-ctk runtime configure --runtime=docker
And then restart `Docker`:

```bash
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```


Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend91B0=1`.
`huawe.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend910B=1`.
`huawei.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2 changes: 1 addition & 1 deletion versioned_docs/version-v2.6.0/userguide/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can update these configurations using one of the following methods:
| `nvidia.resourceCountName` | String | vGPU number resource name. | `"nvidia.com/gpu"` |
| `nvidia.resourceMemoryName` | String | vGPU memory size resource name. | `"nvidia.com/gpumem"` |
| `nvidia.resourceMemoryPercentageName` | String | vGPU memory fraction resource name. | `"nvidia.com/gpumem-percentage"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/cores"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/gpucores"` |
| `nvidia.resourcePriorityName` | String | vGPU job priority name. | `"nvidia.com/priority"` |

## Chart Configs: arguments
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ sudo nvidia-ctk runtime configure --runtime=docker
And then restart Docker:

```bash
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```

#### Configure containerd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ spec:

1. Ascend-sharing in init container is not supported.

2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend91B0=1`.
`huawe.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend910B=1`.
`huawei.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2 changes: 1 addition & 1 deletion versioned_docs/version-v2.7.0/userguide/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ You can update these configurations using one of the following methods:
| `nvidia.resourceCountName` | String | vGPU number resource name. | `"nvidia.com/gpu"` |
| `nvidia.resourceMemoryName` | String | vGPU memory size resource name. | `"nvidia.com/gpumem"` |
| `nvidia.resourceMemoryPercentageName` | String | vGPU memory fraction resource name. | `"nvidia.com/gpumem-percentage"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/cores"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/gpucores"` |
| `nvidia.resourcePriorityName` | String | vGPU job priority name. | `"nvidia.com/priority"` |

## Node Configs: ConfigMap
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ sudo nvidia-ctk runtime configure --runtime=docker
And then restart Docker:

```bash
sudo systemctl daemon-reload && systemctl restart docker
sudo systemctl daemon-reload && sudo systemctl restart docker
```

#### Configure containerd
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -104,5 +104,5 @@ spec:

1. Ascend-sharing in init container is not supported.

1. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend91B0=1`.
`huawe.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
1. `huawei.com/Ascend910B-memory` only works when `huawei.com/Ascend910B=1`.
`huawei.com/Ascend310P-memory` only works when `huawei.com/Ascend310P=1`.
2 changes: 1 addition & 1 deletion versioned_docs/version-v2.8.0/userguide/configure.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ You can update these configurations using one of the following methods:
| `nvidia.resourceCountName` | String | vGPU number resource name. | `"nvidia.com/gpu"` |
| `nvidia.resourceMemoryName` | String | vGPU memory size resource name. | `"nvidia.com/gpumem"` |
| `nvidia.resourceMemoryPercentageName` | String | vGPU memory fraction resource name. | `"nvidia.com/gpumem-percentage"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/cores"` |
| `nvidia.resourceCoreName` | String | vGPU core resource name. | `"nvidia.com/gpucores"` |
| `nvidia.resourcePriorityName` | String | vGPU job priority name. | `"nvidia.com/priority"` |

## Node Configs: ConfigMap
Expand Down
Loading