RE: 2 Real Servers & 2 Directors with only 2 machines

Below is a link to a post by Sebastien's re director failover with
parameters for commands to be run when a director become active and inactive
(active_cmd , inactive_cmd) ... From other posts I have read I am sure that
Sebastien has also said that his request was logged it with Redhat. But that
was back in Dec2002. 

http://www.redhat.com/archives/piranha-list/2002-December/msg00017.html


Can this be added as an enhancement to Piranha as I would think that a lot
of people would find it very very use full.





-----Original Message-----
From: Mike McLean [mailto:[email protected]]
Sent: Wednesday, 4 February 2004 7:04 AM
To: [email protected]
Subject: Re: 2 Real Servers & 2 Directors with only 2 machines


Edward Croft wrote:
> Greg, with Sebastien's permission, I submitted his changes to Red Hat,
> but I think that they have all but abandoned piranha in favor of Cluster
> Manager. Shame too, since piranha seems to work fairly well for
> failover. 

Not abandoned.  Piranha has two modes, FOS and LVS.  When Cluster 
Manager was added to the distro, we had two different products for 
failover.  Since Cluster Manager is superior in the failover department 
it became the preferred solution and Piranha's FOS mode became deprecated.

However, Piranha's LVS mode (which really is its main feature) is still 
the preferred way to perform load balancing.  Failover between the two 
directors is also still supported.

I cannot find an RFE in bugzilla regarding the failover script patch. 
If this applies to director failover I will consider putting it in.


_______________________________________________
Piranha-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/piranha-list


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************