The control file is a file in XML format that contains an installation profile for the target computer. This installation profile contains all the information to complete software installation and configuration on a target computer.
You can create the control file manually in a text editor (not recommended) or you can create or modify this file using the AutoInstallation module in YaST.
To create the control file for one or more computers, you can use the configuration interface in the YaST. This system depends on existing modules that are usually used to configure a computer after OES Linux is installed on a server.
The following procedure contains a quick list of steps to create the control file using the AutoInstallation module in YaST on a server running OES Linux SP1 or later.
On a server that has OES SP1 or later installed, open the YaST2 Control Center.
Click > .
Click > .
In the Create a Reference Control File dialog box, select the Network card check box in the field, then click .
AutoYaST probes the system for software, partitioning, boot loader, network card information, language settings, mouse, and other system wide settings.
Verify the package selections.
Click > .
On the Package Selection page, make sure the items are the same as you previously selected or need. For more information on the addons (software selections) that are selected in the base selections (predefined server types or pattern), see Decide What Type of Server You Are Installing. If the configuration contains the packages and selections you need, skip to Step 7. If not, continue with Step 6.
If you need to change the package selections for the target servers, do the following:
From the Package Selection dialog box, click .
On the Software Selection page, click a base selection (predefined server type or pattern).
If you need to make more specific changes, click .
In the field, select .
Select or deselect the specific software items that you want to be added or removed from the base pattern (predefined server type), then click .
Accept the Automatic Changes by clicking in the Changed Packages dialog box.
Click , then click .
Specify the Partitioning parameters for the target server:
From the Main YaST AutoInstallation menu, click > > .
Set up partitioning on the first drive as desired.
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:
From the Main YaST AutoInstallation menu, click > > .
Select the check box, then click .
On the Configure Monitor screen, select the applicable monitor vendor and model, then click .
Verify the X11 settings. If they are not correct, repeat Step 8.b and Step 8.c.
If you skip this step, the server keyboard mappings might be German.
(Optional) Insert a script to perform a task that you might want, such as a script for removing partitions:
For more information on partitioning options, see “Custom User Scripts” in Automatic Linux Installation and Configuration with YaST2.
From the Main YaST AutoInstallation menu, click > > .
In the User Script Management screen, click .
In the field, specify a descriptive name for the script, such as hello_world_script.
In the field, enter commands such as the following example script:
#!/bin/sh ‘echo "hello world" > /tmp/post-script-output'
Click the drop-down box, then select .
This script runs after the installation is complete. For additional options, see the online help for this dialog box.
Click .
Make sure your script appears in the Post Scripts section of the Custom Scripts screen, then click .
Set the password for the Root user:
From the Main YaST AutoInstallation menu, click > > .
Click, then select from the drop-down menu.
Select user , then click edit.
Type a password for the root user in the fields, click , then click .
Verify that the root user appears in the section of the dialog box.
Set a password for Certificate Authority management:
From the menu, click > > .
Type a password for the certificate in the fields, then click .
Verify that the Password status appears as screen.
Configure OES Network Services:
From the Main YaST AutoInstallation menu, click AutoYaST_configuration_category > module_name > .
Most OES services are in the Network Services 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 base pattern (predefined server type), see Decide What Type of Server You Are Installing.
Type or select the information for each field requested on each screen, then click until a summary of setting is displayed for that service.
See Navigating OES Configuration Screens for default settings and an example of the XML that is generated in the control file.
Verify that the settings for each module are set as desired.
If not, click 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 > .
Browse to a location that you want to save the file to.
Type filename.xml, then click .
Replace filename with an appropriate name to identify the control file for the installation you are performing.
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 > .
Proceed with Setting Up an Installation Source.
Each OES component and the configurable fields associated with it are listed in the following sections. These components also include the default or previously entered values, where applicable. Some components might require some additional configuration as part of the OES installation; this information is also included in the sections. If the component requires configuration that is not part the OES installation, see the component's administration guide for more information. You can find Administration guides for all OES products at the OES Documentation Web site .
We recommend configuring this service first because the information provided here populates the required fields in components that are dependent on this module.
Table 7-1 eDirectory Menu Options and Information
|
Field or Selection |
Default or Previously Entered Values and Comments |
|---|---|
|
|
example_tree |
|
|
IP_address_of_existing_server |
|
|
524 |
|
or |
cn=admin.o=example |
|
|
|
|
|
o=example |
|
|
/var/nds/dib |
|
|
local host |
|
|
389 |
|
|
636 |
|
|
8028 |
|
|
8030 |
IMPORTANT:If you install the OES Linux server into an existing tree with servers with versions previous to NetWare® 5.1 SP7 or later with eDirectory 8.6.x or later, you first need to run Deployment Manager to prepare the network. See eDirectory Rights Required to Install OES Linux. If all the servers in the tree are NetWare 5.1 SP7 or later with eDirectory 8.6.x or later, you do not need to run Deployment Manager.
XML in the control file is generated similar to the following:
<edirectory> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <dib_location>/var/nds/dib</dib_location> <existing_ip>192.65.71.14</existing_ip> <existing_ldap_secure_port config:type="integer">636</existing_ldap_secure_port> <http_port config:type="integer">8028</http_port> <https_port config:type="integer">8030</https_port> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> <ntp_server>192.65.71.82</ntp_server> <server_context>o=novell</server_context> <slp_da /> <slp_mode>none</slp_mode> <slp_scopes>DEFAULT</slp_scopes> <tree_name>OES_EXAMPLE</tree_name> <tree_type>existing</tree_type> </edirectory
eDirectory requires that all OES servers, both NetWare and Linux, are time synchronized.
For information on this important topic, see Implementing Time Synchronization
in the Novell OES SP2 Planning and Implementation Guide.
You have the following options for configuring SLP:
No SLP: This option is good for eDirectory trees with three eDirectory servers or less.
Multicast: This option allows the server to request SLP information using multicast packets. Use this in environments that have not established SLP DAs (Directory Agents).
Use an existing SLP DA: Use this in environments that have established SLP DAs.
For more information about configuring SLP, see Configuring OpenSLP for eDirectory
Novell eDirectory 8.7.3 Administration Guide.
Table 7-2 eGuide Menu Options and Information
XML in the control file is generated similar to the following:
<eguide> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> </eguide>
Table 7-3 iFolder 2.x Menu Options and Information
XML in the control file is generated similar to the following:
<ifolder2>
<admin_context>cn=admin.o=example</admin_context>
<admin_password>novell</admin_password>
<admin_users config:type="list">
<listentry>admin</listentry>
</admin_users>
<ifolder2_ip_address>192.65.71.238</ifolder2_ip_address>
<ldap_ip_address>192.65.71.18</ldap_ip_address>
<ldap_port config:type="integer">389</ldap_port>
<ldap_secure_port config:type="integer">636</ldap_secure_port>
<server_dns>OESserver-ls1.provo.novell.com</server_dns>
<server_netmask>255.255.255.252</server_netmask>
<user_data_path>/var/opt/novell/ifolderdata</user_data_path>
</ifolder2>
Table 7-4 iFolder 3.x Menu Options and Information
XML in the control file is generated similar to the following:
<ifolder> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ifolderadmin_dn>cn=ifolderadmin.o=example</ifolderadmin_dn> <ifolderadmin_password>novell</ifolderadmin_password> <ifolderadmin_password2>novell</ifolderadmin_password2> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> <proxy_context>o=example</proxy_context> <store_path>/var/opt/novell/ifolder3</store_path> <system_description>ifolder 3 example server </system_description> <system_name>if3_example_server</system_name> </ifolder>
Table 7-5 iFolder 3.x Web Access Menu Options and Information
|
Field or Selection |
Default or Previously Entered Values and Comments |
|---|---|
|
|
/ifolder |
|
|
http://localhost |
XML in the control file is generated similar to the following:
<ifolderwebaccess-main> <webaccess_alias>/ifolder</webaccess_alias> <webaccess_server_url>http://localhost</webaccess_server_url> </ifolderwebaccess-main>
Table 7-6 iManager Menu Options and Information
|
Field or Selection |
Default or Previously Entered Values and Comments |
|---|---|
|
|
|
|
|
cn=admin.o=example |
NOTE:iManager is fully functional only from a SUSE Linux server console using Mozilla 1.7 or Mozilla Firefox 1.0 browsers.
XML in the control file is generated similar to the following:
<imanager> <admin_context>cn=admin.o=example</admin_context> <tree_name>192.65.71.18</tree_name> </imanager>
Table 7-7 iPrint Menu Options and Information
XML in the control file is generated similar to the following:
<iprint> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_secure_port config:type="integer">636</ldap_secure_port> <tree_name>oes_example</tree_name> </iprint>
Table 7-8 LDAP Menu Options and Information
|
Field or Selection |
Default or Previously Entered Values and Comments |
|---|---|
|
|
Defaults to the correct selection based on eDirectory entry |
|
|
Add or remove from the list |
|
|
cn=admin.o=example |
|
|
admin_password |
XML in the control file is generated similar to the following:
<oes-ldap> <admin_context>cn=admin.o=novell</admin_context> <ldap_servers>192.65.71.18,389,636</ldap_servers> <tree_name>oes_example</tree_name> </oes-ldap>
Table 7-9 Linux User Management Menu Options and Information
IMPORTANT:Before you accept the default PAM-enabled service settings, be sure you understand the security implications explained in User Restriction Limitations
in the Novell OES SP2 Planning and Implementation Guide.
XML in the control file is generated similar to the following:
<linux-user-mgmt> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> <partition_root>o=example</partition_root> <proxy_user /> <proxy_user_password /> <services config:type="list"> <ftp>no</ftp> <login>no</login> <openwbem>yes</openwbem> <passwd>no</passwd> <rlogin>no</rlogin> <rsh>no</rsh> <sshd>yes</sshd> <su>no</su> <xdm>no</xdm> </services> <ws_context>o=example</ws_context> </linux-user-mgmt>
Table 7-10 NCP Server Menu Options and Information
|
Field or Selection |
Default or Previously Entered Values and Comments |
|---|---|
|
|
cn=admin.o=example |
|
|
admin_password |
XML in the control file is generated similar to the following:
<ncpserver> <admin_dn>cn=admin.o=example</admin_dn> <admin_password>novell</admin_password> </ncpserver>
Table 7-11 NetStorage Menu Options and Information
XML in the control file is generated similar to the following:
<netstorage> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ifolder2_ip_address /> <ldap_ip_address>192.65.71.18</ldap_ip_address> <xtier_address /> <xtier_proxy_context>cn=admin.o=example</xtier_proxy_context> <xtier_proxy_password>novell</xtier_proxy_password> <xtier_users_context>o=example</xtier_users_context> </netstorage>
Table 7-12 Novell Cluster Services Menu Options and Information
On the Configuration screens presented:
Select whether you are installing locally or remotely, accept or change the admin name and password, then click Next.
indicates that you are also installing eDirectory on this server. We recommend that you install eDirectory on cluster nodes. If you are not installing eDirectory on this server, select .
When installing OES Linux clustering into a NetWare 5.1 or NetWare 6 tree, the option should be used or clustering might fail to install. NetWare 5.1 or NetWare 6 LDAP servers are incompatible with the OES Linux Cluster Services installation.
Choose to either create a new cluster or install Novell Cluster Services™ on a server that you will add to an existing cluster, or configure later.
is the default when installing Novell Cluster Services during the OES installation.
Specify the fully distinguished name (FDN) of the cluster.
Use the dot format illustrated in the example. Do not use commas.
If you are creating a new cluster, this is the name you will give the new cluster and the eDirectory context where the new Cluster object will reside.
If you are adding a server to an existing cluster, this is the name and eDirectory context of the cluster that you are adding this server to.
(Conditional) If you are creating a new cluster, specify a unique IP address for the cluster.
The cluster IP address is separate from the server IP address, is required to be on the same IP subnet as the other cluster servers, and is required for certain external network management programs to get cluster status alerts. The cluster IP address provides a single point for cluster access, configuration, and management. A Master IP address resource is automatically created during the Cluster Services installation that makes this possible.
The cluster IP address is bound to the master node and remains with the master node regardless of which server is the master node.
(Conditional) If you chose to install remotely in Step 1, accept the default server name and IP address (recommended), or specify the IP address and server name of a server that has eDirectory installed.
(Conditional) If you are creating a new cluster, do the following:
Specify the device where you want the SBD partition to be created, then click .
For example, the device might be something similar to /dev/sdc.
If you have a shared disk system or SAN attached to your cluster servers, Novell Cluster Services creates a small cluster partition on that shared disk system. This small cluster partition is referred to as the Split Brain Detector (SBD) partition. Provide the drive or device where you want the small cluster partition created.
If you do not have a shared disk system connected to your cluster servers, accept the default (none).
IMPORTANT:You must have at least 20 MB of free space on one of the shared disk drives to create the cluster partition. If no free space is available, the shared disk drives can't be used by Novell Cluster Services.
Specify the IP address that clustering should use. If you have multiple network boards installed, you need to specify the IP address bound to the desired network board.
Select or deselect the option.
indicates whether clustering should start now or after the machine is rebooted.
XML in the control file is generated similar to the following:
<ncs> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <cluster_dn>cn=cluster.o=example</cluster_dn> <cluster_ip /> <config_type>Existing Cluster</config_type> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_secure_port config:type="integer">636</ldap_secure_port> <sbd_dev /> <sbd_dev2 /> <server_name /> <start>Now</start> </ncs>
The values specify LDAP configuration for this service. The configuration management tool generates entries for lifeconsole in the XML source.
Table 7-13 Novell Health Monitoring Menu Options and Information
XML in the control file is generated similar to the following:
<lifeconsole> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_secure_port config:type="integer">636</ldap_secure_port> </lifeconsole>
Table 7-14 Novell QuickFinder Menu Options and Information
XML in the control file is generated similar to the following:
<novell-quickfinder> <admin_name>cn=admin.o=example</admin_name> <admin_password>novell</admin_password> <lum_enable>yes</lum_enable> <shadow_access>no</shadow_access> <user_name>cn=admin.o=example</user_name> <user_password>novell</user_password> </novell-quickfinder>
No configuration required.
Table 7-15 Novell Samba Menu Options and Information
XML in the control file is generated similar to the following:
<novell-samba> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_secure_port config:type="integer">636</ldap_secure_port> <proxy_user_context>cn=proxy.o=example</proxy_user_context> <proxy_user_password>novell</proxy_user_password> <user_context>o=example</user_context> </novell-samba>
Table 7-16 Novell Storage Services Menu Options and Information
XML in the control file is generated similar to the following:
<nss> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> <nssadmin_dn>cn=192657114admin.o=example</nssadmin_dn> </nss>
Table 7-17 SMS Menu Options and Information
XML in the control file is generated similar to the following:
<sms> <admin_context>cn=admin.o=example</admin_context> <admin_password>novell</admin_password> <ldap_ip_address>192.65.71.18</ldap_ip_address> <ldap_port config:type="integer">389</ldap_port> <ldap_secure_port config:type="integer">636</ldap_secure_port> </sms>