IRC-Hispano/ESNET paradigms (II)
Última Actualización:
4 de Agosto de 2.000 - Viernes
Message-ID: <38D0E7CE.B103FD96@argo.es>
Date: Thu, 16 Mar 2000 14:55:26 +0100
From: Jesus Cea Avion
Organization: Argo Redes y Servicios Telematicos, S.A. - http://www.argo.es/
To: coders@undernet.org
CC: Lista CODERS IRC-Hispano <coders@irc-hispano.org>,
Lista IRC Hispano <OPs@irc-hispano.org>,
Lista IRCops ESNET <ircops@esnet.org>, coder-com <coder-com@undernet.org>
Subject: [ops] IRC-Hispano/ESNET paradigms (II)
References: <38C728E4.113637B6@inxpress.net> <38C7B6AD.CAB4D5F9@argo.es> <38C83C1B.648B3190@inxpress.net> <38D0E1B9.44726BC6@argo.es>
The key point in IRC-Hispano/ESNET is the distributed database. The DDB
version TWO (the current one) supports 26 individual databases. Each
database has an specific role: nick registration, clone control, virtual
IP...
We, currently, are not using all the 26 databases. The defined ones can
be listed in "Fase 3: Consolidación de la Gestión Distribuída":
- b -> virtual bots (a sort of distributed X/W)
- i -> Clone control
- n -> Nick registration
- o -> Opers (new level below IRCops)
- t -> Migration DB (it will be deprecated when migration concludes)
- v -> Virtual IP
All the nodes have the same databases. Two aditional key point:
- The databases are "read-only". A node can only updates its copies
under request from another node. So, DB usage is distributed, but
changes must be issued from a control node.
Each DDB needs one and ONLY one control node; that its, the node which
make changes to a particular DDB must be unique. Of course, a single
node can acts as a control node for multiple databases.
- The key access for ALL the features and services is... the nick!!.
When you do "/nick your_nick" you must specify also a key 64 bits
long (12 chars). If your key is invalid, the server refuses your
"/nick command". For example:
/nick X
[14:50] -NiCK- *** El nick X está Registrado, necesitas contraseña.
[14:50] -NiCK- *** Utiliza /NICK X:clave para identificarte.
X Nickname is already in use or registered (missing or wrong password)
All this processing is done locally in the server. No network traffic.
No problem when a server is in split.
Of course, the nick DB doesn't content nick/key pairs, but nick/hash
keys, using 64bit criptography. In this way if the DB is stolen in a
node, real damage is small.
Registro de Nicks <- a bit outdated
To be continued...
PS: http://www.irc-hispano.org/servidores/stats/
--
Jesus Cea Avion _/_/ _/_/_/ _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/ _/_/ _/_/ _/_/ _/_/
_/_/ _/_/ _/_/_/_/_/
PGP Key Available at KeyServ _/_/ _/_/ _/_/ _/_/ _/_/
"Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/
"My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
©2000
jcea@jcea.es
Más información sobre los OpenBadges
Donación BitCoin: 19niBN42ac2pqDQFx6GJZxry2JQSFvwAfS
Blog personal: El hilo del laberinto
