Bug#826551: [Pkg-puppet-devel] RFP: puppetdb-termini -- Enable a Puppet master to connect to PuppetDB

[Apollon Oikonomopoulos <apoikos@debian.org>]

Hi all,

On 22:21 Wed 01 Feb     , Apollon Oikonomopoulos wrote:
> Well, for puppet 4 we could add a puppet-terminus-puppetdb binary 
> package to the puppet source. I don't think it makes sense to upload 
> the PuppetDB source just for a couple of Ruby files which are not a 
> direct part of PuppetDB anyway.

Following up, here's a more detailed course of action:

 - puppet 4.8.2-1 will (hopefully) migrate to testing tomorrow, 3 days 
   before the Freeze. This will be the first version in Stretch 
   supporting Puppet 3 clients.

 - As soon as 4.8.2-1 enters testing, I intend to upload 4.8.2-2, with 
   the following changes:
    * Restore the vim-puppet and puppet-el binary packages, which were 
      removed in 4.4.2-1.
    * Import the PuppetDB terminus from PuppetDB 4.3.0.
    * Ship the PuppetDB terminus in puppet-terminus-puppetdb. (Closes: 
      #826551)

   It will go through NEW for puppet-terminus-puppetdb, vim-puppet and 
   puppet-el, but there should be no problems here.

 - When 4.8.2-2 hits unstable and if all is well, I will file for an 
   unblock request to have 4.8.2-2 migrate to testing. At that point the 
   decision will be up to the release team.

 - If and when 4.8.2-2 is accepted in testing, I will file for a 
   jessie-pu to update 3.7.2-4 in Jessie to also include the PuppetDB 
   terminus (from PuppetDB 2.3.8). Again, the terminus will be provided 
   in a new binary package, puppet-terminus-puppetdb.

If all goes well, we should end up with PuppetDB-enabled versions in 
both Jessie and Stretch. Also, for the puppet-terminus-puppetdb package 
I'm using PuppetDB's version numbers (and not the puppet source 
version), so that the package can be taken over by the puppetdb source 
when the latter is ready for Debian.

Regards,
Apollon