# 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-407
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: tom_tyler
ReportedDate: 2019/07/09 06:24:21
ModifiedBy: tom_tyler
ModifiedDate: 2019/07/09 06:24:21
OwnedBy: tom_tyler
Description:
Enhance p4login to enable edge workspace migration.
To make migration of workspaces across edge servers possible,
the master/commit server must have a service user defined, and
that user must be logged in from each edge server, per:
https://community.perforce.com/s/article/5109
Update p4login so that it verifies that the master/commit server
has a service user, and that the user is logged in from/to
everywhere that it needs to be.
Ideally, this should be a change to the default behavior and not
require an extra flag. However, we also want to prevent adding
undue complexity to simpler environments that don't have a distrubted
topology with edge servers. So errors about the master not having a
service user should only be displayed if there is at least one edge
server in the topology, or perhaps only if there is a server spec
for the master/commit server.
Component: core-unix
Type: Feature