Re: [Ipvsman-users] ipvsman

[Dr. V. J. <vol...@in...>]

Hi Gerry!
Gerry Reno schrieb:
> Dr. Volker Jaenisch wrote:
>> Yes, but this feature is only one day old.
>> In principle there is no problem since ipvsman does only rely on the 
>> ipvs and the desired configuration but not on the daemon that 
>> controls the ipvs.
> Ok, so ipvsman is always looking at the ipvs kernel table for it's 
> information and does not interact directly with any daemon.
Exactly! Please have a look at 
http://wiki.inqbus.de/twiki/bin/view/Ipvsman/Dokumentation .
>>
>> So ipvsman uses the config file of keepalived and the status 
>> information of the ipvs and bring those two parts together in its GUI.
>> ipvsman is not a point and click GUI to interactively build the 
>> configuration file. In all cases you will have to build up a valid 
>> configuration file for keepalived (or for ipvsmand). ipvsman can be 
>> used without any configuration to adjust the weight of the 
>> realservers in realtime and have a look of the number of connections 
>> etc..
>> But if ipvsman should be able to take a realserver completely out of 
>> the loadbalancing it needs the meta information what realserver 
>> belongs to what service. So this functionality is only possible via a 
>> valid config file.
> Ok, so ipvsman cannot create a config file.  
ipvsman creates the desired configuration file. Its file format is 
compatible with ipvsadm -S -n.
> But if you use ipvsman to adjust the function of the realservers then 
> how can you preserve those changes over a reboot?
On reboot the ipvsmand will be started (if configured so). ipvsmand sets 
the state of the ipvs to that saved in the
actual desired config file.
>   Who/what takes care of changing the config file to reflect the 
> realtime changes you made with ipvsman?  
If you alter the state of the ipvs e.g. you adjust the weight of a 
realserver the daemon is not informed as long as you not
SAVE the actual config as the desired config. If you add or remove a 
realserver this changes will be told the
daemon exactly at the time you press OK in the gui. This was one of the 
mayor changes today. I am not absolutly happy with
that solution. From the point of the enduser it is ok - it looks as if 
ipvsman drives the daemon directly.
But this
1) is not the truth
2) is a simplification that can lead to errors
3) can lead people to the conclusion that ipvsman/ipvsmand is not as 
stable as an other lifekeeper since the GUI can interact with the daemon.

>>
>> Yesterday I wrote an import-filter for the keepalived.conf file which 
>> is included in the current release. You are welcome to be my first 
>> tester. To use the keepalived feature please run ipvsman this way:
>> #ipvsman -k
>> Just try it out and keep me informed.
> Yes, I think I will try this.  I should have time in about 2-3 days to 
> start.
cool. I like that. I will give you the best support.
>>
>> Due to the complete rewrite of the code for this public release lots 
>> of bugs were born. The ipvsmand part was severely broken. I'm just 
>> doing the fixes. Tomorrow you can expect 0.9.1-6 with smothly running 
>> ipvsmand.
> That sounds good.
Please use 0.9.1-7 released now. I have done lots of testing.
Fixed a whole bunch of bugs and the code has found its way back to 
stability.

Best regards

Volker

-- 
====================================================
   inqbus it-consulting      +49 ( 341 )  5643800
   Dr.  Volker Jaenisch      http://www.inqbus.de
   Herloßsohnstr.    12      0 4 1 5 5    Leipzig
   N  O  T -  F Ä L L E      +49 ( 170 )  3113748
====================================================