[atlas] Encouraging people to upgrade software probe versions

Hi,

On Fri, Jan 27, 2023 at 02:15:44AM +0100, Robert Scheck wrote:
> On Mon, 09 Jan 2023, Gert Doering wrote:
> > So don't do OS updates.  But *do* update the probe software, automatically,
> > and in normal intervals.
> 
> writing while wearing my hat as a RPM packager: I'm not really sure how
> this shall work practically: If the probe software is run on regular (non-
> hardware probe) systems, there are runtime dependencies to other software,
> e.g. due to dynamic linking. Latter is encouraged by Linux distributions,
[..]

This is all good and true - so, do not distribute as RPM.

Distribute as Docker image, or Flatpack, or whatever all these new
"encapsulate a program and all its dependencies" approaches are called,
and I'm sure some of them have mechanisms to enforce timely updates.

First and foremost, a RIPE Atlas probe is a centrally managed piece of
software, and this is what it needs to be: centrally managed, centrally
upgraded, always at the upgrade level the central controller wants it
to be.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: </ripe/mail/archives/ripe-atlas/attachments/20230129/053faff6/attachment.sig>