Thread: Re: [SSI] new HA-LVS daemon
Brought to you by:
brucewalker,
rogertsang
From: Alexandre C. <ale...@ca...> - 2002-06-19 11:06:43
|
Hi Aneesh, >I have put the files at >http://ssic-linux.sourceforge.net/contrib/ha-lvs.tar.gz . > >README.networking is also a part of the above tar.gz . If anybody need >README.networking I can do a separate check-in of that file alone ??? why not using directly Keepalived instead of backporting code to another tool ? since we have together added support to CI/SSI ? I don t understand :/ regards, Alexandre |
From: Alexandre C. <ale...@ca...> - 2002-06-19 11:53:58
|
> Hi Aneesh, > > >I have put the files at > >http://ssic-linux.sourceforge.net/contrib/ha-lvs.tar.gz . > > > >README.networking is also a part of the above tar.gz . If anybody need > >README.networking I can do a separate check-in of that file alone > > ??? why not using directly Keepalived instead of backporting code to > another tool ? since we have together added support to CI/SSI ? > > I don t understand :/ > > regards, > Alexandre Re, bellow, an example of Keepalived config for use with SSI : ! Configuration File for keepalived ! CI-LINUX configuration sample global_defs { notification_email { lvs...@do... } notification_email_from em...@do... smtp_server 192.168.200.1 smtp_connect_timeout 30 lvs_id CI-LNX } virtual_server 192.168.200.10 80 { delay_loop 10 lb_algo wrr lb_kind DR protocol TCP sorry_server 192.168.200.200 80 real_server 192.168.200.2 80 { weight 1 CI-LINUX } real_server 192.168.200.3 80 { weight 1 CI-LINUX } real_server 192.168.200.4 80 { weight 1 CI-LINUX } real_server 192.168.200.5 80 { weight 1 CI-LINUX } } Regards, Alexandre |
From: Aneesh K. K.V <ane...@di...> - 2002-06-19 13:19:33
|
Hi, Why i wrote the new HA-LVS was. (1). We need to automate the process of adding services to the LVS table. ( ipvsadm -A and ipvsadm -a commands ). ie, In the SSI cluster when a server binds to the CVIP it should automatically get added to the LVS table, (2) When the real server goes down it should remove all the services pertaining to that node. Keepalived brings in a very good service monitoring facility ( IP:PORT) and operate on service as and entity( correct me if am wrong ). I guess it should remain like that and bringing in the concept of node or IP alone is not the right thing. In fact what i really expect is if SSI is getting used for deploying web/mail/enterprise server where service is predefined the best method to go is for is keepalived. It is well tested. Many extensive features is supported. I can have priority in selecting directors and falls back to better one when the node comes back to the cluster. etc etc. But if there is a cluster where service are not predefined like HPTC applications then keepalived may not help . Because i really don't know what port the services are going to come up and keepalived cannot monitor it. So In my opinion both are going to stay with SSI , keepalived in a High availability deployment and the new HA-LVS in a HPTC requirement I don't know whether that make sense. ? But new- HA-LVS is still not a part of SSI CVS yet. I just uploaded the tar.gz. If it is not worth to have it we can always drop it. -aneesh On Wed, 2002-06-19 at 16:33, Alexandre CASSEN wrote: > > Hi Aneesh, > > >I have put the files at > >http://ssic-linux.sourceforge.net/contrib/ha-lvs.tar.gz . > > > >README.networking is also a part of the above tar.gz . If anybody need > >README.networking I can do a separate check-in of that file alone > > ??? why not using directly Keepalived instead of backporting code to > another tool ? since we have together added support to CI/SSI ? > > I don t understand :/ > > regards, > Alexandre > > > ---------------------------------------------------------------------------- > Bringing you mounds of caffeinated joy > >>> http://thinkgeek.com/sf <<< > > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel |