Sepia Lab Wiki

User Tools

Site Tools

Trace:
testnodeaccess

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
testnodeaccess [2022/06/28 14:52] – djgallowaytestnodeaccess [2026/09/14 14:25] (current) – djgalloway
Line 1: Line 1:
 ====== Testnode Access ====== ====== Testnode Access ======
 ===== Summary ===== ===== Summary =====
-We have about 250 baremetal testnodes that get automatically reserved (locked) and unlocked by teuthology "workers."  Workers are daemons on the ''teuthology.front.sepia.ceph.com'' VM that are fed jobs via a beanstalk queue.  This page will cover setting up your workstation to lock and unlock testnodes as well as schedule teuthology suites.+We have about 400 baremetal testnodes that get automatically reserved (locked) and unlocked by teuthology "workers" or "dispatchers."  Workers are daemons on the ''teuthology.front.sepia.ceph.com'' host that are fed jobs via a beanstalk queue.  This page will cover setting up your workstation to lock and unlock testnodes as well as schedule teuthology suites.
  
 Baremetal testnodes get OSes automatically "installed" using [[services:FOG]] when you lock them either via ''teuthology-lock'' or ''teuthology-suite''. Baremetal testnodes get OSes automatically "installed" using [[services:FOG]] when you lock them either via ''teuthology-lock'' or ''teuthology-suite''.
  
 ===== Teuthology Config ===== ===== Teuthology Config =====
-Most developers schedule suites from the ''teuthology.front.sepia.ceph.com'' VM which automatically locks/unlocks machines.+Most developers schedule suites from the ''teuthology.front.sepia.ceph.com'' host which automatically locks/unlocks machines.
  
-However, if you wish to run ''teuthology'' commands from your workstation, see http://docs.ceph.com/teuthology/docs/INSTALL.html#installation-and-setup.+However, if you wish to run ''teuthology'' commands from your workstation, see https://docs.ceph.com/projects/teuthology/en/latest/INSTALL.html#installation-and-setup.
  
 Once you've got ''teuthology'' added to your workstation path, make sure you copy the current ''/etc/teuthology.yaml'' from ''teuthology.front.sepia.ceph.com'' to your **local** workstation's ''~/.teuthology.yaml''. Once you've got ''teuthology'' added to your workstation path, make sure you copy the current ''/etc/teuthology.yaml'' from ''teuthology.front.sepia.ceph.com'' to your **local** workstation's ''~/.teuthology.yaml''.
  
 ===== SSH Config ===== ===== SSH Config =====
-Baremetal testnodes get reprovisioned with an already-configured OS image including a home dir for your user account.  Your ssh public key should be in your user's **and** the ''/home/ubuntu/.ssh/authorized_keys'' file on each testnode.  You should always SSH as your username.+Baremetal testnodes get reprovisioned with an already-configured OS image including a home dir for your user account.  Your SSH public key should be in your user's **and** the ''/home/ubuntu/.ssh/authorized_keys'' file on each testnode.  You should always SSH as your username.
  
 **Example** **Example**
Line 26: Line 26:
  
 <code> <code>
-host teuthology.front.sepia.ceph.com+host teuthology.front.sepia.ceph.com soko04.front.sepia.ceph.com
         User $YOURUSER         User $YOURUSER
         IdentityFile ~/.ssh/id_rsa # (This should be the private key matching the public key you provided in your user access ticket)         IdentityFile ~/.ssh/id_rsa # (This should be the private key matching the public key you provided in your user access ticket)
         ForwardAgent yes # <- This is the important part         ForwardAgent yes # <- This is the important part
  
-host smithi* mira* gibba*+host smithi* gibba* trial*
         StrictHostKeyChecking no         StrictHostKeyChecking no
         UserKnownHostsFile=/dev/null         UserKnownHostsFile=/dev/null
Line 44: Line 44:
   StrictHostKeyChecking no   StrictHostKeyChecking no
   UserKnownHostsFile=/dev/null   UserKnownHostsFile=/dev/null
-</code> 
- 
-===== VPSes ===== 
-VPS (Virtual Private Servers) are ephemeral KVM virtual machines that are spun up on demand using, for example: 
-\\ ''%%teuthology-lock --lock-many 1 --machine-type vps --os-type ubuntu --os-version 14.04%%'' 
- 
-**More Information** 
-  * http://docs.ceph.com/teuthology/docs/downburst_vms.html 
-  * https://github.com/ceph/downburst 
- 
-Their hostnames are ''vpm{001..200}.front.sepia.ceph.com''.  A few [[hardware:mira]] are set aside as hypervisors.  See [[services:vpshosts]]. 
- 
-You must create an RSA SSH keypair (named id_rsa/id_rsa.pub) to ssh to VPSes from the teuthology host.  We also recommend you have us add the public key to your pubkey file in the [[https://github.com/ceph/keys|keys repo]]. 
- 
-//Note: You still need a keypair even when using SSH agent forwarding from your workstation.// 
- 
-The following ''~/.ssh/config'' is required for you to lock VPSes from the teuthology host. 
- 
-<code> 
-Host * 
-  StrictHostKeyChecking no 
-  UserKnownHostsFile /dev/null 
- 
-Host vpm* 
-  User ubuntu 
 </code> </code>
  
Line 82: Line 57:
     - Either generate your SSH key from ''teuthology.front.sepia.ceph.com'' or try ''ssh-keygen -t rsa -m PEM''     - Either generate your SSH key from ''teuthology.front.sepia.ceph.com'' or try ''ssh-keygen -t rsa -m PEM''
   - ''rm -f ~/.ssh/known_hosts'' and add ''UserKnownHostsFile /dev/null'' to your SSH config.   - ''rm -f ~/.ssh/known_hosts'' and add ''UserKnownHostsFile /dev/null'' to your SSH config.
-  - Ask dgalloway to capture new FOG images that include your public SSH key.+  - Ask Adam Kraitman or Dan Mick to capture new FOG images that include your public SSH key.
   - You **must** have ''ForwardAgent yes'' set for ''teuthology.front.sepia.ceph.com'' in your workstation's ''~/.ssh/config'' file.   - You **must** have ''ForwardAgent yes'' set for ''teuthology.front.sepia.ceph.com'' in your workstation's ''~/.ssh/config'' file.
  
testnodeaccess.1656427920.txt.gz · Last modified: by djgalloway