<h1 id="what-is-the-server-deployment-package-sdp-">What is the Server Deployment Package (SDP)?</h1> <h2 id="supported-open-source-software">Supported Open Source Software</h2> <p><em>When deployed or certified by Perforce Consulting</em>, the core functionality of the SDP is officially supported by Perforce Support, except for files in the <code>Unsupported</code> directory tree.</p> <p>The <code>Unsupported</code> folder included with the SDP is community supported, but officially supported by Perforce Support. (Unsupported files were in various folders prior to the 2020.1 release.)</p> <p>The SDP is open source software (see the <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/LICENSE">LICENSE</a>), and accepts contributions (pending code review) from the user community.</p> <p>Please see the <code>doc</code> directory for:</p> <ul> <li>SDP_GUIDE.Unix <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Unix.pdf">PDF version</a>, <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Unix.html">HTML version</a>, or <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Unix.adoc">ASCIIDoctor version</a></li> <li>SDP_GUIDE.Windows <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Windows.pdf">PDF version</a>, <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Windows.html">HTML version</a>, or <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Windows.adoc">ASCIIDoctor version</a></li> <li>SDP_Failover_Guide <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Failover_Guide.pdf">PDF version</a>, <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Failover_Guide.html">HTML version</a>, or <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Failover_Guide.adoc">ASCIIDoctor version</a></li> </ul> <h2 id="high-availability-ha-">High Availability (HA)</h2> <p>The SDP supports a variety of methods for achieving high availability that benefit simple, single-server environments and sophisticated global enterprise environments, and all in between. Standardized and documented recovery procedures, offline databases, and optional replication (made easier with the SDP) all make HA easier to achieve.</p> <p>There is more detailed discussions and references in the SDP Guides noted above.</p> <h2 id="disaster-recovery-dr-">Disaster Recovery (DR)</h2> <p>Just as with HA, the SDP makes it easier to implement robust, reliable DR strategies.</p> <p>There is more detailed discussions and references in the SDP Guides noted above.</p> <h2 id="fast-and-safe-upgrades">Fast and Safe Upgrades</h2> <p>The SDP makes upgrades of Helix server products fast and easy, regardless of the scale of your environment. By taking advantage of the offline database structure, the SDP enables upgrades with just a few minutes of downtime (enough to do a journal rotation).</p> <h2 id="production-focus">Production Focus</h2> <p>The p4d executable, without any configuration, is optimized for evaluation and demonstration purposes. While it has many features that can make it reliable and robust, many of those features must be configured. The SDP is intended to be used for production environments or more realistic Proof of Concept installations.</p> <p>See the <a href="https://swarm.workshop.perforce.com/projects/perforce_software-helix-installer">Helix Installer</a> which makes quick work of installing the SDP for PoC evaluation with a production-like setup, complete with the Sample Depot training data set.</p> <h2 id="best-practice-configurables">Best Practice Configurables</h2> <p>The SDP also maintains, on an ongoing basis, a set of best-practices configuration settings (e.g. 'configurables' and environment settings) suited to production environments, which often differ from p4d defaults.</p> <h2 id="optimal-performance-data-safety-and-simplified-backup">Optimal Performance, Data Safety, and Simplified Backup</h2> <p>The SDP provides a standard structure for operating Perforce that is optimized for performance, scalability, and ease of backup. The SDP Guide includes documentation that promotes volume layout and storage architecture best practices.</p> <p>To simplify backup, all digital assets are in a single directory. Live databases that cannot be backed up live in another, and active log files in another. For any scale environment, this makes it easy to back up the server's critical data. For larger scale environments, these directories become storage volume mount points, with the layout promoting best performance and data safety.</p> <h2 id="sophistication-simplified">Sophistication Simplified</h2> <p>In addition to the basics, the SDP provides structure, standards, guidance, and automation that greatly simplify deployment and management of sophisticated Helix global topologies. For example, the SDP includes tools that greatly simplify complex tasks such as creating new replicas, backing up edge servers without down time, etc.</p> <h2 id="multi-instance-management">Multi-Instance Management</h2> <p>The SDP supports operation of multiple instances of Helix on a machine, allowing each instance to have differing configuration, e.g. different:</p> <ul> <li>versions of software components (p4d, p4broker, etc.)</li> <li>case sensitivity setting (sensitive/insensitive)</li> <li>Unicode setting (enabled/disabled)</li> </ul> <h2 id="shell-environment-management">Shell Environment Management</h2> <p>The SDP provides standard mechanism for defining a controlled shell environment. This benefits p4d and other Perforce software products directly, and also provides good examples of controlling the environment for supporting automation.</p> <h2 id="perforce-automation-standards">Perforce Automation Standards</h2> <p>The SDP defines a standard for installing and configuring derived APIs. For example, Python is built with P4Python in /p4/common/python, and Perl with P4Perl in /p4/common/perl.</p> <h2 id="stock-vs-custom-sdp">Stock vs. Custom SDP</h2> <p>Many Perforce customers use the SDP as-is. Others benefit by incorporating concepts and ideas from the SDP into their own environments, e.g. for development of custom policy enforcement triggers, systems integrations, promoting or enforcing local naming conventions, etc.</p> <h2 id="helix-management-system">Helix Management System</h2> <p>The <a href="https://swarm.workshop.perforce.com/projects/perforce_software-hms">Helix Management System (HMS)</a> is a separate, community-supported product that builds on the SDP. This is likely to be of interest at installations with sophisticated global topologies and/or a fleet of SDP instances to manage.</p> <h1 id="bugs-enhancements-and-future-plans">Bugs, Enhancements, and Future Plans</h1> <p>Perforce Jobs are used to file bugs and request enhancements to the SDP. The list of jobs (other than closed ones) can be viewed <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/jobs" title="SDP Open Jobs">here</a>.</p> <p>You can see all jobs (including closed ones if desired) from the command line interface. Connect to The Workshop and run the <code>p4 jobs</code> command, something like this:</p> <pre><code>p4 <span class="hljs-built_in">jobs</span> <span class="hljs-_">-l</span> <span class="hljs-_">-e</span> <span class="hljs-string">"Project=perforce-software-sdp ^Status=closed"</span> </code></pre><p>While there is currently no formal roadmap for the SDP, it is actively maintained and continues to evolve alongside P4D and other Helix Core components it manages. Jobs are occasionally reviewed and addressed as time allows for consultants and contributors, sometimes driven by customer-funded consulting projects.</p> <h1 id="contributing">Contributing</h1> <p>Contributions to the SDP are most welcome! Note that contributing requires a basic user knowledge of working with Perforce.</p> <h2 id="contributing-by-shelving-small-changes-">Contributing by Shelving (Small Changes)</h2> <p>For contributing small changes, contribute by shelving changelists to the 'dev' branch your workspace.</p> <p>All registered Workshop users have <strong>open</strong> access (but not <strong>write</strong>) to the SDP dev branch. This allows shelving (but not submitting) updates to the SDP dev branch path:</p> <pre><code><span class="hljs-regexp">//gu</span>est<span class="hljs-regexp">/perforce_software/</span>sdp<span class="hljs-regexp">/dev/</span>... </code></pre><p>To contribute by shelving, create a workspace that maps that path, named something like '<em>your_user</em>.<em>your_hostname</em>.sdp'. Make your changes in that workspace, provide a good changelist description, and include a <code>#review</code> tag in your changelist description.</p> <p>When you are ready, shelve the changelist. Perforce Consultants will review the change, and either incorporate it or provide feedback. Be sure to provide a detailed change description, and don't forget include the <code>#review</code> tag in your changelist description to initiate a Swarm pre-commit code review.</p> <h2 id="contributing-by-branching-bigger-changes-">Contributing by Branching (Bigger Changes)</h2> <p>Optionally, you may also branch the SDP dev branch, or some subset of it, into your own guest area. Creating a branch spec is recommended for this purpose, e.g. with a branch spec like this:</p> <pre><code><span class="hljs-attribute">Branch</span>: your_name-sdp <span class="http"><span class="hljs-attribute">Owner</span>: your_name <span class="awk">Description: SDP Updates by your_name. Options: unlocked View: <span class="hljs-regexp">//gu</span>est<span class="hljs-regexp">/perforce_software/</span>sdp<span class="hljs-regexp">/dev/</span>.. <span class="hljs-regexp">//gu</span>est<span class="hljs-regexp">/your_name/</span>sdp<span class="hljs-regexp">/dev/</span>...</span></span> </code></pre><p>If you branch a subset, maintain the full path structure (as in the example above), so you can easily expand the scope of what you branched initially at some later date.</p> <p>Edit, test and submit changes in your branch. Keep your code up to date with other changes by merging down from the shared dev branch to your dev branch, e.g. by doing:</p> <pre><code>p4 merge -<span class="hljs-selector-tag">b</span> your_name-sdp </code></pre><p>... followed by the usual resolve and submit.</p> <p>When you'e ready to copy your versions up to our dev branch, do like so:</p> <pre><code>p4 change p4 <span class="hljs-keyword">copy</span><span class="bash"> -c YourCL -r -b your_name-sdp</span> </code></pre><p>Be sure that your changelist has a clear and accurate description, and that the description contains a <code>#review</code> tag on a line by itself. That will trigger a code review process when you shelve the change, like so:</p> <pre><code>p4 <span class="hljs-built_in">shelve</span> -c YourCL </code></pre><p>Perforce Consultants will review the change, and either incorporate it or provide feedback. Be sure to provide a detailed change description, and don't forget include the <code>#review</code> tag in your changelist description to initiate a Swarm pre-commit code review.</p> <h2 id="guidelines-for-sdp-contributors">Guidelines for SDP Contributors</h2> <ul> <li>Communicate! Use Swarm or email! Let folks know what you're planning before you work too hard on something that might already be underway.</li> <li>File a job (Project=<strong>perforce-software-sdp</strong>) first. That's not required, but increases the transparency of what you're doing, and helps promote it.</li> <li>We prefer changes that are generic, and have a wide appeal.</li> <li>The core of the SDP, the scripts that do offline checkpoints for p4d, prioritize Perforce best practices over scripting magic. Don't get too fancy! :)</li> </ul> <h1 id="versioning-the-sdp-locally">Versioning the SDP Locally</h1> <p>You may want to version the SDP locally. See the SDP Guide for basic versioning instructions.</p> <p>Optionally, sophisticated enterprise installations may want to use the "Tight Ship" style of management, to be in line with the "Version Everything" mindset. For more info, see the <a href="https://swarm.workshop.perforce.com/projects/perforce_software-hms">Helix Management System (HMS)</a>.</p> <h1 id="upgrading-older-existing-sdp-installations">Upgrading Older Existing SDP Installations</h1> <p>See the <a href="https://swarm.workshop.perforce.com/files/guest/perforce_software/sdp/r20.1/doc/SDP_Upgrade_Guide.Unix.html">SDP_Upgrade_Guide.Unix</a></p> <h1 id="the-windows-sdp">The Windows SDP</h1> <p>There are two flavors of the SDP, Unix and Windows. Both are available from the <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/downloads">SDP downloads folder</a>.</p> <h1 id="sdp-code-quality">SDP Code Quality</h1> <p>An automated regression test suite and pre-commit code review processes help ensure code quality. This is supplemented by manual testing in the Battle School training lab environment. Contact <a href="mailto:email@example.com">Perforce Consulting</a> for more information.</p> <p>See more details about the test suite in the <a href="https://swarm.workshop.perforce.com/projects/perforce-software-sdp/files/main/test/README.md">Test Suite README file</a>.</p>
Updated README for coming r21.2 release.
Enhanced product description to emphazise key SDP benefits, better
describing the value of the Offline DB.
* Added Documentation References section, with less clutter and easier links to PDF/HTML versions of key docs, including the upgrade guide.
* Enhanced "Sophistication Simplified" section.
* Simplified Support status text.
* General grammer corrections.
* Removed a broken link.
* Simpflified Contribing sections.
* Enhanced formatting/TOC levels, moved several sections under new "Features and Benefits" section.
|#14||27444||tom_tyler||Fixed issue with broken doc links.|
Replaced notes in README.md re: upgrading SDP with ref to new SDP Upgrade Guide doc.
The doc URL references not-yet-existing SDP r20.1 branch.
This is Tom's change:
Introduced new 'Unsupported' directory to clarify that some files
in the SDP are not officially supported. These files are samples for
illustration, to provide examples, or are deprecated but not yet
ready for removal from the package.
The Maintenance and many SDP triggers have been moved under here,
along with other SDP scripts and triggers.
Added comments to p4_vars indicating that it should not be edited
directly. Added reference to an optional site_global_vars file that,
if it exists, will be sourced to provide global user settings
without needing to edit p4_vars.
As an exception to the refactoring, the totalusers.py Maintenance
script will be moved to indicate that it is supported.
Removed settings to support long-sunset P4Web from supported structure.
Structure under new .../Unsupported folder is:
Samples/bin Sample scripts.
Samples/triggers Sample trigger scripts.
Samples/triggers/tests Sample trigger script tests.
Samples/broker Sample broker filter scripts.
Deprecated/triggers Deprecated triggers.
To Do in a subsequent change: Make corresponding doc changes.
Regenerated README.html from README.md using
The generated README.html is now much smaller than the previous
one, which was created using the "Export as HTML" function of the
MWeb Markdown editor utility.
Clarified that Maintenance folder scripts are samples and are
NOT officially supported.
Updated references to HMS now that it has been split back out
into a separate product.
|#9||25155||robert_cowham||Refer to test/README.md|
Prepared patch SDP/MultiArch/2018.1/23583.p2
* In README, moved 'Supported Open Source Software' section
to the top of the page, to make Support position more visible.
* Copyright updated to 2019.
* Cleanup of excess script recreate_db_sync_replica.sh
* Re-removal of previously deleted script recreate_db_checkpoint.sh,
and corresponding removal from test suite.
* This patch tarball will also contain some Docker test suite updates
already staged in main.
By-passing review to trigger an automated test.
Fixed an obvious doc typo in README files. Bypassing code
|#6||23353||tom_tyler||Fixed typo/grammatical error.|
Overhauled SDP README page to better convey its value, and
much more strongly promote the SDP.
This also documents the the nature of offical Perforce Support
for the SDP, and the limitations of that Support to core SDP
|#4||11535||russell_jackson||Updated dev from main.|
|#3||11463||russell_jackson||Updated dev to prepare for Summit agreed changes.|
|#2||11038||robert_cowham||Catchup from Main|
Merge down from main. No actual merging was needed (just
|#1||10644||tom_tyler||Added README.html generated from README.md.|