Allow iPrint cluster resource the flexibility to load on nodes configured for other iPrint resources

  • Document ID:7010168
  • Creation Date:15-Feb-2012
  • Modified Date:26-Apr-2012
    • Micro Focus Products:
      iPrint

Environment

Novell iPrint for Linux
Novell Cluster Services

Situation

The default iPrint cluster configuration restricts an iPrint cluster resource to load only to a node specifically configured for that iPrint cluster volume.  That restriction occurs when running the iprint_nss_relocate script.  The iprint_nss_relocate script creates symbol links and modifies the iPrint Global Apache Configuration file (iprint_g.conf) which reference the volume hosting iPrint.  If a different iPrint volume attempted to load to that cluster node, the symbolic links and iprint_g.conf would be wrong.  The iPrint resource would load to a Comatose state.  Therefore, no other iPrint volume (which hosts a Print Manager and/or Driver Store) can load to that particular node in the cluster.  Cluster nodes (at least two) must be dedicated for a particular Print Manager and/or Driver Store.
 
This TID shows how to overcome the above described limitation.

Resolution

1.  Configure iPrint Cluster in the traditional way
This TID won't attempt to document how to configure an iPrint cluster.  However, it is important to note that the iprint_nss_relocate script must be run on every node which intends to host an iPrint resource. 
 
2. Understand and configure Resource Mutual Exclusion (RME) Groups

While following this TID allows any iPrint resource to load to any cluster node, these steps will not allow multiple Print Managers or Driver Stores to run on the same node at the same time. You must use RME Groups to define sets of resources which will not run at the same node at the same time.
 

3. Modify the iPrint resource cluster load script

a. iManager -> Cluster Manager -> Select the Cluster -> click the iPrint resource link -> Scripts

b. After the "ncpcon bind" line, add these lines
Note: change the 6 <VolumeName> strings to the actual volume name iPrint is using.

ignore_error rm /etc/opt/novell/iprint/conf
ignore_error ln -s /media/nss/<VolumeName>/etc/opt/novell/iprint/conf /etc/opt/novell/iprint/conf

ignore_error rm /var/opt/novell/iprint
ignore_error ln -s /media/nss/<VolumeName>/var/opt/novell/iprint /var/opt/novell/iprint

ignore_error rm /var/opt/novell/log/iprint
ignore_error ln -s /media/nss/<VolumeName>/var/opt/novell/log/iprint /var/opt/novell/log/iprint

sed -i s:/media/nss/[A-Za-z0-9]*:/media/nss/<VolumeName>:g /etc/opt/novell/iprint/httpd/conf/iprint_g.conf

ignore_error mv /media/nss/<VolumeName>/var/opt/novell/iprint/iprintgw.lpr /media/nss/<VolumeName>/var/opt/novell/iprint/iprintgw.lpr.bak

exit_on_error rcnovell-idsd start
exit_on_error rcnovell-ipsmd start

/etc/init.d/apache2 reload

exit 0

Click Apply

Additional Information

RME Groups requires OES2 SP3 or later.