El 28/08/17 a les 15:04, Cédric Krier ha escrit:
It is not for me because the problem is in the UI because admin user is
not necessary and server administrator. But if the feature is limited to
server administrator, there is no problem.
When using an orchestration system (like kubernetes), there is no tryton
server administration because the system administrator only administres
the orchestration system, and is this system which manages the
applications states.
In kubernetes this is managed by using Readyness proves [1], which will
query (on an interval time) to each server if it's ready to serve and
restart it if not ready. Having some pragmatic way to know if the
process pool have all the required modules, will allow to solve the
problem for us.
[1]
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-probes/
--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk
--
You received this message because you are subscribed to the Google Groups
"tryton-dev" group.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tryton-dev/c3380cf8-c009-9ee6-f422-1734b010e49b%40koolpi.com.