action #179380
openFinish fundamental setup for orion to serve as a vmware 7 server in OSD size:S
0%
Description
Motivation¶
orion.oqa.opensuse.org, which is in O3, is planned to be moved to OSD to serve VT test purpose (IT ticket, https://sd.suse.com/servicedesk/customer/portal/1/SD-182743). It will be installed as esxi7 server. It is one of a key part to mitigate PRG1 lab move impact to MU VT test in https://progress.opensuse.org/issues/168970#note-22, which is planned to be ready before end of May. Given the necessary time for qe-virt to further setup, this ticket's best delivery date is before Mid of April, 2025.
qe-virt squad will handle the installation of esxi7 server and openqa salt to add svirt-vmware workers. But we will need tools team effort to work with SUSE IT to help finish the fundamental infra setup for the machine.
Acceptance Criteria¶
- AC1: orion is used in production openQA tests in OSD
- AC2: orion has an updated domain and netbox entry
Suggestions¶
- setup ipmi for the machine, so that its ipmi management webui can be access via QA engineering network both in DE,CZ and BJ
- setup network (OS) to have fixed domain name, which is proper for OSD testing
- setup its ipxe(legacy boot), similar with other OSD test machines
- Ask someone from virt to provide a reference test, and try the machine once it's part of osd
Updated by okurz 6 days ago
- Status changed from Workable to Feedback
- Assignee set to okurz
- Priority changed from High to Normal
I wrote in https://suse.slack.com/archives/C02CANHLANP/p1742904843848469?thread_ts=1742440098.401619&cid=C02CANHLANP as well as https://sd.suse.com/servicedesk/customer/portal/1/SD-182743
As I saw https://sd.suse.com/servicedesk/customer/portal/1/SD-183671 I think the best way going forward to be able to scale is that you gain the experience within your team how to have machines setup for use and we are ready to support you. Let's try with orion first: Can someone from your team go the next step with help from IT to properly update netbox, e.g. power connection, domain, description, status, have the machine added to the IPMI jump host, add according network config in https://gitlab.suse.de/OPS-Service/salt/
Updated by cachen 5 days ago
okurz wrote in #note-4:
I wrote in https://suse.slack.com/archives/C02CANHLANP/p1742904843848469?thread_ts=1742440098.401619&cid=C02CANHLANP as well as https://sd.suse.com/servicedesk/customer/portal/1/SD-182743
As I saw https://sd.suse.com/servicedesk/customer/portal/1/SD-183671 I think the best way going forward to be able to scale is that you gain the experience within your team how to have machines setup for use and we are ready to support you. Let's try with orion first: Can someone from your team go the next step with help from IT to properly update netbox, e.g. power connection, domain, description, status, have the machine added to the IPMI jump host, add according network config in https://gitlab.suse.de/OPS-Service/salt/
@okurz Hello Oli, I probably have different perspective about HW enabling tasks among team co-working. From my point view:
Step 1. Physical infrastructure setup including hardware receiving, racking machines, cable connections, networking in server room, those need to be done by IT teams via sd-jira ticket requirement.
Step 2. DHCP/PXE enabling including ip/hostname assigning for NIC interface and BMC/IPMI interface, those need the help from Tools team to create MR to salt, as this service is maintained by our department, and our System Admin has the complete picture of how this been designed and maintained.
Step 3. System installation and setup for running tests including adding a system to OSD, those need to be done by each team, once they get the BMC access to control this machine.
I guess we all agree with Step 1. and Step 3.
Regarding Step 2. if Tools team think that is fine to delegate this right to each squad, and giving a good guidance how to do that, in case human mistake there, I guess that should also acceptable to each team. We can have a discussion if need.
Updated by livdywan 5 days ago
- Copied to action #179485: Document self-service workflow for setup of new machines added