Release Notes for Perforce P4CMGR Version 2015.1 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 2015.1 server. It is a tool to simplify the creation and configuration of a cluster. The 2015.1 release supports new features available in the 2015.1 server. 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-r15.1 * RedHat/CentOS 6 using yum install perforce-cluster-manager-r15.1 -------------------------------------------------------------------------- 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 15.1. Previous versions of Perforce 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 2015.1 #986306 Nodes can have multiple routers and the port is no longer set at 1666. When a router is added the next available port starting from 1666 is selected unless the port is specified in the add command. A port can be specified when adding a router to a node using '--port'. If a specified port is in use an error be displayed. #839759 Multiple standby servers are supported. This was possible in the 2014.2 release but untested and unsupported. A second or subsequent standby server can be added with a 'p4cmgr add depot' command. #977909 Import from checkpoints is now supported using the journal import tool. This requires that the perforce-jnltool is used to split a checkpoint into multiple files. When these files are placed into the /p4mnt/shared//checkpoints directory, then they can be automatically picked up by depot and workspace servers. Each checkpoint file should be named based on the server id of the server. #1004917 Repositories can be located on the local machine, removing the need for the cluster to have access to the public repository at package.perforce.com. This allows administrators to retain full control over which versions of packages are installed. -------------------------------------------------------------------------- Features in 2014.2 #972869 A new empty cluster can be created and configured automatically. #972869 Services can be added to and removed from the cluster after it has been created. #972869 A cluster can be stopped and started with a single command that ensures that it is kept in a consistent state. #972869 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. #972869 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 * 'p4cmgr remove depot -s ' of master depot service prevents fail over to standby Workaround: 1. Stop depot-master service with 'p4cmgr stop -s ' 2. Wait for fail over to depot standby. 3. Run remove on stopped depot-master service with 'p4cmgr remove depot -s '. * Upgrades from 14.2 are not supported due to the many changes to the underlying file system structure. If an upgrade is required, then it is recommended that all servers on the cluster are checkpointed, and the checkpoints are used to populate a new 15.1 cluster. * Fail over of workspace server nodes is not currently supported. * Backup of workspace server nodes is not currently managed automatically. * 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. --------------------------------------------------------------------------