Differences

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

--- start [2019/08/13 17:58] – djgalloway
+++ start [2026/09/14 14:08] (current) – djgalloway
@@ Line 3: / Line 3: @@
 This wiki contains notes on managing and using the “Sepia” lab of test machines used by the Ceph upstream developers.
-The target audience for this documentation is administrators and people managing the Sepia machines. If all you need is information on using the lab, [[:gettingstarted|Start Here]].
+The primary audience for this documentation is administrators and people managing the Sepia infrastructure. If all you need is information on using the lab, [[:gettingstarted|Start Here]].
 ==== About ====
-The Sepia lab is located in Red Hat's Community space in a datacenter co-location facility maintained by Peak10. The datacenter in which the Community space resides is commonly referred to as RDU2, RAL3C or The Community Cage.
+The Sepia lab is currently located in one of IBM's datacenters in Poughkeepsie, NY.  Previous homes are Irvine, CA and Morrisville, NC.
-Ping/Power support is provided by Red Hat's PnT DevOps Labs team. Generally, tickets should be submitted by the Infra team.
+Ping/Power support is provided by IBM's OneIT team. Generally, tickets should be submitted by the Infra team.
 Sepia is the name we gave to our pool of test machines. It happens to be both a color and a genus of cuttlefish. When we have different kinds of hardware in the sepia pool, we name them after individual species in the sepia genus (e.g., mira or smithi).
@@ Line 16: / Line 16: @@
 A **very** simplified version of the automation/test workflow is:<code>
-github push -> jenkins ->        baremetal slave       -> shaman <-> chacra -> teuthology -> fog -> testnode -> paddles
+github push -> jenkins -> baremetal jenkins builder -> shaman <-> chacra -> teuthology -> fog -> testnode -> paddles
-                         |             OR              |
-                          \ mita -> prado -> OVH slave /
 </code>