Fix handling of job ids in Lancium adapter

[giffels]

Job id's at Lancium are integers and the Lancium adapter is treating them also as integers. In addition, the job id is used as remote_resource_uuid in TARDIS and is therefore stored in the persistent drone registry.
In the drone registry the remote_resource_uuid is handled as VARCHAR(255). Thus. when TARDIS is restarted after a shutdown, the remote_resource_uuid is treated as a string in TARDIS.

This pull request fixes the handling of jobd ids in the Lancium adapter by always converting the remote_resource_uuid to an integer before actually checking the status of the corresponding job in Lancium.

[codecov-commenter]

Codecov Report

Base: 98.88% // Head: 98.88% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (e2155d0) compared to base (a6566c4).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #280   +/-   ##
=======================================
  Coverage   98.88%   98.88%           
=======================================
  Files          56       56           
  Lines        2325     2328    +3     
=======================================
+ Hits         2299     2302    +3     
  Misses         26       26           

Impacted Files	Coverage Δ
tardis/adapters/sites/lancium.py	100.00% <100.00%> (ø)
tardis/adapters/sites/openstack.py	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[mschnepf]

What about the methods stop_resource and terminate_resourcein the lancium adaper? Is there the conversion also necessary?

[giffels]

What about the methods stop_resource and terminate_resourcein the lancium adaper? Is there the conversion also necessary?

Good point. I think it does not matter here, but it does not harm anyway. So, I have fixed it as well.

[mschnepf]

Thanks for your work. It looks good to me. 👍

[rfvc]

Thanks, @giffels, looks good!