Application Information¶

Architecture¶

The Consolidated Database system uses these components:

Postgres database: This database resides within the same database instance as the exposurelog in order to facilitate joins between the two, but it has distinct schemas. At the Summit, this database runs on the postgresdb01.cp.lsst.org server. At USDF, this database runs on the usdf-summitdb-logical-replica.sdf.slac.stanford.edu server.
hinfo service: This service, running at the Summit, reads the output of the HeaderService for each instrument and inserts it into ConsDB, creating the primary keys for exposures and visits.
transformed_efd package: This container runs periodically at USDF, querying the Engineering and Facilities Database (EFD) and transforming it into per-exposure records inserted into separate schemas within ConsDB.
pqserver service: This service provides a REST API for querying ConsDB and for inserting rows into it. It runs at both the Summit and USDF.

In addition, a TAP service is configured to query the ConsDB Postgres database, including a TAP Schema database describing the ConsDB schema.

Architecture Diagram¶

Associated Systems¶

Rapid Analysis at the Summit analyzes images and computes quality and other metrics that are loaded into the *_quicklook tables within ConsDB schemas.

Other applications may also insert data; each should have its own table suffix.

Configuration Location¶

Config Area	Location
Configuration	lsst-sqre/phalanx
Vault Secrets Dev	rubin/usdf-consdb-dev/transformed-efd
Vault Secrets Prod	rubin/usdf-consdb/transformed-efd rubin/usdf-summitdb/logical-replica

Data Flow¶

Dependencies - S3DF¶

Kubernetes (at Summit and USDF)
Phalanx (at Summit and USDF)
Postgres (usdf-summitdb-logical-replica)
EFD (at USDF)

Dependencies - External¶

Kubernetes (at Summit)
Phalanx (at Summit)
Postgres (postgresdb01.cp.lsst.org)
HeaderService (at Summit)