diff --git a/DC-alp-bedrock b/DC-alp-bedrock index 09719b635..86a42dcab 100644 --- a/DC-alp-bedrock +++ b/DC-alp-bedrock @@ -7,5 +7,5 @@ ASSEMBLY="yes" # ASSEMBLY_DIR="xml" STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" -DOCBOOK5_RNG_URI="http://docbook.org/xml/5.2/rng/docbookxi.rng" +DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" PROFOS="alp-bedrock" diff --git a/DC-alp-micro b/DC-alp-micro index 83b94eef7..ee07f488f 100644 --- a/DC-alp-micro +++ b/DC-alp-micro @@ -7,6 +7,5 @@ ASSEMBLY="yes" # ASSEMBLY_DIR="xml" STYLEROOT="/usr/share/xml/docbook/stylesheet/suse2022-ns" - -DOCBOOK5_RNG_URI="http://docbook.org/xml/5.2/rng/docbookxi.rng" +DOCBOOK5_RNG_URI="urn:x-suse:rng:v2:geekodoc-flat" PROFOS="alp-micro" diff --git a/articles/ALP.asm.xml b/articles/ALP.asm.xml index 74ad19ea2..0fa33d940 100644 --- a/articles/ALP.asm.xml +++ b/articles/ALP.asm.xml @@ -51,6 +51,7 @@ + @@ -72,13 +73,21 @@ The &productname; Guide Changelog + 62023-04-04 + + + Added &zseries; deployment. + + + 52023-03-30 Added an article on running the &ansible; workload. - 42023-03-28 + + 42023-03-28 Updated the &dinstaller; section to include product selection and @@ -171,7 +180,9 @@ - + + + diff --git a/images/src/png/alp-dinstaller-zseries-dasd.png b/images/src/png/alp-dinstaller-zseries-dasd.png new file mode 100644 index 000000000..fed31e8b8 Binary files /dev/null and b/images/src/png/alp-dinstaller-zseries-dasd.png differ diff --git a/images/src/png/alp-zseries-zvm-sles.png b/images/src/png/alp-zseries-zvm-sles.png new file mode 100644 index 000000000..2911344f7 Binary files /dev/null and b/images/src/png/alp-zseries-zvm-sles.png differ diff --git a/images/src/png/alp-zseries-zvm.png b/images/src/png/alp-zseries-zvm.png new file mode 100644 index 000000000..9a876634a Binary files /dev/null and b/images/src/png/alp-zseries-zvm.png differ diff --git a/tasks/deploy-alp-dinstaller.xml b/tasks/deploy-alp-dinstaller.xml index fee74d106..405beb535 100644 --- a/tasks/deploy-alp-dinstaller.xml +++ b/tasks/deploy-alp-dinstaller.xml @@ -133,10 +133,24 @@ - Select the disk device where &productnameshort; should be installed - or click advanced options - menuConfigure iSCSI to - manage iSCSI targets for the installation. + Select the disk device where &productnameshort; should be installed. + Optionally, click Settings to enable LVM or enter + a password for disk encryption. + + + + If you enable disk encryption, you may be asked for a decryption + password on each reboot. Because the &grub; boot loader does not + enable switching keyboard layouts, select a password made of + alphanumeric characters and be aware of national keyboard layout + differences. For extended post-deployment information about disk + encryption, refer to + . + + + + To configure iSCSI targets or DASD disks (for &zseries;) for the + installation, click advanced options menu
Discover iSCSI targets @@ -167,43 +181,27 @@
- - Click Settings from the Storage - screen to enable LVM or enter a password for disk encryption. - - - - If you enable disk encryption, you will be asked for a decryption - password on each reboot. Because the &grub; boot loader does not - enable switching keyboard layouts, select a password made of - alphanumeric characters and be aware of national keyboard layout - differences. For extended post-deployment information about disk - encryption, refer to - . - - - - - - In the Users section, specify a &rootuser; - password, upload a Root SSH public key, or create - an additional user account and optionally enable auto-login for it. -
- Creating a user account + DASD storage contextual menu (&zseries;) - + - + - Creating a user account + DASD storage contextual menu (&zseries;)
+ + + In the Users section, specify a &rootuser; + password, upload a Root SSH public key, or create + an additional user account and optionally enable auto-login for it. + + To begin the installation, click Install and @@ -211,7 +209,8 @@ After the installation is finished, click Reboot - and select ALP from the boot menu after reboot. + and select &productnameshort; from the boot menu + after reboot. diff --git a/tasks/deploy-alp-zseries.xml b/tasks/deploy-alp-zseries.xml new file mode 100644 index 000000000..ae577f6ad --- /dev/null +++ b/tasks/deploy-alp-zseries.xml @@ -0,0 +1,246 @@ + + + + + + %entities; +]> +
+ Deploying &productnameshort; on a &zseries; host +
+ Introduction + + This article describes how to deploy &productnameshort; on an &zseries; + host using &dinstaller;. + + + + In order to run &dinstaller; on &zseries;, bear in mind that the + &dinstaller; live images do not contain + linuxrc, wicked and + the installation-images packages. Therefore + the devices activation and configuration needs adjusting and there is + no interactive menu for configuring certain parameters of the + installation. + + +
+
+ Requirements + + Before installing &productnameshort; on &zseries;, you need to fullfil + the following requirements: + + + + + Deployment on the &zseries; architecture is specific and requires + that you review its basic concepts. Although &productnameshort; is + different from &sle; systems, study the information provided by + + before starting the deployment because most of it is valid for the + &productnameshort; deployment as well. + + + + + Refer to + + for generic system requirements. + + + +
+
+ Download and prepare the installation image + + Download the &dinstaller; image for the &zseries; architecture from + , for + example: + +&prompt.user;curl -LO &alp-dld-site;/Installer:/0.8/images/iso/d-installer-live.s390x-0.8.3-ALP-Build11.1.iso + + Prepare the ISO image to be served by the FTP server. Extract its content + so that you can modify it: + + +&prompt.sudo;mv d-installer-live.s390x-0.8.3-ALP-Build11.1.iso /srv/ftp/d-installer.iso +&prompt.sudo;cd /srv/ftp/ +&prompt.sudo;isoinfo -R -X -i d-installer.iso +&prompt.sudo;chmod a+u boot s390x/initrd + + + + Setting up an installation server (NFS or FTP) is out of the scope of + this article. For further information, refer to + . + + +
+
+ Example deployment procedure + + The following procedure describes steps to deploy &productnameshort; on a + &zseries; machine via a z/VM console. + + + + + Install the x3270 package that provides the + 3270-type terminal emulator. + + + + + Connect to the LPAR server using the x3270 console. When asked, + provide your login credentials. + +
+ Login prompt inside the z/VM console + + + + + + + + Login prompt inside the z/VM console + + +
+ + + + Enter the Conversational Monitoring System (CMS): + +#CP IPL CMS + + + + Link the TCPMAINT disk to have the FTP command available: + +VMLINK TCPMAINT 592 + + + + Connect to the FTP server and download the required files for IPLing + installation. In our case, the anonymous user is allowed: + +FTP example.org (addr ipv4 +anonymous + +cd boot/s390x +locsite fix 80 +ascii +get parmfile sles.parmfile.a (repl +get sles.exec sles.exec.a (repl +locsite fix 80 +binary +get linux sles.linux.a (repl +get initrd sles.initrd.a (repl +quit + + + The locsite fix 80 command sets the VM file + format to a fixed length of 80. This file format is necessary for + punching the binary files to a virtual machine + reader. + + + + + + Optionally, you can use the FILELIST command to + list the files and edit the parmfile + with XEDIT. Our example parmfile has the following content: + +cio_ignore=all,!condev +rd.cio_accept=0.0.0160 +rd.zdev=qeth,0.0.0800:0.0.0801:0.0.0802,layer2=1,portno=0 +ip=192.168.0.111::192.168.0.1:24:zvmtest.example.org:enc800:none +nameserver=192.168.0.1 +root=live:ftp://example.org/d-installer.iso + + + + Although the parameter is optional, + it is used to list only the relevant installation devices and + accept the device that are used for the installation. + + + + + Because we do not have an interactive dialog for enabling and + configuring our network device, we need to provide the settings + through the kernel command line. The + option activates the qeth device and the + option configures network settings for the + enc800 Linux network interface. + + + + + The system boots from a live image retrieved from the specified + URL. Our example uses FTP protocol, but it can be HTTP as well. + + + + + + + The following is the content of the sles.exec + file: + +/* REXX LOAD EXEC FOR SUSE LINUX S/390 VM GUESTS */ +/* LOADS SUSE LINUX S/390 FILES INTO READER */ +SAY '' +SAY 'LOADING SLES FILES INTO READER...' +'CP CLOSE RDR' +'PURGE RDR ALL' +'SPOOL PUNCH * RDR' +'PUNCH SLES LINUX A (NOH' +'PUNCH SLES PARMFILE A (NOH' +'PUNCH SLES INITRD A (NOH' +'IPL 00C' + + Boot the installation image by running the + sles.exec REXX file: + +sles +
+ Booting the installation image + + + + + + + + Booting the installation image + + +
+ + + + After the installation system finishes the booting process, connect + to the machine either with the Web browser (for example, + https://example.host.org:9090) or via SSH using the default + credentials (user name: root, password: + linux). The rest of the installation process is + identical to . + + + +
+