Project

General

Profile

Actions
Copy link

action #37372

closed

[tools][pvm] powerVM production worker

Added by okurz over 6 years ago. Updated about 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
nicksinger
Category:
-
Target version:
-
Start date:
2018-03-15
Due date:
% Done:

0%

Estimated time:

Description

Acceptance criteria

  • AC1: openqa.suse.de has access to at least one powerVM production worker (physical machine)
  • AC2: Production worker is not used for development

Tasks

  • Clarify hardware situation (which machines to use?)
    • potential points of contact: dheidler, nsinger, zluo, coolo, ihno, marita, jloeser
    • According to #37372#note-15 there is a machine ready. That machine should be removed from orthos so that we can dedicate it to OSD
  • Add worker config in salt recipes
  • Ensure the setup is stable, e.g. the worker survives at least two builds of SLE with jobs executed on this machine

Related issues 4 (0 open — 4 closed)

Related to openQA Tests (public) - action #39005: [functional][u][pvm] Enable the existing SLE12 pvm testsuite on SLE15, e.g. "textmode" on SLE12SP4 to SLE15SP1Resolveddheidler2018-08-012018-08-28

Actions
Related to openQA Project (public) - action #33697: [tools][hard][pvm] Enable the powerVM backend to conduct multimachine testsResolvedokurz2018-08-01

Actions
Copied from openQA Tests (public) - action #33340: [tools][functional][u][medium][pvm] Enable graphical installation for the powerVM backendResolvedmgriessmeier2018-03-15

Actions
Copied to openQA Infrastructure (public) - action #39008: [tools][pvm] Redundant powerVM production workersResolvedokurz2018-03-15

Actions
Actions
Copy link
 #1

Updated by okurz over 6 years ago

  • Copied from action #33340: [tools][functional][u][medium][pvm] Enable graphical installation for the powerVM backend added
Actions
Copy link
 #2

Updated by okurz over 6 years ago

  • Status changed from New to Workable
Actions
Copy link
 #3

Updated by okurz over 6 years ago

  • Target version changed from Milestone 18 to Milestone 18
Actions
Copy link
 #4

Updated by okurz over 6 years ago

  • Due date changed from 2018-07-31 to 2018-08-14
Actions
Copy link
 #5

Updated by mgriessmeier over 6 years ago

  • Description updated (diff)
Actions
Copy link
 #6

Updated by okurz over 6 years ago

  • Related to action #39005: [functional][u][pvm] Enable the existing SLE12 pvm testsuite on SLE15, e.g. "textmode" on SLE12SP4 to SLE15SP1 added
Actions
Copy link
 #7

Updated by okurz over 6 years ago

  • Copied to action #39008: [tools][pvm] Redundant powerVM production workers added
Actions
Copy link
 #8

Updated by okurz over 6 years ago

  • Subject changed from [tools][functional][u][pvm] powerVM production workers to [tools][functional][u][pvm] powerVM production worker
  • Description updated (diff)
  • Category changed from New test to Infrastructure
Actions
Copy link
 #9

Updated by oorlov over 6 years ago

I would say, that now the issue should looks like 'poverVM development worker'.

I've discussed the task with Santiago and he told me, that tools team already decided to salt 'grenage' to Production.

Actions
Copy link
 #10

Updated by oorlov over 6 years ago

mgriessmeier talked to ihno. He is checking for the available resources.

Actions
Copy link
 #11

Updated by okurz over 6 years ago

  • Due date changed from 2018-08-14 to 2018-08-28

bulk move to next sprint as could not be discussed in SR

Actions
Copy link
 #12

Updated by okurz over 6 years ago

  • Status changed from Workable to Feedback
  • Assignee set to mgriessmeier

@mgriessmeier According to the latest comment by @oorlov you "talked to ihno". Can you track this ticket or how should we proceed with the ticket?

Actions
Copy link
 #13

Updated by mgriessmeier over 6 years ago

okurz wrote:

@mgriessmeier According to the latest comment by @oorlov you "talked to ihno". Can you track this ticket or how should we proceed with the ticket?

update from Ihno (Aug 21st):
Toni (aeisner) from Stefans team is working on that

Actions
Copy link
 #14

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2018-08-28 to 2018-09-11
Actions
Copy link
 #15

Updated by mgriessmeier over 6 years ago

  • Assignee changed from mgriessmeier to nicksinger

got reply from Toni:

Hi Matthias & Nick,

ich hab eine LPAR (vugava-1.arch.suse.de) für Euch erstellt, sie läuft
auf vugava.arch.suse.de. Musste aber die die CPS aufteilen, Eure hat 4
virtuelle mit je 2,33 GHz, 4GB Speicher und 40GB HDD. Sollte es nicht
ausreichen, erstelle ich Euch eine auf Vilana, da müssen wir allerdings
mit dem Haris reden.

