You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CodeGen/README.md
+49-10Lines changed: 49 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,19 +106,58 @@ flowchart LR
106
106
107
107
This CodeGen example can be deployed manually on various hardware platforms using Docker Compose or Kubernetes. Select the appropriate guide based on your target environment:
_Note: The compose file might read additional variables from set_env.sh. Ensure all required variables like ports (`LLM_SERVICE_PORT`, `MEGA_SERVICE_PORT`, etc.) are setif not using defaults from the compose file._
@@ -146,7 +147,7 @@ Key parameters are configured via environment variables set before running `dock
146
147
Most of these parameters are in `set_env.sh`, you can either modify this file or overwrite the env variables by setting them.
147
148
148
149
```shell
149
-
source CodeGen/docker_compose/set_env.sh
150
+
source CodeGen/docker_compose/intel/set_env.sh
150
151
```
151
152
152
153
#### Compose Files
@@ -252,7 +253,63 @@ Users can interact with the backend service using the `Neural Copilot` VS Code e
252
253
- **"Container name is in use"**: Stop existing containers (`docker compose down`) or change `container_name`in the compose file.
253
254
- **Resource Issues:** CodeGen models can be memory-intensive. Monitor host RAM usage. Increase Docker resources if needed.
254
255
255
-
## Stopping the Application
256
+
## Monitoring Deployment
257
+
258
+
To enable monitoring for the CodeGen application, you can use the monitoring Docker Compose file along with the main deployment.
Copy file name to clipboardExpand all lines: CodeGen/docker_compose/intel/hpu/gaudi/README.md
+60-2Lines changed: 60 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,10 @@ This uses the default vLLM-based deployment using `compose.yaml`.
49
49
# export https_proxy="your_https_proxy"
50
50
# export no_proxy="localhost,127.0.0.1,${HOST_IP}" # Add other hosts if necessary
51
51
source intel/set_env.sh
52
-
cd /intel/hpu/gaudi
52
+
cd intel/hpu/gaudi
53
+
cd grafana/dashboards
54
+
bash download_opea_dashboard.sh
55
+
cd ../..
53
56
```
54
57
55
58
_Note: The compose file might read additional variables from set_env.sh. Ensure all required variables like ports (`LLM_SERVICE_PORT`, `MEGA_SERVICE_PORT`, etc.) are setif not using defaults from the compose file._
@@ -228,7 +231,62 @@ Use the `Neural Copilot` extension configured with the CodeGen backend URL: `htt
228
231
- **Model Download Issues:** Check `HF_TOKEN`, internet access, proxy settings. Check LLM service logs.
229
232
- **Connection Errors:** Verify `HOST_IP`, ports, and proxy settings. Use `docker ps` and check service logs.
230
233
231
-
## Stopping the Application
234
+
## Monitoring Deployment
235
+
236
+
To enable monitoring for the CodeGen application on Gaudi, you can use the monitoring Docker Compose file along with the main deployment.
0 commit comments