Hi there, glad to join the new community…I have discovered this channel only recently and I am happy to read about your proj!
I have been working on a project of my own, called Krill, it manages orchestrations of multi processes. It is designed to be a simple recipe holding all the necessary info for running an entire app and a tui for states, logs and actions.
It has been created to support robotics and with Ros2 in mind, although it is inspired by some other infra tools.
seems a nice work, but not clear to me what really means a “process”.
Looking at the YAML file, I see that the camera, navigation, and dashboard are all modeled using the same abstraction. While that keeps things consistent, it could make the YAML quite verbose in more complex scenarios. I think it might beneficial to introduce some layering in the YAML to improve readability and scalability.
Does it also happen to krill that sometimes the manager dies, but the managed processes still live? Because ros2launch and gz-launch are both very well known for this behavior. Is there some trick we could reuse so that we finally have the reliable process managers we deserve?
