action #131549
closed
QA - coordination #121720: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability
QA - coordination #129280: [epic] Move from SUSE NUE1 (Maxtorhof) to new NBG Datacenters
coordination #131519: [epic] Additional redundancy for OSD virtualization testing
[spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv 2016 worker host size:M
Added by okurz over 1 year ago.
Updated about 1 year ago.
Files
- Subject changed from [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv worker host to [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv worker host size:M
- Description updated (diff)
- Status changed from New to Workable
- Target version changed from Ready to future
Hyperv 2016 will have higher priority than hyperv 2012r2. Suggest to start from 2016 first.
- Assignee set to nanzhang
- Target version changed from future to Ready
@okurz, Hi Oliver, FYI, Nan is familiar with the openqa needed setup for the machine, so he will try to install hyperv 2016 with the machine and set it up in OSD, if the machine can meet the hardware requirement for the tests.
@cachen @Julie_CAO @rcai FYI too, we finally find that hyperv 2016 has the highest priority to build redundancy, so we start trying from it. Given that Roy is busy with another urgent ticket for cutting off MU coverage, we ask Nan to help try first.
- Target version changed from Ready to future
As explained in https://suse.slack.com/archives/C02CANHLANP/p1689241995483089
@here There are a lot of tasks to be done in light of the AC climate issue mitigation, datacenter migrations and infrastructure management. On the other hand SUSE QE Tools is suffering from multiple absences. I am looking for other teams and people to help in particular on tasks on https://progress.opensuse.org/issues?query_id=757 . If you can help over the next days, weeks and months please pick up tasks from there or consult me for how we can most efficiently collaborate.
So removing from our backlog for now due exceeding backlog capacity. Anyone can continue to work on this of course
- Target version changed from future to Ready
It's very slow to load the iso image from local at home. And when I used the virtual media share from web console, there is a limitation on unreal8(supermicro) which CD-ROM image over a Windows share with a maximum size of 4.7GB. The size of hyperv2016 iso is 5.3G.
So I have to go to office for set up this machine.
- Target version changed from Ready to future
- Subject changed from [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv worker host size:M to [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv 2016 worker host size:M
- Due date set to 2023-08-31
Virt team plans to have it done before Sep.
- Priority changed from Normal to High
- Tags set to infra, hyperv, virt, virtualization
- Subject changed from [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv 2016 worker host size:M to Additional redundancy for OSD virtualization testing - Hyperv 2019 and 2022 (or 2012r2) worker host size:M
- Description updated (diff)
- Due date deleted (
2023-08-31)
- Assignee deleted (
nanzhang)
- Priority changed from High to Normal
- Start date deleted (
2023-06-28)
- Copied to action #133247: Additional redundancy for OSD virtualization testing - Hyperv 2019 and 2022 (or 2012r2) worker host size:M added
- Subject changed from Additional redundancy for OSD virtualization testing - Hyperv 2019 and 2022 (or 2012r2) worker host size:M to [spike][timeboxed:20h] Additional redundancy for OSD virtualization testing - Hyperv 2016 worker host size:M
- Description updated (diff)
- Due date set to 2023-08-31
- Assignee set to nanzhang
- Priority changed from Normal to High
- Start date set to 2023-06-28
Sorry, I updated the ticket by mistake. I thought I was working on a copy for hyper2019 instead. That new ticket will be #133247
The installer can't proceed due to missing required drivers.
- Tags set to infra, hyperv, virt
- Priority changed from Normal to High
- Target version changed from Ready to future
- Tags changed from infra, hyperv, virt to infra, hyperv, virt, virtualization
Looks like some hardware of this machine are not compatible with Windows server 2016.
nanzhang wrote:
Looks like some hardware of this machine are not compatible with Windows server 2016.
Ok, what is missing? Maybe we can help with that?
okurz wrote:
I just found https://www.supermicro.com/support/resources/OS/C224.cfm . Apparently the system is explicitly reported to be compatible with Windows Server 2012 R2 64bit but not 2016.
@okurz, thanks for the check. This is very helpful.
@nanzhang It seems to me the machine is very old, and the supported os list does not cover any recent products which we would like to install, namely sles15, vmware 7, hyperv 2016+. Are all these unrealxx machines assigned us the same hardware configurations? If yes, I am afraid the situation won't be very promising for usable machine.
What is proper next step now? Quickly check installing other OS?
Thanks Oliver for checking!
@xlai, Next step I need to check if all other unreal machines are the same model.
As checked, they are the same supermicro model(X10SLD-F/HF) from unreal2 to unreal8. The compatibility list does not include Vmware ESXi7, we still can't ensure if it works or not.
nanzhang wrote:
As checked, they are the same supermicro model(X10SLD-F/HF) from unreal2 to unreal8. The compatibility list does not include Vmware ESXi7, we still can't ensure if it works or not.
I think we'd better give it a try for ESXi7. So does sle15sp5 xen. Then we will know what can these machines install to.
- Description updated (diff)
- Description updated (diff)
Check with Nan to install windows server 2016.
Finally succeed to install it on unreal5 though the documenthttps://www.supermicro.com/support/resources/OS/C224.cfm indicate it is not supported.
Still need make some configuration to be suitable for OSD.
- Status changed from Workable to In Progress
Correct status, it is wip.
@nanzhang @xlai may I ask you to please update the due-date to a reasonable expectable future date as 2023-08-31 has already passed
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Due date deleted (
2023-08-31)
Also available in: Atom
PDF
