Marelle: logic programming for devops

Re:Marelle: logic programming for devops by lars512 on Saturday November 09, 2013 @05:07PM (#6703520)

This sounds like a question of how declarative your deps are, with Chef and Puppet picking different points on the scale.

I can relate that with Babushka now, we commonly rely on ordering of requirements (A <- B, C in that order!) at times when we should really have one of those requirements require the other (A <- B, B <- C). This works fine for the original purpose, but leaves minefields floating around when you want to reuse deps for another project.

[ Parent | on HN ]

Re:Marelle: logic programming for devops by mitchellh on Saturday November 09, 2013 @08:30PM (#6704633)

Hm, part of my consulting agreement when I did Puppet was that I could re-use my own set of Puppet modules (which I never did open source). I shared the same set of Puppet modules among many clients and never had issues with "minefields" because of my explicit requirements.

Therefore, I think this comes down to how you design your Puppet modules.

Personally, I design my Puppet modules much in the way that Jamie Windsor designs Chef cookbooks and talks about in the ChefConf keynote: "The Berkshelf Way".

[ Parent | on HN ]