# 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: HMS-8 Status: open Project: perforce_software-hms Severity: B ReportedBy: tom_tyler ReportedDate: 2020/03/29 10:11:30 ModifiedBy: tom_tyler ModifiedDate: 2020/10/06 06:34:51 OwnedBy: tom_tyler Description: Support HMS automated failover using 'p4 failover' command. Original title was: Support HMS automated failover of 'standby' (journalcopy) replica. HMS supports failover of a forwarding replica, but not a forwarding 'standby' replica that uses journalcopy. The mkrep.sh script knows the details of creating a replica designated as 'ha' (High Availability) or 'ham' (metadata-only variant of 'ha'). Replicas with these tags are sutiable for use with the 'p4 failover' command, which implies many thing: * The Services in server spec is 'standby' or 'forwarding-standby' * The rpl.journalcopy.location=1 is set. * They are creatd with P4D >= 2018.2, and have the ReplicatinFrom field in the server spec set. * Their journalPrefix matches the master. This will need to support a preflight of failover, using 'p4 failover' without the '--yes' flag. We will also want to drop support for other forms of failover, to ensure best results. It is TBD whether that will be done as part of implementing this job. DevNotes: This job, HMS-8, was once SDP-204. Component: fo Type: Feature