koji

#2516 Moving scheduler logic to hub
Closed by tkopecek. Opened by tkopecek.
tkopecek/koji scheduler  into  master

Download 2516.patch

It is a WIP
- We have to move logic to hub
- potentially lower number of calls to hub
- allows us to design some task-based policy
- builder tracks usage of its own resources (mem/disk for now) so it can refuse a task which needs more resources.

What is missing is storing request_resources in db/task. I've started with moving the logic but now it looks that it can be solved without that. (even without uploading resource info to hub). Question is if we want to have such policies or what is the best way to continue now. (discussion starts now)

rebased onto 9ed4368269c6343752b3d7b0f2c39e75fae2b834

@mikem cleaned:
- dropped resources management
- dropped skipped_tasks table
- delaying task is not 1:1 with the old code now, but it is based on task['create_time'] instead with a bit different behaviour, but seems sufficient to me for now.

5 new commits added

  • remove skipped_tasks table and resources management
  • subtract used/reserved resources from free_resources
  • reservations
  • basic task policy
  • move task selection logic to hub

rebased onto 68495711685c9ab22a7aa0514abedcd444fbc39e

rebased onto dde7f0581f05c37ff873b52660cce5ae7410a680

Obsoleted by #3772

Pull-Request has been closed by tkopecek
Metadata
None
No Tags
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.