use openqa-python client instead of subprocess calling
ClosedPublic

Authored by garretraziel on Jul 9 2015, 11:42 AM.

Details

Summary

Since adamw created Python client for OpenQA, we
can use it instead of calling Perl in subprocess. It simplyfies
usage and special code for running in Docker is no longer needed.
This version requires user to create configuration file either
in /etc/openqa/client.conf or in ~/.config/openqa/client.conf
with the same KEY and SECRET as in host machine.

To execute jobs in Docker, just specify correct server and
port (probably [localhost:8080]) in configuration file.

Only problem remains with self-signed certificate. It's
necessary to either disable SSL cert verifying, import
self-signed certificate or use HTTP instead of HTTPS in Docker,
see https://github.com/os-autoinst/openQA-python-client/pull/1.

Test Plan

Tested on running tests for compose F22 Final RC1.

Diff Detail

Repository
rOPENQA fedora_openqa
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
garretraziel retitled this revision from to use openqa-python client instead of subprocess calling.Jul 9 2015, 11:42 AM
garretraziel updated this object.
garretraziel edited the test plan for this revision. (Show Details)
garretraziel added reviewers: adamwill, jskladan.
jskladan accepted this revision.Jul 9 2015, 11:44 AM
This revision is now accepted and ready to land.Jul 9 2015, 11:44 AM

Looks fine, we should probably add info on installing the Python client into the installation guide too.

Closed by commit rOPENQA25a024c46723: use openqa-python client instead of subprocess calling (authored by Garret Raziel <boloomka@gmail.com>). · Explain WhyJul 10 2015, 8:43 AM
This revision was automatically updated to reflect the committed changes.