Ask Your Question
1

How to deal with name conflicts on pupept labs modules?

asked 2014-12-02 05:36:11 -0500

nomike gravatar image

There are often name conflicts with different puppet modules on puppetforge. For example there is a module "example42-jboss" which depends on "example42-firewall". And then there is a module "puppetlabs-puppetdb" which depends on "puppetlabs-firewall".

So I could not use both the "jboss" and the "puppetdb" module within the same environment.

Is there a clean solution/workaround for this problem if I don't want to use the "jboss" and the "puppetdb" module on the same node? What happens if I want to use them on the same node?

edit retag flag offensive close merge delete

Comments

If they're on different nodes, using multiple environments (http://docs.puppetlabs.com/guides/environment.html) is your only choice. You can't really use them on the same node, as they'd probably try and manage the same resources.

domcleal gravatar imagedomcleal ( 2014-12-03 03:26:54 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted
0

answered 2016-07-09 01:30:36 -0500

haloflightleader gravatar image

I have had this same problem and I continue to grapple with it. The easy solution would be to simply choose to use a different module that does the same thing, but one that doesn't have the dependency clash. My example was rtyler-jenkins and KyleAnderson-consul. They both depend on a module named archive except they require them from different places. Needless to say, I needed to make a choice. Pick a different module or do the worst move you could ever make... edit one of the module's source code. Guess which I picked.

I chose to edit the consul module because I didn't want to mess with Jenkins. I wanted to ensure the Jenkins module is upgradable. Jenkins is the spine of my infrastructure and puppet is the brains.

Do I regret it? Yes. Can I change it now? Technically, yes, but realistically, it's going to be expensive considering the role consul plays in the infrastructure. I can turn off Jenkins for a few hours with minor inconvenience even though I just referred to it as the infrastructure's backbone. Consul, I just can't afford for it to be down or the consequences will be dire.

I wish Puppet Labs would create a way that would alleviate this pain.

edit flag offensive delete link more
0

answered 2016-07-09 04:15:59 -0500

updated 2016-07-09 04:16:32 -0500

Unfortunately, there isn't really a good solution to this problem, other than for you to make interoperation a criterion when you select the Forge modules to use. My understanding is that a future version of Puppet will provide a proper solution to the problem. Have a look at this thread here for ideas, where I was dealing with the same issue.

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

Stats

Asked: 2014-12-02 05:36:11 -0500

Seen: 41,880 times

Last updated: Jul 09 '16