Project

General

Profile

Actions
Copy link

action #38018

closed

coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability

coordination #129280: [epic] Move from SUSE NUE1 (Maxtorhof) to new NBG Datacenters

coordination #37910: [tools][epic] Migration of or away from qanet.qa.suse.de

[labs][tools] Setup new qanet

Added by nicksinger over 6 years ago. Updated over 1 year ago.

Status:
Rejected
Priority:
Normal
Assignee:
okurz
Target version:
openQA Project - Ready
Start date:
2018-06-29
Due date:
% Done:

0%

Estimated time:
Tags:
infra

Description

Depending on the decision made in the parent epic, qanet will need the initial setup.
This ticket also need further refinement with AC's and a better task description before being workable.

I decided to go with a virtual machine on qamaster for now. This enables me to partially migrate services over from the old qanet to the new server.

Related issues 1 (0 open — 1 closed)

Precedes QA - action #38012: [tools][labs][medium] Setup DHCPv6 and DNS AAAA records for VLAN12Rejectedokurz2018-06-30

Actions
Actions
Copy link
 #1

Updated by nicksinger over 6 years ago

  • Parent task set to #37910
Actions
Copy link
 #2

Updated by nicksinger over 6 years ago

  • Precedes action #38012: [tools][labs][medium] Setup DHCPv6 and DNS AAAA records for VLAN12 added
Actions
Copy link
 #3

Updated by nicksinger about 5 years ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions
Copy link
 #4

Updated by nicksinger about 5 years ago

The new server is called "qanet2" and currently hosted as VM on qamaster.qa.suse.de
I used Leap15.0 as base operating system and instantly upgraded to Leap15.1 after the initial setup.

I want to manage the whole server by salt from the beginning. Therefore I just installed "salt-master" until now and do some initial configuration to be able to bootstrap eventual other new server with as few manual steps as possible.

Actions
Copy link
 #5

Updated by nicksinger about 5 years ago

Manual steps done (starting with a fresh install of Leap15.1):

zypper in salt-master
zypper in git-core
git config --global user.name "root"
git config --global user.email "root@qanet2.qa.suse.de"
[…hacked together local salt recipes…] (this will end up in https://gitlab.suse.de/qa-sle/qanet-salt and should later just be cloned to get started)
salt-call --local state.apply salt.master
salt-call --local state.apply
salt-key -A
Actions
Copy link
 #6

Updated by okurz over 1 year ago

  • Tags set to infra
  • Category set to Infrastructure
  • Status changed from Workable to Rejected
  • Assignee set to okurz
  • Target version set to Ready

After the above described steps a physical machine "qanet2" was setup, not sure why but shouldn't matter because as of now in the old location qanet is still running and for FC Basement lab we have a different VM based setup as described in https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs which should cover the original requirement better

Actions
Copy link
 #7

Updated by okurz over 1 year ago

  • Subject changed from [labs] Setup new qanet to [labs][tools] Setup new qanet
Actions
Copy link

Also available in: Atom PDF