This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
production:shaman.ceph.com [2021/06/15 14:44] djgalloway |
production:shaman.ceph.com [2023/04/06 00:51] (current) dmick [Summary] |
||
---|---|---|---|
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. | 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 | * 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 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 ===== | ===== User Access ===== |