8 Setting Up the Server Holding the Installation Sources #

1. Log in as root to the machine that should act as installation server.

2. Start YaST › Miscellaneous › Installation Server.

3. Select the repository type (HTTP, FTP, or NFS). The selected service is started automatically every time the system starts. If a service of the selected type is already running on your system and you want to configure it manually for the server, deactivate the automatic configuration of the server service with Do Not Configure Any Network Services. In both cases, define the directory in which the installation data should be made available on the server.

4. Configure the required repository type. This step relates to the automatic configuration of server services. It is skipped when automatic configuration is deactivated.

   Define an alias for the root directory of the FTP or HTTP server on which the installation data should be found. The repository will later be located under ftp://Server-IP/Alias/Name (FTP) or under http://Server-IP/Alias/Name (HTTP). Name stands for the name of the repository, which is defined in the following step. If you selected NFS in the previous step, define wild cards and export options. The NFS server will be accessible under nfs://Server-IP/Name. Details of NFS and exports can be found in Chapter 29, Sharing File Systems with NFS.

   

   Tip: Firewall Settings

   Make sure that the firewall settings of your server system allow traffic on the ports for HTTP, NFS, and FTP. If they currently do not, enable Open Port in Firewall or check Firewall Details first.

5. Configure the repository. Before the installation media are copied to their destination, define the name of the repository (ideally, an easily remembered abbreviation of the product and version). YaST allows providing ISO images of the media instead of copies of the installation DVDs. If you want this, activate the relevant check box and specify the directory path under which the ISO files can be found locally. Depending on the product to distribute using this installation server, it might be necessary to add additional media, such as service pack DVDs as extra repositories. To announce your installation server in the network via OpenSLP, activate the appropriate option.

   

   Tip: Announcing the Repository

   Consider announcing your repository via OpenSLP if your network setup supports this option. This saves you from entering the network installation path on every target machine. The target systems are booted using the SLP boot option and find the network repository without any further configuration. For details on this option, refer to Section 11.2, “Booting the Target System for Installation”.

6. Configuring extra repositories. YaST follows a specific naming convention to configure add-on CDs or service pack CDs repositories. Configuration is accepted only if the repository name of the add-on CDs starts with the repository name of the installation media. In other words, if you chose SLES12SP1 as the repository name for DVD1, then you should choose SLES12SP1addon as the repository name for DVD2. The same applies to SDK CDs.

7. Upload the installation data. The most lengthy step in configuring an installation server is copying the actual installation media. Insert the media in the sequence requested by YaST and wait for the copying procedure to end. When the sources have been fully copied, return to the overview of existing repositories and close the configuration by selecting Finish.

   Your installation server is now fully configured and ready for service. It is automatically started every time the system is started. No further intervention is required. You only need to configure and start this service correctly by hand if you have deactivated the automatic configuration of the selected network service with YaST as an initial step.

To create a directory to hold the installation data, proceed as follows:

1. Log in as root.

2. Create a directory that will later hold all installation data and change into this directory. For example:

   root # mkdir -p /srv/install/PRODUCT/PRODUCTVERSION
   root # cd /srv/install/PRODUCT/PRODUCTVERSION

   Replace PRODUCT with an abbreviation of the product name and PRODUCTVERSION with a string that contains the product name and version.

3. For each DVD contained in the media kit execute the following commands:

   1. Copy the entire content of the installation DVD into the installation server directory:

      root # cp -a /media/PATH_TO_YOUR_DVD_DRIVE .

      Replace PATH_TO_YOUR_DVD_DRIVE with the actual path under which your DVD drive is addressed. Depending on the type of drive used in your system, this can be cdrom, cdrecorder, dvd, or dvdrecorder.

   2. Rename the directory to the DVD number:

      root # mv PATH_TO_YOUR_DVD_DRIVE DVDX

      Replace X with the actual number of your DVD.

On SUSE Linux Enterprise Server, you can export the repository with NFS using YaST. Proceed as follows:

1. Log in as root.

2. Start YaST › Network Services › NFS Server.

3. Select Start and Open Port in Firewall and click Next.

4. Select Add Directory and browse for the directory containing the installation sources, in this case, PRODUCTVERSION.

5. Select Add Host and enter the host names of the machines to which to export the installation data. Instead of specifying host names here, you could also use wild cards, ranges of network addresses, or the domain name of your network. Enter the appropriate export options or leave the default, which works fine in most setups. For more information about the syntax used in exporting NFS shares, read the exports man page.

6. Click Finish. The NFS server holding the SUSE Linux Enterprise Server repository is automatically started and integrated into the boot process.

If you prefer manually exporting the repository via NFS instead of using the YaST NFS Server module, proceed as follows:

1. Log in as root.

2. Open the file /etc/exports and enter the following line:

   /PRODUCTVERSION *(ro,root_squash,sync)

   This exports the directory /PRODUCTVERSION to any host that is part of this network or to any host that can connect to this server. To limit the access to this server, use netmasks or domain names instead of the general wild card *. Refer to the export man page for details. Save and exit this configuration file.

3. To add the NFS service to the list of servers started during system boot, execute the following commands:

   root # systemctl enable nfsserver

4. Start the NFS server with systemctl start nfsserver. If you need to change the configuration of your NFS server later, modify the configuration file and restart the NFS daemon with systemctl restart nfsserver.

