p4_vars.template #37

  • //
  • guest/
  • perforce_software/
  • sdp/
  • main/
  • Server/
  • Unix/
  • p4/
  • common/
  • config/
  • p4_vars.template
  • View
  • Commits
  • Open Download .zip Download (10 KB)
#==============================================================================
# Copyright and license info is available in the LICENSE file included with
# the Server Deployment Package (SDP), and also available online:
# https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/LICENSE
#------------------------------------------------------------------------------
# shellcheck disable=SC2148

# This defines the version of the format of this file, used when the SDP is
# upgraded.

# shellcheck disable=SC2034
# SDP_P4_VARS_FORMAT defines the version of the format of this file,
# used when the SDP is upgraded. DO NOT CHANGE SDP_P4_VARS_FORMAT.
SDP_P4_VARS_FORMAT=1.6

# This p4_vars file sets the standard SDP bash shell environment.  It contains
# global and default settings for all instances. Source this file with a
# parameter, the SDP instance name. For example, to set the shell environment
# for an instance named acme, do:
#
# $ source /p4/common/bin/p4_vars acme
#
# Note that a '.' (dot) command can be used in place of the world 'source'.
#
# Sourcing this p4_vars file causes the instance-specific settings file to
# be sourced if it exists.  Instance-specific settings files are in the
# /p4/common/config directory.  For the acme instance, the instance-specific
# settings file would be p4_acme.vars. 
#
# If the instance parameter is omitted, an instance name of '1' (the digit one)
# is assumed.

# This file should not be modified. If site-specific overrides or additional
# settings are desired, please add this syntax (like this file):
# /p4/common/config/site_global_vars
#
# If that file exists, it will be sourced in by this file after the settings
# in this file are read in, and before any instance-specific overrides are
# set.

# Save SHELLOPTS
_shellopts=$SHELLOPTS

# Trap unbound (undefined) variables, treating them as an error.
set -u

export OSUSER=REPL_OSUSER
export SDP_VERSION="REPL_SDPVERSION"

export AWK=awk
export CUT=cut
export DF="df -h"
export GREP=grep
export ID=id
export SDPMAIL=mail
export PS=ps

OS=$(uname)
if [ "${OS}" = "SunOS" ] ; then
   export AWK=/usr/xpg4/bin/awk
   export ID=/usr/xpg4/bin/id
   export SDPMAIL=mailx
elif [ "${OS}" = "AIX" ] ; then
   export DF="df -m"
fi

# Which perforce instance are we configuring? Defaults to 1.
export SDP_INSTANCE=${1:-1}

# The P4INSTANCE variable is deprecated, and is maintained here for backward
# compatibility.  The SDP_INSTANCE variable should be referenced instead, as
# P4INSTANCE may go away in a future release.
export P4INSTANCE=$SDP_INSTANCE
export P4SERVER="p4_${SDP_INSTANCE}"
export P4SSLDIR=/p4/ssl
export P4HOME="/p4/${SDP_INSTANCE}"
export TMP=${P4HOME}/tmp
export P4TMP=${P4HOME}/tmp

# Explicitly unset environment variables that affect p4d server if they
# are defined at startup, excluding those that are always defined in this
# file, like P4ROOT, P4PORT, P4LOG, and P4JOURNAL.  This prevents cross-
# instance shell environment contamination if p4_vars is sourced multiple
# times for different instances.
unset P4AUTH P4CHANGE P4DEBUG P4AUDIT P4TARGET

