Ask Your Question

A manifest for a single server. A case for modules?

asked 2013-08-09 11:25:10 -0600

maxwell gravatar image

I've been tasked with puppetizing a clients web server. They run a simple static website on a single dedicated server and have no other servers under their control. I've always written seperate modules for each technology being managed (e.g. apache/php/mysql/etc) to create a loose coupling between services. However in this case i'm tempted to simply lump everything in a single module (e.g. web_server) with separate folder (subclass) for each technology/service and the standard install.pp/config.pp/service.pp/ layout in each one. Are there any reasons why I shouldn't ... (more)

edit retag flag offensive close merge delete


That is how I would do it as well. According to Puppet labs best practices - "The classes, defined types, and plugins in a module should all be related, and the ...(more)

timwat gravatar imagetimwat ( 2013-08-09 15:36:06 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted

answered 2013-08-13 09:07:35 -0600

phips gravatar image

As Einstein said 'Make things as simple as they need to be, but no simpler'.

I don't see why you should make this overly complex, but picking Puppet to do your automation is very sensible as it's transferrable. Recently I've had to make the same choice - all my Puppet manifests up this point had been modular. But, for this particular case I couldn't see a good reason to do that, so I actually wrote a single .pp file and used 'puppet apply'.

Sometimes you've got to be pragmatic and do what seems sensible.

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

1 follower


Asked: 2013-08-09 11:25:10 -0600

Seen: 182 times

Last updated: Aug 13 '13