[Pkg-puppet-devel] the future of Puppet inside Debian?

[Stig Sandbeck Mathisen]

Jonas Genannt <jonas.genannt at capi2name.de> writes:

> since Puppet 4 (4.1) is released Puppetlabs has decided to deprecate
> Rack Server support in Puppet [1].
>
> The "new" Puppet-Server is like the PuppetDB written in Clojure and
> also uses JRuby.

I think I can safely say that I'm not up to packaging Clojure based
software.

I've given it a few tries, but the Puppet packaging team would benefit
more from someone with more familiarity with the java packaging tools.

Is anyone else with an interest in Puppet packaging going to Heidelberg
for DebConf this year?  I'd like to work a bit on the Puppet packaging
there.


> There is much work to do:
>
> * facter:
>   facter has switched from Ruby to C, but providing a native C Ruby
>   library. We need to replace the Ruby facter and provide arch=any
>   packages.

C++11, to be more precise.  https://github.com/puppetlabs/facter is
still the upstream.

> * Puppet Client
>   for now in Ruby, but imho will be switched to C like facter

With luck, they'll keep the same building tools as well.  CMake and
Boost seem to be used.

> * Puppet Server (Clojure + JRuby)
>   horrible depends for Puppet-Server many new packages needs to be
>   first inside Debian.

> We need also to provide upgrade paths because Puppetlabs has changed
> all the configuration paths from etc/puppet to etc/puppetlabs.

…with new layout for puppet code inside it as well.

I'm not sure we would need to adopt the /etc/$vendor/$thing layout for
configuration.  It's probably better to let the puppet AIO packages keep
that for themselves, and rather try to coexist.


-- 
Stig Sandbeck Mathisen