Hi, On Mon, Jan 09, 2023 at 11:25:50AM +0100, Michel Stam wrote: > Thank you for pitching in. > > The hardware probes are fully managed by RIPE NCC, and their only purpose is > to execute measurements. I agree here, whether to update is up to RIPE NCC. > On software probes, RIPE NCC is not in control of the unit. The software > probe may run other services and updating is up to its local sysadmin. > Consider operating system updates, which are updated by RIPE NCC on the > hardware probes, but cannot be updated on software probes.
So don't do OS updates. But *do* update the probe software, automatically,
and in normal intervals.
Having probes out there with wildly varying firmware is not helping
measurement accuracy.
> To automatically update, the solution here is a simple CRON job which
> executes yum -q update atlasswprobe periodically (say once per day or so),
> which was the solution that was part of the RPM up to 5080. Would it help if
> we add this to the instructions?
I'm very much of the opinion that upgrades should not be an opt-in service,
*and not even an opt-out*.
If you want a measurement box that does something non-ATLAS based on
ATLAS software - all good, but do not call it an ATLAS probe.
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
signature.asc
Description: PGP signature
-- ripe-atlas mailing list [email protected] https://lists.ripe.net/mailman/listinfo/ripe-atlas
