Bug 1388266

Summary: Koji integration: instead of using a thread pool we need a better asyncio aware integration
Product: [Community] rpm-test-trigger Reporter: Roman Joost <rjoost>
Component: generalAssignee: beaker-dev-list
Status: MODIFIED --- QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unreleased   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1388265    
Bug Blocks:    

Description Roman Joost 2016-10-24 23:27:53 UTC 
The current koji integration uses the koji Python client package. The downside of it is that we're using a threadpool to execute the koji requests to XMLRPC concurrently. This can be expensive and won't scale more than what we're bound by the CPU of the host machine.

Alternatives:

* Don't use a thread pool and the koji client library, but instead use the requests solution from Bug 1388265
* Write your own XMLRPC asyncio library??
Comment 1 Dan Callaghan 2016-12-09 06:16:19 UTC 
https://gerrit.beaker-project.org/5531