[Top][All Lists]

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

Re: Failover redundancy in policyhosts

From: Mark . Burgess
Subject: Re: Failover redundancy in policyhosts
Date: Wed, 26 Jun 2002 07:59:49 +0200 (MET DST)

You could use define= or elsedefine= to trigger new things
based on what the outcome of the copy was. The only disadvantage
is that if no file is copied at all, it will check every policy
host... I shall think about a better way.


On 25 Jun, Paul Paradise wrote:
> Hi all,
> I'm looking at the feasibility of a cfengine distribution across about
> 1000 Solaris 6-8, HPUX 10.20-11i, and Linux machines. With a network
> of this size we're specifically looking at some form of redundant
> policyhost ability.
> While it's easy to distribute the load by defining policyhost based on
> classes and using a splay time, we're planning on distributing a lot
> of files via the copy action from a remote server, but we'd like the
> ability to do something like this:
> control:
>     policyhost = ( copy1 copy2 copy3 )
>     actionsequence = ( copy )
> copy:
>     /files dest=/tmp m=644 server=$policyhost
> I can emulate this by assigning copyhosts to one host based on some
> class and varying the host, but I want the ability to fail over to
> another host in the list if the client cannot connect to the server.

Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :

reply via email to

[Prev in Thread] Current Thread [Next in Thread]