Announcing the NFS server via OpenSLP makes its address known to all clients in your network.

1. Log in as root.

2. Create the /etc/slp.reg.d/install.suse.nfs.reg configuration file with the following lines:

   # Register the NFS Installation Server
   service:install.suse:nfs://$HOSTNAME/PATH_TO_REPOSITORY/DVD1,en,65535
   description=NFS Repository

   Replace PATH_TO_REPOSITORY with the actual path to the installation source on your server.

3. Start the OpenSLP daemon with systemctl start slpd.

1. Create a directory holding the installation sources as described in Section 8.2, “Setting Up an NFS Repository Manually”.

2. Configure the FTP server to distribute the contents of your installation directory:

   1. Log in as root and install the package vsftpd using the YaST software management.

   2. Enter the FTP server root directory:

      root # cd /srv/ftp

   3. Create a subdirectory holding the installation sources in the FTP root directory:

      root # mkdir REPOSITORY

      Replace REPOSITORY with the product name.

   4. Mount the contents of the installation repository into the change root environment of the FTP server:

      root # mount --bind PATH_TO_REPOSITORY /srv/ftp/REPOSITORY

      Replace PATH_TO_REPOSITORY and REPOSITORY with values matching your setup. If you need to make this permanent, add it to /etc/fstab.

   5. Start vsftpd with vsftpd.

3. Announce the repository via OpenSLP, if this is supported by your network setup:

   1. Create the /etc/slp.reg.d/install.suse.ftp.reg configuration file with the following lines:

      # Register the FTP Installation Server
      service:install.suse:ftp://$HOSTNAME/REPOSITORY/DVD1,en,65535
      description=FTP Repository

      Replace REPOSITORY with the actual name to the repository directory on your server. The service: line should be entered as one continuous line.

   2. Start the OpenSLP daemon with systemctl start slpd.

1. Create a directory holding the installation sources as described in Section 8.2, “Setting Up an NFS Repository Manually”.

2. Configure the HTTP server to distribute the contents of your installation directory:

   1. Install the Web server Apache as described in Section 33.1.2, “Installation”.

   2. Enter the root directory of the HTTP server (/srv/www/htdocs) and create the subdirectory that will hold the installation sources:

      root # mkdir REPOSITORY

      Replace REPOSITORY with the product name.

   3. Create a symbolic link from the location of the installation sources to the root directory of the Web server (/srv/www/htdocs):

      root # ln -s /PATH_TO_REPOSITORY/srv/www/htdocs/REPOSITORY

   4. Modify the configuration file of the HTTP server (/etc/apache2/default-server.conf) to make it follow symbolic links. Replace the following line:

      Options None

      with

      Options Indexes FollowSymLinks

   5. Reload the HTTP server configuration using systemctl reload apache2.

3. Announce the repository via OpenSLP, if this is supported by your network setup:

   1. Create the /etc/slp.reg.d/install.suse.http.reg configuration file with the following lines:

      # Register the HTTP Installation Server
      service:install.suse:http://$HOSTNAME/REPOSITORY/DVD1/,en,65535
      description=HTTP Repository

      Replace REPOSITORY with the actual path to the repository on your server. The service: line should be entered as one continuous line.

   2. Start the OpenSLP daemon using systemctl start slpd.

To set up an exported Windows Share holding your SUSE Linux Enterprise Server repository, proceed as follows:

1. Log in to your Windows machine.

2. Create a new directory that will hold the entire installation tree and name it INSTALL, for example.

3. Export this share according the procedure outlined in your Windows documentation.

4. Enter this share and create a subdirectory, called PRODUCT. Replace PRODUCT with the actual product name.

5. Enter the INSTALL/PRODUCT directory and copy each DVD to a separate directory, such as DVD1 and DVD2.

1. Boot the installation target.

2. Select Installation.

3. Press F4 for a selection of the repository.

4. Choose SMB and enter the Windows machine's name or IP address, the share name (INSTALL/PRODUCT/DVD1, in this example), user name, and password. The syntax looks like this:

   smb://workdomain;user:password@server/INSTALL/DVD1

   After you press Enter, YaST starts and you can perform the installation.

1. Download the ISO images and save them to the machine to use as the installation server.

2. Log in as root.

3. Choose and create an appropriate location for the installation data, as described in Section 8.2, “Setting Up an NFS Repository Manually”, Section 8.3, “Setting Up an FTP Repository Manually”, or Section 8.4, “Setting Up an HTTP Repository Manually”.

4. Create subdirectories for each DVD.

5. To mount and unpack each ISO image to the final location, issue the following command:

   root # mount -o loop PATH_TO_ISO PATH_TO_REPOSITORY/PRODUCT/MEDIUMX

   Replace PATH_TO_ISO with the path to your local copy of the ISO image, PATH_TO_REPOSITORY with the source directory of your server, PRODUCT with the product name, and MEDIUMX with the type (CD or DVD) and number of media you are using.

6. Repeat the previous step to mount all ISO images needed for your product.

7. Start your installation server as usual, as described in Section 8.2, “Setting Up an NFS Repository Manually”, Section 8.3, “Setting Up an FTP Repository Manually”, or Section 8.4, “Setting Up an HTTP Repository Manually”.