This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
start [2019/07/25 18:50] djgalloway |
start [2019/08/13 17:58] djgalloway |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | __false__ | + | ====== Home ====== |
+ | |||
+ | 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]]. | ||
+ | |||
+ | ==== 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. | ||
+ | |||
+ | Ping/Power support is provided by Red Hat's PnT DevOps Labs 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). | ||
+ | |||
+ | A useful reference for such things is [[http://animaldiversity.org/|http://animaldiversity.org/]] or [[wp>Sepia_(genus)|]] | ||
+ | |||
+ | A **very** simplified version of the automation/test workflow is:<code> | ||
+ | github push -> jenkins -> baremetal slave -> shaman <-> chacra -> teuthology -> fog -> testnode -> paddles | ||
+ | | OR | | ||
+ | \ mita -> prado -> OVH slave / | ||
+ | </code> | ||