Best Practices for naming Devices in a Topology
Are there any Best Practices for naming Devices in a Topology? As the Topology is the connection between the Device Projects and the Automation Projects, I would imagine there are some naming conventions that result in confusion (device1, device2, device3) or that obscure opportunities for portability (embedding the IP address in the device name). What works, what doesn't, ITRW? Related question: when adding a Session to a device in the Topology Editor, are there any Best Practices in naming the profile? It defaults to the Session Type. Any reason to change it?
Usually what we do is name devices by their *function* in the test case. For example we did residential gateway testing at AT&T we named the device "RG". For topologies that required two devices of the same type would label them something like: RG_source RG_destination When doing a test from one RG to the other. I think these names are better than "RG_1" and "RG_2". For naming the session associated with the device. I recommend using the session type as the name (all lower case) > telnet > ssh > web > ... etc
Well, in general, more descriptive is better, without being way too verbose. I wouldn't say there are any hard-and-fast rules for naming, but something that includes session type and something usage-specific . Examples: 'server#sshPerformanceTesting' 'sourceRouter#telnet' I like to make sure my names are "variable-friendly", using underscores, dashes, or other characters that can be used as delimiters when replacing portions of the name with variables.
16 People are following this question.
