Ask Your Question
1

serving large files "formally code artifacts" best practices

asked 2013-03-09 15:20:27 -0500

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

any other practices that seems better than what i do ?

Thanks in advance

edit retag flag offensive close merge delete

2 Answers

Sort by » oldest newest most voted
2

answered 2013-03-09 16:42:09 -0500

Daenney gravatar image

My best practice is don't. We tried a bunch of methods, deploying it with puppet, exec+wget, using a custom mount in the Puppet file server but we eventually settled on wrapping everything in packages.

What we do is we create a debian package with the structure of where we want the tar.gz and the actual tar.gz, package it up and put it in our own APT repository. Now we can just install it using a package resource and whenever we package up a new version of that and upload it to our repositories we can just ... (more)

edit flag offensive delete link more

Comments

FPM is a really easy way to get started with packaging. https://github.com/jordansissel/fpm

Ancillas gravatar imageAncillas ( 2013-10-21 16:44:44 -0500 )edit
0

answered 2013-10-21 16:08:42 -0500

scoopex gravatar image

I fully agree.

Using operating system packages provides the following advantages over tarballs:

  • it´s easy to get a defined version on your target system (i.e. by using ensure => "latest", ensure => "1.3.18")
  • it is easy to add dependencies to a package (dependencies to operating-system tools/libs or software you also packaged)
  • up- and downgrading is less complex with package dependencies
  • packages are not managed by the puppet file archiving (this will not eat up your puppet server diskspace)
  • you can speedup your installation dramatically by using the package cache of your package management (the system often know ...
(more)
edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

Stats

Asked: 2013-03-09 15:20:27 -0500

Seen: 754 times

Last updated: Oct 21 '13