# 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-40
Status: punted
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2017/04/02 17:24:34
ModifiedBy: tom_tyler
ModifiedDate: 2022/02/05 16:46:59
OwnedBy: tom_tyler
Description:
Add 'maint-start' and 'maint-stop' to broker init scripts.
Simplify Maintencne Mode operations by providing a way
to swap out p4broker config files to signify the start
and stop of maintence windows.
With maint-start, a predefined "Maintenance Mode" p4broker
config file, which simply tell uses the server is down for
maintenance, is used. That would be:
/p4/common/config/p4_<instance>.broker.maint_mode.cfg
With maint-stop, the standard production configuration
broker is used.
DevNotes:
2017-04-02 tom_tyler: Punted this job. This feature is now
well handled by documented features to have multiple broker
configs, and a 'dfm' broker ("Down for Maintenance") is a
common use case.
2017-04-02 tom_tyler: This job, SDP-40, was originally named job000485.
Food for thought: We may also want to support the
configuration where a broker is in routine operation,
but only used to listen on the standard p4d port
during maintenance windows.
For this case, there would be no need to swap
broker config files; as the broker would only be
used for maintenance mode.
Component: core-unix
Type: Feature