action #37372
closed[tools][pvm] powerVM production worker
Added by okurz almost 6 years ago. Updated over 5 years ago.
0%
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
Updated by okurz almost 6 years ago
- Copied from action #33340: [tools][functional][u][medium][pvm] Enable graphical installation for the powerVM backend added
Updated by okurz almost 6 years ago
- Target version changed from Milestone 18 to Milestone 18
Updated by okurz almost 6 years ago
- Due date changed from 2018-07-31 to 2018-08-14
Updated by okurz over 5 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
Updated by okurz over 5 years ago
- Copied to action #39008: [tools][pvm] Redundant powerVM production workers added
Updated by okurz over 5 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
Updated by oorlov over 5 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.
Updated by oorlov over 5 years ago
mgriessmeier talked to ihno. He is checking for the available resources.
Updated by okurz over 5 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
Updated by okurz over 5 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?
Updated by mgriessmeier over 5 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
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-08-28 to 2018-09-11
Updated by mgriessmeier over 5 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
Updated by mgriessmeier over 5 years ago
- Due date changed from 2018-09-11 to 2018-09-25
- Target version changed from Milestone 18 to Milestone 19
Updated by nicksinger over 5 years ago
- Status changed from Feedback to Workable
Updated by okurz over 5 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.
Updated by okurz over 5 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".
Updated by nicksinger over 5 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.
Updated by okurz over 5 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.
Updated by okurz over 5 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
Updated by okurz over 5 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.
Updated by nicksinger over 5 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.
Updated by nicksinger over 5 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 =)
Updated by nicksinger over 5 years ago
https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/125
Installing vugava-1 now for shared-development purposes.
Updated by nicksinger over 5 years ago
- Status changed from In Progress to Feedback
Updated by okurz over 5 years ago
- Related to action #33697: [tools][hard][pvm] Enable the powerVM backend to conduct multimachine tests added
Updated by coolo over 5 years ago
- Project changed from openQA Tests to openQA Infrastructure
- Category deleted (
Infrastructure)
Updated by okurz over 5 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"
Updated by nicksinger over 5 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/