The production setup mostly splits the stack into separate service containers. The main migrid container still runs multiple services due to service dependencies and in practice keeps the dependencies internal to the container.
The other containers are mostly independent as long as they share the user data file system(s) and a few additional state folders like mig_system_run.
Some services and facilities like the auth notifications additionally rely on ''named pipes'' in the file system for inter-process communication.
All such internal and external dependencies must be identified and at least documented. Providing suggestions on how they can be managed in a distributed setup is a next logical step and outlining or supporting a distributed production setup would be the final goal. This could involve docker swarm mode or manual distribution of containers.
The
productionsetup mostly splits the stack into separate service containers. The mainmigridcontainer still runs multiple services due to service dependencies and in practice keeps the dependencies internal to the container. The other containers are mostly independent as long as they share the user data file system(s) and a few additional state folders likemig_system_run. Some services and facilities like the auth notifications additionally rely on ''named pipes'' in the file system for inter-process communication. All such internal and external dependencies must be identified and at least documented. Providing suggestions on how they can be managed in a distributed setup is a next logical step and outlining or supporting a distributedproductionsetup would be the final goal. This could involve dockerswarm modeor manual distribution of containers.