# The form data below was edited by tom_tyler
# Perforce Workshop Jobs
#
# Job: The job name. 'new' generates a sequenced job number.
#
# Status: Job status; required field. There is no enforced or
# promoted workflow for transition of jobs from one
# status to another, just a set of job status values
# for users to apply as they see fit. Possible values:
#
# open - Issue is available to be worked on.
#
# inprogress - Active development is in progress.
#
# blocked - Issue cannot be implemented for some reason.
#
# fixed - Fixed, optional status to use before closed.
#
# closed - Issue has been dealt with definitively.
#
# punted - Decision made not to address the issue,
# possibly not ever.
#
# suspended - Decision made not to address the issue
# in the immediate future, but noting that it may
# have some merit and may be revisited later.
#
# duplicate - Duplicate of another issue that.
#
# obsolete - The need behind the request has become
# overcome by events.
#
# Project: The project this job is for. Required.
#
# Severity: [A/B/C] (A is highest) Required.
#
# ReportedBy The user who created the job. Can be changed.
#
# ReportedDate: The date the job was created. Automatic.
#
# ModifiedBy: The user who last modified this job. Automatic.
#
# ModifiedDate: The date this job was last modified. Automatic.
#
# OwnedBy: The owner, responsible for doing the job. Optional.
#
# Description: Description of the job. Required.
#
# DevNotes: Developer's comments. Optional. Can be used to
# explain a status, e.g. for blocked, punted,
# obsolete or duplicate jobs. May also provide
# additional information such as the earliest release
# in which a bug is known to exist.
#
# Component: Projects may use this optional field to indicate
# which component of the project a givenjob is associated
# with.
#
# For the SDP, the list of components is defined in:
# //guest/perforce_software/sdp/tools/components.txt
#
# Type: Type of job [Bug/Feature/Problem]. Required.
# Feature and Bug are common terms.
# A Problem is suspected bug, or one without a clear
# understanding of exactly what is broken.
#
# Release: Release in which job is intended to be fixed.
Job: SDP-795
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2022/05/23 07:59:24
ModifiedBy: tom_tyler
ModifiedDate: 2022/05/23 07:59:24
OwnedBy: tom_tyler
Description:
Deploy all possible SDP Scheduled Tasks on Windows, enable/disable as needed.
The goal here is to simplify failover and simplify creation of live
checkpoints. One approach is vaguely akin to what we do on the Linux
side with the run_if_{master|edge|replica}.sh scripts, done by
enabling/disabling Scheduled Tasks based on the machine's role.
The Windows SDP should be configured with all possible Scheduled
Tasks for all roles the machine might take on. For example, if a
machine is an HA replica of the master, it should have all Scheduled
Tasks for its role as replica defined, as well as all scheduled
tasks for its role as a master. Those that that are unnecessary
for its current role should be defined but disabled.
The Description field for each Scheduled Task should be beefed
up, as that's an easy way to catch the attention of a Windows
admin unfamiliar with the SDP.
Following is a good set of scheduled tasks to defined:
* P4 Daily Checkpoint
* P4 Live Checkpoint - On Demand Only
* P4 Replica Status
* P4 Fast Verifiy
* P4 Full Verifiy
* Remove Redundant Audit Logs on Replica
== P4 Daily Checkpoint
Enabled for master and edge servers, but not other replica types
(at least, not until/unless the script works on those servers).
== P4 Live Checkpoint - On Demand Only
Always disabled. This is for on-demand use only. This is essentially
using the Sheduled Tasks applet in Windows as the user interface,
as opposed to using the command line.
== P4 Replica Status
Enabled on replica and edge servers only.
== P4 Full Verifiy
Enabled on all servers.
== P4 Fast Verifiy
Enabled on all servers.
Component: core-win
Type: Feature