Naming Convention DNS Elements - PROPOSAL -

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.

This documentation follows Eupraxia-PM-QA-0020-NamingConvention.pdf and integrates pre-existent conventions with some simplification to be more suitable to be used as DNS

Format

The format is the following:

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.

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, 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:

Often an object is instead identified by its the commercial name: 

Often an object is instead identified by its functionality: 

Examples

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