SDP-198 | DOC: SDP Guide needs more detail on SDP-controlled replica setup. Following t...he SDP Guide to set up an SDP-controlled replica. On page 20 of 36 it explains how you seed the replica's database from checkpoint, then log in the service user to create a tickets file. The latter might need additional clarification. Recovering from checkpoint does not recreate the tickets file. This is created when the user runs 'p4 login', or you create the tickets file manually. The commands I found to work are not quite as written; I used: export P4TICKETS=/p4/1/.p4tickets p4 -u svc_replica1 -p svrmaster:1667 login Restoring the checkpoint, the 'p4d -jr' command, creates the database that your replica server instance will use. Before you start this server instance, your service user needs a valid ticket. You create the ticket using 'p4 login' and make sure it's in the P4TICKETS file - this is the 'export/p4 login' commands. Technically, these are independent events - you can create the database first then the ticket, or the other way around - but both need to be completed on the replica server before you attempt to start the server instance. Please consider updating the docs to provide this additional clarity! « | |
SDP-255 | Update SDP documentation to deal with SSL enabled servers. Cover things such... as: * Location of P4TRUST file * Order of steps to run through * Verification of scripts to ensure they are running correctly « | |
SDP-327 | DOC: must I create /hx*? The documentation is unclear on the purpose of the /hx...* directories. For example, can I omit the step of creating the '/hx* directories as it appears as though the SDP is tied up with /p4 instead. « | |
SDP-328 | DOC: mismatch between setup instructions and setup script Incorrect username in... the initial setup steps. Documentation states to use 'p4admin' as the OS user, but the default in the script configuration is perforce, so it won't work. « | |
SDP-329 | DOC: folder permissions When creating/mounting the /hx* volumes, do I need to a...djust ownership/permissions? If so, what should they be? It appears that they are adjusted by the mkdirs setup script - but what about hxdepots/sdp? « | |
SDP-330 | DOC: to where should we copy the tgz file? "Copy the SDP to the directory /hxde...pots/sdp" - need to be clear what is meant by 'SDP'. On a new install, one downloads the sdp.[platform.version].tgz, copies it to the /hxdepots directory and unpacks it. Incidentally, placing this tgz file in /hxdepots/sdp/ and unpacking adds an unnecessary layer - /hxdepots/sdp/sdp/... « | |
SDP-331 | DOC: lack of clarity on folder ownership. Make this [/hxdepots/sdp] directory w...ritable - to whom? And what are the full permissions? Does it need to be owned by 'p4admin' or (if you're using the script default) 'perforce'? Is this not handled by the mkdirs script alongside the other /hx directories? UPDATE: reopened - the SDP Guide still states "make the entire $SDP directory writable" but doesn't clarify ownership, nor if this is handled by the mkdirs script. « | |
SDP-332 | DOC: setting executable bit on p4 etc. Do I need to change the p4/p4d/p4p/p4bro...ker files to executable (chmod +x) once downloaded from the FTP site, or is this handled by the mkdirs script? (appears to be done by the script) « | |
SDP-333 | DOC: reorder the create user/group sequence on Linux. Appears to be simpler to... create group first, then add user to that group. Note that (for some OS) the latter will prompt for full name, phone number, etc. « | |
SDP-335 | DOC: no comment on ssl certificate generation. Suggestion: # switch to SSL... directory, edit 'config.txt' to add preferred configuration cd /p4/ssl vi config.txt # create the certificates /p4/common/bin/p4master_run 1 /p4/1/bin/p4d_1 -Gc [creates cert's in current directory - /p4/ssl] « | |
SDP-338 | DOC: server upgrades and checkpoint The upgrade instructions advise the runni...ng of 'upgrade.sh'. This does not initiate the process of creating a checkpoint (although some of the output suggests otherwise), but a subsequent section of the documentation appears to suggest 'live_checkpoint' is mandatory as part of the upgrade. The upgrade process needs clarifying, to confirm whether 'live_checkpoint' or similar action must be carried out as part of the server upgrade. « | |
SDP-339 | DOC: non-existent script referenced in docs The section "Recovering a replica... from a checkpoint" states that the reader should review "weekly_sync_replica.sh" for details on a particular process. There is a Windows "bat" file with the same name, but nothing for Linux. This reference needs to be corrected. [ REOPENED - the SDP Guide still contains this reference ] « | |
SDP-49 | SDP Guide: inconsistent user name used in setup instructions. Page 9 of the pdf..., step 1 says create user 'p4admin'. The rest of the guide that I've read, and the mkdirs.sh script, all refer to user 'perforce'. « | |
Add Job |