You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 21, 2021. It is now read-only.
One of the core components of the Agent will be to manage processes.
We decided to use systemd as the tool doing the actual supervision as it's available on all our target systems (Debian, Ubuntu, RHEL).
The Agent needs a way to manager systemd Units and this ticket is about implementing this functionality.
Every time a process starts it'll need configuration data on disk which needs to be materialized from configuration in the Operator/Orchestrator resources.
To make debugging easier we'd like to have a new uniquely named directory in a configurable location (e.g. /var/run/stackable/...) which has all the files a process needs.
An open question is whether restarts due to failure reuse an existing configuration directory or not.
This is the epic for this task and these are the dependencies:
Implement systemd unit monitoring #10 Receive and process notifications from systemd about process state changes (e.g. a process dying or restarting) - this will probably happen via D-Bus
One of the core components of the Agent will be to manage processes.
We decided to use systemd as the tool doing the actual supervision as it's available on all our target systems (Debian, Ubuntu, RHEL).
The Agent needs a way to manager systemd Units and this ticket is about implementing this functionality.
Every time a process starts it'll need configuration data on disk which needs to be materialized from configuration in the Operator/Orchestrator resources.
To make debugging easier we'd like to have a new uniquely named directory in a configurable location (e.g. /var/run/stackable/...) which has all the files a process needs.
An open question is whether restarts due to failure reuse an existing configuration directory or not.
This is the epic for this task and these are the dependencies:
Open Issues/questions:
The text was updated successfully, but these errors were encountered: