Re: Anouncement: ipvsman/d more than a GUI to IPVS

To: Manuel Arostegui Ramirez <manuel@xxxxxxxxxxxxxx>, <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: Anouncement: ipvsman/d more than a GUI to IPVS
From: "Dr. Volker Jaenisch" <volker.jaenisch@xxxxxxxxx>
Date: Mon, 30 Apr 2007 09:51:52 +0200
Hello Manuel!

Manuel Arostegui Ramirez schrieb:
El Sábado, 28 de Abril de 2007 22:50, Dr. Volker Jaenisch escribió:

I've already written an small module taking advantaje of ipvsadm output in order to know if any of the realserver went down, when went down I wanna mean one of the services the Real Server is supposed to serve, If so, and alert will be fired. I've also written some modules to get information about incoming packets/bytes to each node. This is simply, I know, but keep in mind this is a spefic solution a client wanted us to do. So first off, I did what they want, and now, we're using that to improve PandoraFMS and build some more generalistic modules to work with LVS solutions :-)
ipvsman/d does nothing magically or much more sophisticated as your straight 
forward aproach.
ipvsman also gets the information by calling ipvsadm and parsing the output.

But as i stated earlier ipvsmand has more (meta) information than that.
>/ It should be possible to write an interface (text-dump in file,/
>/ tcp-status-port, xml-rpc, ..) to retrieve/
>/ status information from the ipvsmand. You will know best what type of/
>/ interface you like the most for application in pandora/
>/ - just tell me./

Really? If it possible to get a dump file of all the data showed in ipvsmand? (I'm sorry I didn't go deep into ipvsmand, there's such a good weather in Madrid and I went out ;-) ) Having a dump file with all the data in plain text would be wonderful, cause to write a module to parse all that data and send it to the PandoraFMS server would be so easy and that's _exactly_ what we need.

There is one crucial point to mention. It is necessary, that ipvsman/d is used and not ldirectord nor keepalived for livekeeping. ipvsman can be used in parallel with ldirectord or keepalived. But ipvsman/d requires meta data (e.g. the topology) of the cluster. without this metadata it is nothing more than a parser to ipvsadm and therefore not of great use to you. Taking it the other way around a user with ipvsman AND an other livechecker has to maintain two configurations for one task. This you will agree seems not to be a good solution from the user perspective.

If your customer uses keepalived i recomend that you ask the people from keepalived to build an interface with pandora. :-)

If you have a customer using exclusively ipvsmand for livechecking than an interface between ipvsmand and pandora seems to be a fruitfull solution. You must decide if this limitation is ok for you?

Best regards


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

<Prev in Thread] Current Thread [Next in Thread>