| Job | Status | Reported By | Description | Modified Date |
|---|---|---|---|---|
| HMS-9 | Open | C. Thomas Tyler | The hms start can report successful service start when it did not. | 5 years ago |
| HMS-8 | Open | C. Thomas Tyler | Support HMS automated failover using 'p4 failover' command. Original title was: Support HMS autom...ated failover of 'standby' (journalcopy) replica. HMS supports failover of a forwarding replica, but not a forwarding 'standby' replica that uses journalcopy. The mkrep.sh script knows the details of creating a replica designated as 'ha' (High Availability) or 'ham' (metadata-only variant of 'ha'). Replicas with these tags are sutiable for use with the 'p4 failover' command, which implies many thing: * The Services in server spec is 'standby' or 'forwarding-standby' * The rpl.journalcopy.location=1 is set. * They are creatd with P4D >= 2018.2, and have the ReplicatinFrom field in the server spec set. * Their journalPrefix matches the master. This will need to support a preflight of failover, using 'p4 failover' without the '--yes' flag. We will also want to drop support for other forms of failover, to ensure best results. It is TBD whether that will be done as part of implementing this job. « | 4 years ago |
| HMS-7 | Closed | C. Thomas Tyler | Enable hms_ts_setup.sh to install on a dedicated hms host. | 5 years ago |
| HMS-6 | Closed | C. Thomas Tyler | hms_ts_setup.sh should not require OSUSER to be perforce. | 4 years ago |
| HMS-5 | Closed | C. Thomas Tyler | hms_ts_setup.sh should allow P4USER and OSUSER to be different. The actual issue is in the templa...te file, superuser.user.p4t, which users OSUER rather than ADMINUSER. « | 4 years ago |
| HMS-4 | Open | C. Thomas Tyler | hms_ts_setup.sh wrongly returns 0 exit code on failure. | 5 years ago |
| HMS-33 | Open | C. Thomas Tyler | Added timeout to handle ssh calls blocked by firewall, etc. | 2 years ago |
| HMS-32 | Open | C. Thomas Tyler | Add non-default of brokers with non-default configs. | 2 years ago |
| HMS-31 | Open | C. Thomas Tyler | Refactor so all things HMS live under /p4/common/site/hms. | 2 years ago |
| HMS-30 | Open | roadkills_r_us | sdp_sync.sh: The '-H' runs on specified host but does crontab check on all hosts. | 2 years ago |
| HMS-3 | Open | C. Thomas Tyler | Enhance hms_ts_setup.sh to make and detect updates in /p4/common/config | 5 years ago |
| HMS-29 | Closed | C. Thomas Tyler | Add ParentView to generated stream specs for P4D 2020.2+. | 2 years ago |
| HMS-28 | Closed | C. Thomas Tyler | In DLP, bypass for super users other than perforce was broken. | 3 years ago |
| HMS-27 | Open | roadkills_r_us | /p4/hms/tmp/ has lots of rcmd.* files. After 400+ days or running HMS, we have thousands of rcmd.* f...iles in /p4/hms/tmp/ . There should be either a cron job to clean these up, or it could be handled as an additional rcmd (insert ironic emoji). If these need to be kept for debugging, I'd think a week's or at most a month's worth of files would suffice. In the interim, I'm implementing a cron job on each HMS-managed host, using find to select files older than N days and removing them. « | 2 years ago |
| HMS-26 | Closed | C. Thomas Tyler | Clean SDP layering separation and move to /p4/common/site. This change is confluent with the SDP... direction of moving files not part of the stock SDP into /p4/common/site. This change entails: * Move of hms files in /p4/common/bin to /p4/common/site/bin. * Move of hms files in /p4/common/lib to /p4/common/site/lib. * Elimination of dependency on SDP files in /p4/common/lib, so that HMS can be deployed on a wider range of SDP versions, and not be dependent on SDP bash library files. « | 2 years ago |
| HMS-25 | Open | C. Thomas Tyler | Added required ParentView field value to stream specs. Requires changes to *.stream.p4t files and... also the hms_ts_setup.sh. « | 3 years ago |
| HMS-24 | Open | C. Thomas Tyler | Handle management of /p4/ssl with Tight Ship, fixing perms post-sync. Also add trigger to push-sy...nc & fix perms immediately after submit. « | 3 years ago |
| HMS-23 | Open | C. Thomas Tyler | Codify changes to support versioning of P4DTG common/dtg folder. Currently, we avoid versioning t...he /p4/common/dtg folder in the SDP structure where P4DTG runs, because P4DTG puts a mix of static configuration files (which should be versioned) and dynamic files including certain XML and log files (which should not be versioned) in the same directory. To version that folder would require a versioned P4IGNORE file that appears as /p4/common/dtg/.p4ignore. Then the default SDP_STATUS_DIRS setting in sdp_hosts.cfg could be expanded to include the /p4/common/dtg folder. See also: SDP-700 and P4DTG job job108521 (Perforce-internal). « | 3 years ago |
| HMS-22 | Closed | C. Thomas Tyler | sdp_sync.sh no longer generates output with '-si'. | 3 years ago |
| HMS-21 | Open | Tim Addenbrooke | Enable hms_ts_setup.sh to deploy a greenfiled HMS instance. | 3 years ago |
| HMS-20 | Punted | C. Thomas Tyler | For DLP, the 'p4 opened -a' command leaks data. | 3 years ago |
| HMS-2 | Closed | C. Thomas Tyler | Added Data Leakage Protection (DLP) as optional component to HMS. This provides support the "mult...i-vendor hosted P4D" use case, where different users on a server aren't supposed to see anything about what anyone else is up to on the same server, or who is even there. « | 6 years ago |
| HMS-19 | Closed | roadkills_r_us | Mistake. This should have been filed as an SDP bug. | 2 years ago |
| HMS-18 | Open | roadkills_r_us | sdp_sync.sh email: Add hostname being accessed at top of output for that host Not a big deal, but... it would be nice to have the hostname at the top of its output section; as is, you have to read down to understand what you're looking at. « | 2 years ago |
| HMS-17 | Open | roadkills_r_us | sdp_sync.sh email says "Warning" when no files are updated on a host If no files are updated on a... host, sdp_synch.sh reports "warning: File(s) up-to-date." before exiting, Shouldn't that be "info" rather than "warning"? « | 2 years ago |
| HMS-16 | Open | roadkills_r_us | Adding host-specific sdp_status-dirs.<host>.cfg forces all subsequent hosts in the list to nee...d them. « | 4 years ago |
| HMS-15 | Closed | allenb | sdp_sync.sh to pass -n flag to p4 sync In dry-run mode - it would be useful to pass -n to the p4 s...ync commands so I can see the files that would get updated by p4 sync. UPDATE: This is implemented as '-N' flag, separtate from '-n'. The '-n' shows the 'ssh' commands that would be used to access other hosts, but does not get as for as getting to the other hosts. The '-N' goes to the remote hosts, and does a 'p4 sync -n' on the hosts (but not a live 'p4 sync'). « | 4 years ago |
| HMS-14 | Closed | wolfmann | Implement 'hms update' and 'hms upgrade' features. | 4 years ago |
| HMS-13 | Closed | allenb | Can we have a Version file in this package similar to SDP? Thanks | 2 years ago |
| HMS-12 | Closed | C. Thomas Tyler | Promote "Tight Ship" terminology, add to output when compliant. | 5 years ago |
| HMS-11 | Open | wolfmann | Simplify update of license files to all servers with HMS. Per email: --- It would actually be v...ery cool to be able to drop license files into a secure folder, that would allow HMS to act like a license server... not in a P4AUTH way, but the server would be automatically renewed based upon dropping a file in there. --- Commonly with SDP deployments, licenses are versioned in /p4/common/config/licenses, and that folder is sync'd to all hosts with sdp_sync.sh. That 'licenses' folder hasn't been documented and enshrined as a formal SDP standard yet, but that can be done as part of implementing this. « | 5 years ago |
| HMS-10 | Suspended | C. Thomas Tyler | Deprecate sdp_hosts.cfg in favor of HelixTopology.cfg. The sdp_sync.sh ("tight ship enforcer" scr...ipt) and the global_replica_status.sh script use the sdp_hosts.cfg file, but should be retooled to use the HelixTopology.cfg file instead of the sdp_hosts.cfg. Some concerns with doing this: * The sdp_hosts.cfg file is simpler and less intimidating, and has a narrow scope. Despite some overlap, it may be worth keeping it as a separate file from the more comprehensive but possibly daunting HelixTopology.cfg. * Presently sdp_hosts.cfg is a pre-requisite to running hms_ts_setup.sh. * We need to decide whether to make it backward-compatible, e.g. support both sdp_hosts.cfg and HelixTopology.cfg, deferring to HelixTopology.cfg if it exists. That would make it more complex and potentially confusing, but could simplify the upgrade process for customers using sdp_hosts.cfg but not doing the full HMS thing yet. « | 5 years ago |
| HMS-1 | Closed | albert | hms_ts_setup.sh isn't picking up "."/dot depots, e.g. "//.swarm" From the log: .... Loading... depot spec file dot_swarm.depot.p4s. hms_ts_setup.sh: FATAL: Failed to load depot spec file dot_swarm.depot.p4s with contents: Depot: .swarm After commenting out lines to ignore the above issue, user hits this: .... Starting new HMS instance of p4d. Setting P4JOURNAL in the database to /p4/hms/logs/journal. /p4/hms/bin/p4d_hms -r /p4/hms/root -cset P4JOURNAL=/p4/hms/logs/journal Failed to rotate journal. Aborting p4d server start. hms_ts_setup.sh: FATAL: Failed to start new HMS instance. .... « | 4 years ago |