-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
8 changed files
with
292 additions
and
37 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,246 @@ | ||
| <?xml version="1.0" encoding="UTF-8"?> | ||
| <!-- This file originates from the project https://github.com/openSUSE/doc-kit --> | ||
| <!-- This file can be edited downstream. --> | ||
| <?xml-stylesheet href="urn:x-suse:xslt:profiling:docbook51-profile.xsl" | ||
| type="text/xml" | ||
| title="Profiling step"?> | ||
| <!DOCTYPE article | ||
| [ | ||
| <!ENTITY % entities SYSTEM "../common/generic-entities.ent"> | ||
| %entities; | ||
| ]> | ||
| <article xml:id="task-deploy-alp-zseries" xml:lang="en" | ||
| role="task" | ||
| xmlns="http://docbook.org/ns/docbook" version="5.1" | ||
| xmlns:its="http://www.w3.org/2005/11/its" | ||
| xmlns:xi="http://www.w3.org/2001/XInclude" | ||
| xmlns:xlink="http://www.w3.org/1999/xlink"> | ||
| <title>Deploying &productnameshort; on a &zseries; host</title> | ||
| <section xml:id="introduction-deploy-alp-zseries"> | ||
| <title>Introduction</title> | ||
| <para> | ||
| This article describes how to deploy &productnameshort; on an &zseries; | ||
| host using &dinstaller;. | ||
| </para> | ||
| <note> | ||
| <para> | ||
| In order to run &dinstaller; on &zseries;, bear in mind that the | ||
| &dinstaller; live images do not contain | ||
| <systemitem>linuxrc</systemitem>, <systemitem>wicked</systemitem> and | ||
| the <systemitem>installation-images</systemitem> packages. Therefore | ||
| the devices activation and configuration needs adjusting and there is | ||
| no interactive menu for configuring certain parameters of the | ||
| installation. | ||
| </para> | ||
| </note> | ||
| </section> | ||
| <section xml:id="requirements-deploy-alp-zseries"> | ||
| <title>Requirements</title> | ||
| <para> | ||
| Before installing &productnameshort; on &zseries;, you need to fullfil | ||
| the following requirements: | ||
| </para> | ||
| <itemizedlist> | ||
| <listitem> | ||
| <para> | ||
| 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 | ||
| <link xlink:href="https://documentation.suse.com/sles/html/SLES-all/cha-zseries.html#sec-zseries-prep"/> | ||
| before starting the deployment because most of it is valid for the | ||
| &productnameshort; deployment as well. | ||
| </para> | ||
| </listitem> | ||
| <listitem> | ||
| <para> | ||
| Refer to | ||
| <link | ||
| xlink:href="https://documentation.suse.com/sles/html/SLES-all/cha-zseries.html#sec-zseries-requirements"/> | ||
| for generic system requirements. | ||
| </para> | ||
| </listitem> | ||
| </itemizedlist> | ||
| </section> | ||
| <section xml:id="alp-zseries-prepare-iso-image"> | ||
| <title>Download and prepare the installation image</title> | ||
| <para> | ||
| Download the &dinstaller; image for the &zseries; architecture from | ||
| <link xlink:href="&alp-dld-site;/Installer:/0.8/images/iso"/>, for | ||
| example: | ||
| </para> | ||
| <screen>&prompt.user;curl -LO &alp-dld-site;/Installer:/0.8/images/iso/d-installer-live.s390x-0.8.3-ALP-Build11.1.iso</screen> | ||
| <para> | ||
| Prepare the ISO image to be served by the FTP server. Extract its content | ||
| so that you can modify it: | ||
| </para> | ||
| <screen> | ||
| &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 | ||
| </screen> | ||
| <tip> | ||
| <para> | ||
| Setting up an installation server (NFS or FTP) is out of the scope of | ||
| this article. For further information, refer to | ||
| <link xlink:href="https://documentation.suse.com/sles/html/SLES-all/cha-zseries.html#sec-zseries-prep"/>. | ||
| </para> | ||
| </tip> | ||
| </section> | ||
| <section xml:id="alp-zseries-example-deployment"> | ||
| <title>Example deployment procedure</title> | ||
| <para> | ||
| The following procedure describes steps to deploy &productnameshort; on a | ||
| &zseries; machine via a z/VM console. | ||
| </para> | ||
| <procedure> | ||
| <step> | ||
| <para> | ||
| Install the <package>x3270</package> package that provides the | ||
| 3270-type terminal emulator. | ||
| </para> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Connect to the LPAR server using the x3270 console. When asked, | ||
| provide your login credentials. | ||
| </para> | ||
| <figure> | ||
| <title>Login prompt inside the z/VM console</title> | ||
| <mediaobject> | ||
| <imageobject role="fo"> | ||
| <imagedata fileref="alp-zseries-zvm.png" width="50%"/> | ||
| </imageobject> | ||
| <imageobject role="html"> | ||
| <imagedata fileref="alp-zseries-zvm.png" width="50%"/> | ||
| </imageobject> | ||
| <textobject role="description"><phrase>Login prompt inside the z/VM console</phrase> | ||
| </textobject> | ||
| </mediaobject> | ||
| </figure> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Enter the Conversational Monitoring System (CMS): | ||
| </para> | ||
| <screen>#CP IPL CMS</screen> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Link the TCPMAINT disk to have the FTP command available: | ||
| </para> | ||
| <screen>VMLINK TCPMAINT 592</screen> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Connect to the FTP server and download the required files for IPLing | ||
| installation. In our case, the anonymous user is allowed: | ||
| </para> | ||
| <screen>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</screen> | ||
| <note> | ||
| <para> | ||
| The <command>locsite fix 80</command> command sets the VM file | ||
| format to a fixed length of 80. This file format is necessary for | ||
| <emphasis>punching</emphasis> the binary files to a virtual machine | ||
| reader. | ||
| </para> | ||
| </note> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| Optionally, you can use the <command>FILELIST</command> command to | ||
| list the files and edit the <emphasis role="bold">parmfile</emphasis> | ||
| with XEDIT. Our example parmfile has the following content: | ||
| </para> | ||
| <screen>cio_ignore=all,!condev<co xml:id="alp-zseries-cioignore"/> | ||
| rd.cio_accept=0.0.0160 | ||
| rd.zdev=qeth,0.0.0800:0.0.0801:0.0.0802,layer2=1,portno=0<co xml:id="alp-zseries-rdzdev"/> | ||
| ip=192.168.0.111::192.168.0.1:24:zvmtest.example.org:enc800:none<co xml:id="alp-zseries-ip"/> | ||
| nameserver=192.168.0.1 | ||
| root=live:ftp://example.org/d-installer.iso<co xml:id="alp-zseries-live"/></screen> | ||
| <calloutlist> | ||
| <callout arearefs="alp-zseries-cioignore"> | ||
| <para> | ||
| Although the <option>cio_ignore</option> parameter is optional, | ||
| it is used to list only the relevant installation devices and | ||
| accept the device that are used for the installation. | ||
| </para> | ||
| </callout> | ||
| <callout arearefs="alp-zseries-rdzdev alp-zseries-ip"> | ||
| <para> | ||
| 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>rd.zdev</option> | ||
| option activates the <literal>qeth</literal> device and the | ||
| <option>ip</option> option configures network settings for the | ||
| <literal>enc800</literal> Linux network interface. | ||
| </para> | ||
| </callout> | ||
| <callout arearefs="alp-zseries-live"> | ||
| <para> | ||
| The system boots from a live image retrieved from the specified | ||
| URL. Our example uses FTP protocol, but it can be HTTP as well. | ||
| </para> | ||
| </callout> | ||
| </calloutlist> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| The following is the content of the <filename>sles.exec</filename> | ||
| file: | ||
| </para> | ||
| <screen>/* 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'</screen> | ||
| <para> | ||
| Boot the installation image by running the | ||
| <filename>sles.exec</filename> REXX file: | ||
| </para> | ||
| <screen>sles</screen> | ||
| <figure> | ||
| <title>Booting the installation image</title> | ||
| <mediaobject> | ||
| <imageobject role="fo"> | ||
| <imagedata fileref="alp-zseries-zvm-sles.png" width="50%"/> | ||
| </imageobject> | ||
| <imageobject role="html"> | ||
| <imagedata fileref="alp-zseries-zvm-sles.png" width="50%"/> | ||
| </imageobject> | ||
| <textobject role="description"><phrase>Booting the installation image</phrase> | ||
| </textobject> | ||
| </mediaobject> | ||
| </figure> | ||
| </step> | ||
| <step> | ||
| <para> | ||
| 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: <literal>root</literal>, password: | ||
| <literal>linux</literal>). The rest of the installation process is | ||
| identical to <xref linkend="task-deploy-alp-dinstaller"/>. | ||
| </para> | ||
| </step> | ||
| </procedure> | ||
| </section> | ||
| </article> |