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) | |||
|---|---|---|---|
| facility/group/experiment | funtionality/family/type | sequential(3digit) | |
use lower case, no underscore (use dash instead).
Prefix
The prefix is 2 digit is used to quickly determine the network element type. In bold prefixes already used.
| 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) |
| dc | digital converter |
| ac | analog converter |
| io | generic i/o device | os | oscilloscope
| 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) |
| dd | DAQ Device |
| da | DAC Device |
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 , cg (Control Group), eg ( Electronic Group : Selced)
Funtionality/family/type
This field should give additional information on the object functionality/family/type. In bold functionality/family/type already used.
This information is up to the owner, but should recall the functionality of the object.
Examples
Often a machine/docker/device has a particular functionality. Specify the functionality is the preferred extension that we use:
funtionality | Description |
|---|---|
| mem | Memory Cache generic (memcached/couchbase) |
| couch | Memory Cache (couchbase) |
| db | Generic Database |
| influx | InfluxDB |
| sql | Generic SQL |
| dbn | Generic no-SQL |
| dbs | Generic SQL |
| mysql | mysql/mariadb |
| mongo | MongoDB |
| grafana | grafana |
| bpm | Beam Position Monitor |
| ctr | Control (current in use in BTF) |
| mon | Monitoring, similar to grafana, but generic - (current in use) |
| dev | Devil - (current in use) |
| co | Console Control Room - (current in use) |
| pc | Personal Computer |
| rad | Device for Radio Protection |
| dom | Domain (domain started by the Xen hypervisor on boot) - (used but usable for Hypervisor or Containers host machines) |
Often an object is instead identified by its the commercial name:
family/type | Description |
|---|---|
| moxa | For moxa ethernet to serial converters |
| icpdas | For ADC/DAC converters |
| nuc | For CPUs used mainly for consoles |
| libera | For beam position monitor |
| ... | |
..... |
Often an object is instead identified by its functionality:
family/type | Description |
|---|---|
| moxa | For moxa ethernet to serial converters |
| icpdas | For ADC/DAC converters | nuc | For CPUs used mainly for consoles
| bpm | beam position monitor |
| cam | camera |
| temp | thermometer |
| ... | |
| ... | |
..... |
Examples
| Code Block | ||||
|---|---|---|---|---|
| ||||
vldantemem001 ## a good example of a memcached server on a virtual linux machine for the DanteControSystem
plsparcmem001 ## a good example of a memcached server on a physical linux machine serving sparc
bdsparcbpm001 ## a generic bpm in sparc
vwbtfhactr005 ## a virtual windows server in btf
pwfismelrad001 ## a physical windows machine of fismel for radio protection
|