Release Notes for SDP - the Server Deployment Package for the Perforce Server Introduction This document notes major changes to the SDP. There are two flavors of the SDP, Unix and Windows. At a high level, the core function of the SDP is similar on Unix and Windows: To maintain an offline of the Perforce databases, and perform routine offline checkpoints in preparation for backups. At a detailed level, there are differences in both implementation and behavior on the various platforms. Enhancements are need-driven, and not necessarily applied across Unix and Windows platforms. -------------------------------------------------------------------------- Upgrading the SDP on Unix To incorporate a new version of the SDP into an existing SDP installation, first stage the deployment as in this example, assuming you have put the SDP distribution tar file in /depotdata. Working as user root on a Perforce server: cd /depotdata # If an sdp folder exists here, move it aside, e.g. to # sdp.MOVED_2014-09-11 tar -xzpf sdp.Unix.2014.2.10649.tgz chown -R perforce:perforce sdp.Unix.2014.2.10649.tgz /depotdata/sdp cd /depotdata/sdp/Server/Unix/p4/common/bin # Copy 'p4', 'p4d', 'p4broker', 'p4web', 'p4p', etc. (only # those currently used) into this 'bin' folder. cd /depotdata/sdp/Server/Unix/setup vi mkdirs.sh # Review and adjustments to mkdirs.sh suit your environment. ./mkdirs.sh 1 -test Using 'mkdirs.sh' script with the '-test' flag as illustrated above will deploy to the SDP to /tmp/p4 rather than /p4 area. If working on the Production server directly, DO NOT forget to use the '-test' flag. -------------------------------------------------------------------------- Upgrading the SDP on Windows: Install the SDP onto a different machine - configure sdp_master_config.ini - run create_env.py Manually copy resulting files to the appropriate places in your existing installation. -------------------------------------------------------------------------- Versioning the SDP: We strongly recommend that files in the following locations are versioned in Perforce: On Unix: /p4//bin /p4/common On Windows: C:\p4\\root\license C:\p4\common\... C:\p4\config\... -------------------------------------------------------------------------- CHANGE HISTORY: SDP/MultiArch/2014.3/10962 (2014/11/23): install_sdp_python.sh v1.3.5: * Updated P4API, P4Python, and Python versions. * Cosmetic fixes. SDP/MultiArch/2014.3/10872 (2014/11/12): Added SDP for Windows to The Workshop. SDP/Unix/2014.2/10868 (2014/11/12): Fixed p4p_base to enable proper service stop. This file is used by the Perforce Proxy init scripts p4p_n_init. SDP/Unix/2014.2/10824 (2014/11/06): Fixed issues with sdp_sync.sh. Silenced harmless but scary warnings when sourcing p4_vars on an SDP host that does not have the defined P4ROOT dir. SDP/Unix/2014.2/10733 (2014/10/22): Fix to sdp_sync.sh so it properly cleans its own log files. SDP/Unix/2014.2/10649 (2014/10/08): Added README.md and generated README.html files describing contribution workflow, etc. Added install_sdp_python.sh utility for installing Python and P4Python to /p4/common/python (as referenced in PATH setting in p4_vars.template). Enhanced server start/stop section in docs.. SDP/Unix/2014.2/10464 (2014/09/30): Minor adjustments to Maintenance scripts, e.g. fixing typos and adding import sys. Adjusted SDP test Vagrant file comments to account for new home in The Workshop. SDP/Unix/2014.2/10148 (2014/09/11): First release of the Server Deployment Package (SDP), into The Perforce Workshop.