sdp_install.cfg #5

#------------------------------------------------------------------------------
# Config file for install_sdp.sh version MAIN.33670.
#------------------------------------------------------------------------------
# This file is in bash shell script syntax.
# Note: Avoid spaces before and after the '=' sign.

# For demo and training installations, usually all defaults in this file
# are fine.

# For Proof of Concept (PoC) installation, Section 1 (Localization) settings
# should all be changed to local values. Some settings in Section 2 (Data
# Specific) might also be changed.

# Changing settings in Section 3 (Deep Customization) is generally
# discouraged unless necessary when bootstrapping a production installation or
# a high-realism PoC.

#------------------------------------------------------------------------------
# Section 1: Localization
#------------------------------------------------------------------------------
# Changing all these is typical and expected, even for PoC installations.

# Specify email server for the p4review script. Ignore if P4 Code Review is used.
SMTPServer=smtp.p4demo.com

# Specify an email address to receive updates from admin scripts. This may be
# a distribution list or comma-separated list of addresses (with no spaces).
[email protected]

# Specify an email address from which emails from admin scripts are sent.
# This must be a single email address.
[email protected]

# Specify the DNS alias to refer to the commit server, e.g. by end
# users. This might be something like 'perforce.example.com' or
# simply 'perforce', but probably not an actual host name like
# 'perforce-01', which would be known only to admins. The default value,
# localhost, is valid only for a single server topology.
DNS_name_of_master_server=localhost

# Specify a geographic site tag for the master server location,
# e.g. 'bos' for Boston, MA, USA.
SiteTag=bos

# Specify the hostname.  This can be left blank. If set on a system that supports
# the 'hostnamectl' utility, that utility will be used to set the hostname.  If the
# command line parameter '-H <hostname>' is used, that will override this setting.
Hostname=

# Specify the timezone.  This can be left blank. If set on a system that supports
# the 'timedatectl' utility, that utility will be used to set the timezone.  If the
# command line parameter '-T <timezone>' is used, that will override this setting.
Timezone=

#------------------------------------------------------------------------------
# Section 2: Data Specific
#------------------------------------------------------------------------------
# These settings can be changed to desired values, though default values are
# preferred for demo installations.

# Specify the TCP port for p4d to listen on. Typically this is 1999 if 
# p4broker is used, or 1666 if only p4d is used.
P4_PORT=1999

# Specify the TCP port for p4broker to listen on. Must be different
# from the P4_PORT.
P4BROKER_PORT=1666

# Specify SDP instance name, e.g. '1' for /p4/1.
Instance=1

# P4 Server case sensitivity, '1' (sensitive) or '0' (insensitive). If
# data from a checkpoint is to be migrated into this instance, set this
# CaseSensitive value to match the case handling of the incoming data set
# (as shown with 'p4 info').
CaseSensitive=1

# If SSL (Secure Sockets Layer) encryption is to be used, specify the prefix,
# typically 'ssl:'. Leave blank if not using SSL.
SSLPrefix=ssl:

# Set the P4USER value for the Perforce super user.
P4USER=perforce

# Set the password for the super user (see P4USER). If using this installer to
# bootstrap a production installation, replace this default password with your own.
Password=F@stSCM!

# Set to 1 to use encoded password files, 0 for cleartext.
UseEncryptedPassword=1

# Set to 1 to include broker with p4d, 0 for p4d only. If set to 0 and if
# using port numbers 1666 and 1999 for p4broker and p4d, consider moving p4d to
# 1666 and the unused p4broker to 1999.
DeployBrokerWithP4D=1

# Specify '1' to avoid sending email from admin scripts, or 0 to send
# email from admin scripts.
SimulateEmail=1

# Optional host-wide identifier (e.g. a company or division/team name) used
# to make the default ServerID (for a master/commit server) and the default
# auth.id more unique across an enterprise. Leave blank to preserve
# prior-release defaults. See the Server Spec Naming Standard:
# https://workshop.perforce.com/view/p4-sdp/main/doc/SDP_Guide.Unix.html#_server_spec_naming_standard
OrgName=

# Specify a ServerID value. If left blank for a master/commit server, a sensible
# default value will be assigned (incorporating OrgName, if set). See the
# Server Spec Naming Standard:
# https://workshop.perforce.com/view/p4-sdp/main/doc/SDP_Guide.Unix.html#_server_spec_naming_standard
ServerID=

