Actions
User story #6475
closedGeneric rudder init script
Status:
Rejected
Priority:
2
Assignee:
Matthieu CERDA
Category:
System integration
Target version:
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We rely on multiple init scripts (rudder-jetty, rudder-slapd, rudder-server-root, rudder-agent).
Problem is, it causes:- Dependency problems on old inits
- Consistency issues (the "status" command outputs different patterns on all commands...)
- Remove the rudder-server-root script
- Package a "rudder" one in the rudder-agent package, that would:
- Handle dependencies correctly (jetty comes after slapd and postgres)
- Output things consistently
- Ease support of alternative init systems (systemd, launchd, OpenRC, SMF, ...) => only one job/unit/... to create
- Our rudder script to handle depdendencies if needed
- A dependency aware init system if available, that would reduce further the complexity of our code (init handles the dependencies itself, not us)
- role-aware (an absent role is not to be started)
- nice on the eyes (colors, consistent output, clear)
- clean and easy to maintain
Actions