On Oct 18, 2009, at 2:15 AM, Adam Ryczkowski wrote:
>
> Good afternoon all,
>
> How one can predict a problem with copying before puppet actualy
> starts it? Copying is expensive, because I'm talking about many GB of
> data. I suspect that it should be easy to know how much free space and
> how many free nodes are available on the target device. I realize that
> it is not so easy to accurately predict the space requirements
> beforehand, but from the other hand, since I don't use compressed file
> systems, there are obvious checks one can make to predict a failure in
> many cases. One cannot fit directory of 1GB files when there is only
> 500MB free space on target...
This would be possible once we move the Exec checks into metaparams.
Someone's working on that right now and we're shepherding it in, but
it's probably not going to make it until the next major release at the
end of the year.
Really, though, you probably don't want to use Puppet to copy a 1gb
file - it still copies the files into memory. Use an exec, for now,
and have it conditional on there being space.
Or, of course, use NFS. :)
--
You don't learn anything the second time you're kicked by a mule.
-- Anonymous Texan
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@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
-~----------~----~----~----~------~----~------~--~---
