# 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 given job 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/Doc/Feature/Problem]. Required.
#
# Bug: is a problem that is fairly well understood,
# e.g. one for which there is a reproduction or clear
# articulation of the problem.
#
# Doc: A Documentation fix.
#
# Feature: An enhancement request, perhaps adding
# a new product features, improving maintainability,
# essentially any new software improvement other than
# a fix to something broken.
#
# Problem: a 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-833
Status: open
Project: perforce-software-sdp
Severity: C
ReportedBy: rwillyoung
ReportedDate: 2022/10/03 14:51:42
ModifiedBy: tom_tyler
ModifiedDate: 2022/10/03 14:51:42
OwnedBy: tom_tyler
Description:
Add docs and/or script to remove an SDP instance.
This would be the opposite of mkdirs.sh. To do:
Files to cleanup (pseudocode):
rm -f /p4/common/config/.p4passwd.p4_<N>.*
rm -f /p4/common/config/p4_<N>.*
rm -rf /p4/<N>/bin
rm -rf /p4/<N>
rm -rf <HxDepots>/p4/<N>/
rf -rf <HxLogs>/p4/<N>/
rm -rf <HxMetadata*>/p4/<N>/
Some output from mkdirs helps show what to clean up:
Running: chmod 700 /hxmetadata/p4
Running: chmod 700 /hxdepots/p4
Running: chmod 700 /hxlogs/p4
Running: chmod -R 700 /hxmetadata/p4/sample
Running: chmod -R 700 /p4/common
Running: chmod -R 700 /hxlogs/p4/sample
Running: ln -s /p4/1/root/license /p4/sample/root/license
Running: chown perforce:perforce /p4/sample/root/license
Running: chmod 755 /p4/sample/bin/p4broker_sample_init
Running: chmod 755 /p4/sample/bin/p4d_sample_init
Running: chmod 600 /p4/common/config/.p4passwd.p4_sample.admin
Running: chmod 600 /p4/common/config/.p4passwd.p4_sample.service
Component: core-unix
Type: Feature