Gregory's ServerMon 2024-10-21, starting around 18.00 UTC / 20.00 CEST: We are shipping a new system to the datacenter, proceeding with our infrastructure expansion and redundancy plans. This requires the installation of a new network card into existing hardware and a reboot following the operation. Service to Codeberg.org will be interrupted for up to 30 minutes. If all goes well, this will allow us to transition services to the new setup gracefully, avoiding downtime due to hardware reboots.
|
20 comments
 @mupan We'll publish a blog post on the introduction of quotas with Forgejo v9 soon (which can be manually increased on demand). It will reiterate our policy on private repositories. We don't have any plans to deal with such cases automatically at the moment - each situation is different. ~n @mupan If they're not licensed, they're technically a subset of the category you're talking about. We have explained how we deal with such cases manually over the past few days as well. Is there anything specific that I can help with here? ~n EDIT: https://social.anoxinon.de/@Codeberg/113318420447158446 Reminder: We're soon on our way to the datacenter, starting maintenance in about two hours, which involves about 30 minutes of downtime for Codeberg. We know that our availability was limited recently due to various factors, and we're sorry to add on it today, but it's the way to make the future setup more reliable. We'll keep you updated as time permits. *click* - a new server was just installed physically. Now cabling and testing begins. A hardware reboot of the existing machine is scheduled later. We're now installing new network hardware, requiring to take down the machine. We are going down for maintenance now. Installation successful, rebooting ... it will, unfortunately, take a while until the service is fully restored. The maintenance was successfully completed and Codeberg is back in service. Additionally, we now have a 10G fiber interconnect to our next server, an important step towards our new setup. 👋 Say hi to "Aburayama", our second server named after the mountain that inspired the first (now retired) Codeberg logo: https://en.wikipedia.org/wiki/Mount_Abura Just in case people want to know what's running inside it, we placed some stickers prominently on front. Thanks to everyone involved for their work, and for your patience during the setup.  @andre_601 https://codeberg.org/Codeberg-Infrastructure/build-deploy-forgejo/src/commit/43fd75dbded8fb9c9a23b39800a5d00ab41c0e84/etc/gitea/public/img/codeberg.png and https://codeberg.org/Codeberg-Infrastructure/build-deploy-forgejo/src/commit/42d20b19e73b792b8cb10676be8be6d799d70f17/etc/gitea/public/img/codeberg.png  |
@Codeberg Thank you.
How is the fight against the proprietary wave going? Have you found a rather non-manual way to ensure compliance?