Project

General

Profile

Actions
Copy link

action #48887

closed

[tools][virtualization][s390x automation][deployment] New s390x lpar as worker need to be deployed into OSD

Added by xguo about 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
xguo
Category:
Infrastructure
Target version:
-
Start date:
2019-03-08
Due date:
2019-03-22
% Done:

100%

Estimated time:
Difficulty:

Description

We are QA-APAC2 team, plan to deploy one s390x lpar(i.e s390zp14.suse.de) openQA virtualization automation environment into the official OSD.
its dns name end with suse.de, so it was located at Nuremberg. Please find detailed information below.

WORKER:
hostname=s390zp14.suse.de
ip=10.161.159.119
host system=sles15sp1beta4

Actions
Copy link
 #1

Updated by xguo about 5 years ago

  • Subject changed from [tools][ipmi][s390x automation][deployment] New s390x lpar as worker need to be deployed into OSD to [tools][s390x automation][deployment] New s390x lpar as worker need to be deployed into OSD
Actions
Copy link
 #2

Updated by xguo about 5 years ago

  • Subject changed from [tools][s390x automation][deployment] New s390x lpar as worker need to be deployed into OSD to [tools][virtualization][s390x automation][deployment] New s390x lpar as worker need to be deployed into OSD
Actions
Copy link
 #3

Updated by SLindoMansilla about 5 years ago

  • Description updated (diff)
  • Category set to Infrastructure

This is a public ticket system. User and password removed from the description.

Category set as a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Actions
Copy link
 #4

Updated by xguo about 5 years ago

SLindoMansilla wrote:

This is a public ticket system. User and password removed from the description.

Category set as a result of backlog triaging (see https://progress.opensuse.org/projects/openqatests/wiki#ticket-backlog-triaging for more information).

Please, feel free to adjust the category or the "[label]" if you think different.

Got it.

Thank you so much for your suggestion and great help.

Actions
Copy link
 #6

Updated by xguo about 5 years ago

s390x: Add worker for s390x SUSE ON KVM for sle15sp1 MR#164 was merged by mgriessmeier's great help.
https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/164

Actions
Copy link
 #7

Updated by xguo about 5 years ago

  • Due date set to 2019-03-15
  • Status changed from New to Resolved
  • Assignee set to xguo
  • % Done changed from 0 to 100
Actions
Copy link
 #8

Updated by xguo about 5 years ago

  • Due date changed from 2019-03-15 to 2019-03-22
  • % Done changed from 100 to 80

Add worker for s390x SUSE ON KVM for sles15 and sles12sp4
Summit MR!168
https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/168

Actions
Copy link
 #9

Updated by xguo about 5 years ago

xguo wrote:

We are QA-APAC2 team, plan to deploy one s390x lpar(i.e s390zp14.suse.de) openQA virtualization automation environment into the official OSD.
its dns name end with suse.de, so it was located at Nuremberg. Please find detailed information below.

WORKER:
hostname=s390zp14.suse.de
ip=10.161.159.119
host system=sles15sp1beta4

WORKER:
hostname=s390zp12.suse.de
ip=10.161.159.117
host system=sles12sp4

WORKER:
hostname=s390zp15.suse.de
ip=10.161.159.120
host system=sles15

Actions
Copy link
 #10

Updated by xguo about 5 years ago

  • % Done changed from 80 to 100

mgriessmeier help merge MR!168

Actions
Copy link
 #11

Updated by xlai about 5 years ago

Totally 3 tests are deployed on osd,

gi-guest_developing-on-host_sles12sp4-kvm 35 virt-s390x-kvm-sle12sp4
gi-guest_developing-on-host_sles15-kvm 35 virt-s390x-kvm-sle15
gi-guest_developing-on-host-developing-kvm 35 virt-s390x-kvm-sle15sp1

Actions
Copy link

Also available in: Atom PDF