Server Deployment Package Overview June 2017 v 3

  • Slides: 20
Download presentation
Server Deployment Package Overview June, 2017 v 3. 1 © Perforce Software Inc. All

Server Deployment Package Overview June, 2017 v 3. 1 © Perforce Software Inc. All Rights Reserved.

Helix Core VCS Server Deployment Package © Perforce Software Inc. All Rights Reserved. 2

Helix Core VCS Server Deployment Package © Perforce Software Inc. All Rights Reserved. 2

Agenda • Overview • Volume Layout Recommendations • SDP Structure • Common Paths •

Agenda • Overview • Volume Layout Recommendations • SDP Structure • Common Paths • Upgrades • Sample Best Practices © Perforce Software Inc. All Rights Reserved. 3

What the SDP Is: • Deployment of a Helix Core VCS server according to

What the SDP Is: • Deployment of a Helix Core VCS server according to best practices. • Open source software, available in The Workshop • A collection of basic, yet proven, Perforce administration utilities. • Supported by Perforce Support • We balance maintainability vs. functionality when making updates. © Perforce Software Inc. All Rights Reserved. 4

Volume Layout (1/2) Volume Name Contents & Backup Notes /hxmetadata 1 /hxmetadata 2 DO

Volume Layout (1/2) Volume Name Contents & Backup Notes /hxmetadata 1 /hxmetadata 2 DO NOT BACK UP! 1 contain live db. * files 2 contains offline_db files /hxdepots Versioned files, checkpoints, inactive journals, admin utilities and scripts. Backup this filesystem fully. Performance Considerations, Sample Storage Optimize for random I/O. Expect 10 x to 1000 x I/O demands vs. depot storage. RAID 1+0 on XFS, 15 K RPM drives or solid state storage. More sequential I/O. RAID 5/6 on XFS. Growable! SAN/NAS. Disclaimer: Generalizations here reflect the nature of the Perforce application and typical usage. Your mileage may vary. © Perforce Software Inc. All Rights Reserved. 5

Volume Layout (2/2) Volume Name Contents & Backup Notes / Backup per local policy.

Volume Layout (2/2) Volume Name Contents & Backup Notes / Backup per local policy. Contains the /p 4 with symlinks to volumes. /hxlogs Contains active journal and server log. Backup optional; exclude active journal*. Performance Considerations, Sample Storage High performance needs. RAID 1+0 on XFS, DAS w/15 K drives. © Perforce Software Inc. All Rights Reserved. 6

SDP Structure Goals • Apply Volume Layout to optimize for performance and reduce risk

SDP Structure Goals • Apply Volume Layout to optimize for performance and reduce risk of data loss • Simplify Backup: Only one volume (/hxdepots) to back up. • Provide Sys. Admin/IT view of Physical Layout • Provide App Admin with app-centric view • Simplify Failover Automation • Simplify Upgrades © Perforce Software Inc. All Rights Reserved. 7

Physical Layout /hxdepots/p 4/1/checkpoints /hxdepots/p 4/1/depots /hxdepots/p 4/1/bin /hxdepots/p 4/1/etc /hxdepots/p 4/common/bin /hxmetadata 1/p

Physical Layout /hxdepots/p 4/1/checkpoints /hxdepots/p 4/1/depots /hxdepots/p 4/1/bin /hxdepots/p 4/1/etc /hxdepots/p 4/common/bin /hxmetadata 1/p 4/1/root /hxmetadata 2/p 4/1/offline_db /hxmetadata 1 /hxmetadata 2 /hxlogs/p 4/1/hxlogs/p 4/1/tmp /OS /p 4 © Perforce Software Inc. All Rights Reserved. 8

Logical View /p 4/1/ /hxdepots/p 4/1/checkpoints /hxdepots/p 4/1/depots /hxdepots/p 4/1/bin /hxdepots/p 4/1/etc root offline_db

Logical View /p 4/1/ /hxdepots/p 4/1/checkpoints /hxdepots/p 4/1/depots /hxdepots/p 4/1/bin /hxdepots/p 4/1/etc root offline_db logs tmp /p 4/common /hxdepots/p 4/common /hxmetadata 1/p 4/1/root /hxmetadata 1/p 4/1/offline_db /hxlogs/p 4/1/hxlogs/p 4/1/tmp © Perforce Software Inc. All Rights Reserved. 9

Common Paths (UNIX/Linux/Mac Server) P 4 ROOT /p 4/1/root/license P 4 LOG /p 4/1/logs/log

Common Paths (UNIX/Linux/Mac Server) P 4 ROOT /p 4/1/root/license P 4 LOG /p 4/1/logs/log /p 4/1/logs/checkpoint. log /p 4/1/logs/verify. log /p 4/1/logs/p 4 audit. log P 4 JOURNAL /p 4/1/logs/journal Scripts /p 4/common/bin, /p 4/common/bin/triggers Depots /p 4/1/depots/<depot> © Perforce Software Inc. All Rights Reserved. 10

