YARR-LocalDB interaction: April 2023 Mini-workshop summary
-
dbAccessor
can now accept "bare miniminal" connectivity json to push to LocalDB.-
It does not need anymore the module serial number written -
It does not need the "name" of each FE written (now it is taken from the chip config contents)
-
-
dbAccessor
now checks the LocalDB readiness before accepting the scan record. Scans are pushed when:- The module and FE SNs are properly registered in LocalDB
- The stage of the module is later than "MODULE/INITIAL_WARM"
- The initial config is already generated at LocalDB.
-
@gstark's plan: remove all dbAccessor
stuffs fromYARR
and migrate it tomodule-qc-database-tools
: Not for the May release. -
ChipConfigAPI
is integrated inmoduleq-qc-database-tools
.-
The API is now commonly used in
YARR-dbAccessor
and inlocaldb-tools
. -
Uploading FE configs between YARR and LocalDB has been tested to work.
-
Config revision history is now browsable on LocalDB
-
-
YARR is still not able to pull the latest FE configs from LocalDB and bootstrap it in the connectivity+config files "on the fly". So far the "local" initial config is generated by a local command mqdbt generate-yarr-config
.