-
Type:
Improvement
-
Status: Open
-
Priority:
3 - High
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Mission-Control
-
Labels:None
-
Environment:
CentOS/RedHat 7.7 and later
Versions: Mission Control 3.5.5 and later
Currently mission control runs under the old model of init scripts which is still supported in RedHat 7 through backwards compatibility. However, manually converting the service to use systemd unit files is a bit of a pain on the customer's side if they wish to use the more advanced systemd functionality.
I propose updating these sysV init scripts to systemd:
/etc/init.d/jfi-executor
/etc/init.d/jfi-insight-server
/etc/init.d/jfi-scheduler
/etc/init.d/mission-control
Additionally, service unit files would need to be created under /usr/lib/systemd/system like a standard rpm installation does in RedHat 7 and 8. Then service start would just be managed through systemctl start <service-name>. The components of the jfmc.sh should be integrated into the systemd startup scripts and that shell script should be deprecated as it wouldn't make sense once its components were integrated into the other scripts.