Release Notes for Red Hat Cluster Configuration

Version 1.0.1-1 Updates (since 1.0.0-5)
---------------------------------------
  * Added edit to ensure that if entered, the Tiebreaker IP
    address must NOT be one of the cluster members, nor any
    cluster service ip address, nor localhost.

  * Changed wording on the Daemon Properties 'clumembd' tab
    to make Disk vs. Network tiebreaker fields more clear.

  * Cluster Status dialog - change 'Configure' menu item
    in Cluster => Configure from Alt-C to Ctrl-C. Because
    'Cluster' menu is invoked by Alt-C, Alt-C was just
    displaying the Cluster menu.  So, since Alt-C is already
    used, the 'Configure' menu item was changed to Ctrl-C.
    This(Ctrl) is also more consistent with other menu items.

  * Cluster Configuration dialog - fixed Ctrl-P accelerator
    key to properly display the 'Properties' dialog for the
    selected list item.

  * Fixed bug 105732 for the Samba Share Druid - If an
    "Existing Service" was selected, then don't automatically
    pre-select "Existing Device" - now count the number of
    devices that the selected service has.  If there are no
    devices, then pre-select "New Device" instead.

  * Fixed bug 106028 - added manpages for cluster-config and
    cluster-convert.

  * Fixed bug 106232 - Cluster Status 'memberDialog' was not
    displaying the Login value of a network powercontroller.
    Problem was the config file XML was using tag 'user'
    instead of 'login' - changed memberDialog to use 'user',
    and renamed screen column from 'Login' to 'User'.

============================================================

Service relocation:
  In Cluster Status, when relocating a service to a
  specific member by dragging the service to that
  member, if the service cannot be started on that
  member, but the service can be started on another
  member, then the service will be started on the
  other member and there will be NO notification to
  the user that there was a problem starting the
  service on the original target member.  However,
  the logs on the original target member will reflect
  the error (log level 'error') starting the service,
  and the logs on the member that actually started
  the service will reflect that it did start the
  service (log level 'notice').

Disk Tiebreaker restriction:
  When using a disk tiebreaker (gui Daemon 'cluquorumd'
  option 'pinginterval'), if you start with a 3-member
  cluster, and delete one member leaving 2 members, you
  need to restart the cluster software on each member.
  The reason is that pinging the shared disk is done by
  a separate thread that only gets spawned at cluster
  startup.

Failover Seconds / Disk Ping Interval Relationship:
  MINIMUM_TKO_COUNT is a constant specified both in the
  clumanager cluster code, and in the gui code.
  MINIMUM_TKO_COUNT is referenced in the following
  paragraphs.

  For clusters with 2 members, when a 'cluquorumd' disk
  'pinginterval' is specified, an edit exists in the gui -
  failover seconds must be greater than the minimum disk
  pinginterval (pinginterval * MINIMUM_TKO_COUNT).  If it
  is, then the test passes.  If it is not, then the test
  fails, and a warning is displayed in the gui allowing
  the user to select a pinginterval that is valid.

  This edit does NOT exist in the command line tool
  redhat-config-cluster-cmd.  If a pinginterval is
  specified that when multiplied with the MININUM_TKO_COUNT
  is greater than or equal to the failover seconds,
  then the cluster will NOT start properly, and a
  message will be logged.

APC MasterSwitch Network Powercontroller requirements:
  - APC MasterSwitch needs AOS 3.0.3 and APP(firmware) rev 2.2.0.
  - APC MasterSwitch Plus needs AOS 2.5.4, and APP(firmware) rev 2.0.0.

Shared State:
  - Shared State has been set to 'Shared Raw Device' and can not
    be changed.

Samba Share Configuration Files:
  - Samba Share names may NOT contain spaces.
  - Code now exists within redhat-config-cluster to create, update,
    and delete the samba share configuration files for cluster
    services that specify samba shares.
  - Removing the Samba Share Name in redhat-config-cluster or
    redhat-config-cluster-cmd will NOT cause the samba share
    configuration file corresponding to the previous share name
    /etc/samba/smb.conf.[previous sharename] to be deleted.
  - Changing the Samba Share Name in redhat-config-cluster
    or redhat-config-cluster-cmd *WILL* cause
      1. the Samba configuration file to be renamed
           from: /etc/samba/smb.conf.[old share name]
           to:   /etc/samba/smb.conf.[new share name]
      2. all occurrences of [old share name] inside
         that file to be changed to [new share name].
    but ***ONLY ON THE CURRENT MEMBER***.  The user is
    responsible for copying that new samba share
    configuration file to all the other cluster members,
    *AND* for removing the samba share configuration file
    with the "old" share name from all the other cluster
    members.

Device *Mount* Options:
  - Device 'Mount' options are *NOT* validated by
    redhat-config-cluster, nor by redhat-config-cluster-cmd.
    For information on which options are valid for the
    device mount, see 'man exports'

Command Line Tool:
  - The cluster configuration command line tool
    'redhat-config-cluster-cmd' is functional, and a manpage
    is present.  Users can use it, but are encouraged to use
    the gui tool redhat-config-cluster to configure a
    Clumanager cluster.
