Merge pull request #2460 from weaveworks/issues/2427-detect-peerid-clashes
Detect and report peer name collisions
This commit is contained in:
commit
c79b6a8bd7
3 files changed
+38
-20
No files matched your search
@@ -49,12 +49,16 @@ When the router is launched on a host, it derives its peer name in order of pref
|
||||
|
||||
* From the command line, where the user is responsible for uniqueness and
|
||||
stability
|
||||
* From the BIOS product UUID, which is generally stable across
|
||||
restarts and unique across different physical hardware and certain
|
||||
cloned VMs
|
||||
* From the hypervisor UUID, which is generally stable across restarts
|
||||
and unique across VMs which do not provide access to a BIOS product
|
||||
UUID
|
||||
* From the concatenated result of any of the following:
|
||||
* The unique machine ID, which is generated either by [systemd](https://www.freedesktop.org/software/systemd/man/machine-id.html)
|
||||
or [D-Bus](https://dbus.freedesktop.org/doc/dbus-uuidgen.1.html) and is
|
||||
practically stable across restarts unless a user re-generates it.
|
||||
* The BIOS product UUID, which is generally stable across
|
||||
restarts and unique across different physical hardware and certain
|
||||
cloned VMs
|
||||
* The hypervisor UUID, which is generally stable across restarts
|
||||
and unique across VMs which do not provide access to a BIOS product
|
||||
UUID
|
||||
* From a random value, practically unique across different physical
|
||||
hardware and cloned VMs but not stable across restarts
|
||||
|
||||
|
||||
Reference in new issue
Block a user