[Pkg-puppet-devel] puppetserver_8.4.0-5_source.changes ACCEPTED into unstable

[Jérôme Charaoui]

Hi Zigo,

Le 2024-08-27 à 13 h 33, thomas at goirand.fr a écrit :
> 
> On Aug 27, 2024 3:48 PM, Antoine Beaupré <anarcat at debian.org> wrote:
>  >
>  > Hey Jerome,
>  >
>  > I talked with zigo over IRC and will handle this in the git repo,
>  > reverting back to the 30 days, and addressing the lack of upgrade path.
> 
> As I wrote on IRC, 30 days is NOT acceptable.
> 
> On a reasonably large OpenStack cluster, just 2 days of reports means 
> 6GB. Do the math: 30 days would mean nearly 100GB of reports. My puppet 
> VMs, I set then usually with 40GB of system disks...
> 
> Also, what will you do with 48 puppet report per server per day? 
> Probably nothing...
> 
> Plaase do NOT revert to 30 days. This is extremely armful for no reason.
> 
> Thomas Goirand (zigo)
> 
> P.S: my commit leaves 2 days of reports, not 1, even if it reads "ctime 
> 1"...

This confirms my hunch that the optimal cleanup period is very dependent 
on the environment. In this case we should opt to document in 
README.Debian or NEWS our suggestion for administrators to deploy such a 
cron job, which they will be able to customize to their needs.

I'll also mention that although the default directory for reports is 
"$vardir/reports", this can be changed in puppet.conf, and reports may 
even be disabled altogether with "reports = none". In either situation, 
the cron job shipped by the package becomes wrong.

-- Jérôme