2015-06-04 20:21 GMT+02:00 John Florian <john.florian(a)dart.biz>:
I’ve been curious how Fedora plans to tackle inclusion of Puppet 4,
but
haven’t heard even a peep on the subject. As described[1], they’ve moved to
an all-in-one packaging process that “includes Puppet 4, both Facter 2.4 and
CFacter 0.4, the latest Hiera and Mcollective, as well Ruby 2.1.5, OpenSSL
1.0.0r, and our gem dependencies.” Furthermore, “the package installs into
its own area in /opt/puppetlabs”. Thus upstream is both bundling and using
very Fedora-unfriendly file locations. L
Hi,
F22 provides Ruby 2.2 and upstream has stated they will only support it starting
Puppet 4.x.
I've been working with puppeteers to port Puppet 4.x on F22, and it has been for
a long time in testing but Puppet 4.1 is being currently pushed to stable.
I'm not backporting it to older Fedora, as Puppet 3.x is still
supported on these
platforms.
As Orion and I were the ones doing Puppet updates recently, I found a new
maintainer for Puppet who will be able to keep it in a sane state.
I’ve long awaited having PuppetDB provided within Fedora[2] and from what I
understand the bundling has hindered that effort substantially. Are we
going to lose Puppet in Fedora, or be stuck with an ever aging old release?
At home, I did the most undesirable thing and enabled the PuppetLabs
repositories and love the newer products. Meanwhile I still am waiting for
PL to support Fedora 21 -- and F22 is already out! At work I’m hesitant
with either route (native Fedora packages vs. PL’s repos) for fear of being
stuck in an unsupported situation. (Yes, we probably should be on a EL-ish
distro if it’s critical, but we use Fedora almost exclusively.)
PuppetDB is a mess, it requires a lot of unbundling work and it's in java.
We're considering packaging it for OpenStack but outside Fedora as it will
be too much effort for us.
If you're willing to contribute packaging it, then I could help you in
this task.
Regards,
H.