Complete OCM Server Migration to Dashboard

techsfree-web-01: Complete OCM Server Migration to Dashboard — Retiring the Dual System Root Cause: Two Systems, Two Data Sources, One Big Mess When I took over the system, I discovered a serious data source problem: The "node management UI" users see ← Actually Dashboard v1's embedded feature Dashboard node data ← Uses hardcoded BOTS_DATA , completely outdated OCM Server (8001) ← Accurate data, but no frontend UI Result : T440 server actually has 9 Bots, Dashboard shows 4 This isn't a minor discrepancy — it's fundamental data chaos. The only solution: pipe OCM Server's accurate data into Dashboard, then retire OCM Server. Migration Implementation The core work broke down into three blocks: 1. SSH Function Porting Moved the ssh_cmd() function and node status query logic from OCM Server to server.py , enabling real-time SSH connections to each node for data retrieval. 2. Replacing Hardcoded Data with APIs /api/nodes-status → Real-time node status via SSH /api/node-bots → Real-time Bot l