This documentation gives rules for the naming convention of interconnected devices involved in a control system, in particular the DNS name of servers/cpu/console and networked instrumentation.
...
The format is the following
| prefix(2digit) | zonefacility/group/experiment | funtionality/family/type | sequential(3digit) |
|---|---|---|---|
...
| Prefix | Description | |
|---|---|---|
| vl | Virtual Linux machine/server/cpu | |
| pl | Physical Linux machine/server/cpu | |
| vw | Virtual Windows | |
| pw | Physical Windows | |
| sw | switch | |
| il | ilo | |
| mv | motor controller | |
| cc | camera | |
| sc | serial converter (i.e moxa) | |
| gd | generic device (termother, sensors) | |
| ps | power supply | |
| bd | Beam instrumentation | |
| fd | Fluid device controllers | |
| rd | RF device | |
| vd | Vacuum device | |
| qd | Cryogenic device | |
| un | undulator device | |
| sd | Safety device, Radioprotection, Access System Convetional sagety | ..... |
...
| ns | storage device (nas) |
facility/group/experiment
This field should give indication of the logic location/group/experiment where the device is located or to what group/experiment it belongs. Note that networked elements may change the physical position so specify an exact position/location must be carefully evaluated.
Examples
sparc, btf, tex, dcs, dafne... can be good for devices in the control of the facilities.dafne,flame
Funtionality/family/type
This field should give additional information on the object functionality/family/type. In bold functionality/family/type already used.
...