SDP-22
Suspended
Create simple info SDP script to detail current settings, file locations, and basic usage.
(sdp_info.py ?)
Such a file will help customers and support personnel alike
by giving quick insight into a particular configuration without
having to refer to external doc or remember the particular
names and locations of SDP files.
For example:
> sdp_info.py -h
usage: sdp_info.py [-hsu]
Show usage and setting information for the collection of scripts
collectively known as the Server Deployment Package (SDP).
-h print this message
-s summary of server and connection info
-u summary of usage infromation
====== ( -s summary option)
master P4PORT: myhost:1666
case handling: sensitive
broker: yes
broker PORT: myhost:1888
proxy: no
log file location:
db file location:
archive file location:
See the instance_vars file for specific instance details: <here>
====== ( -u usage option)
Common commands:
# setup
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/init.py
# restart
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
# daily checkpoint
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
# weekly checkpoint and db rotation
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
Note: Checkpoint operations on the master server instance can
entail significant downtime. Recommend timing during low activity
period and setting downtime expectation with end users.
Warning: The weekly checkpoint and db rotation will...
Administrators are advised to ensure that the backup db ifiles are
up to date and uncorrupted by reviewing the logs in <here> and
verifying that checkpoints are completing and being moved without error.
UPDATES:
[ 2014-10-08 ttyler ]
A requirement of this new 'sdp info' mechanism is that it should
behave well with all versions of the SDP dating back to the
first version submitted to p4prod (2007/10/08). That way, Support
can distributed it to customers and ask them to run it to at least
get some sense of what a customer has.
It will be able to display more info for newer versions (e.g. those
with a 'Id:' ktext marker in mkdirs.sh, and even newer ones with a
'Version' file to display). But should at least function with older
versions, even if it's just wrapping 'p4master_run <instance> p4
set' for older versions (with instance defaulting to 1).
[ 2014-09-18 amorriss ]
The inclusion of a post-info trigger by default in all SDP installs
could be used to flag the existence of the SDP; whether simply
"echo SDP installed here" at least, better with some sanity check
(the existence of a certain flag or file?) and retrieving
'p4 configure show' information and similar would be most useful.
[ 2014-09-18 amorriss ]
Once identified as an 'SDP' installation, then the info-gathering
tools could be used. Alternatively, a 'p4 info' command could be
reworked such that it does some self-identification and provides
the output required.
Note that some or more of the information requested is displayed
by the following command:
/p4/common/bin/p4master_run <instance> /p4/common/bin/p4 set
(sdp_info.py ?)
Such a file will help customers and support personnel alike
by giving quick insight into a particular configuration without
having to refer to external doc or remember the particular
names and locations of SDP files.
For example:
> sdp_info.py -h
usage: sdp_info.py [-hsu]
Show usage and setting information for the collection of scripts
collectively known as the Server Deployment Package (SDP).
-h print this message
-s summary of server and connection info
-u summary of usage infromation
====== ( -s summary option)
master P4PORT: myhost:1666
case handling: sensitive
broker: yes
broker PORT: myhost:1888
proxy: no
log file location:
db file location:
archive file location:
See the instance_vars file for specific instance details: <here>
====== ( -u usage option)
Common commands:
# setup
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/init.py
# restart
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
# daily checkpoint
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
# weekly checkpoint and db rotation
<path to SDP scripts>/bin/master_run.py $INSTANCE_VAR/
Note: Checkpoint operations on the master server instance can
entail significant downtime. Recommend timing during low activity
period and setting downtime expectation with end users.
Warning: The weekly checkpoint and db rotation will...
Administrators are advised to ensure that the backup db ifiles are
up to date and uncorrupted by reviewing the logs in <here> and
verifying that checkpoints are completing and being moved without error.
UPDATES:
[ 2014-10-08 ttyler ]
A requirement of this new 'sdp info' mechanism is that it should
behave well with all versions of the SDP dating back to the
first version submitted to p4prod (2007/10/08). That way, Support
can distributed it to customers and ask them to run it to at least
get some sense of what a customer has.
It will be able to display more info for newer versions (e.g. those
with a 'Id:' ktext marker in mkdirs.sh, and even newer ones with a
'Version' file to display). But should at least function with older
versions, even if it's just wrapping 'p4master_run <instance> p4
set' for older versions (with instance defaulting to 1).
[ 2014-09-18 amorriss ]
The inclusion of a post-info trigger by default in all SDP installs
could be used to flag the existence of the SDP; whether simply
"echo SDP installed here" at least, better with some sanity check
(the existence of a certain flag or file?) and retrieving
'p4 configure show' information and similar would be most useful.
[ 2014-09-18 amorriss ]
Once identified as an 'SDP' installation, then the info-gathering
tools could be used. Alternatively, a 'p4 info' command could be
reworked such that it does some self-identification and provides
the output required.
Note that some or more of the information requested is displayed
by the following command:
/p4/common/bin/p4master_run <instance> /p4/common/bin/p4 set
- Status
- Suspended
- Project
- perforce-software-sdp
- Severity
- C
- Reported By
- michael
- Reported Date
- 8 years ago
- Modified By
- C. Thomas Tyler
- Modified Date
- 4 years ago
- Owned By
- russell_jackson
- Dev Notes
- This job, SDP-22, was originally named job000261.
The answer to this job is:
p4 -p server:port configure show
or, for a an old server that doesn't have configure:
/p4/common/bin/p4master_run <instance> p4 set
No other special command/tool needed. - Type
- Feature
Log in to comment