[Nodedb-interop] Let's continue
Mitar
(spam-protected)
Wed Jan 6 00:27:34 CET 2010
Hi!
OK, I have to do my thesis so I did not have much time this last weeks.
But I setup a wiki we have been talking about. So that we can continue
with work on interoperability.
http://interop.wlan-lj.net/
After some thought I have decided for Trac wiki as it is not bloated, i
is easily extendable (we can simply integrate source code repository and
also other systems into its MVC framework if there will be some day
need) and I have good experience with it. Hope it will serve all our
purposes well. (Suggestions for improvements are of course welcome. Also
if you have ideas for what we could automatize or integrate, for example
there is also graphviz support: http://interop.wlan-lj.net/wiki/SandBox)
I have configured wiki so that for editing registration is necessary. I
think this is OK as it is useful to know who has edited or contributed
something so that we can easier discuss things and also limits possible
spam. After registration user has almost all rights on wiki, except
deletion and editing of read-only pages (there are currently none). If
anybody wants to share this administration burden with me, you are
welcome. It is also setup in an independent virtual machine if there
will be someday need to cooperate on the system itself.
I have also made sections I think we could work on. If you think I have
missed feel free to tell me. I have also populated wiki with some data
we have send to the mailing list. And some of my suggestions. Please
feel free to discus them. (One idea I was playing with is also a "best
practices" wiki where we could publish things which really worked well,
from routing protocols to good antenna designs. (It could be just link
of course, it is not necessary to copy things.))
One interesting thing I come up with is a list of IP addresses:
http://interop.wlan-lj.net/wiki/IPAddressing/List
Which is automatically parsed and duplicated in the second table. I do
not think we need a full-fetched allocation system (as offered by Ramon)
as we are talking about whole ranges here and not independent nodes (for
that I would recommend some other system based on common schema and data
aggregation). And also with IPv6 we will not need precise cooperation on
IP ranges anymore. I think this is the easiest for people to edit and
add themselves and we could just add some checks and issue warnings if
there are problems how people entered data.
The other I would like to emphasize is our own top-level domain and DNS
root servers we could work on?
http://interop.wlan-lj.net/wiki/DNS/TLD
And now about database schema. I think it would be useful if we now
publish everything on the wiki and see what is common ground. For
example Ramon's example is very good of what is missing in our schema
which comes directly from experience and needs (we have currently only
one city with network in Slovenia so we had little use of making a
hierarchy for nodes, on other side we have worked on monitoring a lot).
As have also Ramon's suggested our work will probably be mostly seeing
what everybody has, combining it and name attributes and classes.
I also think it would be useful to invite everybody again to
participate. For example list of IP ranges is almost empty.
So, let's continue!
Mitar
More information about the Nodedb-interop
mailing list