Hello,
The system has 2 nodes: NodeA (active) and NodeB (passive). I want to design a
scheme for updating the software and it seems that updating the passive node,
forcing a failoverm, and updating the now passive (formerly active) node should
work (actually seems like the trivial thing to do:) ). If I pull this off I
should have the new software installed on both node, with NodeB active and
NodeA passive. Any reason why this would not be a good approach? Any other
suggestions?
If the above is a good way to go, I wonder how can I interact with the passive
node from outside the 2-node system. My understanding is that the entire system
is seen from the outside as a single entity behind one IP address which
identifies the active node (which can change in case of a failover). In this
case, how do I get to talk to the passive node and prepare the new software on
it? Let's assume the upgrade is as easy as copying file.ext on the passive
node. It seems running a custom piece of software on the active node (that can
be reached from "outside") and have it do things on my behalf on the passive
node (reachable vis the internal or backplane communication) might be a
solution. Is there such a mechanism already provided or do I need to write this
myself? Any other ideas about how to do this?
I have to mention I have no hands-on experience yet and as you can see my
discussion is at a theoretical level for now.
Thanks for any suggestions,
Radu
____________________________________________________________________________________
Tonight's top picks. What will you watch tonight? Preview the hottest shows on
Yahoo! TV.
http://tv.yahoo.com/
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
