**KernelCI Weekly Newsletter (Week 1)**
Denys Fedoryshchenko <[email protected]> Fri, 03 Jan 2025 09:39:16 +0200
| Newsgroups | dev.linux.lists.kernelci |
|---|---|
| Message-ID | <[email protected]> |
**Summary** Welcome to the first issue of the KernelCI Weekly Newsletter for 2024. Happy New Year once again to the entire KernelCI community! This week, we have several updates to share. The KernelCI team has been working on a new storage backend, which is now live on the staging environment. This backend is built using Rust, Axum, and Azure Blob (a big thanks to Microsoft for providing the storage). The new system is designed to be more reliable and scalable than the previous setup. The team is currently focusing on migrating the production backend to this improved system. The new backend has already helped uncover some issues within the KernelCI infrastructure. One notable issue involves certain log analysis tools repeatedly attempting to download the same log file—over 40 times—resulting in excessive egress traffic. Thanks to the enhanced visibility and flexibility provided by the new backend, the team is now working to resolve this issue. This includes identifying the root cause, fixing it, and, in some cases, redirecting these requests to a more cost-effective egress path. **New Backend Deployment Plan** The deployment of the new backend will proceed in the following stages: 1. Create an `A` record for `files.kernelci.org` to point to the new backend. 2. Take a final snapshot of the legacy production server. 3. Develop a new Ansible playbook for deploying the backend and attach the old backend's block device to the new system. 4. Deploy the new backend on staging. 5. Configure `nginx` to proxy requests to the new backend while providing access to static website docs.kernelci.org and temporary access to the old storage. **Important Note** If you have any valuable data stored at `storage.kernelci.org`, please inform the team. They can take a snapshot of the data before the migration and propose a method to move it to the new backend.