Moved from https://pagure.io/fedora-qa/qa-ansible/issue/3 :
@smilner wrote: We'd like to start testing resultsdb integration from Atomic Host Tests to resultsdb. To do this we'd like to test out integration against the fedora stage instance while we work out any issues we may fine. We've provided the IP ranges that our instances will be posting from outside of this ticket but have opened this for tracking purposes.
/cc @miabbott @mnguyen @dustymabe
@tflink wrote: I don't have any objections to doing this - @puiterwijk , would you be OK with us whitelisting some RH (I assume, they're 10.) for resultsdb (stg for now, eventually production, I imagine).
This is also a reminder to actually get the cert stuff into resultsdb and resultsdb_api, I suppose.
The reason I filed this in qa-ansible, @kparal , is that I thought the whitelist was actually maintained in the ansible plays for Taskotron, not in the Taskotron source itself. It's a configuration detail of the Fedora infrastructure deployment of Taskotron, after all, not a property of Taskotron-the-software-project.
I think it's a shame issues were disabled on qa-ansible, it seems a perfectly useful place to track work that needs to be done in the QA-related bits of infra ansible...
Yes, and this umbrella project does not contain any source code, it serves as a place to file generic feature requests tickets and infra tickets. If you look into issues, half of them have the infra tag. I really don't want to have two different places where to have infra issues filed. I'll clarify the README to mention that Taskotron-related infra tickets are filed here.
infra
I created qa-ansible pagure repo just to have a place where to review PR requests for infra ansible, nothing more. If you want to track QA-related infra issues in there, I don't care much. But I prefer to have Taskotron-related infra issues filed in one project, not two.
Log in to comment on this ticket.