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 amount of changes that are happening.
Every week/two-weeks I do some code changes, and since I tried adding
some of the spec tests through TravisCI, I've encountered errors about
`validate_string` being obsoleted.
Then, looking deeper into the rabbit hole. I've encountered this:
https://github.com/puppetlabs/puppetlabs-ntp/blob/master/manifests/init.pp
And I was shocked... :D WTF just happened? :D
It's becoming overwhelming to follow all these changes even for a puppet
veteran, what about newcomers?
I've been using ansible for a year due to requirements in my new
position, and I've been gaining understanding why is puppet seemingly
losing ground vs other CM tools. It's like the puppet has become a
purpose of it's own, and not a tool to solve actual problems...
Don't get me wrong, I did survive migration from sysv to SMF, sysv to
systemd, mmap to wiredtiger, and gazilion other changes, and I'm not
some old grumpy guy :) But... coming back to a tool after 6 months of
absence and finding that I have difficulties reading and understanding
code? Doesn't really make sense...
And, on the other hand - all this complexity to manage a NTP?
And again - there are features that are really lacking - for example:
1) Remote agent runs, meaning:
- local puppet compiling manifest
- ssh-ing into a box, scp-ing all the needed shit
- applying catalog over there
This would eliminate a need for master server (or code living on all VMs
in case of masterless puppet) for smaller installations.
2) Something like search function in chef instead of exported resources
and puppetdb
3) Simpler and more integrated orchestration - mcollective is
over-engineered and learning curve is almost vertical uphill battle.
I've been using exactly ansible to orchestrate puppet managed
environments :) And when you hear that from a 4-5 year-old puppet user -
that means something is wrong in this ecosystem.
4) Built in management of cloud infrastructure resources (ec2 instances,
ami images, etc)
Sorry if I offended anybody here, it was not my intention... I hope
community picks up some hints from my rant... Maybe I completely missed
the ball, but since I was/still am passionate puppet user, I had to
share this with community.
Please don't be harsh in your comments ;)
--
Jakov
--
You received this message because you are subscribed to the Google Groups "Puppet
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/d7250279-33b4-9d91-445c-7eaf81a13b14%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
