Skip to content

Latest commit

 

History

History
49 lines (29 loc) · 1.43 KB

File metadata and controls

49 lines (29 loc) · 1.43 KB

Network Next


Datacenter and relay naming conventions

A full production system has thousands of datacenters and hundreds of relays.

Let's keep them all organized with a clear naming convention :)

1. Datacenter naming convention

Each datacenter must be named:

  • [seller].[cityname].[number]

For example:

  • google.losangeles.1
  • google.losangeles.2
  • amazon.virginia.5

In cases where there is only one datacenter in a city for that seller, the number may be omitted.

  • i3d.istanbul

When chosing a city name, prefer a cityname as already used for existing relays. This makes it easier to find other relays in the same city, which is a common operation when you are building your relay fleet.

Relay naming convention

Relays must include the datacenter name, followed by a,b,c etc. for each relay in that datacenter.

  • [datacenter].[a|b|c...]

For example:

  • google.losangeles.2.a
  • google.losangeles.2.b
  • google.losangeles.2.c
  • amazon.virginia.1.a
  • amazon.virginia.1.b
  • i3d.istanbul.a
  • i3d.istanbul.b

In cases where there is only one relay in a datacenter, it is OK to omit the a,b,c if you wish, and then the relay is named the same as the datacenter:

  • google.losangeles.1

Back to main documentation