From: Gustavo Padovan <gus@collabora.com>
To: "kernelci lists.linux.dev" <kernelci@lists.linux.dev>
Cc: "Nikolai Kondrashov" <nikolai.kondrashov@redhat.com>
Subject: [RFP] KernelCI KCIDB - DBA Remote Contract
Date: Thu, 20 Feb 2025 09:27:10 -0300 [thread overview]
Message-ID: <1952353828f.11bf7ab40849072.7749176993724033096@collabora.com> (raw)
In-Reply-To:
[-- Attachment #1.1: Type: text/plain, Size: 3456 bytes --]
Hello,
The Linux Foundation KernelCI project is looking for PostgreSQL DBA contract
proposals to help improve the aggregated report database for the various Linux
Kernel CI systems - "KCIDB".
The contracted company/individual needs to be regularly available for
cooperation in the EU time zones (specifically around UTC+3). Generally
part-time work is expected to take 2-4 months, projected between 1 May 2025
and 31 Aug 2025, but may shift and/or stretch to six months.
The deadline to respond to this request for proposals is 26 Mar 2025, followed
by a board vote picking the contractor on 2 Apr 2025. Exact dates might be
subject to change in case of a major practical issue or unavailability of
voting members.
KCIDB Challenges
----------------
At the moment, KCIDB receives up to half a million of test and related data
rows per day (330K average). We keep six months worth of data in PostgreSQL
(117GB in tables and 16GB in indexes) for displaying on dashboards, analyzing,
and generating notifications. The complete archive is stored in BigQuery.
While our dashboards and notifications generally function, their performance
has been degrading recently, due to increasing ingestion, no longer leaving us
space and time to experiment and develop new and exciting features.
Additionally we would like to keep more historical data in the operational
PostgreSQL database, so we can make queries over a larger time-span.
Deliverables
------------
* A design of a scalable database architecture, and an assessment of capacity
required to hold 10x the current load/scale.
* Documented production deployment code integrated with KCIDB CI (existing or
modified), deploying the following:
* A PostgreSQL server tuned for serving the main KCIDB database.
* An empty KCIDB database tuned and ready for accepting data.
* Automated server/schema upgrades NOT included in the automatic
deployment, but available separately.
* Google Cloud and/or Docker/Podman containers as supported deployment
targets.
* All code licensed under GPLv2 or LGPL-2.1
The deliverable process needs to be iterative, gathering extensive feedback
multiple times from the Sysadmin working group and the community at large.
About KernelCI
--------------
KernelCI was created several years ago by Linux kernel maintainers in order to
provide an automated test system for the upstream kernel. It then became a
Linux Foundation project in 2019 and the founding members are still part of
the project. An annual budget is collected from the members’ contributions
which makes it possible to fund work packages, this being one of them.
Responding
-------------
Send you questions and proposals to kernelci-members@groups.io.
Links
-----
Primary KCIDB dashboard
https://kcidb.kernelci.org/
A custom dashboard feeding its database off KCIDB
https://dashboard.kernelci.org/
KCIDB source code
https://github.com/kernelci/kcidb/
https://github.com/kernelci/kcidb-io/
KernelCI project
https://kernelci.org/
Attached is also the official RFP document.
--
Gustavo Padovan
Kernel Lead
Collabora Ltd.
Platinum Building, St John's Innovation Park
Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718
[-- Attachment #1.2: Type: text/html, Size: 49936 bytes --]
[-- Attachment #2: RFP KCIDB DBA.pdf --]
[-- Type: application/pdf, Size: 544491 bytes --]
reply other threads:[~2025-02-20 12:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1952353828f.11bf7ab40849072.7749176993724033096@collabora.com \
--to=gus@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=nikolai.kondrashov@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).