# 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-397

Status:	open

Project:	perforce-software-sdp

Severity:	C

ReportedBy:	tom_tyler

ReportedDate:	2019/06/01 06:43:38

ModifiedBy:	tom_tyler

ModifiedDate:	2019/06/01 06:43:38

OwnedBy:	tom_tyler

Description:
	Support SDP hosts without p4d, p4p/p4broker or p4dtg only.
	
	The SDP mkdirs.cfg describes SERVER_TYPE values of p4broker
	and p4proxy, but they need to fully implemented.
	
	Some things to address:
	
	* The default shell environment mechansim (sourcing p4_vars)
	gives ugly errors if P4ROOT doesn't exist -- but P4ROOT wouldn't
	be expected to exist on a host running only p4broker or p4p.
	* mkdirs.sh can't resist putting p4d in /p4/N/bin when setting
	up a new instance, but shouldn't based on the SERVER_TYPE.
	* upgrade.sh might have a cow if there is no P4ROOT.
	host with only p4p and/or p4broker, it should do the right
	thing and upgrade them. Something like: service stop, replace
	exes, do symlink adjustment, and service start. (See  SDP-278;
	this may already be done. Double check).

DevNotes:
	This affects multiple components:  core-unix, setup, and env.

Component:	core-unix

Type:	Feature