# 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.
#
# 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.
Job: SDP-294
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2018/02/03 08:13:26
ModifiedBy: tom_tyler
ModifiedDate: 2018/02/03 08:13:26
OwnedBy: tom_tyler
Description:
Deprecate sdp_hosts.cfg in favor of HelixTopology.cfg.
The sdp_sync.sh ("tight ship enforcer" script) and the
global_replica_status.sh script use the sdp_hosts.cfg file,
but should be retooled to use the HelixTopology.cfg file
instead of the sdp_hosts.cfg.
Some concerns with doing this:
* The sdp_hosts.cfg file is simpler and less intimidating,
and has a narrow scope. Despite some overlap, it may be
worth keeping it as a separate file from the more comprehensive
but possibly daunting HelixTopology.cfg.
* Presently sdp_hosts.cfg is a pre-requisite to running hms_ts_setup.sh.
* We need to decide whether to make it backward-compatible,
e.g. support both sdp_hosts.cfg and HelixTopology.cfg,
deferring to HelixTopology.cfg if it exists. That would
make it more complex and potentially confusing, but could
simplify the upgrade process for customers using sdp_hosts.cfg
but not doing the full HMS thing yet.
Component: hms
Type: Feature