# 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-743
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2022/02/06 20:24:20
ModifiedBy: tom_tyler
ModifiedDate: 2022/02/06 20:24:20
OwnedBy: tom_tyler
Description:
Enhance load_checkpoint.sh to use full checkpoints for new edges.
The '-t <Type>' will indicate a the server type, and this value
is inferred from '-s <ServerID>' if the SDP Server Spec Naming
Standard is followed.
The normal workflow for creating edge servers is to use the SDP
edge_dump.sh to create a special edge seed checkpoint, and then
load that checkpoint.
This special seed checkpoint must be used for existing edge servers
(those with any useful local data) and if the edge server is
filtered.
However, when creating new edge servers, it may be more convenient
to use a full checkpoint taken on the master rather than creating
a special purpose checkpoint using edge_dump.sh, since standard
checkpoints are readily available from routine processing on the
master. When loading checkpoins for an edge server,
load_checkpoint.sh must handle the exclusion of edge-specifc
tables.
Component: core-unix
Type: Feature