Skip to content

adding-ibm-z-lpar-agent.adoc

Latest commit

 

History

History
78 lines (69 loc) · 3.19 KB

adding-ibm-z-lpar-agent.adoc

File metadata and controls

78 lines (69 loc) · 3.19 KB
Raw

Adding {ibm-z-title} agents in a Logical Partition (LPAR)

Use the following procedure to manually add {ibm-z-name} agents to your cluster that runs in an LPAR environment. Use this procedure only for {ibm-z-name} clusters running in an LPAR.

Prerequisites

  • You have Python 3 installed.

  • A running file server with access to the Logical Partition (LPAR).

Procedure

  1. Create a boot parameter file for the agents.

    Example parameter file
    rd.neednet=1 cio_ignore=all,!condev \
console=ttysclp0 \
ignition.firstboot ignition.platform.id=metal
coreos.live.rootfs_url=http://<http_server>/rhcos-<version>-live-rootfs.<architecture>.img \// (1)
coreos.inst.persistent-kargs=console=ttysclp0 \
ip=<ip>::<gateway>:<netmask>:<hostname>::none nameserver=<dns> \// (2)
rd.znet=qeth,<network_adaptor_range>,layer2=1
rd.<disk_type>=<adapter> \// (3)
fips=1 \// (4)
zfcp.allow_lun_scan=0 \
ai.ip_cfg_override=1 \
random.trust_cpu=on rd.luks.options=discard

    1. For the coreos.live.rootfs_url artifact, specify the matching rootfs artifact for the kernel and initramfs that you are starting. Only HTTP and HTTPS protocols are supported.

    2. For the ip parameter, manually assign the IP address, as described in Installing a cluster with z/VM on IBM Z and IBM LinuxONE.

    3. For installations on DASD-type disks, use rd.dasd to specify the DASD where {op-system-first} is to be installed. For installations on FCP-type disks, use rd.zfcp=<adapter>,<wwpn>,<lun> to specify the FCP disk where {op-system} is to be installed.

      Note

      For FCP multipath configurations, provide available multiple paths to the disk instead of a single path, and add rd.multipath=default to enable multipath during installation.
      Example
      rd.zfcp=<adapter1>,<wwpn1>,<lun1> \
rd.zfcp=<adapter2>,<wwpn2>,<lun2> \
rd.multipath=default

    4. To enable FIPS mode, specify fips=1. This entry is required in addition to setting the fips parameter to true in the install-config.yaml file.

      Note

      The .ins and initrd.img.addrsize files are automatically generated for s390x architecture as part of boot-artifacts from the installation program and are only used when booting in an LPAR environment.
      Example filesystem with LPAR boot
      boot-artifacts
    ├─ agent.s390x-generic.ins
    ├─ agent.s390x-initrd.addrsize
    ├─ agent.s390x-rootfs.img
    └─ agent.s390x-kernel.img
    └─ agent.s390x-rootfs.img

  2. Rename the boot-artifacts file present in the generic.ins parameter file to match the names of the boot-artifacts file generated by the installation program.

  3. Transfer the initrd, kernel, generic.ins, and initrd.img.addrsize parameter files to the file server. For more information, see Booting Linux in LPAR mode (IBM documentation).

  4. Start the machine.

  5. Repeat the procedure for all other machines in the cluster.