export P4ROOT=${P4HOME}/root
export P4DTG_ROOT=/p4/common/dtg
export P4JOURNAL=${P4HOME}/logs/journal
export P4CONFIG=${P4HOME}/.p4config
export P4TICKETS=${P4HOME}/.p4tickets
export P4TRUST=${P4HOME}/.p4trust
export P4ENVIRO=/dev/null/.p4enviro
export DEPOTS=${P4HOME}/depots
export CHECKPOINTS=${P4HOME}/checkpoints
export LOGS=${P4HOME}/logs
export P4LOG=${LOGS}/log
export P4LOGS=$P4HOME/logs
export P4CBIN=/p4/common/bin
export P4CSBIN=/p4/common/site/bin
export P4CCFG=/p4/common/config
export P4CLIB=/p4/common/lib
export PERLHOME=/p4/common/perl
export PERL5LIB=$PERLHOME/lib:$P4CLIB:${PERL5LIB:-}
export PYHOME=/p4/common/python
export RBHOME=/p4/common/ruby
export HMS_HOME=/p4/common/hms
export PATH=$P4HOME/bin:$P4CBIN:$PYHOME/bin:$PERLHOME/site/bin:$PERLHOME/bin:$RBHOME/bin:$P4CSBIN:$PATH:.
export MANPATH=$PERLHOME/site/man:$PERLHOME/man:${MANPATH:-}
export SERVERID=

if [[ -r "${P4ROOT}/server.id" ]]; then
   SERVERID=$(head -1 "${P4ROOT}/server.id")
else
   # If a real ServerID is not set via a server.id file, use the short
   # hostname as a default.  This is not appropriate for a real p4d,
   # but is fine for SDP-managed machines that use just a proxy or broker.
   # In those cases, SERVERID is used to define the service user, prefixed
   # with 'svc_'. This works well if reasonable host names are assigned.
   SERVERID=${HOSTNAME%%.*}
fi

# P4Proxy Settings
export P4PCACHE="$P4HOME/cache"

# Set KEEPCKPS to the number of checkpoint & journal files and their
# corresponding log files to keep.  Checkpoints and their log file are
# numbered with the same journal counter number.  Checkpoints/journals
# and their logs are removed when daily_checkpoint.sh, live_checkpoint.sh,
# or recreate_db_checkpoint.sh are run.
#  Set KEEPCKPS=0 to avoid automated cleanup of checkpoints and logs.
export KEEPCKPS=21

# KEEPJNLS allows you to keep a different number of journals than checkpoints
# in case you rotate the journal more frequently than you run checkpoints.
export KEEPJNLS=21

# Set KEEPLOGS to the number of server logs to keep, counting back from
# the most recent.  Server logs are numbered with their corresponding
# journal counter number, since server logs are rotated when checkpoint
# logs are rotated.  Keep in mind that if scripts are set to run
# more than once per day, this will not correspond to the number
# of days, just the number of iterations of script calls.
# KEEPLOGS affects all log files other than checkpoint logs, which are
# governed by KEEPCKPS.
# Set KEEPLOGS=0 to avoid automated cleanup of old server logs.
export KEEPLOGS=21

# Don't change this; change or comment the above as needed
export P4BIN=${P4HOME}/bin/p4_${SDP_INSTANCE}
export P4DBIN=${P4HOME}/bin/p4d_${SDP_INSTANCE}
export P4PBIN=${P4HOME}/bin/p4p_${SDP_INSTANCE}
export P4BROKERBIN=${P4HOME}/bin/p4broker_${SDP_INSTANCE}
export P4DTGBIN=${P4HOME}/bin/p4dtg_${SDP_INSTANCE}
export P4_VERSION P4D_VERSION P4BROKER_VERSION P4P_VERSION

export SDP_ADMIN_PASSWORD_FILE="$P4CCFG/.p4passwd.${P4SERVER}.admin"

# Define *_VERSION values.  These will look like "2014.1.899321"
# or "2015.1_BETA.903064".  For example, to specify behavior specific
# to 2014.1 or later P4D, test with [[ "$P4D_VERSION" > "2014.1" ]].
# That expression will be true 2014.1 and any subsequent release.  Since
# the values contain the patch number, all releases of "2014.1.*" will
# be greater than the string "2014.1", so "greater than or equal to" is
# implied.
export P4_VERSION P4D_VERSION P4P_VERSION P4BROKER_VERSION

[[ -x $P4BIN ]] && P4_VERSION=$($P4BIN -V|$GREP ^Rev.|$CUT -d '/' -f 3).$($P4BIN -V|$GREP ^Rev.|$CUT -d '/' -f 4|$CUT -d ' ' -f 1)
[[ -x $P4DBIN ]] && P4D_VERSION=$($P4DBIN -V 2>/dev/null|$GREP ^Rev.|$CUT -d '/' -f 3).$($P4DBIN -V 2>/dev/null|$GREP ^Rev.|$CUT -d '/' -f 4|$CUT -d ' ' -f 1)

