serviced roadmap #1

New Issue

Open

opened 2025-09-21 19:16:00 +00:00 by ryan · 0 comments

ryan commented

2025-09-21 19:16:00 +00:00

Owner

serviced pivots to pid1 to take over after nit sets up the essentials. Its goal is to act as a service manager and reaper.

Config format should be TOML, styled similarly to how systemd and supervisord work. Dependencies should be a thing, and we should support some way to check whether a process is considered "ready" - whether a socket is listening, whether a file has been created, etc. to ensure dependencies are loaded when they're ready, alongside oneshot binaries.

Goals in order are:

Reaper
Long-lived binaries
Oneshot binaries
Dependency binaries
Liveness checks or delays for dependencies
- Timer
- Socket exists
- File exists

serviced pivots to pid1 to take over after `nit` sets up the essentials. Its goal is to act as a service manager and reaper. Config format should be TOML, styled similarly to how systemd and supervisord work. Dependencies should be a thing, and we should support some way to check whether a process is considered "ready" - whether a socket is listening, whether a file has been created, etc. to ensure dependencies are loaded when they're ready, alongside oneshot binaries. Goals in order are: * [ ] Reaper * [ ] Long-lived binaries * [ ] Oneshot binaries * [ ] Dependency binaries * [ ] Liveness checks or delays for dependencies * [ ] Timer * [ ] Socket exists * [ ] File exists

ryan added this to the Verifiable Compute Platform project 2025-09-21 19:16:00 +00:00

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: public/serviced#1

No description provided.