Puppet users - Mar 2013 - serving large files "formally code artifacts" best practices

Hi All, I''d like to know best practices in serving code artifacts
"tarballs" though puppet , I used to serve them using file{} resource
but
this method doesn''t seem a good way as i have to either include code
artifacts "tarballs" in puppet codebase repository or configuring
puppet
codebase repository to ignore such tarballs and providing a way to inject
code artifacts in $path*to*puppet/modules/module_1/files

-- 
Best Regards,
Eslam Mamdouh El Husseiny
*Systems Administrator**
Cloud Niners Ltd.

*
*Cellular: (+2) 011 198 40 40
Mansoura: (+2) 050 234 70 81
Cairo:    (+2) 022 *268 34 60
Fax:      (+2) 022 268 34 63

-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

Ideally, use packages instead.
But if that is not possible. Put the tarballs on a web server and have the
agents pull the files from there. It will be much faster than puppet
distributing the files and they will not be in the codebase.

On my repo server, I have a directory for tarballs for when this issue comes up.

Steven

Date: Sat, 9 Mar 2013 23:21:06 +0200
Subject: [Puppet Users] serving large files "formally code artifacts"
best practices
From: emamdouh@cloud9ers.com
To: puppet-users@googlegroups.com

Hi All, I''d like to know best practices in serving code artifacts
"tarballs" though puppet , I used to serve them using file{} resource
but this method doesn''t seem a good way as i have to either include
code artifacts "tarballs" in puppet codebase repository or configuring
puppet codebase repository to ignore such tarballs and providing a way to inject
code artifacts in $pathtopuppet/modules/module_1/files

-- 
Best Regards, 
Eslam Mamdouh El Husseiny
Systems Administrator

Cloud Niners Ltd.

Cellular: (+2) 011 198 40 40

Mansoura: (+2) 050 234 70 81
Cairo:    (+2) 022 268 34 60
Fax:      (+2) 022 268 34 63








-- 

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+unsubscribe@googlegroups.com.

To post to this group, send email to puppet-users@googlegroups.com.

Visit this group at http://groups.google.com/group/puppet-users?hl=en.

For more options, visit https://groups.google.com/groups/opt_out.

 

 
 		 	   		  

-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

On 3/9/13 4:21 PM, Eslam Mamdouh El Husseiny wrote:
> Hi All, I''d like to know best practices in serving code artifacts
> "tarballs" though puppet , I used to serve them using file{}
resource
> but this method doesn''t seem a good way as i have to either
include code
> artifacts "tarballs" in puppet codebase repository or configuring
puppet
> codebase repository to ignore such tarballs and providing a way to
> inject code artifacts in $path/to/puppet/modules/module_1/files
> 
> -- 
> Best Regards,
> Eslam Mamdouh El Husseiny
> /Systems Administrator//*
> Cloud Niners* Ltd.
Hello,

I initially wrote an rsync module[1] to handle this, as using Puppet''s
file transfer method is not really suited for > 1GB files. Other ways to
solve this would be to turn your tarball into a package. A quick way to
do this would be with FPM[2]. You could use a version control system to
manage your code artifact and have a post commit hook that turns it into
a package and places that in your repo. Another approach would be using
BitTorrent to propagate your code artifacts to all the systems.

[1] - https://github.com/puppetlabs/puppetlabs-rsync/
[2] - https://github.com/jordansissel/fpm/

Regards,
-g


-- 
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.