In addition to bug fixes, the following changes and enhancements were made for Novell Cluster Services for Linux in OES 2 SP1.
The administrator of a Novell eDirectory tree can now extend the schema for cluster objects before clusters are installed in the tree. This allows container administrators to install Novell Cluster Services without needing tree-level administrator rights. See Section 5.2, Extending the eDirectory Schema to Add Cluster Objects.
Container administrators can install Novell Cluster Services without needing tree-level administrator rights. Ensure that you have the rights needed for the install. See Section 5.3, Assigning Install Rights for Container Administrators (or Non-Administrator Users).
In this release, a behavior change was made to address a deadlock defect. After adding a new node to the cluster, the new node cannot be displayed in the Clusters plug-in to iManager until the ncs-configd.py -init script is run, or until the cluster is restarted.
IMPORTANT:A Novell Cluster Services patch is available in the patch channel and on the Novell Downloads Web site that allows you to add a new node seamlessly again on a Linux server. For cluster conversions, a cluster restart is still necessary after all NetWare nodes have been removed from the cluster.
Run one of the following commands in order to make cluster view display the new node’s name correctly. It is okay to run ncs-configd.py on an active cluster.
/opt/novell/ncs/bin/ncs-configd.py -init
or
rcnovell-ncs restart
If you are converting a cluster from NetWare to Linux, you must restart the cluster instead so that clstrlib.ko is reloaded.
For example, if you install a server named sales_03 in an existing cluster named oes2_sales_cluster with two existing member nodes named sales_01 and sales_02, the new node is generically displayed as Node_03 when you enter the cluster view command:
Cluster OES2_SALES_CLUSTER This node SALES_02 [ epoch 4 master node SALES_02 ] Cluster nodes [ SALES_01, SALES_02, Node_03 ]
After running the cluster configuration daemon or restarting Novell Cluster Services, the new node’s name is properly displayed as SALES_03, and the node is visible in iManager.
Cluster OES2_SALES_CLUSTER This node SALES_02 [ epoch 4 master node SALES_02 ] Cluster nodes [ SALES_01, SALES_02, SALES_03 ]
Beginning in OES 2 SP1 Linux, the attribute in the Cluster object is no longer maintained. This applies to Linux clusters and mixed NetWare and Linux clusters.
This release supports Novell AFP (Apple Filing Protocol) for Linux in combination with Novell Storage Services (NSS) volumes on OES 2 SP1 Linux. See Novell AFP.
This release supports Novell CIFS for Linux in combination with NSS volumes on OES 2 SP1 Linux. See Novell CIFS.
This release supports using clusters in Domain Services for Windows contexts for OES 2 SP1 Linux. See Novell Domain Services for Windows.