add Hero OS and the orchestrator (hero_orchestrator) to the sandbox as apps #257
Labels
No labels
meeting-notes
meeting-transcript
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#257
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add Hero OS itself and the orchestrator (hero_orchestrator) to the Hero sandbox as apps, alongside the other catalog apps. Hero OS as an app is worth doing because the full desktop is impressive to show, and the orchestrator gives the sandbox a way to drive updates and multi-service operations from inside the product. For each one this means deciding whether it ships in the per-tester install bundle or as a shared service on the admin VM, wiring its sockets and a gateway route like the other apps, and giving it a tile in the cockpit. Same integration pattern as #254 (the hero_livekit backlog item). This is a backlog item to pick up after the current roadmap, not now. We will know it is done when a tester can open both Hero OS and the orchestrator from their cockpit. Related: #239.
Signed-by: mik-tf mik-tf@noreply.invalid
Backlog: add Hero OS and the orchestrator (hero_orchestrator) to the sandbox as appsto add Hero OS and the orchestrator (hero_orchestrator) to the sandbox as apps