Project

General

Profile

Actions

action #128495

closed

coordination #121855: [epic] Agama web interactive installation

[Timebox: 24h] Investigate how to run Agama in s390x

Added by JERiveraMoya about 1 year ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2023-05-02
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Once development of ALP will be moved to OBS, we can investigate how to run Agama in s390x
Image is available in OBS: https://build.opensuse.org/package/binaries/YaST:Head:Agama/agama-live:ALP/images

Acceptance criteria

AC1: Investigate how to run Agama in s390x

Additional information

Existing documentation in the repo: https://github.com/openSUSE/agama/blob/master/doc/deployment_guide_s390.md


Related issues 1 (0 open1 closed)

Related to qe-yam - action #132548: Run manual testing for Agama on s390x z/VMResolvedsyrianidou_sofia2023-07-11

Actions
Actions #1

Updated by JERiveraMoya about 1 year ago

I remember some documentation presented by YaST team, asked in this thread:
https://suse.slack.com/archives/C02TLF25571/p1683004842567129

Actions #2

Updated by JERiveraMoya about 1 year ago

  • Description updated (diff)
Actions #3

Updated by JERiveraMoya about 1 year ago

  • Status changed from Workable to New

Let's postpone this as ALP development is being moved to OBS.

Actions #4

Updated by JERiveraMoya about 1 year ago

  • Target version deleted (Current)
Actions #5

Updated by JERiveraMoya about 1 year ago

  • Subject changed from [Timebox: 24h] Investigate if infrastructure allow us to enable Agama in s390x only in O3 to [Timebox: 24h] Investigate how to run Agama in s390x
  • Description updated (diff)
  • Priority changed from Normal to Low
Actions #6

Updated by JERiveraMoya 11 months ago

  • Status changed from New to Workable
  • Target version set to Current
Actions #7

Updated by hjluo 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to hjluo
Actions #8

Updated by JERiveraMoya 11 months ago

  • Due date set to 2023-06-28

this ticket could be quite tricky, setting due date according to those 24h (3 days aprox.)
Please, share with the squad your finding after this period and we will decide what to do with the ticket.

Actions #9

Updated by hjluo 11 months ago

Status till 06/26:

  • Asked Lemon for how to use x3270 terminal {host/user/passwd}
  • read the s390x doc
  • asked the related guy.(Ladislav Slezak)
Hi Ladislav, I'm now checking agama on s390x, and checked out https://github.com/openSUSE/agama/blob/master/doc/deployment_guide_s390.md
and found this
FTP example.org (addr ipv4
anonymous
cd boot/s390x
locsite fix 80
ascii
get parmfile sles.parmfile.a (repl
what does the (addr ipv4 and (repl means in commands   FTP example.org (addr ipv4  and get parmfile sles.parmfile.a (repl
Ah, I actually did just some small renames in the document, I'm not an s390 expert. Please ask @Knut Anderssen for more details, he is the original author and has much more s390 experience. :slightly_smiling_face:
  • now asking Knut Anderssen
> Knut Anderssen
> the main point here is that current images are not published on dist.suse.de
> or nue.suse.de so, I think you relied mainly in the ftpboot REXP script

the most important thing I needed to change in the vsftpd conf was (ascii_download_enable=YES) for the parmfile and the sles REXP script

I allow anonymous user and use the root as anon_root=/mnt/ftp
so just mounting the image there as described is enough, you don't need to extract it anymore.
Actions #10

Updated by hjluo 11 months ago

Status till 06/27:
asked Knut and he said:

the main point here is that current images are not published on dist.suse.de
or nue.suse.de so, I think you relied mainly in the ftpboot REXP script.
which is not useful for Agama unless they start publishing the images there, therefore, a custom FTP server is needed for that.

Q: do we have detailed info for how to setup that server?
A: don't think so
what is needed is already documented there but is quite easy
you can do it with YaST or by hand it is just a vsftpd server

there is this section alp-zseries-prepare-iso-image And cha-zseries.html#sec-zseries-prep

there is the documentation about the ftp setup also linked sec-deployment-instserver-sles9

the most important thing I needed to change in the vsftpd conf was (ascii_download_enable=YES)
for the parmfile and the sles REXP script
I allow anonymous user
and use the root as anon_root=/mnt/ftp
so just mounting the image there as described is enough, you don't need to extract it anymore

Actions #11

Updated by JERiveraMoya 11 months ago

For the ftp we can use qaboot in the way described in our doc:
https://confluence.suse.com/display/qasle/How-To%3A+Manual+Testing+Guide#HowTo:ManualTestingGuide-zVM
Last available server I remember we could use was s390zp13 @Xuguang Guo maintained.

Actions #12

Updated by hjluo 11 months ago

OK. now just blocked by setup the vsftp server to agama.iso

Actions #13

Updated by hjluo 11 months ago

status till 06/28:
Now the s390x expert Knut Anderssen suggests me use ftp://10.160.0.207/ which
was used by openQA, and we'd first upload d-installer-live.s390x-0.8.3-ALP-Build11.1.iso to that vsftp server. and use the following configuration. cause currently I'm stuck at "it looks like you don't have permissions to on local disk"


vsftpd settings

# Limit passive ports to this range to assis firewalling
pasv_min_port=30000
pasv_max_port=30100
anon_mkdir_write_enable=NO
anon_root=/mnt/ftp
anon_upload_enable=NO
chroot_local_user=YES
ftpd_banner=Welcome message
idle_session_timeout=900
log_ftp_protocol=YES
max_clients=10
max_per_ip=3
pasv_enable=YES
ssl_tlsv1=YES
xferlog_enable=YES

# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
ascii_upload_enable=YES
ascii_download_enable=YES

Now the problem is at the temporal disk file assigned to you. if you have no write permissions you should ask Ihno. but you can use a temporal disk instead

this guide is very useful
https://confluence.suse.com/display/hardwareenablement/Working+with+s390x+at+SUSE

Actions #14

Updated by hjluo 11 months ago

Now can we just stop here? cause I'm not familiar with the s390x zvm operations and 3 days passed while asking and waiting for the developer's reply cost most of the time. @JERiveraMoya

Actions #15

Updated by JERiveraMoya 11 months ago

  • Due date deleted (2023-06-28)
  • Status changed from In Progress to Workable
  • Assignee deleted (hjluo)
  • Priority changed from Low to Normal

yes, thanks for the investigation, let's move the ticket to the backlog for someone else to try out.
I will keep the same timebox.

Actions #16

Updated by coolgw 11 months ago

  • Status changed from Workable to In Progress
  • Assignee set to coolgw
Actions #18

Updated by leli 11 months ago

  • Related to action #132548: Run manual testing for Agama on s390x z/VM added
Actions #19

Updated by JERiveraMoya 11 months ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF