Sepia Lab Wiki

User Tools

Site Tools

Trace:
devplayground

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
devplayground [2024/06/03 19:49] – pdonnelldevplayground [2026/09/14 14:23] (current) – djgalloway
Line 8: Line 8:
  
 ^ Name                                             ^ Notes            ^ ^ Name                                             ^ Notes            ^
-| [[hardware:senta|senta01.front.sepia.ceph.com]]  | General purpose  | 
-| [[hardware:senta|senta02.front.sepia.ceph.com]]  | General purpose  | 
-| [[hardware:senta|senta03.front.sepia.ceph.com]]  | General purpose  | 
 | [[hardware:vossi|vossi01.front.sepia.ceph.com]]  | General purpose  | | [[hardware:vossi|vossi01.front.sepia.ceph.com]]  | General purpose  |
 | [[hardware:vossi|vossi04.front.sepia.ceph.com]]  | CephFS Team      | | [[hardware:vossi|vossi04.front.sepia.ceph.com]]  | CephFS Team      |
Line 19: Line 16:
 ==== Playing Nice ==== ==== 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 [[hardware:smithi]] and build there. Or, use a container to do the build/testing!+Developer playgrounds should be able to build the ''main'' branch. It is okay to use ''./install-deps.sh'' top-level script 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 [[hardware:smithi]] and build there. Or, use a container to do the build/testing!
  
 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. 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.
Line 52: Line 49:
 ==== Configuring CephFS Mounts ==== ==== Configuring CephFS Mounts ====
  
-The following script can be run to setup CephFS mounts on a new developer playground machines:+The following ansible playbook can be run to setup CephFS mounts on a new developer playground machines: https://wiki.sepia.ceph.com/doku.php?id=services:cephfs
  
-<code> 
-#!/bin/bash 
  
-HOST="$1"+==== Teuthology scheduling ====
  
-function run { +Configure the dev playground node to schedule jobs:
-  printf '%s\n' "$*" >&2 +
-  "$@" +
-} +
- +
-function mssh { +
-  run ssh "$HOST" -- "$*" +
-} +
- +
-mssh sudo mkdir -p -m 755 /etc/ceph +
-ssh reesi001.front.sepia.ceph.com 'env CEPH_KEYRING=/etc/ceph/client.sepian.keyring ceph --id sepian config generate-minimal-conf' | mssh sudo tee /etc/ceph/ceph.conf +
-mssh sudo chmod 644 /etc/ceph/ceph.conf +
-ssh reesi001.front.sepia.ceph.com 'cat /etc/ceph/client.sepian.keyring' | mssh sudo tee /etc/ceph/client.sepian.keyring +
-mssh sudo chmod 644 /etc/ceph/client.sepian.keyring +
-ssh reesi001.front.sepia.ceph.com 'ceph-authtool /etc/ceph/client.sepian.keyring -n client.sepian -p' | mssh sudo tee /etc/ceph/client.sepian.secret +
-mssh sudo chmod 600 /etc/ceph/client.sepian.secret +
- +
- +
-function genmount { +
-  local secret=$(mssh sudo cat /etc/ceph/client.sepian.secret) +
-  # create mountpoint +
-  mssh sudo mkdir -p -- "$2" +
-  # make the mountpoint directory (shadowed) unwriteable to prevent accidental modification +
-  mssh sudo chmod 000 -- "$2" +
-  # set it immutable to enforce that even for root +
-  mssh sudo chattr +i -- "$2" +
-  printf '172.21.2.201,172.21.2.202,172.21.2.203:%s\t%s\tceph\tname=sepian,secret=%s,mds_namespace=%s,_netdev\t0\t2\n' "$1" "$2" "$secret" "$3" | mssh sudo tee -a /etc/fstab +
-} +
- +
-genmount /teuthology-archive /teuthology teuthology +
-genmount / /scratch scratch +
-genmount / /postfile postfile +
- +
-mssh sudo systemctl daemon-reload +
-mssh sudo mount /teuthology +
-mssh sudo mount /scratch +
-mssh sudo mount /postfile +
-mssh sudo ln -s /teuthology /a +
-</code> +
- +
- +
-==== Teuthology scheduling ====+
  
 <code> <code>
Line 109: Line 63:
 active_machine_types: active_machine_types:
   - smithi   - smithi
 +  - trial
 +  - gibba
 EOF EOF
 </code> </code>
  
 +Note: killing a run is (generally) still necessary on [[services:teuthology|teuthology host]]. This is because teuthology-kill requires killing the test processes running there.
  
 ==== Configuring LVM volumes using spare disks ==== ==== Configuring LVM volumes using spare disks ====
Line 144: Line 101:
 sudo chattr +i $HOME/build sudo chattr +i $HOME/build
 echo "/dev/DevPlayground/$(whoami)-build $HOME/build xfs defaults 1 1" | sudo tee -a /etc/fstab echo "/dev/DevPlayground/$(whoami)-build $HOME/build xfs defaults 1 1" | sudo tee -a /etc/fstab
-sudo systemctl daemon reload+sudo systemctl daemon-reload
 sudo mount $HOME/build sudo mount $HOME/build
 </code> </code>
devplayground.1717444148.txt.gz · Last modified: by pdonnell