action #25924
closed
[infrastructure][tools] Install the new openQA x86 workers
Added by nicksinger over 6 years ago.
Updated over 4 years ago.
Description
openqaworker10=10.160.2.20
openqaworker10-IPMI=10.160.2.21
openqaworker11=10.160.2.22
openqaworker11-IPMI=10.160.2.23
openqaworker12=10.160.2.24
openqaworker12-IPMI=10.160.2.25
openqaworker13=10.160.2.26
openqaworker13-IPMI=10.160.2.27
needs to be setup
- Description updated (diff)
- Category set to Infrastructure
How to setup an openqa worker (last step equals current status of openqaworker10):
- Leap42.3
- Formatting:
- Full size btrfs on the ~1TB HDD without separate home
- Snapshots and subvolumes enabled
- After installation:
- $
hostnamectl set-hostname openqaworker10
- $
zypper ref && zypper up
- $
zypper in openQA-worker && zypper in salt-minion #with all recommends
- $
fdisk /dev/nvme0n1 -> n[ew partition] with everything default and confirm the warning at the end (about the ntfs signature) and exit fdisk with "w" to write the partitioning layout
- $
mkfs.ext2 /dev/nvme0n1p1
- $
lsblk -o NAME,UUID and edit the /etc/fstab to mount the NVMe: e.g.: UUID=fbc2f555-ba70-4af7-8ec2-0291c2d49957 /var/lib/openqa/pool ext2 acl,user_xattr 0 0
- $
mount /var/lib/openqa/pool/
- Edit
/etc/salt/minion and adjust to our salt master: master: openqa.suse.de
- Add the new worker into our salt config (workerconf.sls) and request a merge with:
https://gitlab.suse.de/openqa/salt-pillars-openqa
- $
systemctl start salt-minion #check with salt-key -L on openqa.suse.de if the worker now shows up under "Unaccepted Keys" with the correct hostname
UEFI tests cannot run on this worker. Some package was installed on the other workers manually. Need to find out which one it is and include it into salt.
- Subject changed from [infrastructure] Install the new openQA x86 workers to [infrastructure][tools] Install the new openQA x86 workers
- Status changed from In Progress to New
- Checklist item changed from to [x] Put openqaworker10 in production, [ ] Put openqaworker11 in production, [ ] Put openqaworker12 in production, [ ] Put openqaworker13 in production
- % Done changed from 0 to 20
As already discussed with @foursixnine I pass this to the tools team.
- Assignee deleted (
nicksinger)
- Checklist item changed from [x] Put openqaworker10 in production, [ ] Put openqaworker11 in production, [ ] Put openqaworker12 in production, [ ] Put openqaworker13 in production to [x] Put openqaworker10 in production, [x] Put openqaworker11 in production, [x] Put openqaworker12 in production, [x] Put openqaworker13 in production
- Project changed from openQA Tests to openQA Infrastructure
- Category deleted (
Infrastructure)
I'm sure that this is solved by now, I'm not sure however, about the status of openQA worker 10 :) That's a story :D.
openqaworker13.suse.de is the only one in production, 11 and 12 are being used by the tools team.
- Status changed from New to Resolved
Also available in: Atom
PDF