Patrick wrote:
On Apr 8, 2010, at 2:15 AM, Thomas Bellman wrote:
This does two things: when run the first time, it actually does
an rsync of a directory tree. And then it creates a cron job
for keeping the tree synchronized with the source. You use the
'creates' parameter to indicate a file that you expect to exist
in the tree, so Puppet itself doesn't have to run rsync every
time. If you mirror a large tree that could take a long time,
even if no files actually need to be transferred (I use it to
keep a mirror of CentOS and EPEL on a cluster, so we can re-install
our nodes anytime without being dependant on external servers).
It sounds like we have very different ideas how this should work.
For me, an ideal module would use the the schedule argument, and
not have anything to do with cron.
Luckily, what I have implemented actually supports that mode of
operation as well. :-) Just don't specify the 'hour' and 'minute'
parameters, and don't use the 'creates' parameter.
Using the schedule metaparameter might not be what you really want.
If you do something like:
rsync_mirror {
mymirror: ..., schedule => nightly;
}
sometype {
foo: ..., require => Rsync_mirror[mymirror];
}
where Sometype[foo] needs some files from the rsync, if you run
your manifests on a fresh machine, and it isn't in the middle of
the night, then Sometype[foo] will fail.
I wouldn't use use any of these tags, but here are more ideas while
you are asking:
require
depends
subscribe
notify
onlyif
unless
refreshonly
Luke implemented 'require' and 'subscribe' for me long before I
started using Puppet, so I got that for free... But 'subscribe'
probably doesn't make much sense without 'refreshonly'; should
be easy to implement, so I might do that. I don't think it is
something I would use, though.
I suppose you would want 'notify' to send a notification when there
has been some files actually changed by the rsync. That would only
make sense when you don't use cron to offload the work from Puppet.
But I don't think that can be done from a define with exec, so it
would need to be implemented in Ruby. If someone can come up with
a good use case I'll think about it.
'Onlyif' and 'unless' is already implemented.
I don't know what 'depends' would do. Explanation?
/Bellman
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
