# 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-629 Status: open Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2021/04/02 12:41:40 ModifiedBy: tom_tyler ModifiedDate: 2021/08/26 19:40:50 OwnedBy: tom_tyler Description: Enhanced mkrep.sh to support hanging an edge off a replica. It is a valid conifguration to have an edge server chained off a replica. For example, you might have master in EU, an regional replica in the US, and edge servers in Canada and Mexico connected to the regional US replica (to avoid pulling across the pond more than once). The mkrep.sh script needs to add support for this configuration. Currently, the '-f <ServerID>' flag, as docmented currently, is only be used used for an HA of an edge server. We'll need to make code and docs expand the use of '-f' to include allowing an edge to target a replica. Sharing archives between the replica and edge is not allowed in this configuration (at least as of 2020.2), so we'll need a safety check to prevent targeting a ServerID that has lbr.replication=shared set. That might change in p4d in the future; if so we'll need need logic to account for that with a 'p4d' version check. We'll also need know what configurations are supported on the target ServerID and enforce them. For example, can it be forwarding-standby? Can it be a forwarding-replica? Can it be a filtered forarding replica? This will require changes in the documentation embedded in the Helix Installer's settings.cfg for the TargetServerID setting, which (as with '-f <ServerID>' for mkrep.sh) indicates it is only to be used for the HA of an edge server. This is tracked as HI-73. Component: core-unix Type: Feature