LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

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

To: "Dr. Volker Jaenisch" <volker.jaenisch@xxxxxxxxx>
Subject: Re: Anouncement: ipvsman/d more than a GUI to IPVS
Cc: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: Manuel Arostegui Ramirez <manuel@xxxxxxxxxxxxxx>
Date: Tue, 1 May 2007 09:43:16 +0200
El Lunes, 30 de Abril de 2007 09:51, escribió:
>
> 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.

I already supposed that. There's not so much more information available from 
calling ipvsadm than the one I wrote the module for. But, that's the reason I 
said ipvsman can help me, to find out all the one which is available. I'm not 
an expert in LVS, so I'll be probably missing something important, so that's 
why I wanted to take a deep look into ipvsman :-)

>
> 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
>
> Volker

I think you misunderstood me.
Our costumer already has want he wants, he paid us to do what he wanted and we 
did, that's all.
The point here is trying to use your knowledge about ipvsadm to improve our 
Free Software Project, just trying to make PandoraFMS to be able to keep 
monitorice LVS with a new module. As I said on my previos emails, I wrote 
down one, but I suppose it's not as good as it could be.
I mean, if someone wants to use PandoraFMS with a LVS+Keepalive system, it's 
possible to use the module I wrote, it's actually quite good and keep the 
basics or the useful information about LVS and Keepalive under control.
But on the other hand, if they satisfy the requirements of ipvsman, this 
person can use the other module in order to find out all that ipvsman is able 
to get.
Hope you understand more or less what I mean right now.
As a resume, a text file with the output of ipvsman could let me write another 
module which let the user get much more information. Aside from the one I 
already wrote.

All the best.
Manuel
-- 
Manuel Arostegui Ramirez.

Electronic Mail is not secure, may not be read every day, and should not
be used for urgent or sensitive issues.

<Prev in Thread] Current Thread [Next in Thread>
  • Re: Anouncement: ipvsman/d more than a GUI to IPVS, Manuel Arostegui Ramirez <=