action #151696
closedEvaluate use of https://itpe.io.suse.de/open-platform/docs/ size:M
Added by okurz 6 months ago. Updated 2 months ago.
0%
Description
Motivation¶
We are often asked to provide some VM for developers for personal development environment so we need to maintain hypervisor hosts which so far we do rather manually. More modern tooling and cloud solutions should be able to do a much better job at that.
Announcement from today that OpenPlatform is ready for everyone in SUSE, newsletter https://itpe.io.suse.de/open-platform/docs/news/this-sprint-in-openplatform-9/
(I saw that first mentioned in https://suse.slack.com/archives/C029APBKLGK/p1701266764648529?thread_ts=1701266303.318549&cid=C029APBKLGK)
Acceptance criteria¶
- AC1: It is known if this new platform can be used in any form for individual openQA deployments or personal VMs for us or our SUSE internal users
Suggestions¶
- Read https://itpe.io.suse.de/open-platform/docs/ , create a simple virtual machine, demonstrate it to the team
- If it works out fine include instructions in a corresponding wiki place e.g. on https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs/QA-SLE_cluster so that our fellow SUSE colleagues know how to use it to create personal VMs rather than relying on our limited hosts
- For further support join Slack channel #proj-it-open-platform
Updated by ybonatakis 4 months ago
i need some details to fill in the sd ticket as reqired by the steps here https://itpe.io.suse.de/open-platform/docs/docs/getting_started/requesting_access/
team: BCL
owner: runger@suse.com
environment: test (i guess thats fine)
just confirm/reject the above
missing info i need:
stakeholder: < the budget owner, usually your L3 manager > (who is?)
admin_contacts: < account owner + account administrators, will be the main contact for technical or security topics >Limits:Memory: < how much ram should the project be limited to >
CPU: < how much cpu should the project be limited to >```
Updated by ybonatakis 4 months ago
I hope it looks ok
https://sd.suse.com/servicedesk/customer/portal/1/SD-145337
Updated by ybonatakis 4 months ago
- Status changed from Workable to Blocked
The Ticket has been assigned to the responsible Team to further investigate/respond to this case. blocked for now
Updated by josegomezr 4 months ago
from #152284 there's a template you can follow in this SD Ticket:
This template should help
Select a system
OpenPlatform
Line Manager/Request Approver
Matthias Griessmeier %adjust appropriately%
Description
Please create the following project:
Team: QE-Core team %adjust appropriately%
Project: op-prg2-openqa-integration
Cluster: op-prg2-1
Information: This needs to be the closest to CC compliance as it will be used for testing SLE and test development
stakeholder: %people in your team or managers of your team%
Department: LSG QE
team: QE Core %adjust this%
owner: %developers in your team owners%
environment: testing
admin_contacts: qe-core@suse.de
Limits:
Memory: 8G RAM %tune this appropriately%
CPU: 4vCPU
%description%
Updated by ybonatakis 4 months ago
josegomezr wrote in #note-9:
from #152284 there's a template you can follow in this SD Ticket:
This template should help
Select a system OpenPlatform Line Manager/Request Approver Matthias Griessmeier %adjust appropriately% Description Please create the following project: Team: QE-Core team %adjust appropriately% Project: op-prg2-openqa-integration Cluster: op-prg2-1 Information: This needs to be the closest to CC compliance as it will be used for testing SLE and test development stakeholder: %people in your team or managers of your team% Department: LSG QE team: QE Core %adjust this% owner: %developers in your team owners% environment: testing admin_contacts: qe-core@suse.de Limits: Memory: 8G RAM %tune this appropriately% CPU: 4vCPU %description%
This is quite different than the submitted one. Should i create another? Also note that i requested access to op-prg2-harvester and not to op-prg2-1
Updated by ybonatakis 4 months ago ยท Edited
waiting https://sd.suse.com/servicedesk/customer/portal/1/SD-145766 which is Waiting for approval. After that we should be able to login to the cluster
Updated by tinita 4 months ago
I cannot read https://sd.suse.com/servicedesk/customer/portal/1/SD-145766
Can it be shared with OSD Admins?
Updated by ybonatakis 4 months ago
tinita wrote in #note-12:
I cannot read https://sd.suse.com/servicedesk/customer/portal/1/SD-145766
Can it be shared with OSD Admins?
Done
Updated by livdywan 4 months ago
ybonatakis wrote in #note-11:
waiting https://sd.suse.com/servicedesk/customer/portal/1/SD-145766 which is Waiting for approval. After that we should be able to login to the cluster
We got two approvals. Added a comment to ask if we can proceed (as per our SLO's I checked how to unblock this ticket).
Updated by ybonatakis 3 months ago
- Status changed from In Progress to Blocked
https://sd.suse.com/servicedesk/customer/portal/1/SD-147952
I requested for a wrong account so i filled a new ticket
Updated by ybonatakis 3 months ago
Today i finally managed to login
I create a project openqa-dev in the namespace quickstart
observations:
- easy to control and start an VM from your own image in a few minutes.
- easy access to the VM from web vnc
- I encounter issues with serial. Specifically
ip,psandsystemctlfreezed the serial and terminated the connectionThe requested file could not be read, typically due to permission problems that have occurred after a reference to a file was acquired.
problem found with upload of large files[0]. Url[1] though worked.
[0] https://jira.suse.com/browse/PLAT-278
[1] https://openqa.opensuse.org/tests/3935720/asset/hdd/opensuse-Tumbleweed-x86_64@64bit-2G-:TW.26519.qcow2
Updated by openqa_review 3 months ago
- Due date set to 2024-02-28
Setting due date based on mean cycle time of SUSE QE Tools
Updated by ybonatakis 3 months ago
- Due date deleted (
2024-02-28)
Another approach today. Run TW image and install a server following steps from docs and test jobs. Not fully functional but it is up and running on the VM ip address: http://10.144.103.69/
Updated by openqa_review 3 months ago
- Due date set to 2024-03-01
Setting due date based on mean cycle time of SUSE QE Tools
Updated by ybonatakis 3 months ago
I experimented with a variety of images. I was able to utilize the ones provided
- sles15-sp4-minimal-vm.x86_64-openstack-cloud-gm.qcow2
- sles15-sp5-minimal-vm.x86_64-cloud-gm.qcow2
Any other image i tried from https://download.opensuse.org/repositories/Cloud:/ didnt work with the cloud-init configuration
The cloud-init configuration that worked
#cloud-config
package_update: false
runcmd:
- curl -sSLkO https://rmt.scc.suse.de/tools/rmt-client-setup
- bash ./rmt-client-setup --de-register --host rmt.scc.suse.de --fingerprint
B9:F9:49:29:E7:31:21:AB:1B:EF:27:A0:4F:4F:BE:66:C0:D3:6F:08 --yes
- systemctl enable --now qemu-guest-agent.service
- zypper -n ar
https://download.opensuse.org/repositories/SUSE:/CA/15.4/SUSE:CA.repo
- zypper --gpg-auto-import-keys refresh
- zypper -n in ca-certificates-suse iptables
- zypper -n in open-iscsi
- zypper in -y qemu-guest-agent kernel-default
- zypper -n rm kernel-default-base
- systemctl enable --now qemu-guest-agent.service
- zypper -n up
- zypper -n in emacs
users:
- name: iob
passwd: $6$SalTsaLt$27SSSaieYaREPJu/UZMOCbphGZBzokPJt8Xboy0oqxMCZN.A.g4QDNq/LoZtgwXnOxl927B5a.epeDVEkP8gL.
sudo: ALL=(ALL) NOPASSWD:ALL
groups: users
shell: /bin/bash
lock_passwd: false
ssh_authorized_keys:
- ssh-rsa
<my pub key>
hash created with openssl passwd -6 -salt SalTsaLt iob
and lock_passwd: false is required for passwd login as by default is enabled https://documentation.suse.com/fr-fr/sles/15-SP5/html/SLES-all/article-minimal-vm.html#cloud-init-user1
Updated by ybonatakis 3 months ago
Can someone try login into https://op-prg2.openplatform.suse.com/dashboard/auth?
Updated by okurz 3 months ago
- Status changed from Feedback to Workable
I tried with a username "okurz" and got "An error occurred logging in: Permission denied". For "okurz@suse.com" I get "Invalid username or password. Please try again." so I guess the first is correct but I am missing permissions. How can we ensure that all members from https://progress.opensuse.org/projects/qa/wiki/tools#Team have access?
Updated by ybonatakis 3 months ago
okurz wrote in #note-27:
I tried with a username "okurz" and got "An error occurred logging in: Permission denied". For "okurz@suse.com" I get "Invalid username or password. Please try again." so I guess the first is correct but I am missing permissions. How can we ensure that all members from https://progress.opensuse.org/projects/qa/wiki/tools#Team have access?
We need one SD ticket as https://sd.suse.com/servicedesk/customer/portal/1/SD-147952 with all the members.
Updated by okurz 3 months ago
- Status changed from Resolved to Feedback
tinita wrote in #note-33:
ybonatakis wrote in #note-28:
We need one SD ticket as https://sd.suse.com/servicedesk/customer/portal/1/SD-147952 with all the members.
It would be nice if we could all read this ticket in order to be able to work on #156214
true. @ybonatakis please share the above ticket with the group "OSD Admins" as explained on https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling
Updated by livdywan 2 months ago
We need one SD ticket as https://sd.suse.com/servicedesk/customer/portal/1/SD-147952 with all the members.
It would be nice if we could all read this ticket in order to be able to work on #156214
true. @ybonatakis please share the above ticket with the group "OSD Admins" as explained on https://progress.opensuse.org/projects/qa/wiki/Tools#SUSE-IT-ticket-handling
@ybonatakis maybe we can check it together on Jitsi if you can't figure out how to share the ticket with OSD Admins. Then we can resolve this ticket - and we have follow-ups for other points already.
Updated by ybonatakis 2 months ago
https://sd.suse.com/servicedesk/customer/portal/1/SD-147952 should be visible to all OSD Admins now. can someone check?