Koji operator demo
by Leonardo Rossetti
Hello all,
I would like to share a video[1] where I show how to deploy Koji in
Kubernetes through the operator[2] (in its current state) that I am
currently working on.
I also try to explain some of the internal mechanics of the operator in the
video, such as how it uses custom resources to deploy and run Koji
components.
This is part of an effort in making it available in Kubernetes through the
operator-hub[3] and possibly with other applications/tools used by
Fedora/CentOS as well.
Warning: the video is 21 minutes log :-)
Any feedback is always welcome :-)
[1] - https://youtu.be/rXZaO8LxqWw
[2] - https://pagure.io/kube-sig/koji-operator
[3] - https://operatorhub.io/
Regards,
--
Leonardo Rossetti
Senior Software Engineer,
Red Hat <https://www.redhat.com>
lrossett(a)redhat.com
<https://www.redhat.com>
1 year, 9 months
Koji 1.27.1 release
by Tomas Kopecek
Koji 1.27.1 is out. Another minor update. So, the update should be
straightforward (no db schema changes) and safe for everybody. End-users
(CLI) are encouraged to update too as there are also minor client-side
fixes.
Thanks to everyone who contributed!
You can read the release notes here:
https://docs.pagure.org/koji/release_notes/release_notes_1.27.1/
Highlights:
- #3172 CLI regression fix (dropped --keytab option)
- #3186 fix policy failing on missing buildtag (content generators)
- #3166 kojira now will not fail on deleted (side)tags
- new docs
- improved testing (including migration to pytest)
- 11 issues fixed
You can view the 1.26.1 roadmap at https://pagure.io/koji/roadmap/1.27.1/
For the current roadmap, see https://pagure.io/koji/roadmap
You can download this and other releases at https://pagure.io/koji/releases
or PyPi.
See you again with major release 1.28 in ~two months!
--
Tomas Kopecek <tkopecek(a)redhat.com>
RHEL Build Development, RedHat
1 year, 10 months
eliminating tags' package lists in Koji
by Ken Dreyer
What if we removed the concept of package lists for tags in Koji?
In other words, we would remove these concepts:
koji add-pkg ...
koji remove-pkg ...
It's a lot of manual work to keep package lists (especially owners!)
up-to-date. It's a simpler workflow if users can just:
Step 1) Create a dist-git repo for a package
Step 2) Perform a build of the package
This would eliminate the following steps:
- "Discover who the human owner will be"
- "Ensure that human owner has a user account in Koji's database
(possibly asking them to pre-create their account)"
- "Keep the ownership records up-to-date over time" (for example:
so-and-so has left the Perl team, how should that developer update
Koji to stop getting emails?)
- Ken
1 year, 10 months
Koji-Postgres max_connection limits
by Robby Callicotte
Greetings all,
I have recently installed koji(-hub/web) 1.27.0 on CentOS 8 stream and I'm
seeing some very odd behavior. It appears that koji is maxing out the
connections to the postgres database. I'm running postgres 13 with all
default connection settings (max_connections=100) using unix-sockets instead
of tcp-sockets.
Periodically, clicking around in the koji-web interface yields the message
"Server is offline". After some time I am able to resume clicking links.
Postgres logs show this message when the "Server offline" message appears:
2022-01-07 15:41:48.449 CST [185432] FATAL: remaining connection slots are
reserved for non-replication superuser connections
2022-01-07 15:43:09.907 CST [185558] FATAL: remaining connection slots are
reserved for non-replication superuser connections
Systemd shows the following:
● postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor
preset: disabled)
Active: active (running) since Fri 2022-01-07 17:25:12 CST; 3min 8s ago
Process: 199845 ExecStartPre=/usr/libexec/postgresql-check-db-dir postgresql
(code=exited, status=0/SUCCESS)
Main PID: 199848 (postmaster)
Tasks: 100 (limit: 75288)
Memory: 201.8M
CGroup: /system.slice/postgresql.service
├─199848 /usr/bin/postmaster -D /var/lib/pgsql/data
├─199849 postgres: logger
├─199851 postgres: checkpointer
├─199852 postgres: background writer
├─199853 postgres: walwriter
├─199854 postgres: autovacuum launcher
├─199855 postgres: stats collector
├─199856 postgres: logical replication launcher
├─199867 postgres: koji koji [local] idle
├─199869 postgres: koji koji [local] idle
├─199870 postgres: koji koji [local] idle
├─199871 postgres: koji koji [local] idle
├─199872 postgres: koji koji [local] idle
...
The host that runs koji has only been active for one day and is not configured
with any tags, buildroots, or packages. There are only two build hosts
connected to the hub.
I would appreciate any assistance you could give.
PS - I increased the max_connections setting in postgres to 200 and eventually
that limit is also reached.
--
Robby Callicotte
He/Him/His
Timezone: America/Chicago
IRC: c4t3l | Twitter: @robbycl2v
1 year, 10 months
