= SDP Windows to Linux Migration Guide Perforce Professional Services <consulting@perforce.com> :revnumber: v2023.1 :revdate: 2023-08-11 :doctype: book :icons: font :toc: :toclevels: 5 :sectnumlevels: 4 :xrefstyle: full // Attribute for ifdef usage :unix_doc: true == Preface This guide documents the process for migrating a Helix Core service from Windows to Linux. A common scenario is that an on-premisis (on-prem) Windows Helix Core service is being migrated to a cloud server, perhapns in AWS, Azure, or GCP. *Please Give Us Feedback* Perforce welcomes feedback from our users. Please send any suggestions for improving this document to consulting@perforce.com. :sectnums: == Overview A Migration has these elements: * Deploy New Linux Server machine * Upgrade P4D to 2019.2+ on Windows * Setup of a server spec for a Linux Replica on the Windows master. Each of these components is covered, in detail, in this guide. === Deploy New Linux Server machine ==== Select Operating System As of this writing, the best options are: * Ubuntu 20.04 (not 22.04 just yet) * RHEL/Rocky Linux 8 (not 9 just yet) * Amazon Linux 2 (not Amazon Linux 2023 just yet) Use the Helix Installer, do a Configured Install: su - mkdir -p /hxdepots/reset cd /hxdepots/reset curl -L -s -O https://swarm.workshop.perforce.com/download/guest/perforce_software/helix-installer/main/src/reset_sdp.sh chmod +x reset_sdp.sh ./reset_sdp.sh -C > settings.cfg In `settings.cfg` DNS_name_of_master_server= SiteTag= P4_PORT= Instance= Password= CaseSensitive= P4USER= ServerID= ServerType= P4BinRel= P4APIRel= ./reset_sdp.sh -no_sd -c settings.cfg 2>&1 | tee log.reset_sdp.txt su - perforce p4 set cd /p4/common/site [[ -d config ]] || mkdir config cd config Temporary Hack: vi /p4/common/site/config/p4_N.vars.local export P4MASTER_ID= export P4MASTERPORT= export P4PORT=$P4MASTERPORT vi /p4/common/config/.p4passwd.p4_mocap.admin p4login -v cd /p4/common/config vi SiteTags.cfg azwestus2: Azure data center mkrep.sh -t fs -s azwestus2 -r TestMachine [appendix] == Why Migrate? [appendix] == Why Migrate? EDITME - add content later.
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #19 | 30910 | C. Thomas Tyler | Updated rev{number,date} fields in adoc files for release. | ||
| #18 | 30829 | C. Thomas Tyler | Fixed typo. | ||
| #17 | 30383 | C. Thomas Tyler | Updated rev{number,date} fields in adoc files for release. | ||
| #16 | 30342 | C. Thomas Tyler |
Fixed bogus revs to the dev branch in released docs. #review-30343 @amo |
||
| #15 | 30207 | C. Thomas Tyler | Doc work WIP | ||
| #14 | 30206 | C. Thomas Tyler | WIP. | ||
| #13 | 30204 | C. Thomas Tyler | Doc work in progress ... | ||
| #12 | 30202 | C. Thomas Tyler | Doc work in progress ... | ||
| #11 | 30201 | C. Thomas Tyler | Doc work in progress ... | ||
| #10 | 30178 | C. Thomas Tyler | Doc in progress updates. | ||
| #9 | 30159 | C. Thomas Tyler | Documentation work in progress. | ||
| #8 | 30000 | C. Thomas Tyler |
Refined Release Notes and top-level README.md file in preparation for coming 2023.2 release. Adjusted Makefile in doc directory to also generate top-level README.html from top-level README.md file so that the HTML file is reliably updated in the SDP release process. Updated :revnumber: and :revdate: docs in AsciiDoc files to indicate that the are still current. Avoiding regen of ReleaseNotes.pdf binary file since that will need at least one more update before shipping SDP 2023.2. |
||
| #7 | 29953 | C. Thomas Tyler | Regeneratd docs. | ||
| #6 | 29937 | C. Thomas Tyler | Very rough draft still WIP. | ||
| #5 | 29934 | C. Thomas Tyler | WIP. | ||
| #4 | 29931 | C. Thomas Tyler | WIP - Windows to Linux guide; still very raw. | ||
| #3 | 29742 | C. Thomas Tyler | WIP. | ||
| #2 | 29741 | C. Thomas Tyler | WIP. | ||
| #1 | 29740 | C. Thomas Tyler | Bootstrapped empty doc. |