Deployments
Field deployment history of model versions, per-step progress, health checks, logs and rollback.
Required permission: View
This screen shows the records of model versions deployed to targets (field devices and so on). Each deployment goes through build → push → pull → health → activate in order. The screen shows each step's result, the health checks and the logs. Every member can view; new deployments need deploy (OPERATOR, ADMIN) and rollback needs rollback (ADMIN).
Deployment list
| # | Area | Description |
|---|---|---|
| ① | Status filter | All, In progress, Succeeded, Failed, Rolled back. In progress (진행중) and Succeeded (성공) do not match the server status values (IN_PROGRESS, ACTIVE), so they always return 0 results. Find in-progress or successful deployments under All (전체). |
| ② | New deployment (새 배포) | Opens the deployment dialog (deploy). |
| ③ | Deployment | Model and version, target, strategy, status, time (created). Newest first, refreshed every 60 seconds. Click to open the detail. |
Deployment detail
| # | Area | Description |
|---|---|---|
| ① | Deployment info (배포 정보) | Strategy, target, previous version, start, end. For deployments created from this screen the previous version is —. Errors (including the rollback reason) are shown in red. Click the model version in the title to open the model version detail. |
| ② | Roll back (롤백) | Rollback confirmation dialog (rollback, ADMIN). Disabled on a deployment that is already rolled back. |
| ③ | Progress steps (진행 단계) | Result and duration of the Build · Push · Pull · Health · Activate steps. A step with no record shows PENDING. |
| ④ | Health check (헬스 체크) | Post-deployment check results. When all steps pass, inference_smoke: PASS is recorded. |
| ⑤ | Logs | Per-step logs and Download (다운로드). Visible only with the operate permission. |
Main tasks
New deployment
- Press New deployment (새 배포).
- Set the model name (모델 이름), version (버전) (for example 3), target device ID (대상 디바이스 ID) (optional; a device ID from Edge Fleet) and deployment strategy (배포 전략) (Rolling · Blue-Green · Canary), then press Deploy (배포). The model name and version are not checked against the model registry, and the strategy is only recorded.
New deployment — model name, version, target device and strategy - Once started, the deployment detail opens and shows the step progress.
Rollback
- On the deployment detail, press Roll back (롤백).
- In the confirmation dialog, press Run rollback (롤백 실행). The status changes to ROLLED_BACK at once.
Rollback confirmation — Run rollback changes the status to ROLLED_BACK
Statuses and badges
Deployment status is shown in English as is.
| Value | Color | Meaning |
|---|---|---|
| IN_PROGRESS | Blue | Going through the steps. A deployment created from this screen finishes its steps within the request, so this is rarely seen |
| ACTIVE | Green | Passed all steps and activated |
| FAILED | Red | Failed at some step — check the progress steps and logs |
| ROLLED_BACK | Yellow | Rolled back. The reason is kept in the error field of the deployment info (manual rollback for a manual rollback). |
Step statuses are RUNNING · SUCCEEDED · FAILED.