# Set version values for optional executables.
[[ -x $P4PBIN ]] && P4P_VERSION=$($P4PBIN -V|$GREP ^Rev.|$CUT -d '/' -f 3).$($P4PBIN -V|$GREP ^Rev.|$CUT -d '/' -f 4|$CUT -d ' ' -f 1)
[[ -x $P4BROKERBIN ]] && P4BROKER_VERSION=$($P4BROKERBIN -V|$GREP ^Rev.|$CUT -d '/' -f 3).$($P4BROKERBIN -V|$GREP ^Rev.|$CUT -d '/' -f 4|$CUT -d ' ' -f 1)

# Number of seconds to delay service start for p4d/p4broker/p4p.  This helps
# prevent issues with a too-fast service restart when the port may still not
# be cleared, system resources may not be available during the boot process,
# or similar timing issues. Delaying on start is also a workaround for issues
# where the license file references a not-quite-static reserved IP address
# that may not be be accessible early in the machine reboot process; for
# this purpose a value as high as 20 may be needed.  This can be set
# to a value of 0 if no delay is desired.
export SDP_START_DELAY=2

# If a site global settings file exits, source it here.
if [[ -f "$P4CCFG/site_global_vars" ]]; then
   # shellcheck disable=SC1091
   source "$P4CCFG/site_global_vars"
fi

#------------------------------------------------------------------------------
# Custom Local Changes
#------------------------------------------------------------------------------
# Any local customizations that apply to all instances should appear in the
# file sourced below in the /p4/common/site structure, which contains site-
# specific that are not part of the SDP package.

