+43
−0
+30
−0
+214
−8
go-apps/meep-dai/server/api_unsupported.go
deleted100644 → 0
+0
−32
Loading
This commit introduces a new experimental Dynamic Application Catalog feature in the frontend (Admin Console) and backend (virt-engine), allowing users to onboard new .tgz applications dynamically. It ensures full compliance with the MEC 016 GS specification by allowing the Device Application Interface (DAI) to track both dynamically onboarded apps and statically deployed scenario applications. Key features and changes: - Added a frontend Application Catalog page to the Admin Console for uploading .tgz application packages. - Implemented an onboard_app handler in meep-virt-engine to persist onboarded application metadata in a dedicated Persistent Volume (/data/app-catalog/app_catalog.json). - Updated meepctl to properly inject NGINX authentication annotations for the virt-engine endpoints, securing the onboard API. - Re-architected meep-dai to retrieve dynamic applications from virt-engine upon initialization using an internal FQDN to resolve cross-namespace DNS requests. - Merged active scenario processes (NodeTypeEdgeApp) with dynamically onboarded applications directly in the DAI Service Boundary Interface (SBI) to ensure the GET /app_list endpoint returns a comprehensive list of all applications running in the MEC Sandbox. - Resolved a runtime panic in meep-dai caused by missing AppLocation objects by gracefully handling nil pointers during ApplicationList construction. - Corrected Kubernetes Ingress templates and values for meep-virt-engine to ensure proper routing and prevent 404 Not Found errors.