Changes for go-apps/meep-simu5g-mobility-adapter/README.md: 18 added lines, 3 removed lines.
Original line number
Diff line number
Diff line
# meep-simu5g-mobility-adapter
Runs on **NativeEdge Connector**. Listens for UDP telemetry from **Network Emulation Stack (Simu5G/SimuLTE)** (`UeTelemetryUdpSender`, port 9100) and publishes UE locations to GIS (TODO).
Runs on **NativeEdge Connector**. Listens for UDP telemetry from **Network Emulation Stack (Simu5G/SimuLTE)** (`UeTelemetryUdpSender`, port 9100) and publishes UE locations to `meep-gis-engine` via `POST /gis/v1/geodata/{assetName}`.
GIS asset names are `ue-car-*` / `ue-ped-*` from the companion YAML. The adapter talks to the GIS **ClusterIP** (no ingress session cookie). `--dry-run` skips GIS writes.
monaco-harbor must be **active** in the sandbox UI. NEM running on host S is not enough: GIS returns `No active scenario` until the companion scenario is loaded.
## Run (live, two-host)
Rebuild after pulling code:
```bash
go run .--config /path/to/simu5g-config.json
go build -o bin/meep-simu5g-mobility-adapter ./go-apps/meep-simu5g-mobility-adapter
Configure the Network Emulation Stack to send telemetry to `NativeEdgeConnectorNode:9100`.
Listens on **UDP 9100**. monaco-harbor INI must send to host B (`172.29.10.53:9100`). After each GIS write the adapter GETs `poaInRange` and logs when the set changes.
Optional: `--gis-url http://<gis-cluster-ip>/gis/v1` or `--sandbox <ns>` if `gis.sandboxName` in the JSON is wrong.