# kernel test app

https://docs.google.com/document/d/176etJNloUTBoLMhttIqrL4AtNEtz5VJxY7R_efSNXg4/edit
https://pagure.io/cpe/initiatives-proposal/issue/22

Meet with Justin to gather full requirements

Get it running locally

# Issues
Packaged in el7-infra tags
machine is rhel 7(py2 only)
local vagrant is f25
uses travis CI
conflicting readmes
Version 1.2.1 released but v2 in code
supposedly uses fedmsg (we think badges)
Rewrite of code by jcline(https://github.com/jmflinuxtx/kerneltest-harness/commit/5f95a19f3276e11b3f21873adcb1c16d5047f8c1#diff-8b8238839d9c98a26d9a1d5a504a38807afa0dbee153e4d565de8e617e98e51f)

# Meeting with Justin Forbes

Has the rewrite ever been used?
What was wrong with it?

3 different ways to submit results anonymous, authed, api key
Api key should only be avaialble to a select few as these are what appears on the front page

Version 2 is not fully finished. Missing some functionality. May not be worth our while to use it

At the moment it works but unmaintained (v1.2)
nobody getting badges
auth needs to be updated
community issues rather than functionality issues

Next test window Oct30 - Nov6th

Problems:
update auth
fedmsg -> fedora messaging
python2 -> python3
containerization
Documentation - QA has some

Functionality:
* Be able to upload logs anonymous, auth, super user
* Be able to view logs with front page showing super user one
* When you click on release it should show all logs for a release
* Stats: https://apps.fedoraproject.org/kerneltest/stats - postgres -db01
* Logs saved in persistent volume
* Send Fedora Messages for badges
* Uploads not currently allowed anonymously but should be(ideal but not required)
* Size limitation on logs built into code to stop ddos
* Facelift

# Conclusion

Although v1.2.1 is running as expected it is not advisable to keep using it as it is in a poor state.
Version 2 is not feature complete and the database schema is quite different to the live database so some transformation would need to be written.

# Roadmap
1. Get dev env up to date
2. Rewrite of code
3. Write data migration/transformation script
4. Create openshift deployment
5. migrate db