[X2Go-Dev] Bug#684: Bug#684: select_session offers offline servers to X2Go Client
If you make a x2goclient connection to each farm server, then time will be increased by seconds for such connection. And if the server farm consist of more then 2-3 servers, then connection time will increase strongly. - Исходное сообщение - Plus, I still think, that X2Go Client should request another machine, if the provided server was offline and more than one server is configured in the broker's session profile. ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#684: Bug#684: select_session offers offline servers to X2Go Client
clone #684 -1 retitle -1 select_session offers offline servers to X2Go Client thanks Hi Sergey, On So 07 Dez 2014 00:45:28 CET, Sergey Savko wrote: If the server will give the address to which it can not connect, there will be no load balancing works. Since the server is connected to receive the coefficient of loading. Actually, after a third or fourth though: in cases where we use SSH to connected from broker server to broker agent, there we can evaluate the online status of the X2Go Server. So, in those cases we should filter out, if a server is down or not and exclude that server from the list of possible X2Go Servers. Plus, I still think, that X2Go Client should request another machine, if the provided server was offline and more than one server is configured in the broker's session profile. So, cloning this bug again... #684: for tracking the new feature of re-requesting a server address new bug: filter out offline servers on the broker side already Greets, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpQScLMf6Y1k.pgp Description: Digitale PGP-Signatur ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#684: Bug#684: select_session offers offline servers to X2Go Client
Control: clone -1 -2 -3 Control: reassign -2 x2goclient Control: reassign -3 python-x2go Control: retitle -1 add exclude-hosts parameter to selectsession task Control: retitle -2 request another server from broker provided server is down Control: retitle -3 request another server from broker provided server is down Control: severity -1 wishlist Control: severity -2 wishlist Control: severity -3 wishlist Control: block -2 by -1 Control: block -3 by -1 Control: tag -1 - patch Hi Sergey, On Fr 05 Dez 2014 17:14:51 CET, Sergey Savko wrote: This patch work after patch from http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=686 After thinking this through a little, I come to the conclusion that the broker cannot decide if a machine is down or not. We have to think very generically. There may be a scenario where the broker machine may be on an network segment where it cannot ping/reach the X2Go Servers. The X2Go Clients can reach the X2Go Broker. The broker provides an X2Go Server address on the selectsession broker task to the X2Go Client. Then the X2Go Client should test if that X2Go Server address works (via a simple ping6/ping command, machines should always be pingable!!!). If the ping fails, X2Go Client should go back to the broker and say: hey, that server failed for me, give me another one (but not the one you already gave me). I fear we need to do four things for this bug to get fixed: 1. extend broker/client communication protocol (second/third/... selectsession call with a list of hosts that did not work on previous attempts) 2. extend X2Go Session Broker with an exclude-hosts (or so) parameter for the selectsession task 3. Adapt X2Go Client: ping X2Go Server, go back to the broker if server is down and request another server 4. Adapt Python X2Go: dito Regards, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpm3tHfEX52N.pgp Description: Digitale PGP-Signatur ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
[X2Go-Dev] Bug#684: Bug#684: select_session offers offline servers to X2Go Client
If the server will give the address to which it can not connect, there will be no load balancing works. Since the server is connected to receive the coefficient of loading. - Исходное сообщение - От: Mike Gabriel mike.gabr...@das-netzwerkteam.de Кому: Sergey Savko sa...@tophouse.ru, 6...@bugs.x2go.org Отправленные: Воскресенье, 7 Декабрь 2014 г 1:56:05 Тема: Re: [X2Go-Dev] Bug#684: select_session offers offline servers to X2Go Client Control: clone -1 -2 -3 Control: reassign -2 x2goclient Control: reassign -3 python-x2go Control: retitle -1 add exclude-hosts parameter to selectsession task Control: retitle -2 request another server from broker provided server is down Control: retitle -3 request another server from broker provided server is down Control: severity -1 wishlist Control: severity -2 wishlist Control: severity -3 wishlist Control: block -2 by -1 Control: block -3 by -1 Control: tag -1 - patch Hi Sergey, On Fr 05 Dez 2014 17:14:51 CET, Sergey Savko wrote: This patch work after patch from http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=686 After thinking this through a little, I come to the conclusion that the broker cannot decide if a machine is down or not. We have to think very generically. There may be a scenario where the broker machine may be on an network segment where it cannot ping/reach the X2Go Servers. The X2Go Clients can reach the X2Go Broker. The broker provides an X2Go Server address on the selectsession broker task to the X2Go Client. Then the X2Go Client should test if that X2Go Server address works (via a simple ping6/ping command, machines should always be pingable!!!). If the ping fails, X2Go Client should go back to the broker and say: hey, that server failed for me, give me another one (but not the one you already gave me). I fear we need to do four things for this bug to get fixed: 1. extend broker/client communication protocol (second/third/... selectsession call with a list of hosts that did not work on previous attempts) 2. extend X2Go Session Broker with an exclude-hosts (or so) parameter for the selectsession task 3. Adapt X2Go Client: ping X2Go Server, go back to the broker if server is down and request another server 4. Adapt Python X2Go: dito Regards, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb ___ x2go-dev mailing list x2go-dev@lists.x2go.org http://lists.x2go.org/listinfo/x2go-dev
