Added RHEL question.

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.

router-001 is out of scope as long as T1939 is implemented

Can be automated with grain osmajorrelease.

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

Other changes seem needed:

The Etherpad projects offers a procedure to install Etherpad with npm link. That works well if we combine D3260 and D3261.

This is a draft prepared last June for the script which prepared the database currently live in Odderon.

Small fixes from flake8

Complector done.

FreeBSD integrates OpenSSH to the base OS.

Code change merged, thanks for the task :)

Checked the rendering with arc patch D3255 (to get the branch) then python3 -m http.server, looks good to me.

Good idea to have chosen the same size, that will give a more coherent look.

Thanks for the contribution.

WindRiver done last week. Works perfectly fine.

Align correctly YAML

TODO: Cleanup certbot_dir from webserver-core