Wednesday Dec 03, 2008

Editing Cluster Properties on the Fly

Ajax-based in-page editing is fast becoming a standard feature in various web applications nowadays. It is a very useful feature when one wants to quickly edit data that is displayed on a web page.

We have pages in Sun Cluster Manager (SCM) that list all the properties corresponding to related resource groups and resources. To edit any of these properties, the latest performance-enhanced SCM version for Solaris Cluster 3.2 2/08 provides the option of using in-page editing. The idea is to just click on the data and you are ready to edit!
Compared with the earlier, tedious way of invoking the Edit Properties Wizard for the same task, in-page editing is surely a quick way to get around things.



As with the Edit Properties Wizard, the benefits of using in-page Editing include not having to remember the exact command you need to change a property. But for the ever-curious ones, this feature also displays the command executed and errors (ifany) while editing a property.

Care is taken to permit users to edit only editable properties; properties like Resource Group Name cannot be modified. Properties that can be edited are differentiated by the use of a rectangular “sweet spot” around the property value. On clicking this space, a popup appears that prompts the user to provide a modified value. Lastly, the modification is done by clicking the OK button on the popup, which then executes the corresponding command on the cluster.



To edit more than one property at once, which is not allowed through this feature, the best way is to use the Edit Properties wizard, which is invoked by clicking the Edit Properties button near the top of the Properties page. This wizard would also perform some extra validation checks before the command execution.


Happy Editing...
Madhur Bansal
Solaris Cluster Engineering

Friday Aug 10, 2007

Sun Cluster 3.2 Patch 2 Version Manager Requirement

Sun Cluster 3.2 Patch 2 requires the version manager command to commit patch changes after you apply any patch that contains a new protocol or changes a protocol. As a result, you must use the scversions command to apply Sun Cluster 3.2 Patch 2 and any subsequent patches. The scversions command determines if the new patch contains protocol changes that require a commit.

To download patches, go to http://sunsolve.sun.com.

Complete the following steps after you have applied a patch to all of your cluster nodes using any of the patch methods provided in the Patching Sun Cluster Software and Firmware chapter in the System Administration Guide.


  1. Check to see if you need to commit the patch software by using the scversions command.

    # /usr/cluster/bin/scversions

    You will see one of the following results:

    Upgrade commit is needed.
    Upgrade commit is NOT needed. All versions match.

  2. If a commit is needed, commit the patch software.

    # /usr/cluster/bin/scversions -c

    The -c option causes the cluster to commit to and run the new patched software.


Note: Running scversions will cause one or more Cluster Membership Monitor (CMM) reconfigurations, depending on the situation.

Rita McKissick
Sun Cluster Documentation

About

mkb

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today