Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Fabrice Bacchella
> Le 8 janv. 2017 à 03:00, Jakov Sosic a écrit : > > Hi guys, > > this is maybe a topic better suited for -dev list, but, well, here goes. > > I've been using puppet heavily for 3-4 years, up until version 4, now I'm > mostly maintaining my own open source modules. > > What stumped me lately

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread R.I.Pienaar
- Original Message - > From: "Fabrice Bacchella" > To: "puppet-users" > Sent: Sunday, 8 January, 2017 11:04:18 > Subject: Re: [Puppet Users] Over-engineering rant >> Le 8 janv. 2017 à 03:00, Jakov Sosic a écrit : >> >> Hi guys, >> >> this is maybe a topic better suited for -dev list

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Jakov Sosic
On 01/08/2017 11:04 AM, Fabrice Bacchella wrote: And that's for something that for a given environment > never change, have no options. So dropping a standard > file that is hand made once in a lifetime is enough for > the vast majority of people. Exactly my point... I never really understood

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Fabrice Bacchella
> Le 8 janv. 2017 à 14:54, Jakov Sosic a écrit : > > On 01/08/2017 11:04 AM, Fabrice Bacchella wrote: > >> And that's for something that for a given environment > > never change, have no options. So dropping a standard > > file that is hand made once in a lifetime is enough for > > the vast maj

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Gareth Rushgrove
On 8 January 2017 at 02:00, Jakov Sosic wrote: > Hi guys, > > this is maybe a topic better suited for -dev list, but, well, here goes. > > I've been using puppet heavily for 3-4 years, up until version 4, now I'm > mostly maintaining my own open source modules. > > What stumped me lately is the am

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Matthew Kennedy
IMHO, the changes made to the language in 4.x allows for better and more complete modeling of systems. Yes you have more 'things' to learn, the types/lookup systems for example but they are relatively simple to understand. Look at your ntp example, I image it was the specification of Types that loo

Re: [Puppet Users] lspci via facter

2017-01-08 Thread John Gelnaw
I've been using the following code for a really long time now-- I think I 'borrowed' it from someone else. # videocards.rb controllers = [] output = %x{lspci} output.each_line {|s| controllers.push($1) if s =~ /VGA compa

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Rob Nelson
There are a lot of very valid issues and concerns you bring up here. I do want to start by saying, however, that puppet 4 is more than 6 months old - about 20 months to be precise - and most of the significant language changes were introduced somewhat earlier in the future parser in puppet 3. These

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Ramin K
On 1/8/2017 5:54 AM, Jakov Sosic wrote: On 01/08/2017 11:04 AM, Fabrice Bacchella wrote: And that's for something that for a given environment never change, have no options. So dropping a standard file that is hand made once in a lifetime is enough for the vast majority of people. Exactly my

[Puppet Users] Could not find resource, but it's there.

2017-01-08 Thread chris smith
Hi, This seems like a pretty simple thing but I can't figure out why this is throwing a warning. I'm using puppet 4.8.1 installed from the puppetlabs-pc1 on scientific linux 6. # puppet -V 4.8.1 # rpm -q puppet-agent puppet-agent-1.8.2-1.el6.x86_64 My file is as simple as I can make it:

Re: [Puppet Users] Over-engineering rant

2017-01-08 Thread Dirk Heinrichs
Am 08.01.2017 um 11:04 schrieb Fabrice Bacchella: >> And, on the other hand - all this complexity to manage a NTP? > And that's for something that for a given environment never change, > have no options. So dropping a standard file that is hand made once in > a lifetime is enough for the vast maj