Skip to content

Commit

Permalink
Added preparation of the TFTP server.
Browse files Browse the repository at this point in the history
  • Loading branch information
@lvicoun
lvicoun committed Oct 18, 2024
1 parent 7b79db8 commit abd84c0
Show file tree
Hide file tree
Showing 2 changed files with 128 additions and 34 deletions.
57 changes: 23 additions & 34 deletions tasks/deployment-network-dhcp.xml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ in the assembly -->
A DHCP server provides both dynamic and static IP address assignments to your network clients.
It advertises servers, routes, and domains. The clients transmit their architecture type in their DHCP requests. Based on this information, the DHCP server decides which files the client must download for booting.
</para>
<section xml:id="deployment-network-dhcp">
<section xml:id="deployment-network-dhcp-dynamic">
<title>Dynamic address assignment</title>
<para>
The following example shows how to set up a DHCP server that dynamically
Expand Down Expand Up @@ -100,42 +100,31 @@ in the assembly -->
</step>
</procedure>
</section>
<section xml:id="task-example-executing">
<title>Executing the task</title>
<section xml:id="deployment-network-dhcp--static">
<title>Assigning static IP addresses</title>
<para>
A paragraph of text.
A DHCP server may also assign static IP addresses and host names to
network clients. One use case is assigning static addresses to servers.
Another use case is restricting which clients may join the network to
those with assigned static IP addresses, and providing no dynamic address
pools.
</para>
<para>
Modify the above DHCP configuration according to the following example:
</para>
<procedure>
<para>
A short introduction to the procedure.
</para>
<step>
<para>
A step.
</para>
</step>
<step>
<para>
A second step.
</para>
</step>
<step>
<para>
A third step.
</para>
</step>
</procedure>
</section>
<section xml:id="task-example-summary">
<title>Summary</title>
<para>
A paragraph of text, summing up the result of the task.
</para>
</section>
<section xml:id="task-example-troubleshooting">
<title>Troubleshooting</title>
<screen>group {
host test {
hardware ethernet <replaceable>MAC_ADDRESS</replaceable>;
fixed-address <replaceable>IP_ADDRESS</replaceable>;
}
}
</screen>
<para>
Add some troubleshooting information, if applicable.
The host statement assigns a host name to the installation target. To
bind the host name and IP address to a specific host, you must
specify the client's hardware (MAC) address. Replace all the variables used
in this example with the actual values that match your environment, then
save your changes and restart the DHCP server.
</para>
</section>
</topic>
105 changes: 105 additions & 0 deletions tasks/deployment-network-tftp.xml
View file
Original file line number Diff line number Diff line change
@@ -0,0 +1,105 @@
<?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. -->
<!DOCTYPE topic
[
<!ENTITY % entities SYSTEM "../common/generic-entities.ent">
%entities;
]>
<!-- refers to legacy doc: <add github link to legacy doc piece, if applicable> -->
<!-- point back to this document with a similar comment added to your legacy doc piece -->
<!-- refer to README.md for file and id naming conventions -->
<!-- metadata is dealt with on the assembly level -->
<topic xml:id="task-example"
role="task" xml:lang="en"
xmlns="http://docbook.org/ns/docbook" version="5.2"
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"
xmlns:trans="http://docbook.org/ns/transclusion">
<info>
<title>Preparing configuration on the TFTP server</title><!-- can be changed via merge
in the assembly -->
<!-- add author's e-mail -->
<meta name="maintainer" content="[email protected]" its:translate="no"/>
<abstract><!-- can be changed via merge in the assembly -->
<para>
The topic describes how to prepare the server so that the
client machines with UEFI can boot remotely using files exported by
TFTP.
</para>
</abstract>
</info>
<para>
To deploy &productname; using the PXE client, you need to perform the following steps:
</para>
<procedure>
<step>
<para>
Review the <systemitem class="daemon">tftpd</systemitem> configuration in
<filename>/etc/sysconfig/tftp</filename> and add or change options as
required. Refer to <command>man 8 tftpd</command> for more details.
The TFTP daemon works without changing the configuration. The default root
directory for the files is <filename>/srv/tftpboot</filename>.
</para>
</step>
<step>
<para>
Ensure that <systemitem class="daemon">tftpd</systemitem> is started at
boot time, and restart it to read the new configuration.
</para>
<screen>&prompt.sudo;<command>systemctl enable tftp.socket</command>
&prompt.sudo;<command>systemctl restart tftp.socket</command></screen>
</step>
<step>
<para>
Prepare the directory structure:
</para>
<screen>
&prompt.sudo;mkdir /srv/tftpboot/sl-micro
</screen>
</step>
<step>
<para>
Navigate to the directory:
</para>
<screen>&prompt.user;<command>cd /srv/tftpboot/sl-micro</command></screen>
</step>
<step>
<para>
Download the
<literal>SL-Micro.<replaceable>ARCHITECTURE</replaceable>-6.1-<replaceable>IMAGE_TYPE</replaceable>-GM.install.tar</literal>
to the TFTP server.
</para>
</step>
<step>
<para>
Unpack the TAR file:
</para>
<screen>&prompt.sudo;<command>tar xvf <replaceable>IMAGE_TAR</replaceable> -C .</command></screen>
</step>
<step>
<para>
Create symlinks as follows:
</para>
<screen>
&prompt.sudo;<command>ln -s pxeboot.*.kernel linux</command>

&prompt.sudo;<command>ln -s pxeboot.*.initrd initrd</command>
</screen>
</step>
<step>
<para>
Create a configuration file with specific boot parameters.
</para>
<screen>
rd.zdev=qeth,0.0.0800:0.0.0801:0.0.0802,layer2=1,portno=0
ip=10.144.136.50::10.144.136.254:255.255.255.0
rd.kiwi.install.pxe
rd.kiwi.install.image=ftp://10.144.55.15/fvogt/slm-fcp/SL-Micro.s390x-6.0.xz
hvc_iucv=8 TERM=dumb security=selinux selinux=1
rd.kiwi.install.pass.bootparam
</screen>
</step>
</procedure>
</topic>

0 comments on commit abd84c0

Please sign in to comment.