Differences

This shows you the differences between two versions of the page.

--- services:paddles [2026/10/02 18:47] – djgalloway
+++ services:paddles [2026/10/02 18:49] (current) – djgalloway
@@ Line 19: / Line 19: @@
 <code>
-oc exec -n paddles $(oc get pods -n paddles -o name | grep -v build |  head -1) -- pecan expire_jobs config.py -q 14 -r 30
+oc -n paddles exec deploy/paddles -- pecan expire_jobs config.py -q 14 -r 30
 </code>
@@ Line 36: / Line 36: @@
 </code>
-==== Upgrade Paddles ====
+==== Upgrading Paddles ====
-The paddles API / Web UI services live in Openshift in the ''paddles'' namespace.  There is a cronjob that checks quay.io/ceph/paddles for a new image every 5 minutes.  The ImageStream will automatically deploy any new images.  See https://github.com/ceph/sepia-openshift/tree/main/paddles
+Merges to paddles ''main'' deploy themselves: GitHub Actions pushes ''quay.io/ceph-infra/paddles:main'' (~10 min), the ImageStream polls Quay every 5 minutes, and the trigger annotation on the Deployment rolls out the new digest.  Alembic migrations are applied by the new pod at startup - see the paddles-db README for the migration runbook.
+To check what's deployed or force a roll:
+<code>
+oc -n paddles get istag paddles:main
+oc -n paddles rollout restart deploy/paddles
+</code>
+==== Restarting ====
+<code>
+oc -n paddles rollout restart deploy/paddles
+</code>
+==== Getting a psql shell ====
+Replicas are read-only, so find the leader first:
+<code>
+oc -n paddles-db exec -it $(oc -n paddles-db get pod -l postgres-operator.crunchydata.com/role=master -o name) -c database -- psql paddles
+# or: patronictl list from any inst pod
+</code>