Server spec names provide info at a glance - where the server is physically located, whether it is filtered (as filtering disqualifies a replica from being an edge server target), and the type of replica (read-on, forwarding, or edge).
The naming convention intentionally does not account for all possible server specs available with p4d. The standard accounts only for the distilled list of server spec types supported by HMS, which are the most useful and commonly used ones.
The general form is:
HelixServer_ReplicaType_SiteTag
Where:
HelixServer is one of:
ReplicaType is one of:
SiteTag looks something like these samples:
The site tag needs to distinguish the data centers used by a single enterprise, and so generally short tag names are appropriate. Each site tag may be understood to be a true data center (Tier 1, Tier 4, etc.), a computer room, computer closet, or reserved space under a developer's desk.
For master server specs, we drop the geo tag and server type.
Sample server spec names:
Server Spec Naming Standard === Server spec names provide info at a glance - where the server is physically located, whether it is filtered (as filtering disqualifies a replica from being an edge server target), and the type of replica (read-on, forwarding, or edge). The naming convention intentionally does not account for all possible server specs available with p4d. The standard accounts only for the distilled list of server spec types supported by HMS, which are the most useful and commonly used ones. The general form is: *HelixServer*\_*ReplicaType*\_*SiteTag* Where: *HelixServer* is one of: * p4d * p4broker * p4p * p4web * p4gf * swarm *ReplicaType* is one of: * master - A Master/Commit server (not a replica at all) * fr - Forwarding Replica * ffr - Filtered Forwarding Replica (Note: Filtered replicas are not valid failover targets). * ro - Read Only replica * edge - Edge server *SiteTag* looks something like these samples: * syd - Sydney, Australia * bos - Boston, MA, USA * blr - Bangalore, India The site tag needs to distinguish the data centers used by a single enterprise, and so generally short tag names are appropriate. Each site tag may be understood to be a true data center (Tier 1, Tier 4, etc.), a computer room, computer closet, or reserved space under a developer's desk. For master server specs, we drop the geo tag and server type. Sample server spec names: * p4d_fr_chi * p4d_fr_pune * p4d_edge_blr
| # | Change | User | Description | Committed | |
|---|---|---|---|---|---|
| #3 | 27331 | C. Thomas Tyler |
Released SDP 2020.1.27325 (2021/01/29). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #2 | 26161 | C. Thomas Tyler |
Released SDP 2019.3.26159 (2019/11/06). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| #1 | 20767 | C. Thomas Tyler |
Released SDP 2016.2.20755 (2016/09/29). Copy Up using 'p4 copy -r -b perforce_software-sdp-dev'. |
||
| //guest/perforce_software/sdp/dev/doc/ServerSpecNamingStandard.md | |||||
| #1 | 20745 | C. Thomas Tyler |
Approving as is since it isn't changing core SDP functionality, and reviewing it all line by line will take some time. We can do that as we move forward with it. First addition of HMS v1.0 files. This change is a soft launch HMS for initial deployment and testing. Updates to HMS-related files are expected and will bypass pre-commit code review until stabilized. |
||