Differences

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

--- production:shaman.ceph.com [2020/03/07 01:00] – djgalloway
+++ production:shaman.ceph.com [2023/04/06 00:51] (current) – [Summary] dmick
@@ Line 4: / Line 4: @@
 There are three VMs in the [[https://wiki.sepia.ceph.com/doku.php?id=services:ovh#production_services|OVH CI region]] that make up shaman.
-  * shaman.ceph.com is just a load balancing VM
+  * shaman.ceph.com is just a load balancing VM.  Accesses are proxied to either 1.shaman.ceph.com or 2.shaman.ceph.com with an 'upstream shaman' clause in /etc/nginx/nginx.conf, which is then referred to by the site config for shaman.ceph.com.
   * 1.shaman.ceph.com is the primary shaman node that has the postgres DB with all the repo information
   * 2.shaman.ceph.com is a **READ ONLY** backup in the event 1.shaman.ceph.com goes down
+  * 2.shaman.ceph.com can handle write requests because pecan, the web framework, is also aware of the primary/hot standby configuration, and so will redirect writes to 1.shaman.ceph.com on its own, if they appear.
 ===== User Access =====
@@ Line 66: / Line 67: @@
     irvingi_builds = {}
     braggi_builds = {}
+    adami_builds = {}
     rest_of_the_world = {}
     ovh_count = 0
     irvingi_count = 0
     braggi_count = 0
+    adami_count = 0
     for build in builds:
@@ Line 82: / Line 85: @@
             mapping = braggi_builds
             counter = braggi_count
+        elif 'adami' in node_name:
+            mapping = adami_builds
+            counter = adami_count
         else:
             mapping = rest_of_the_world
@@ Line 90: / Line 96: @@
             mapping[node_name] = 1
-    for mapping in [ovh_builds, irvingi_builds, braggi_builds]:
+    for mapping in [ovh_builds, irvingi_builds, braggi_builds, adami_builds]:
         count = 0
         for key, value in mapping.items():
@@ Line 108: / Line 114: @@
 In [4]: two_week_stats.report()
+</code>
+==== Delete builds/repos from database ====
+HYPOTHETICALLY ;-) if a repo/build got pushed to shaman that contains an embargoed security fix, you can delete the entries from shaman's DB.  The packages will still be on chacra servers but shaman won't know about them.  You can always [[production:chacra.ceph.com#manually_delete_a_repo_from_postgres_db|delete]] them from chacra too if necessary.
+<code>
+ssh 1.shaman.ceph.com
+sudo su - postgres
+postgres@1:~$ psql -d shaman
+psql (9.5.23)
+Type "help" for help.
+shaman=# \dt
+             List of relations
+ Schema |      Name       | Type  | Owner
+--------+-----------------+-------+--------
+ public | alembic_version | table | shaman
+ public | archs           | table | shaman
+ public | builds          | table | shaman
+ public | nodes           | table | shaman
+ public | projects        | table | shaman
+ public | repos           | table | shaman
+(6 rows)
+shaman=# delete from public.builds where sha1 = 'f73b19678311b996984c30e7c0eb96a22ffa29ce';
+DELETE 6
+shaman=# select id from public.repos where sha1 = 'f73b19678311b996984c30e7c0eb96a22ffa29ce';
+   id
+--------
+shaman=# delete from public.archs where repo_id = '197001';
+DELETE 1
+shaman=# delete from public.archs where repo_id = '197010';
+DELETE 2
+shaman=# delete from public.archs where repo_id = '197011';
+DELETE 2
+shaman=# delete from public.archs where repo_id = '197012';
+DELETE 2
+shaman=# delete from public.archs where repo_id = '197030';
+DELETE 2
+shaman=# delete from public.archs where repo_id = '196999';
+DELETE 1
+shaman=# delete from public.repos where sha1 = 'f73b19678311b996984c30e7c0eb96a22ffa29ce';
+DELETE 6
 </code>