[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Hobbit following cluster nodes (or can I include a file in localclient.cfg)


  I have a passive/active cluster on 2 Linux servers : 
   * on machine MA :
       - we use to run the applications A01 and A02
       - with the IP addresses IP0A and logical IP0A:1
       - we want to monitor file systems FS01, FS02, applications A01 and

    * on machine MB :
       - we use to run the applications B01 and B02
       - with the IP addresses IP0B and logical IP0B:1
       - we want to monitor file systems FS03, FS04, applications B01 and

  My first solution was to install one hobbit client on each machine MA and
  Problems occurs when the cluster switch from a node to the second node : 
   - Applications A01 and A02 could be started on machine MB who keep
running applications B01 and B02. Machine MB will have 4 file systems now :
FS01, FS02, FS03, FS04 to monitor and 3 IP addresses : IP0B, IP0B:1 and
   - Also, it possible to have the opposite : all applications (and file
systems and IPs) could be on machine MA.
   - Finally, applications can be switch from MA to MB : FS03, FS04, B01
and B02 and IP0B:1 could be run on MA and machine MB could run FS01, FS02,
A01 and A02 and IP0A:1

  As you can guess, it's a total mess to monitor. Everything is in red when
machine MA acts as MB and so on. We had several ideas : 
   1) Install a hobbit Client linked to the application cluster group of
[A01,A02] and [B01,B02], it will follow the applications who needs to be
      -> problem : when everything is running on only one machine, the
second one switch to PURPLE (none hobbit clients report datas)
   2) Install a hobbit Client linked to the application cluster group of
[A01,A02] and [B01,B02] and also install another hobbit client on each
      -> problem : with 2 machines, one could be running 3 hobbit client
are the same time, image with 4 node cluster, one machine could run 5
hobbit clients each on them checking RAM, CPU, disk space... Not a solution
   3) Install a Hobbit client on each machine, switch the hobbit client
configuration to the server (not LOCAL mode)
      -> problem : I still have install 2 clients each following the
application cluster group. 
                   The hobbit client use the first IP of the machine IP0A
on machine MA (eth0). Can I force to use the virtual IP (IP0A:1 = eth0:1) ?

 Any ideas is welcome! Thanks by advance!