[autotest] Let TKO parser always talk to global database
In order to have the test results of distributed moblabs in one
central place, the TKO parser must always talk to the global
database, not to the local one that the local AFE and scheduler_db
are talking to.
This adds a second database configuration to the global_config and
makes the TKO parser always use that one.
BUG=None
DEPLOY=tko
TEST=Ran suites.
Change-Id: I613fd393e2d9d26c36e77c81badb86b589fd980e
Reviewed-on: https://chromium-review.googlesource.com/213259
Tested-by: Jakob Jülich <jakobjuelich@chromium.org>
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Jakob Jülich <jakobjuelich@chromium.org>
diff --git a/global_config.ini b/global_config.ini
index 1468d88..16f2d4a 100644
--- a/global_config.ini
+++ b/global_config.ini
@@ -31,6 +31,18 @@
# is too much verbosity for 'production' systems, hence turned off by default.
sql_debug_mode: False
+# The tko parser will use these database settings.
+# This is for sharding: Even when sharding, the results (tko tables) should
+# still be written to the master database.
+global_db_host: 172.18.72.10
+global_db_database: chromeos_autotest_db
+global_db_type: mysql
+global_db_user: chromeosqa-admin
+global_db_password: USE SHADOW PASSWORD
+global_db_query_timeout: 3600
+global_db_min_retry_delay: 20
+global_db_max_retry_delay: 60
+
[SHARD]
# If this is not None, the instance is considered a shard.
# The value should be the hostname of the local shard.