action #57461

Remove openqaw1/2/3/4 as OSD workers - openqaw3/4 have been unused since probably 2 years (!)

Added by okurz 5 months ago. Updated 4 months ago.

Status:ResolvedStart date:27/09/2019
Priority:NormalDue date:14/10/2019
Assignee:nicksinger% Done:

0%

Category:-
Target version:openQA Project - Current Sprint
Duration: 12

Description

I wonder about openqaw1 and openqaw2, both are only running a single worker instance now. https://gitlab.suse.de/openqa/salt-pillars-openqa/commit/29b20f917f6b510a3ab3193343fb620e54073a8e moved of the remote workers to grenache that do not impact performance much because they are for remote runners, not qemu.

History

#1 Updated by okurz 5 months ago

  • Status changed from In Progress to Feedback

#2 Updated by okurz 5 months ago

  • Subject changed from Make use of openqaw1 and openqaw2 more to Make proper use of openqaw1/2/3/4 again (or decommission) - openqaw3/4 have been unused since probably 2 years (!)

Discussed in rocket chat: We should repurpose openqaw1/2 as IMPI hardware - if possible. As worker hardware they are not good enough.

"w3 and w4 have been repurposed long ago". But actually they are assigned with a special worker class having them unused for generic IPMI, see https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/47 . coolo decided to completely decommission the four machines

Updated https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/193 to decommission the four workers.

#3 Updated by okurz 5 months ago

  • Subject changed from Make proper use of openqaw1/2/3/4 again (or decommission) - openqaw3/4 have been unused since probably 2 years (!) to Decommission openqaw1/2/3/4 (Or make proper use of them again) - openqaw3/4 have been unused since probably 2 years (!)
  • Due date set to 14/10/2019
  • Status changed from Feedback to Workable
  • Assignee changed from okurz to nicksinger

@nicksinger I guess you need to help here as I don't have access to the lab to pull the plug. Alternatively we can ask mgriessmeier when he's back.

#4 Updated by nicksinger 5 months ago

  • Assignee changed from nicksinger to okurz

First disable them where they are used - you already kind of started this by https://gitlab.suse.de/openqa/salt-pillars-openqa/merge_requests/193 (therefore I'll not interfere here). Afterwards you can assign the ticket again to me and I take care about flagging them in racktables.

#5 Updated by okurz 5 months ago

  • Assignee changed from okurz to nicksinger

#6 Updated by okurz 5 months ago

powered down openqaw1 and openqaw2 and removed salt keys. I failed to delete alerts from https://stats.openqa-monitor.qa.suse.de/alerting/list but I paused all for openqaw1 and openqaw2.

#7 Updated by nicksinger 5 months ago

as discussed with @okurz I will come up with a salt recipe ensuring we only have active workers in our dashboard-templating-directory on the monitoring host. Currently we only create them (based on active salt-minions) but never delete any.

#8 Updated by nicksinger 4 months ago

  • Status changed from Workable to Feedback

#9 Updated by nicksinger 4 months ago

  • Subject changed from Decommission openqaw1/2/3/4 (Or make proper use of them again) - openqaw3/4 have been unused since probably 2 years (!) to Remove openqaw1/2/3/4 as OSD workers - openqaw3/4 have been unused since probably 2 years (!)
  • Status changed from Feedback to Resolved

Renamed the title to actually reflect what was our main purpose with that ticket. Closing as this is done.

Also available in: Atom PDF