# Specify the type of server. Valid values are:
# * p4d_commit - A master/commit p4d server.
# * p4d_master - A synonym for p4d_commit.
# * p4d_replica - Any type of p4d replica (except edge) with all metadata from the master, not filtered in
#   any way. May or may not be forwarding or forwarding-standby.
# * p4d_filtered_replica - A filtered replica or filtered forwarding replica.
# * p4d_edge - An edge server.
# * p4d_edge_replica - Replica of an edge server. Also set TargetServerID.
# * p4broker - An SDP host running only a p4broker, e.g. as standalone broker
#   possibly deployed in a DMZ.
# * p4p - An SDP host running only a p4p.
# * p4proxy - A synonym for p4p.
#
# The ServerID must also be set if the ServerType is any p4d_* type other than
# 'p4d_commit' or 'p4d_master'.
ServerType=p4d_commit

# Set only if ServerType is p4d_edge_replica. The value is the ServerID of
# edge server that this server is a replica of, and must match the
# 'ReplicatingFrom:' field of the server spec.
TargetServerID=

# Specify the target port for a p4p or p4broker.
TargetPort=

# Specify the listening port for a p4p or p4broker.
ListenPort=

#------------------------------------------------------------------------------
# Section 3: Deep Customization
#------------------------------------------------------------------------------
# Changing these settings is gently discouraged, but may be necessary for
# bootstrapping some production environments with hard-to-change default values
# for settings such as OSUSER, OSGROUP, P4*, etc.
#
# Changing these settings is gently discouraged because changing these values
# will cause the configuration to be out of alignment with documentation and
# sample instructions for settings that are typically left as defaults.
# However, there are no functional limitations to changing these settings.

# Specify the Linux Operating System account under which p4d and other P4
# services will run as. This user will be created if it does not exist. If
# created, the password will match that of the P4USER.
OSUSER=perforce

# Specify the primary group for the Linux Operating System account specified
# as OSUSER.
OSGROUP=perforce

#Specify a comma-delimited list of any additional groups the OSUSER to be
# created should be in.  This is passed to the 'useradd' command the '-G'
# flag. These groups must already exist.
OSUSER_ADDITIONAL_GROUPS=

# Specify home directory of the Linux account under which p4d and other P4
# services will run as, and the group, in the form <user>:<group>.  This user
# and group will be created if they do not exist.
OSUSER_HOME=/home/perforce

# Set HomeDirBackupMode to indicate whether the home directory of the OSUSER is
# to be backed up in such a way that it can be recovered with the recover
# script generated by the opt_perforce_sdp_backup service.  Valid values are:
# * Off: The OSUSER home directory is not backed up.
# * Basic: Only key files in the OSUSER home directory are backed up, such as:
#   - .profile*
#   - .bash*
#   - .p4*
#   - .ssh*
# * Full:  The entire OSUSER home directory is backed.
# When 'Full' is chosen, the backup is done using 'rsync -a' with '--delete',
# so files removed from the user home directory on any given day are removed
# from the backup on the next run. WARNING: This may consume disk space if
# large files are stored in the OSUSER home directory. To change this setting
# after installation, see the file .p4-sdp.home_dir_backup in the home
# directory of the OSUSER.
HomeDirBackupMode=Full

# The version of P4 binaries to be downloaded: p4, p4d, p4broker, and p4p.
P4BinRel=r26.1

# The following P4* settings reference directories that store Perforce
# P4 data.  If configuring for optimal performance and scalability,
# these folders can be mount points for storage volumes.  If so, they must
# be mounted prior to running the install_sdp.sh script (other than to generate
# this configuration file).
#
# See the Server Deployment Package (SDP) for information and guidance on
# provisioning these volumes.

# Define the directory that stores critical digital assets that must be
# backed up, including contents of submitted and shelved versioned files.
P4Depots=/mnt/p4depots

# Define the directory that stores critical digital assets that must be
# backed up, including metadata checkpoints and numbered journal files. If set to the same value as P4Depots, all critical assets to be backed will be on a single volume.
P4Checkpoints=/mnt/p4depots

# Define the directory used to store the active journal (P4JOURNAL) and
# various logs.
P4Logs=/mnt/p4logs

# The /P4DB1 and /P4DB1 settings define two interchangeable
# directories that store either active/live metadata databases (P4ROOT) or
# offline copies of the same (offline_db). These typically point to the same
# directory. Pointing them to the same directory simplifies infrastructure
# and enables the fastest recovery options. Using multiple metadata volumes
# is typically done when forced to due to capacity limitations for metadata
# on a single volume, or to provide operational survivability of the host in
# event of loss of a single metadata volume.
P4DB1=/mnt/p4db
P4DB2=/mnt/p4db