HAproxy is also very interesting. I fully agree
but then when I look at Zentyal implementation, I'm totally disappointed, perhaps because I was dreaming about something else
If one tell me "Zentyal is now bringing HAproxy in the landscape", what I'm thinking about is reverse proxy component that will permit to:
- act as reverse proxy for incoming (external) connections so that one can reach internal web servers in a secure, controlled and potentially authenticated manner
- act as HA component so that such component can be used as fail-over enabler in front of active/passive or, much better, active/active web servers
- act as load balancer to provide scale-out capability in case of service offered to large audience
I've installed 3.4 beta and as I wrote in
this post, if I remember well, HAproxy component is not exposed as an available component for system admins.
You will have it by default, this is your listener when accessing.... Zentyal GUI
- if you configure your Zentyal console to listen on port 1443, then:
- HA proxy listen on this port (1443)
- Nginx is configured to listen on port 61443
I didn't check but I suppose HAproxy is also in the scope of Zentyal cluster, or at least it will be. I do not intend to perform reverse engineering steps here in order to make some guesses.
Like HA, HAproxy may evolve (and I hope it will) but as of today, I do not perceive the real added value of such implementation.
If I add to give priority to features, HA in term of end-user access is more critical (and impacting) than HA for sys admin who can almost always find its way to access his system.
I would really like to be wrong with my analysis BTW. Let's wait for documentation...
my fears here being that documentation for "true" (exposed) components is made mainly of screen-shot, thus for "hidden" components, the risk that is is reduced to almost nothing is bigger
Am I the only one with this (wrong ?) perception