On Tue, Jul 12, 2016 at 2:02 PM, Anuruddha Liyanarachchi <
[email protected]> wrote:
> Hi,
>
> I have configured cookie based sticky sessions with marathon-lb for wso2
> servers using JSESSIONID. The following labels are required to generate the
> correct ha-proxy config values and should be passed in the application
> definition.
>
> "labels": {
> "HAPROXY_1_GROUP": "marathon-lb",
> "HAPROXY_2_GROUP": "marathon-lb",
> "HAPROXY_2_BACKEND_SERVER_OPTIONS": " server {serverName}
> {host_ipv4}:{port}{cookieOptions} ssl verify none \n",
>
A production deployment would need SSL verification enabled. Therefore, we
might need to clearly mentioned that it in the documentation/README.md
files.
> "HAPROXY_2_BACKEND_STICKY_OPTIONS": " cookie JSESSIONID prefix
> nocache \n",
> "HAPROXY_2_STICKY": "true",
> "HAPROXY_2_SSL_CERT": "/etc/ssl/cert.pem",
>
> "HAPROXY_2_MODE": "http"
> },
>
>
We would need to explain what n means in HAPROXY_{n}_ labels and how to
apply this to a specific set of ports.
> Shall we add these labels to our mesos artifacts to enable sticky session
> with 9443 port ?
>
> Yes please, will add this to all the management console/UI transports in
all Marathon applications.
Thanks
>
> [1] https://github.com/mesosphere/marathon-lb/blob/master/Longhelp.md
>
> --
> *Thanks and Regards,*
> Anuruddha Lanka Liyanarachchi
> Software Engineer - WSO2
> Mobile : +94 (0) 712762611
> Tel : +94 112 145 345
> a <[email protected]>[email protected]
>
--
*Imesh Gunaratne*
Software Architect
WSO2 Inc: http://wso2.com
T: +94 11 214 5345 M: +94 77 374 2057
W: https://medium.com/@imesh TW: @imesh
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
