Use rdo registry for rdo third party check job

In order to reduce dependency on docker.io, let's consume
containers from rdo registry in software factory jobs and
since they exists in same cloud, so it will pretty much
faster.

We are setting the same for rdo and vexxhost cloud.

Depends-On: https://review.opendev.org/#/c/753265/

Change-Id: I372be4816b9c068259f7742a5be68dbb5934dd2b
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>

toci-quickstart/config/testenv/multinode-rdocloud.yml

@@ -39,6 +39,9 @@ build_undercloud: false
 # We don't need to cleanup TripleO CI
 tempest_track_resources: false
 
+# Rely on RDO registry instead of docker.io due to rate limit
+docker_registry_host: trunk.registry.rdoproject.org
+
 # Use cirros cached image
 tempest_test_image_path: /opt/cache/files/cirros-0.3.5-x86_64-disk.img
 tempest_tempest_conf_overrides:

toci-quickstart/config/testenv/multinode-vexxhost.yml

@@ -35,6 +35,9 @@ image_cache_dir_cleanup: true
 build_image_isolated: false
 build_undercloud: false
 
+# Rely on RDO registry instead of docker.io due to rate limit
+docker_registry_host: trunk.registry.rdoproject.org
+
 # We don't need to cleanup TripleO CI
 tempest_track_resources: false
 

toci-quickstart/config/testenv/ovb-rdocloud.yml

@@ -25,6 +25,9 @@ update_containers: >-
   true
   {%- endif -%}
 
+# Rely on RDO registry instead of docker.io due to rate limit
+docker_registry_host: trunk.registry.rdoproject.org
+
 # We don't need to cleanup TripleO CI
 tempest_track_resources: false
 

toci-quickstart/config/testenv/ovb-vexxhost.yml

@@ -25,6 +25,9 @@ update_containers: >-
   true
   {%- endif -%}
 
+# Rely on RDO registry instead of docker.io due to rate limit
+docker_registry_host: trunk.registry.rdoproject.org
+
 # We don't need to cleanup TripleO CI
 tempest_track_resources: false