Release Notes for
                                 Perforce P4CMGR

                               Version 2014.2 Release


Introduction

    Perforce P4CMGR provides administrators with a way to create and manage
    a Perforce cluster using a single command line tool. P4CMGR does not add
    any clustering functionality over that provided by Perforce Cluster
    features in 2014.2 server. It is a tool to simplify the creation and
    configuration of a cluster.

    The 2014.2 release is the initial public release.

    Perforce numbers releases YYYY.R/CCCCC, e.g. 2014.1/123456.
    YYYY is the year; R is the release of that year; CCCCC is the
    bug fix change level.  Each bug fix in these release notes is
    marked by its change number.  Any release includes (1) all bug
    fixes of all previous releases and (2) all bug fixes of the
    current release up to the bug fix change level.

    Please send all feedback to support@perforce.com.

--------------------------------------------------------------------------

Provided Packages

    P4CMGR is provided as installation packages for both Ubuntu and
    CentOS. The packages are available from the Perforce package repository
    which is located here:

    http://package.perforce.com/

    This site includes instructions for setting up your server to download
    and install P4CMGR using your system's standard installation command.

    Packages are available for:

    * Ubuntu 12.04 using apt-get install perforce-cluster-manager
    * RedHat/CentOS 6 using yum install perforce-cluster-manager

--------------------------------------------------------------------------

Documentation

    P4CMGR documentation is included online at:

      http://www.perforce.com/p4cmgr

--------------------------------------------------------------------------

Supported Platforms

    P4CMGR has been tested on the following platforms:

    * Ubuntu 12.04 LTS
    * CentOS 6 (6.4 or later)
    * RedHat 6 (6.5 or later)

--------------------------------------------------------------------------

Server Dependencies

    P4CMGR requires the latest version of Perforce server 14.2. Previous
    versions of Perforce (including the initial 14.2 release) are not
    supported.

    When installing the P4CMGR packages, the correct version of Perforce
    Server will be automatically installed.

    P4CMGR has a number of system configuration requirements that must be met
    before it is installed. Normally, P4CMGR is used to configure a Perforce
    cluster that spans several host machines, and each of these must be
    correctly configured.

    These are documented in the online help here:

    http://www.perforce.com/p4cmgr

    
--------------------------------------------------------------------------

Features in 2014.2

    * A new empty cluster can be created and configured automatically.

    * Services can be added to and removed from the cluster after it has been
      created.

    * A cluster can be stopped and started with a single command that ensures
      that it is kept in a consistent state.

    * We support a standard cluster configuration, which consists of exactly
      two depot servers, one or more workspace servers and a router. This
      provides fail over for the depot server and scalability for the
      workspace servers.

    * We support a workspaceless cluster configuration, which consists of two
      or more depot server, no workspace servers and one or more routers. This
      provides scalability for the depot servers.

--------------------------------------------------------------------------

Known Limitations and Behaviours

    * Creation of a cluster from an existing checkpoint is not supported.

    * Only a single standby server is supported in a depot server HA
      configuration. Multiple standby servers can be added, but this is not
      a supported configuration.

    * Fail over of workspace server nodes is not currently supported.

    * Backup of workspace server nodes is not currently managed automatically.

    * A node can only have a single router running on it.

    * The usage specifies that -l can be used to apply a license to a service
      when it is added to the cluster. This is true, but the -l option must
      be specified after the node type, not before it.

    * If the OS user does not have 'NOPASSWD' sudo access to the target
      systems, init and add commands will silently hang waiting for a
      password. 

    * The zkMonitor utility is limited to running as root. If it is run as
      a non-root user, you will get a "No module named kazoo.client" error.

--------------------------------------------------------------------------