diff --git a/docs/installation/how-to-use-volcano-vgpu.md b/docs/installation/how-to-use-volcano-vgpu.md index b581bcb5..99fe714e 100644 --- a/docs/installation/how-to-use-volcano-vgpu.md +++ b/docs/installation/how-to-use-volcano-vgpu.md @@ -61,7 +61,7 @@ kubectl create -f https://raw.githubusercontent.com/Project-HAMi/volcano-vgpu-de Check the node status, it is ok if `volcano.sh/vgpu-number` is included in the allocatable resources. ```shell -kubectl get node {node name} -oyaml +kubectl get node -oyaml ``` ```yaml @@ -129,5 +129,5 @@ If you do not request GPUs when using the device plugin with NVIDIA images, all volcano-scheduler-metrics records all GPU usage and limits. Visit the following address to get the metrics. ```shell -curl {volcano scheduler cluster ip}:8080/metrics +curl :8080/metrics ``` diff --git a/docs/userguide/monitoring/device-allocation.md b/docs/userguide/monitoring/device-allocation.md index 5efb93c3..9e43e22f 100644 --- a/docs/userguide/monitoring/device-allocation.md +++ b/docs/userguide/monitoring/device-allocation.md @@ -3,10 +3,10 @@ title: Cluster device allocation endpoint sidebar_label: Cluster device allocation --- -You can get the overview of cluster device allocation and limit by visiting `{scheduler node ip}:31993/metrics`, or add it to a prometheus endpoint, as the command below: +You can get the overview of cluster device allocation and limit by visiting `:31993/metrics`, or add it to a prometheus endpoint, as the command below: ```bash -curl {scheduler node ip}:31993/metrics +curl :31993/metrics ``` It contains the following metrics: diff --git a/docs/userguide/monitoring/real-time-device-usage.md b/docs/userguide/monitoring/real-time-device-usage.md index 2083d777..204d4b2c 100644 --- a/docs/userguide/monitoring/real-time-device-usage.md +++ b/docs/userguide/monitoring/real-time-device-usage.md @@ -3,10 +3,10 @@ title: Real-time device usage endpoint sidebar_label: Real-time device usage --- -You can get the real-time device memory and core utilization by visiting `{GPU node ip}:31992/metrics`, or add it to a prometheus endpoint, as the command below: +You can get the real-time device memory and core utilization by visiting `:31992/metrics`, or add it to a prometheus endpoint, as the command below: ```bash -curl {GPU node ip}:31992/metrics +curl :31992/metrics ``` It contains the following metrics: diff --git a/docs/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md b/docs/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md index c6e647c1..207a534d 100644 --- a/docs/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md +++ b/docs/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md @@ -61,7 +61,7 @@ kubectl create -f https://raw.githubusercontent.com/Project-HAMi/volcano-vgpu-de Check the node status, it is ok if `volcano.sh/vgpu-number` is included in the allocatable resources. ```shell -kubectl get node {node name} -oyaml +kubectl get node -oyaml ``` ```yaml @@ -129,5 +129,5 @@ If you do not request GPUs when using the device plugin with NVIDIA images, all volcano-scheduler-metrics records all GPU usage and limits. Visit the following address to get the metrics. ```shell -curl {volcano scheduler cluster ip}:8080/metrics +curl :8080/metrics ``` diff --git a/docs/userguide/volcano-vgpu/nvidia-gpu/monitor.md b/docs/userguide/volcano-vgpu/nvidia-gpu/monitor.md index df50f0cf..ac39f5b0 100644 --- a/docs/userguide/volcano-vgpu/nvidia-gpu/monitor.md +++ b/docs/userguide/volcano-vgpu/nvidia-gpu/monitor.md @@ -5,7 +5,7 @@ title: Monitor volcano-vgpu volcano-scheduler-metrics records all GPU usage and limits. Visit the following address to get the metrics. ```shell -curl {volcano scheduler cluster ip}:8080/metrics +curl :8080/metrics ``` It contains the following metrics: