action #128222
open
[virtualization] The Xen specific host configuration on openqaw5-xen can be re-created from salt size:M
Added by okurz about 1 year ago.
Updated 6 months ago.
Description
Motivation¶
With #125534 resolved the host openqaw5-xen.qa.suse.de is covered in salt using https://gitlab.suse.de/openqa/salt-states-openqa as a generic host. To ensure that the Xen specific host configuration can be preserved we should cover Xen specific rules in salt as well.
Acceptance criteria¶
Suggestions¶
- Due date set to 2023-05-08
- Status changed from In Progress to Feedback
Wrote in https://suse.slack.com/archives/C02CANHLANP/p1682341543790809
@Calen Chen @Xiaoli Ai openqaw5-xen.qa.suse.de is now properly monitored and updated using the salt recipes maintained by the tools team. The next step would be https://progress.opensuse.org/issues/123754 "The Xen specific host configuration on openqaw5-xen can be re-created from salt" . Can you help me to collect the requirements? At best someone from QE Virtualization can come up with salt recipes for a Xen openQA virtualization host but I can help with that part if you can give me documentation/instruction/notes on what needs to be done to setup such a system
- Project changed from 175 to openQA Infrastructure
(Nan Zhang) I talked with Alice for the ticket, I will give a config list on the Xen host including all required steps in the first week after Labor Day
- Subject changed from [virtualization] The Xen specific host configuration on openqaw5-xen can be re-created from salt to [virtualization] The Xen specific host configuration on openqaw5-xen can be re-created from salt size:M
- Related to action #128417: [alert][grafana] openqaw5-xen: partitions usage (%) alert fired and quickly after recovered again size:M added
- Due date changed from 2023-05-08 to 2023-05-26
- Due date changed from 2023-05-26 to 2023-06-23
We voted to give Nan Zhang more time and I pinged them in Slack.
- Due date deleted (
2023-06-23)
- Status changed from Feedback to Workable
- Assignee deleted (
okurz)
We discussed this in our unblock meeting and decided that we plan to do it on our own.
- Status changed from Workable to Feedback
- Assignee set to okurz
Let's try again after discussion with xlai, cachen, Nan Zhang
- Status changed from Feedback to New
- Assignee deleted (
okurz)
- Target version changed from Ready to future
Still no update. We will not further follow up with this within our backlog for now meaning that Xen testing capabilities are not guaranteed and are under risk of breakage.
- Parent task deleted (
#123754)
according to last comment
Also available in: Atom
PDF