Die Maschine hab ich in Orthos eingetragen und auf aeisner
übergangsweise reserviert. Sollte sie aus Orthos raus müssen, oder auf
einen von Euch resaviert werden sollen, sagt bitte den Thomas R.
bescheid, bin erst wieder Montag im Haus.

Nick can proceed from here, reassigning

Actions
Copy link
 #16

Updated by mgriessmeier over 6 years ago

  • Due date changed from 2018-09-11 to 2018-09-25
  • Target version changed from Milestone 18 to Milestone 19
Actions
Copy link
 #17

Updated by nicksinger over 6 years ago

  • Status changed from Feedback to Workable
Actions
Copy link
 #18

Updated by okurz over 6 years ago

@nicksinger I leave it to your professional opinion regarding the state of monitoring and integration of the existing workers if we are ready yet to bring in more workers. E.g. we would make sure our workers are better monitored first before continuing here.

Actions
Copy link
 #19

Updated by okurz over 6 years ago

  • Due date deleted (2018-09-25)
  • Assignee deleted (nicksinger)
  • Target version changed from Milestone 19 to Milestone 20

I'll take that as a "yes, we should wait for proper monitoring first".

Actions
Copy link
 #20

Updated by nicksinger over 6 years ago

  • Assignee set to nicksinger
  • Target version changed from Milestone 20 to Milestone 19

We already have grenache on OSD for whatever reason: https://openqa.suse.de/admin/workers/1103
I couldn't find any traces in salt so I guess its yet another worker hotpatched into OSD.

I'll wait until somebody starts whining again about missing resources with power.

Actions
Copy link
 #21

Updated by okurz over 6 years ago

nicksinger wrote:

We already have grenache on OSD for whatever reason: https://openqa.suse.de/admin/workers/1103
I couldn't find any traces in salt so I guess its yet another worker hotpatched into OSD.

Yes, that's the point of this ticket. We have grenache as an "spvm" worker in osd but it has only been added manually. It is used for development as well and most likely something will break sometime in the future. I do not even know if any updates are installed.

I'll wait until somebody starts whining again about missing resources with power.

Either that or at best when "monitoring" is in place for at least the s390x and aarch64 and ppc64le-kvm workers we already have in production, agreed? Please link the according monitoring ticket(s) as blocking ones. I will communicate the state in the QA SLE coordination meeting as well.

Actions
Copy link
 #22

Updated by okurz over 6 years ago

  • Target version changed from Milestone 19 to Milestone 21

adjusting based on my assumption when we would have monitoring for all existing production workers in place and when we would be able to have this ticket finished covering the machine mentioned in #37372#note-15

Actions
Copy link
 #23

Updated by nicksinger about 6 years ago

  • Assignee deleted (nicksinger)
Actions
Copy link
 #24

Updated by okurz about 6 years ago

  • Description updated (diff)
  • Status changed from Workable to Blocked
  • Assignee set to okurz
  • Target version changed from Milestone 21 to Milestone 20

I understood that this is seen as "blocked" by the monitoring work where we need to invest. So I will assign this ticket to myself to find the blockers first.

Actions
Copy link
 #25

Updated by nicksinger about 6 years ago

oorlov wrote:

I would say, that now the issue should looks like 'poverVM development worker'.

I've discussed the task with Santiago and he told me, that tools team already decided to salt 'grenage' to Production.

Just want to highlight this comment from oorlov once more.

Actions
Copy link
 #27

Updated by nicksinger about 6 years ago

  • Status changed from Blocked to In Progress
  • Assignee changed from okurz to nicksinger

Kind of blocks the powerVM shared dev worker so therefore I'll get it out of our way =)

Actions
Copy link
 #28

Updated by nicksinger about 6 years ago

https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/125
Installing vugava-1 now for shared-development purposes.

Actions
Copy link
 #29

Updated by nicksinger about 6 years ago

  • Status changed from In Progress to Feedback
Actions
Copy link
 #31

Updated by okurz about 6 years ago

  • Related to action #33697: [tools][hard][pvm] Enable the powerVM backend to conduct multimachine tests added
Actions
Copy link
 #32

Updated by coolo about 6 years ago

  • Project changed from openQA Tests (public) to openQA Infrastructure (public)
  • Category deleted (Infrastructure)
Actions
Copy link
 #33

Updated by okurz about 6 years ago

  • Subject changed from [tools][functional][u][pvm] powerVM production worker to [tools][pvm] powerVM production worker
  • Target version deleted (Milestone 20)

nicksinger moved to "QA tools"

Actions
Copy link
 #34

Updated by nicksinger about 6 years ago

  • Status changed from Feedback to Resolved

No bigger problems observed and it survived at least two builds. Guess we're done here \o/

Actions
Copy link

Also available in: Atom PDF