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 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:
|#2||26083||tom_tyler||Updated Server Spec Naming Standard.|
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.