To deploy to all IntraNought VMs.

Virtually OK, but one critical flag missing from pillarize for ongoing IPv6 connectivity

For context, when we apply Salt configuration, it currently checks if ipv6-setup-tunnel is running.

@Duranzed As a follow-up for the Terminator plugin, that one could be interesting too.

Plugin works, but now we need to polish the two README files.

Configuration logic. Looks good to me.

Service part OK.

Per https://cbea.ms/git-commit/ titles of your commit messages should be much shorter.

Pillar OK.

No link to a task in description?

OK for Wolfplex too.

Applied to WindRiver.

Request authenticated through IRC + DevCentral commit + prior knowledge of upcoming commit irl + familiar pattern of activity.

@yousra I think pip install salt==3006.8 should work, with dependencies.

Caught this issue during dependencies test.

Salt dependencies are reasonable enough to add to requirements.txt:

Plugin works, but we need more metadata:

If Salt dependencies are the issue, a possibility is to define requirements from https://github.com/saltstack/salt/tree/master/requirements

Repository move

Not for the operations repository, it's for rRESOLVEHASH.

For (1), it was disabled between March 2022 (D2569) and August 2024 (forum thread reporting the issue).

19:21 < Yousra> Dereckson router-003: IP= 178.32.70.111/30, en fait .111 c'est la broadcast

Copying from Discord:

Clean and straightforward.

This task should be clarified.

We've some work on the wiki too:
https://agora.nasqueron.org/index.php?search=master&title=Special%3ASearch&go=Go

The default branch is master, as that was one of the main use of my remote delete script when we switched repositories to main branch.

Note to spawn process was traditionally the TC2 role. That could clearly benefit of T2228.

So I’d suggest we hold off on adding any donation call-to-action for the moment.

Deployment wasn't up-to-date and families configuration for Agora was missing, that's why fallback was on testwiki.

Yousra asked on #nasqueron-ops

22:24:01 < yousra> Dereckson Je me disais que, dans la configuration actuelle, router-004 ne serait utilisé qu’en cas de panne. En fonctionnement normal, une des deux
machines resterait donc presque inactive. Je trouvais que se serait plutôt bien que les deux routeurs travaillent en permanence tout en gardant la redondance.
22:24:02 < yousra> Mais comme on n’a pas vraiment plusieurs VLAN ou réseaux distincts, je ne suis pas sûr que la topologie actuelle permette cette répartition. Est-ce qu’on > pourrait quand même optimiser ça d’une certaine manière ?

Deployed