Lars Marowsky-Bree wrote:
On 2005-12-06T11:12:52, Alan Robertson <[EMAIL PROTECTED]> wrote:
Shouldn't this be a resource? You need a cluster IP, after all, as
there is no default cluster IP? Otherwise, how would anyone know what
node to direct it to. If the node you've chosen is down, you would have
to manually choose another IP.
But, if you make it a cluster resource, then it will be highly available :-)
As pointed out, how do you configure the cluster ip though? ;-)
I'd simply run the management daemon on each and every node. One could
then connect either to the admin IP of each node (maybe via the
management net only based on ACLs), or to a "Cluster IP" as soon as one
is added to the cluster (probably co-located with DC status)...
If it didn't require the administrator to be smarter, and work harder, I
like the idea of just running it once. But, it _does_ require them to
be smarter and work harder - so I guess I've changed my mind.
Your current scheme will work nicely.
--
Alan Robertson <[EMAIL PROTECTED]>
"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/
