summaryrefslogtreecommitdiff
path: root/netconf-service/README.txt
diff options
context:
space:
mode:
authorAdam Ierymenko <adam.ierymenko@gmail.com>2013-11-08 09:34:17 -0500
committerAdam Ierymenko <adam.ierymenko@gmail.com>2013-11-08 09:34:17 -0500
commitc93de67d793c859aac6a83f21c694796d10bed26 (patch)
treed6b9faee95c35911efa2bd8768a373e45bee6eb4 /netconf-service/README.txt
parent5179dfafbeeaf4e678d42dd9bd9902e11a29bcac (diff)
downloadinfinitytier-c93de67d793c859aac6a83f21c694796d10bed26.tar.gz
infinitytier-c93de67d793c859aac6a83f21c694796d10bed26.zip
Add netconf-service readme.
Diffstat (limited to 'netconf-service/README.txt')
-rw-r--r--netconf-service/README.txt16
1 files changed, 16 insertions, 0 deletions
diff --git a/netconf-service/README.txt b/netconf-service/README.txt
new file mode 100644
index 00000000..6ec7eeba
--- /dev/null
+++ b/netconf-service/README.txt
@@ -0,0 +1,16 @@
+This is the netconf service, which can be built and run by placing it in the
+services.d subfolder of the ZeroTier One home directory.
+
+Users probably won't be interested in this. It's for running a "netconf
+master," which handles certificate issuing, static IP assignment, and other
+things for a network. The ZeroTier address of the netconf master forms the
+first 40 bits of a hexadecimal network ID, permitting the master to be
+located and queried.
+
+Masters currently don't support multi-homing, but they can easily be made
+fault tolerant via fail-over. If the master node goes down, it can be
+started elsewhere with the same ZT1 identity. (The underlying database would
+also have to be fault tolerant.)
+
+For this to work it requires a MySQL backend with a properly structured
+database.