size of fileserver files?

33 views
Skip to first unread message

Christopher Wood

unread,
Feb 3, 2015, 1:34:16 PM2/3/15
to puppet...@googlegroups.com
I've read through tickets.puppetlabs.com bug reports and can't find anything, asking here before I go down that road.

Have any of you had trouble with large files served from the puppetmaster fileserver? If you had any issues how big were the files and what was your puppetmaster version (3.7.2 here)?

The background:

I'm trying to remove somebody's large binary from a module files subdir and prototype some basic large file distribution (that's not manually placing things on nfs mounts). Plus if I distribute via puppet I can check the reports to see if we had any distribution issues.

Trevor Vaughan

unread,
Feb 3, 2015, 4:59:13 PM2/3/15
to puppet...@googlegroups.com
Hi Chris,

It definitely works but I would not use it for large files due to the serialization/deserialization overhead issues, that it will checksum the file at each run, and that it will transfer the entire file should the transfer need to occur.

I would recommend using something like rsync or creating a native package for your operating system and using the 'package' resource as the best way to get the files onto the system.

Thanks,

Trevor


--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/20150203183358.GA17576%40iniquitous.heresiarch.ca.
For more options, visit https://groups.google.com/d/optout.



--
Trevor Vaughan
Vice President, Onyx Point, Inc
(410) 541-6699
tvau...@onyxpoint.com

-- This account not approved for unencrypted proprietary information --

Christopher Wood

unread,
Feb 3, 2015, 6:11:12 PM2/3/15
to puppet...@googlegroups.com
On Tue, Feb 03, 2015 at 04:59:01PM -0500, Trevor Vaughan wrote:
> Hi Chris,
>
> It definitely works but I would not use it for large files due to the
> serialization/deserialization overhead issues, that it will checksum the
> file at each run, and that it will transfer the entire file should the
> transfer need to occur.

Yes and yes, and another really important feature: any resource change is recorded and that record is added to the report that is sent to puppetdb.

> I would recommend using something like rsync or creating a native package
> for your operating system and using the 'package' resource as the best way
> to get the files onto the system.

In any other situation I would agree with you about rsync and packages. Unfortunately there are interdepartmental issues about holes in firewalls and ssh keys and rsync daemons; I need to fight different battles right now. Every server that will obtain the files via file resources already has puppetmaster access. Also, a package resource doesn't monitor whether each individual file in the package has been manually replaced and automagically fix that.

(These would probably sound more reassuring if I explained them in business jargon, ahem.)

> Thanks,
>
> Trevor
> On Tue, Feb 3, 2015 at 1:33 PM, Christopher Wood
> <[1]christop...@pobox.com> wrote:
>
> I've read through [2]tickets.puppetlabs.com bug reports and can't find
> anything, asking here before I go down that road.
>
> Have any of you had trouble with large files served from the
> puppetmaster fileserver? If you had any issues how big were the files
> and what was your puppetmaster version (3.7.2 here)?
>
> The background:
>
> I'm trying to remove somebody's large binary from a module files subdir
> and prototype some basic large file distribution (that's not manually
> placing things on nfs mounts). Plus if I distribute via puppet I can
> check the reports to see if we had any distribution issues.
> --
> You received this message because you are subscribed to the Google
> Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [3]puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> [4]https://groups.google.com/d/msgid/puppet-users/20150203183358.GA17576%40iniquitous.heresiarch.ca.
> For more options, visit [5]https://groups.google.com/d/optout.
>
> --
> Trevor Vaughan
> Vice President, Onyx Point, Inc
> (410) 541-6699
> [6]tvau...@onyxpoint.com
>
> -- This account not approved for unencrypted proprietary information --
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [7]puppet-users...@googlegroups.com.
> To view this discussion on the web visit
> [8]https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX0sJHFueh8u_VfbNSEg%3D0z7qgwG_9jKF5VD5gk2%2BOuUA%40mail.gmail.com.
> For more options, visit [9]https://groups.google.com/d/optout.
>
> References
>
> Visible links
> 1. mailto:christop...@pobox.com
> 2. http://tickets.puppetlabs.com/
> 3. mailto:puppet-users%2Bunsu...@googlegroups.com
> 4. https://groups.google.com/d/msgid/puppet-users/20150203183358.GA17576%40iniquitous.heresiarch.ca
> 5. https://groups.google.com/d/optout
> 6. mailto:tvau...@onyxpoint.com
> 7. mailto:puppet-users...@googlegroups.com
> 8. https://groups.google.com/d/msgid/puppet-users/CANs%2BFoX0sJHFueh8u_VfbNSEg%3D0z7qgwG_9jKF5VD5gk2%2BOuUA%40mail.gmail.com?utm_medium=email&utm_source=footer
> 9. https://groups.google.com/d/optout
Reply all
Reply to author
Forward
0 new messages