Was actually correctly configured in rOPS, but not deployed, so old version was still there.

Merged D3469 so we can have secrets.

Same issue after 2025-06-02 reboot for kernel upgrade, route to 172.27.27.1 is still missing.

Probably interesting to replace redis by valkey per T1938.

Increasing priority as FreeBSD 13.2 is now EOL for one month (2024-06-30).

In T1924#28790, @dereckson wrote:

router-001 update would cut network connections between Ysul, WindRiver, CloudHugger and IntraNought VMs.

I think that's actually acceptable, as production services can reach web-001/db-*/ directly through their dedicated network card.

Impact:

• IRC bots wouldn't be able to reach MySQL or Vault as they're still on Ysul
• Services still on Ysul can't reach
• Development servers can't reach production services, or Dwellers

Another issue is we lose connections to all those machines, as router-001 is used to route traffic to them.

Probably best to ship router-002 under FreeBSD 14 so we can prepare to minimize this impact if we need more hypervisors in the future.

Created this week-end a netbox database on db-A-001.

WindRiver doesn't start PostgreSQL, Redis, NetBox services on boot.

Meanwhile, we configured correctly GRE interface and IPv6 tunnel separately,
so at next Dwellers reboot, we need to state what works