if [[ -d "/p4/common/site/config/p4_vars.local.d" ]]; then
   # shellcheck disable=SC1090
   for f in /p4/common/site/config/p4_vars.local.d/*; do source $f; done
fi

if [[ -r /p4/common/site/config/p4_vars.local ]]; then
   # shellcheck disable=SC1091
   source /p4/common/site/config/p4_vars.local
fi

# Sets instance-specific vars.  Last so that the caller sees the error.
if [[ -f "/p4/common/config/${P4SERVER}.vars" ]]; then
   # shellcheck disable=SC1090
   source "$P4CCFG/${P4SERVER}.vars"
fi

# If 'nounset' was not in SHELLOPTS when we started (i.e. 'set -u' mode), call
# 'set +u'.  This is a workaround to a Linux bug:
# https://bugzilla.redhat.com/show_bug.cgi?id=1055784
# 
# The goal: We want it so p4_vars can be sourced safely in scripts and in user
# shell environments.  In scripts, we want 'set -u' to be set, as a bash
# programming best practice disallowing reference of undefined variables
# ("unbound variables" in bash parlance).  However, in some versions of
# Linux and more specifically bash, the tab command completion is broken
# if 'set -u' is set, such that when you hit the 'tab' key interactively,
# instead of getting completion, you get a hideous error.  This workaround
# gives you optimal behavior in scripts that have already called 'set -u'
# before sourcing the SDP environment file, as well as interactive shells
# (where the 'set +u' workaround applies).
if [[ "$_shellopts" != *"nounset"* ]]; then
    set +u
fi
# Change User Description Committed
#39 31566 C. Thomas Tyler Released SDP 2024.2.31564 (2025/05/14).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#38 31077 C. Thomas Tyler Released SDP 2024.2.31075 (2024/12/20).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#37 30915 C. Thomas Tyler Released SDP 2024.1.30913 (2024/11/20).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#36 29891 C. Thomas Tyler Released SDP 2023.1.29699 (2023/07/11).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#35 29612 C. Thomas Tyler Released SDP 2023.1.29610 (2023/05/25).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#34 29401 C. Thomas Tyler Released SDP 2022.2.29399 (2023/02/06).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#33 28412 C. Thomas Tyler Released SDP 2021.2.28410 (2021/11/24).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#32 28240 C. Thomas Tyler Released SDP 2021.1.28238 (2021/11/12).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#31 27761 C. Thomas Tyler Released SDP 2020.1.27759 (2021/05/07).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#30 27331 C. Thomas Tyler Released SDP 2020.1.27325 (2021/01/29).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#29 26403 C. Thomas Tyler Released SDP 2019.3.26400 (2020/03/28).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#28 25245 C. Thomas Tyler Released SDP 2019.1.25238 (2019/03/02).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#27 23510 C. Thomas Tyler Released SDP 2018.1.23504 (2018/01/19).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev',
with selective removal of work-in-progress files.
#26 22685 Russell C. Jackson (Rusty) Update main with current changes from dev.
#25 21774 akwan update p4p_base to incorporate proxy monitoring and set default value in p4_vars
#24 21483 C. Thomas Tyler Released SDP 2016.2.21480 (2017/01/11).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#23 20767 C. Thomas Tyler Released SDP 2016.2.20755 (2016/09/29).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#22 20390 C. Thomas Tyler Released SDP 2016.1.20387.
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev',
with selective removal of changes related to work-in-progress files.
#21 20353 C. Thomas Tyler Released SDP 2016.1.20348.
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev',
with selective removal of changes related to work-in-progress
changes.
#20 20050 C. Thomas Tyler Released: 2016.1.20028 (2016/08/03).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#19 19898 C. Thomas Tyler Released SDP/MultiArch/2016.1/19888 (2016/07/07).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#18 19694 C. Thomas Tyler Released SDP/MultiArch/2016.1/19661 (2016/06/08).
Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'.
#17 18961 C. Thomas Tyler Released: SDP/MultiArch/2016.1/18958 (2016/04/08).
#16 18619 Russell C. Jackson (Rusty) Updating main with current changes.
#15 15856 C. Thomas Tyler Replaced the big license comment block with a shortened
form referencing the LICENSE file included with the SDP
package, and also by the URL for the license file in
The Workshop.
#14 15691 Russell C. Jackson (Rusty) Changed to always create a checkpoints.rep directory on the logs volume so that moving
the pre-rotated journal back to be the live journal will be a move operation when doing
a failover.

Added a SHAREDDATA setting to p4_vars so that I could check for that in sync_replica and
weekly_sync replica. That allowed me to delete weekly_sync_shared_replica and sync_shared_replica.

Added cleanup of checkpoints.rep to sync_replica and weekly_sync_replica since that is
where the replica journals should always be located now.

Removed cleanup of checkpoints.rep from daily and weekly backup scripts since those
should not be handling replica file clean up.

The SDP is now designed to be used with the journalcopy and p4 pull -L commands rather
than the old style replication using just pull. Failover requires that you move the
pre-rotated journal that is in the checkpoints.rep directory back to
/p4/${SDP_INSTANCE}/logs/journal now along with updating the server.id file.
#13 15370 C. Thomas Tyler Minor tweaks to p4_vars.template:
* Added comments for MAILTO and MAILFROM, clarifying that MAILTO can have a
comma-delimited list (no spaces) and MAILFROM must be a single address.

Cleanup:  Added 'export' declarations so a few extra lines containing only export
declarations could be deleted.  Collateral benefit is that CUT, GREP, and PS are
now exported consistently along with their friends AWK, SED, MAIL, DF, ID, etc.
#12 14073 Russell C. Jackson (Rusty) Backed out changes that moved variables to p4_vars.
The variables are intended to be in instance vars
 to keep everything about a particular instance in one location. It was confusing for people to see
a setting in p4_vars and not understand that setting was being overridden in the instance vars.

 There shouldn't be any overlap between p4_vars and instance vars anymore.

Also, server.id is not optional. It must exist. It is how you control whether the instance is a master
 or a replica. It is not set by the scripts anymore because that was also confusing people. They would
 try to change the role of a server by changing server.id and we previously would just overwrite their
changes. Now, the SDP just reads the server.id so that the user has control over it. That doesn't
 confuse them since that is how our docs tells them to change a server's role.
#11 14045 Robert Cowham Move some stuff from instance_vars to p4_vars (or at least for defaults).
Clarify user messages.
#10 13937 C. Thomas Tyler Pushing SDP 2015.1.13934.
#9 13908 C. Thomas Tyler Pushing SDP 2015.1.13906.
#8 12463 Russell C. Jackson (Rusty) Changed keeplogs to 7 to match checkpoints.
#7 12113 Russell C. Jackson (Rusty) Moved ssl dir to /p4.
There is no need for an ssl directory under each instance.

 There are also some signs of possible issues with the certificates residing on an
 NFS mounted volume in one environment so far.
#6 11919 Russell C. Jackson (Rusty) Added a SERVERID variable to p4_vars and updated backup_functions to use it.

 Changed the location and the names of the config files so that they could
 live in /p4/common/config (You're welcome Tom). The files names are:

 p4_$INSTANCE.vars
 p4_$INSTANCE.p4review.cfg

 p4_$INSTANCE.vars will now set P4REPLICA to FALSE if SERVERID matches
 MASTERNAME, otherwise it is TRUE.

 This change means that a user must change server.id now in order to change
 the role of the server rather than changing the instance vars file. This
 makes more sense to a user that is reading the admin guide about server.id
 rather than overwriting the file based on a setting that isn't in the admin guide.

 Change mkdirs to reflect all of the above changes.
#5 11908 adrian_waters Use set -u to trap unbounded variables
#4 11758 Russell C. Jackson (Rusty) Change MAIL variable to SDPMAIL to avoid conflicts with customer variables.

 Changed sdp_sync.sh to use get_mail_opts from backup_functions to avoid
 duplicate functions.
#3 11730 Russell C. Jackson (Rusty) Moved P4SERVER variable to p4_vars so that all scripts can use it properly.
 replica_status.sh referenced it, but it wasn't working since it was only in
 backup_functions.sh
#2 11570 Russell C. Jackson (Rusty) Brought in changes from Mark Foundry to add -S $MAILFROM to mail commands.

 Changed sync_replica.sh and weekly_sync_replica.sh to use $LOGFILE for consistency.

 Added mail command to both files as well.
#1 11524 Russell C. Jackson (Rusty) Released updated version of the SDP from Dev.
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/config/p4_vars.template
#1 11477 Russell C. Jackson (Rusty) Updated to use /usr/bin/env python

Added workshop header.

 Changed cfg to config.
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/cfg/p4_vars.template
#1 11474 Russell C. Jackson (Rusty) Had to move the cfg directory to the metadata volume and link it under the instance
directory to provide the proper separation in a shared volume environment. The
 instance specific vars cannot be in a shared directory since they need to be different
 on each node using the shared volume.

 Since the files moved back to the instance directory, I changed the names back to:
   instance_vars
   p4review.cfg
 to keep things simple.

 Also moved p4_vars.template to SDP/Server/Unix/p4/common/cfg so that it doesn't get
 copied to the /p4/common/bin folder. Plus, it makes more sense for it to be in that
 directory in the SDP structure.
//guest/perforce_software/sdp/dev/Server/Unix/p4/common/bin/p4_vars.template
#4 11466 Russell C. Jackson (Rusty) Initial work to simplify p4_vars and remove cluster stuff.

 Testing of named instances surfaced some bugs that are in prod sdp,
 now fixed in dev.

 Added three triggers from RCJ SDP

 Moved p4review.cfg into the new /p4/common/cfg to go along with the
 instance_vars files. mkdirs.sh now generates an instance_p4review.cfg
 as well.

 Removed incremental p4verify to clean up a bit. It didn't support replicas
 and was really never used.

 All port settings now live in <instance>_vars file. You set what you want
 the ports to be in mkdirs.sh. There is no more fancy logic to try to guess
 what the port should be. You set it, and that is what it is.

 Remaining to do is to updated scripts to not need p4master_run. Saved
 that work for later since this is tested and works.
#3 10994 Robert Cowham Catchup from Main
#2 10867 C. Thomas Tyler Merge Down: Rereshed 'dev' from 'main'.
#1 10638 C. Thomas Tyler Populate perforce_software-sdp-dev.
//guest/perforce_software/sdp/main/Server/Unix/p4/common/bin/p4_vars.template
#1 10148 C. Thomas Tyler Promoted the Perforce Server Deployment Package to The Workshop.