This is an old revision of the document!
Table of Contents
Developer Playgrounds
Developer playground machines are used for developing Ceph.
All machines have cephfs mounts for accessing the teuthology, scratch, and postfile file systems. It is encouraged to use these machines to view teuthology logs as they will be significantly faster than the teuthology VM, which is often memory/CPU starved.
Machines
| Name | Notes |
|---|---|
| senta01.front.sepia.ceph.com | General purpose |
| senta02.front.sepia.ceph.com | General purpose |
| senta03.front.sepia.ceph.com | General purpose |
| vossi01.front.sepia.ceph.com | General purpose |
| vossi04.front.sepia.ceph.com | CephFS Team |
| vossi04.front.sepia.ceph.com | RADOS Team |
| folio02.front.sepia.ceph.com | General purpose |
Playing Nice
Developer playgrounds should be able to build the main branch. It is okay to use ./install-deps.sh top-level scrip from the ceph source tree to update dependencies. Do not run that script from an older release of Ceph as it may break other developer's work. If you need to build an older release, lock a throwaway node like smithi and build there.
Using the developer machines to look at teuthology QA artifacts is encouraged. Try to avoid using a text editor to look at large (1GB+) debug logs as this can be RAM intensive/disruptive. Instead, prefer less or use tail -c xM | $EDITOR - to look at portions of the log in a text editor.
Many of the developer playground nodes have extra disks for testing Ceph. It's okay to use these for vstart clusters but it may be more flexible to build LVM volumes on top of these devices so others may use them too.
