# 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-217 Status: punted Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2017/05/10 12:22:34 ModifiedBy: tom_tyler ModifiedDate: 2020/06/01 06:36:30 OwnedBy: tom_tyler Description: Enhance SDP init scripts to support RHEL/CentOS 6/7 and Ubuntu 14/16. The current init script generation logic generates scripts with a comment block compatible with the chkconfig utility on CentOS 6 and 7. It looks something like this: # Init script for Helix Server. # # chkconfig: - 90 30 # description: Start Helix Server instance REPL_SDP_INSTANCE. We might as well complete the job and do the 'chkconfig' stuff on RHEL/CentOS 6. On RHEL/CentOS 7, which uses systemd, we have sample systemd wrappers to those init scripts, but don't do everything needed to activate them. Might as well complete the job, and simplify the doc. On Unbutu 14 and 16, research is needed. systemd apears to work with Ubuntu 16. For Ubuntu 14, I think we need a comment block compatible with update-rc.d, as documented here: https://wiki.debian.org/LSBInitScripts I think it will look like this: ### BEGIN INIT INFO # Provides: p4d_1_init # Required-Start: $syslog # Required-Stop: $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: p4d_1 # Description: Enable Helix SDP Instance 1 P4D Server on boot. ### END INIT INFO We should make sure suppor the popular/supported OS's. No need to support Ubuntu 12 (which just went EOS recently) nor RHEL/CentOS 5. DevNotes: Punted as obsolete due to systemd being the prevalent method now. Component: init Type: Feature