# 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]. Required. # # Release: Release in which job is intended to be fixed. Job: SDP-646 Status: suspended Project: perforce-software-sdp Severity: C ReportedBy: robert_cowham ReportedDate: 2021/06/04 07:49:28 ModifiedBy: tom_tyler ModifiedDate: 2021/06/04 08:22:00 OwnedBy: tom_tyler Description: Enhance load_checkpoint.sh to load an edge with a standard checkpoint. This could only work if the edge checkpoint wasn't filtered; we'd need to verify that. In this context, "filtered" means making use of the *DataFilter fields in the server spec. Note that an earlier version did a pre-flight scan of the checkpoint to determine if the ServerID (specified with '-s' or in server.id) was for an edge server. That approach was 100% reliable and idiot- proof (err, I mean "safe"). However, that pre-flight scan of every checkpoint was too costly, making all checkpoint loads slower, and thus that approach was abandoned. Adding a command line flag to let the user specify that a checkpoint is to be loaded as an edge server is a possibility, and would eliminate the need for a preflight scan. However, that introduces new failure modes (of the "pilot error" variety) with increased operational complexity that could make for a mess for Support to clean up. And even then, it wouldn't honor any filtering in the server spec, and so additional checks would be needed. Note that if the edge server's seed checkpoint was created using the edge_dump.sh script, that can be used with load_checkpoint.sh as it is now. This enhancement is specifically to consider allowing a standard/full checkpoint to be used to seed an edge. DevNotes: 2021-06-04 ttyler: I have suspended this job immediately after filing it, due to concerns noted in the job. Component: core-unix Type: Feature