ITP: puppetserver -- the next-generation application for managing Puppet agents

Debian Bug report logs - #830904
ITP: puppetserver -- the next-generation application for managing Puppet agents

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Mathieu Parent <sathieu@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: RFP: puppetserver -- the next-generation application for managing Puppet agents

Date: Tue, 12 Jul 2016 22:20:45 +0200

Package: wnpp
Severity: wishlist
Control: block -1 by 819811

* Package name    : puppetserver
  Version         : 2.4
  Upstream Author : Puppetlabs
* URL             : https://docs.puppet.com/puppetserver/latest/
* License         : Apache-2.0
  Programming Lang: Clojure, Ruby
  Description     : the next-generation application for managing Puppet agents

Puppet Server is the next-generation application for managing Puppet agents. This platform implements Puppet's server-side components in a more distributed, service-oriented architecture. We've built Puppet Server on top of the same technologies that make PuppetDB successful, and which allow us to greatly improve performance, scalability, advanced metrics collection, and fine-grained control over the Ruby runtime.

This package needs some additionnal dependencies, most of them needed by puppetdb too (#673515).

It would also benefit from leiningen (#819811).

Message #22 received at 830904@bugs.debian.org (full text, mbox, reply):

From: Louis-Philippe Véronneau <pollo@debian.org>

To: 830904@bugs.debian.org

Subject: Re: RFP: puppetserver -- the next-generation application for managing Puppet agents

Date: Tue, 7 Jul 2020 17:42:09 -0400

[Message part 1 (text/plain, inline)]

On Tue, 12 Jul 2016 22:20:45 +0200 Mathieu Parent <sathieu@debian.org>
wrote:
> Package: wnpp
> Severity: wishlist
> Control: block -1 by 819811
> 
> * Package name    : puppetserver
>   Version         : 2.4
>   Upstream Author : Puppetlabs
> * URL             : https://docs.puppet.com/puppetserver/latest/
> * License         : Apache-2.0
>   Programming Lang: Clojure, Ruby
>   Description     : the next-generation application for managing Puppet agents
> 
> Puppet Server is the next-generation application for managing Puppet agents. This platform implements Puppet's server-side components in a more distributed, service-oriented architecture. We've built Puppet Server on top of the same technologies that make PuppetDB successful, and which allow us to greatly improve performance, scalability, advanced metrics collection, and fine-grained control over the Ruby runtime.
> 
> This package needs some additionnal dependencies, most of them needed by puppetdb too (#673515).
> 
> It would also benefit from leiningen (#819811).
> 
> 

Work to package puppetserver is being tracked here:

https://wiki.debian.org/Teams/Puppet/Work#Puppet_Server

Help appreciated. Please coordinate with the Puppet Team on
#debian-puppet or on the team's mailing list.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[signature.asc (application/pgp-signature, attachment)]

Message #29 received at 830904@bugs.debian.org (full text, mbox, reply):

From: Louis-Philippe Véronneau <pollo@debian.org>

To: 830904@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: ITP: puppetserver -- the next-generation application for managing Puppet agents

Date: Mon, 4 Jan 2021 14:14:57 -0500

[Message part 1 (text/plain, inline)]

retitle 830904 ITP: puppetserver -- the next-generation application for managing Puppet agents
owner 830904 pollo@debian.org
thanks

Packaging work done on puppetserver can be found at:

https://salsa.debian.org/puppet-team/puppetserver

Cheers,

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   pollo@debian.org / veronneau.org
  ⠈⠳⣄

[OpenPGP_signature (application/pgp-signature, attachment)]

Message #40 received at 830904@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: Thomas Goirand <zigo@debian.org>, 950182@bugs.debian.org, Martin Konrad <info@martin-konrad.net>

Cc: 830904@bugs.debian.org

Subject: Re: Bug#950182: [Pkg-puppet-devel] Bug#950182: Puppet 5.5 EOL in November 2020

Date: Wed, 30 Mar 2022 16:28:40 -0400

On 2022-03-29 15:21:52, Antoine Beaupré wrote:
> On 2022-03-29 21:14:42, Thomas Goirand wrote:

[...]

>> At this time, maybe we should giveup on having jruby work with Ruby 3,
>> and accept the parts of it which are embedded (like the ruby
>> interpreter).
>
> Yeah, that would make sense I think. But maybe that conversation would
> be better to have on the jruby side of things (e.g. #972230) or in the
> puppetserver ITP (#830904).

I've actually opened up a discussion about this in:

https://alioth-lists.debian.net/pipermail/pkg-puppet-devel/2022-March/012662.html

-- 
What people say, what people do, and what they say they do are
entirely different things.
                        - Margaret Mead

Message #45 received at 830904@bugs.debian.org (full text, mbox, reply):

From: Antoine Beaupré <anarcat@debian.org>

To: pkg-puppet-devel@alioth-lists.debian.net

Cc: Thomas Goirand <zigo@debian.org>, 950182@bugs.debian.org, 830904@bugs.debian.org

Subject: Re: a proposal to salvage Puppet Debian packages

Date: Thu, 14 Apr 2022 10:23:26 -0400

On 2022-03-30 11:28:09, Antoine Beaupré wrote:
> Hi,

Following up on my own thread, two weeks later.

> TL:DR; (1) I want to join the team (2) let's package puppet agent 6
> clean, then puppetserver 6 and/or 7 for bookworm.

It seems I was granted access to the Puppet team on salsa, thanks! :)

And since then, I noticed some critical information that I hadn't
noticed before: Ruby 2.7 was removed from bookworm.

https://tracker.debian.org/news/1311269/ruby27-removed-from-testing/

This means that any Puppet version before Puppet 7.8 will likely not run
in Debian bookworm at all, since that's the first version which added
support for Ruby 3+:

https://puppet.com/docs/puppet/7/release_notes_puppet.html#release_notes_puppet_7-8-0

I still think my proposal makes sense. We should focus on upgrading the
client to Puppet agent 6, which should hopefully survive that transition
regardless. Then we could focus on packaging Puppet Server *seven*,
since it *will* be compatible with the Puppet agent 6. We would, in
effect, be skipping Puppet Server 6.

This has a few implications for our users. They will either need to:

 * upgrade everything at once, that is: upgrade the server from Puppet
   master 5 to Puppet server 7, and *simultaneously* upgrade from Puppet
   agent 5 to Puppet agent 6 (an alternative would be to setup a
   different Puppet server 7 and migrate machines over to that server
   progressively, but this could be messy with exported resources)

 * use the upstream packages for Puppet server 6 while the fleet is
   upgraded to Puppet agent 6, then switch back to the Debian package
   for Puppet server 7

I don't really see another way around this, because Puppet server 6
can't possibly work in Debian bookworm and above anymore, because of the
Ruby 2.7 removal.

The Puppet Server 7 work could happen in th Clojure team sprint in May,
which would land us a Puppet server ready for the bookworm freeze.

We *could* also work on Puppet server 6 and "fast track" it to bullseye:

https://fasttrack.debian.net/

But that feels like duplication of work a little. If I would have to
choose between Puppet server 6 and 7, I would choose the latter. And
given how much availability we all seem to have to work on this problem,
it *does* seem like we need to choose.

If there are no objections, I'll start working on the agent 6 in the
next few weeks/months.

Thanks for any feedback,

A.
-- 
In serious work commanding and discipline are of little avail.
                         - Peter Kropotkin

Send a report that this bug log contains spam.