The control file is an XML file that contains an installation profile for the target computer. This installation profile contains all the information to complete software installation and configuration on the target computer.
To create a control file:
You can create the control file manually in a text editor (not recommended).
When you complete an installation, you can click Clone for AutoYaST. If you use this option, the resulting file is /root/autoinst.xml. This file must be edited manually before using it. See Section 9.2.1, Fixing an Automatically Created Control File.
You can create or modify a control file by using the AutoInstallation module in YaST. For procedures, see Section 9.2.2, Using the AutoInstallation Module to Create the Control File.
This system depends on existing modules that are usually used to configure a computer after OES 2015 SP1 is installed on a server.
Review the following issues and solutions to fix the automatically created control file.
Issue 1: If you install all OES Services through AutoYaST, Apache does not run.
Solution: Reboot the server when the installation is complete; or, when you create the profile or control file, deselect the Print Server pattern in the Primary Functions category. If you have already created the control file, remove the following section:
- <printer> <cups_installation config:type="symbol">server< cups_installation> <default /> <printcap config:type="list" /> <server_hostname /> <spooler>cups</spooler> </printer>
Issue 2: The Certificate Authorities section of the control file is not created.
Solution: You must insert the CA section manually.
To add this information to the control file:
1. Open YaST as root.
2. Click Miscellaneous > Autoinstallation.
3. Select Security and Users > CA Management, then click Edit.
4. In the Common Name File field, specify a name for the certificate. For example YaST_Default_CA(hostname).
5. Specify an e-mail name in the Email field.
6. Specify a password in the Password field.
7. Click File > Save to save the file. Ignore any error messages that you receive.
8. Click View Source to ensure that the CA entry was entered.
It should look similar to the following:
<ca_mgm>
<CAName>YaST_Default_CA</CAName>
<ca_commonName>YaST_Default_CA(hostname)</ca_commonName>
<country>US</country>
<importCertificate config:type="boolean">false</importCertificate>
<locality></locality>
<organization></organization>
<organizationUnit></organizationUnit>
<password>actual_password</password>
<server_email>name@example.com</server_email>
<state></state>
<takeLocalServerName config:type="boolean">true</takeLocalServerName>
</ca_mgm>Issue 3: If you install Novell Cluster Services, one package does not install correctly.
Solution: Comment out the following line in the control file.
<package>novell-cluster-services-kmp-smp</package>
For example:
<!--<package>novell-cluster-services-kmp-smp</package>-->
Issue 4: If you did not patch the server during the installation, the OES product is not identified correctly in the control file.
Solution: When creating the profile or control file, change the product line from:
<product>Novell Open Enterprise Server 11</product>
to
<product>OPEN_ENTERPRISE_SERVER</product>
The following procedure contains a quick list of steps to create the control file by using the AutoInstallation module in YaST on a server running OES 2015 SP1.
On a server that has OES 2015 SP1 installed, Click Computer > YaST Administrator Settings.
Click Miscellaneous > Autoinstallation.
The AutoYaST Configuration Management System application window opens, referred to hereafter as the main window.
Click Tools > Create Reference Profile.
In the Create a Reference Control File dialog box under Select Additional Resources, select the Network Settings check box, then click Create.
AutoYaST probes the server it is running on for software, partitioning, boot loader, network card information, language settings, mouse, and other system settings. After the information has been collected, the status messages cease and only the main window is displayed.
Verify the package selections:
In the left frame of the main window, click Software, then under Available Modules, click Package Selection.
On the Package Selection page, make sure the items are the same as you previously installed on the server. For more information on the add-ons (software selections) that are selected in the base selections or patterns, see Deciding What Patterns to Install. If the configuration contains the packages and selections you need, skip to Step 7. If not, continue with Step 6.
If necessary, change the package selections for the target servers:
In the Package Selection dialog box, click Configure.
On the Software Selection page, click Patterns in the Filter field.
Select the specific software items that you want to be added, then click Accept.
If you are prompted to accept the AGFA Monotype Corporation End User License Agreement, click Accept.
Accept the automatic changes by clicking Continue in the Changed Packages dialog box.
Specify the Partitioning parameters for the target server:
In the left frame of the main window, click Hardware, under Available Modules, click Partitioning, then click the Edit button.
Set up partitioning on the first drive as desired, then click Finish.
See the online help for details about limitations.
For more information on partitioning options, see “Partitioning” in Automatic Linux Installation and Configuration with Yast2.
Specify the settings for the graphics card and monitor:
In the left frame of the main window, click Hardware, under Available Modules, click Graphics Card and Monitor, then click the Configure button.
In the General Options field of the X11 Configuration page, specify the settings that you want.
In the Desktop field of the X11 Configuration page, select the settings that you want for the Display Manager and Window Manager, then click Next.
On the Configure Monitor page, select the applicable monitor vendor and model, then click Next.
Verify the X11 settings. If they are not correct, repeat Step 8.a and Step 8.d.
If you skip this step, the server keyboard mappings might be German.
(Optional) Insert a script to perform a task that you want, such as a script for removing partitions:
For more information on custom user scripts, see “Custom User Scripts” in Automatic Linux Installation and Configuration with Yast2.
In the main window, click Miscellaneous > Custom Scripts > Configure.
On the User Script Management page, click New.
In the File Name field, specify a descriptive name for the script, such as hello_world_script.
In the Script Source field, specify commands such as the following example script:
#!/bin/sh ‘echo "hello world" > /tmp/post-script-output'
Click the Type drop-down box, then select Post.
This script runs after the installation is complete. For additional options, see the online help for this dialog box.
Click Save.
Make sure your script appears in the Available Scripts section of the User Script Management page, then click Finish.
Make sure your script appears in the Post Scripts section of the Custom Scripts page.
Set the password for the root user:
From the main window, click Security and Users > User Management > Configure.
Click Set Filter, then select Select System Users from the drop-down menu.
Select user root, then click Edit.
Type a password for the root user in the Password and Verify Password fields, click Accept, then click Finish.
Verify that the root user appears in the Users section of the User Management dialog box.
Set a password for Certificate Authority management:
From the main window, click Security and Users > CA Management > Configure.
Type a password for the certificate in the Password and Confirm Password fields, then click Finish.
Verify that the Password status appears as Set on the CA Management page.
Configure OES Services:
From the main window, click Open Enterprise Server > module_name > Configure.
All OES services are in the Open Enterprise Server category.
We recommend configuring eDirectory first. Although there are dependencies for some of the components, in this release AutoYaST does not verify whether one module is configured or not.
See the following table for category names and dependencies. You should configure all the modules that were selected for the software selections in Step 5. For more information about which modules are in each pattern, see Deciding What Patterns to Install.
|
Pattern |
Other Module Dependencies |
|---|---|
|
Novell AFP |
|
|
Novell Backup/Storage Management Services (SMS) |
|
|
Novell CIFS |
|
|
Novell Cluster Services (NCS) |
|
|
Novell DHCP |
|
|
Novell DNS |
|
|
Novell Domain Services for Windows |
|
|
NetIQ eDirectory |
|
|
Novell FTP |
|
|
Novell iFolder |
|
|
Novell iManager |
|
|
Novell iPrint |
|
|
Novell Linux User Management (LUM) |
|
|
Novell NCP Server / Dynamic Storage Technology |
|
|
Novell NetStorage |
|
|
Novell Pre-Migration Server |
|
|
Novell Remote Manager (NRM) |
|
|
Novell Samba |
|
|
Novell Storage Services (NSS) |
|
|
Novell Storage Service AD Support |
|
Type or select the information for each field requested on each page, then click Next until a summary of settings is displayed for that service.
Verify that the settings for each module are what you want.
If not, click Reset Configuration and provide the corrected settings.
Repeat Step 12.a through Step 12.c until all the required modules have been configured, then continue with Step 13.
Save the file.:
Click File > Save.
Browse to a location that you want to save the file to.
Type filename.xml, then click Save.
Replace filename with an appropriate name to identify the control file for the installation you are performing.
By default, the file is saved in the /var/lib/autoinstall/repository/ directory.
For additional filename requirements and recommendations, see “The Auto-Installation Process” in Automatic Linux Installation and Configuration with Yast2.
Exit the configuration management tool by clicking File > Exit.
Proceed with Setting Up an Installation Source.