Common Paths (Windows Server) P 4 ROOT M: p 41rootlicense P 4 LOG L:

Common Paths (Windows Server) P 4 ROOT M: p 41rootlicense P 4 LOG L: p 41logslog L: p 41logscheckpoint. log L: p 41logsverify. log P 4 JOURNAL L: p 41logsjournal Scripts S: p 4commonbin Depots S: p 41depots<depot> M: hxmetadata 1 L: hxlogs S: hxdepots © Perforce Software Inc. All Rights Reserved. 11

Common Commands Starting: /p 4/1/bin/p 4 d_1_init start /p 4/1/bin/p 4 d_1_init stop /p

Common Commands Starting: /p 4/1/bin/p 4 d_1_init start /p 4/1/bin/p 4 d_1_init stop /p 4/1/bin/p 4 d_1_init restart /p 4/1/bin/p 4 d_1_init status /etc/init. d/p 4 d_1_init is a symlink to /p 4/1/bin/p 4 d_1_init Init scripts run as ‘root’ or ‘perforce’ user. Processing always runs as ‘perforce’. Wrappers for systemd (*. service xml files) are available. © Perforce Software Inc. All Rights Reserved. 12

Upgrades (UNIX/Linux Server) Download exes (p 4/p 4 d/p 4 broker/p 4 p) to

Upgrades (UNIX/Linux Server) Download exes (p 4/p 4 d/p 4 broker/p 4 p) to /p 4/common/bin Run: /p 4/common/bin/p 4 master_run instance /p 4/common/bin/upgrade. sh © Perforce Software Inc. All Rights Reserved. 13

Upgrades (Windows) Server) Major Windows Upgrades: Find <depotdata_drive>: p 4 depots (Check the map

Upgrades (Windows) Server) Major Windows Upgrades: Find <depotdata_drive>: p 4 depots (Check the map field. It is hard coded to the depotdata drive location. ) Copy in new p 4 d. exe and p 4. exe into <depotdata_drive>: p 4commonbin cd <depotdata_drive>: p 4commonbin p 4 env. bat 1 upgrade. bat Minor/Patch Upgrades: net stop p 4_1 Copy new p 4 d. exe to <depotdata_drive>: p 41bin and copy to p 4 s. exe as well. net start p 4_1 © Perforce Software Inc. All Rights Reserved. 14

Upgrades Continued Other tools just shutdown and install new versions and replace links. P

Upgrades Continued Other tools just shutdown and install new versions and replace links. P 4 Broker as an example: Download new p 4 broker to /p 4/common/bin Then, do the following: Using 2012. 1. 442152 and instance 1 of a server as an example: cd /p 4/common/bin mv p 4 broker_2012. 1. 442152 unlink p 4 broker_1_bin unlink p 4 broker_2012. 1_bin ln –s p 4 broker_2012. 1. 442152 p 4 broker_2012. 1_bin ln -s p 4 broker_2012. 1_bin p 4 broker_1_bin /p 4/1/bin/p 4 broker_1_init restart © Perforce Software Inc. All Rights Reserved. 15

Default Protections and Groups: Goals • • • Disable implicit user creation • Customize

Default Protections and Groups: Goals • • • Disable implicit user creation • Customize per customer requirements. Proactively deny access to the ‘remote’ user. Provide sensible defaults for Max. Scan. Rows, Max. Results, and Max. Lock. Time. © Perforce Software Inc. All Rights Reserved. 16

Default Typemap • Use '+Fl' for pre-compressed filetypes. binary+Fl //. . jpg binary+Fl //.

Default Typemap • Use '+Fl' for pre-compressed filetypes. binary+Fl //. . jpg binary+Fl //. . tgz • Use '+l' for MSWord/Power. Point/Excel binary+l //. . xls • Use ’text+C' for large (e. g. generated) text files. text+C //. . gentxt © Perforce Software Inc. All Rights Reserved. 17

Applied Common Practices (1/2) • • Enable Monitoring. Create & populate ‘spec’ depot. Set

Applied Common Practices (1/2) • • Enable Monitoring. Create & populate ‘spec’ depot. Set appropriate logging verbosity. Set ‘security’ counter or use external authentication w/AD, LDAP. © Perforce Software Inc. All Rights Reserved. 18

Applied Common Practices (2/2) • • Daily checkpoint creation/verification. • • • Enable email

Applied Common Practices (2/2) • • Daily checkpoint creation/verification. • • • Enable email reviews (Swarm or stand-alone script) Archive file verification, replica status health checks, etc. HMS “Tight Ship” - Apply SCM to the SDP! And much more… © Perforce Software Inc. All Rights Reserved. 19

Questions? © Perforce Software Inc. All Rights Reserved. 20

Questions? © Perforce Software Inc. All Rights Reserved. 20