Database Information

Architecture

The database is named summit-db-logical-replica in the summit-db-logical-replica Kubernetes namespace.

Logical replication uses a publication and subscription model. Both the publication and subscription summit database instances are deployed with the Cloud Native Postgres (CNPG) Operator. The publication is configured at the Summit with a CNPG cluster name of cnpg in the cloudnativepg Kubernetes namespace. Contact the devops-team Slack channel for assistance with the Summit database to update the publication or with troubleshooting.

No external connectivity is configured or needed for the database. Logical replication traffic uses the LHN. The DNS name is usdf-summitdb-replica.slac.stanford.edu

Architecture Diagram

Summit DB Logical Replication

Associated Systems

Consolidated Database API, ExposureLog API, NarrativeLog API, and Nightreport API applications use the database as a data source for the APIs.

Configuration Location

The database cluster configuration is the GitHub repository. SQL for the table structures are in the SQL folder in the overlay.

Data Flow

Postgres replication is from the Summit to the USDF. The Summit has the publications configured and the USDF has the subscriptions. The subscriptions pull from the publication.

Dependencies - S3DF

Below are the S3DF Dependencies.

  • Kubernetes

  • SLAC LDAP to authenticate to vCluster

  • LHN connectivity to the Summit

  • DNS to resolution of cp.lsst.org domain to resolve the Summit database

  • Weka storage for Kubernetes. The database uses a persistent volume claim.

  • S3 for backups and WAL archiving

Dependencies - External

The external dependencies is the LHN connectivity to the Summit.

Disaster Recovery