The first time that you install OES Cluster Services in an eDirectory tree, the directory schema for the tree is extended to include the Cluster object container and the following types of objects in it:
Cluster Node objects
Cluster Resource objects
Cluster Template objects
Volume Resource objects
A tree administrator user with the eDirectory credentials to do so can extend the eDirectory schema before a cluster is installed anywhere in a tree. This allows container administrators (or non-administrator users) to install a cluster in a container in that same tree without needing full administrator rights for the tree. After the schema has been extended, you must assign some eDirectory rights to the container administrators (or non-administrator users) who will install OES Cluster Services clusters.
If the schema is not extended separately, the installer of the first cluster server in the tree must be an administrator with credentials to extend the eDirectory schema. The schema is automatically extended during the install. Subsequent cluster servers can be installed by container administrators (or non-administrator users) with sufficient rights to install OES Cluster Services.
IMPORTANT:For information about the eDirectory rights needed to install OES Cluster Services in a tree after the schema has been extended, see Section 5.3, Assigning Install Rights for Container Administrators or Non-Administrator Users.
See the following sections for information about extending the schema before you install OES Cluster Services in a tree.
This procedure assumes that no clusters currently exist in the tree, and the schema needs to be extended for cluster objects.
You need the tree administrator credentials for extending the eDirectory schema.
You need the following information about the tree where you want to install OES Cluster Services clusters:
Table 5-1 Tree Information Needed for the Schema Expansion
Parameter |
Description |
Example |
---|---|---|
port_num |
The port number you assigned for eDirectory communications in the tree where you plan to install clusters. The default port is 636. |
636 |
admin_username |
The typeful fully distinguished user name of the administrator who has the eDirectory rights needed to extend the schema. |
cn=admin,o=example |
admin_password |
The password of the administrator user. |
password |
server_ip_address |
The IP address of the eDirectory server that contains the schema files. |
10.10.10.102 |
You need to extend the schema only one time in the tree where you will be installing clusters.
IMPORTANT:It is not necessary to extend the schema separately from the OES Cluster Services installation if the installer of the first cluster server in the tree has the eDirectory rights necessary to change the schema, because the schema can be automatically extended during the install.
To extend the schema before OES Cluster Services is installed in the tree, the tree administrator user can expand the schema as follows:
As a user with rights to modify the eDirectory schema, log in as the root user, then open a terminal console.
In a text editor, create a text file, specify the configuration information for the OES Cluster Services cluster in it, then save the file.
The following lines are an example of the content of the file, with sample values. The directives are self-explanatory.
IMPORTANT:Ensure that you change the values inside the quotation marks to the actual settings for your cluster.
CONFIG_NCS_LDAP_IP="10.1.1.102" CONFIG_NCS_LDAP_PORT="636" CONFIG_NCS_ADMIN_DN="cn=admin.o=context" CONFIG_NCS_ADMIN_PASSWORD="password"
As the root user, enter the following command at a command prompt:
mkdir -p /var/opt/novell/install
As the root user, enter the following command at a command prompt:
/opt/novell/ncs/install/ncs_install.py -e -f configuration_filename
Replace configuration_filename with the actual name of the file that you created in Step 2, such as
/opt/novell/ncs/install/ncs_install.py -e -f /root/Desktop/my_schema_info.txt
Delete the configuration file ( configuration_filename) that you created.
This file contains a password in clear text. For security reasons, ensure that you delete the file when you are done.
Continue with Section 5.3, Assigning Install Rights for Container Administrators or Non-Administrator Users.