RE: Strategy for "one-off" tasks

[Nielsen, Steve]

This is something that I have been wanting to tackle for a while as well.
Just have not had the time to get around to it. The controlled roll-out
should also include some way to track if a task was completed on a given
machine. I was planning on implementing something using mysql and a module
in cfengine. What ideas have you had about this?

Steve

-----Original Message-----
From: David Douthitt [mailto:ssrat@mailbag.com]
Sent: Monday, July 14, 2003 8:06 AM
To: Help-cfengine@gnu.org
Subject: Re: Strategy for "one-off" tasks



On Thursday, July 10, 2003, at 05:34  PM, Darren Dunham wrote:

> I think the idea is "why would you need to perform a one-time-only
> task"?  Can you give an example of what this would be?  Why would it 
> not
> need to be performed if a machine were being installed?  (possibly for 
> a
> conversion of somthing)?

One thing I've been thinking about for a while is some way to do a 
controlled roll-out, which is similar to a one-off command.

Controlled update roll-outs are making this more of a necessity.  THe 
idea is that I can update certain machines now, more machines one week 
later, and more machines the week after that, until all are done.  This 
is related to a one-time-only task in that this sort of thing would 
only be done periodically.

Installs also come to mind.  There are certain things I don't want done 
all the time that are only done during an installation.  If the 
installation requirements change (that is, a new utility needs to be 
installed) then I would want to install that utility once only 
throughout the enterprise.



_______________________________________________
Help-cfengine mailing list
Help-cfengine@gnu.org
http://mail.gnu.org/mailman/listinfo/help-cfengine