3 Feb
2015
3 Feb
'15
3:37 p.m.
Did you already read this ?
https://github.com/libre-mesh/lime-packages/blob/develop/packages/lime-syst…
yes, we took this as a start for the analysis
btw lime-default options are readed in case of
something missing from lime
Questions :
1.is there any "override" mechanism to stop lime-config touching
original config files or params within ?
2. overall view of the design "/usr/bin/lime-config" ( lua script
with no "lua" extension ?)
3. list of keywords used in "/usr/bin/lime-config" and respective
scripts / files
4. there is some "mingle" between lime and lime-defaults - whats the
meaning of "missing" compared to what.
Next halt : Parsing of lime / lime-defauls and the respective list of
keywords with their actions have to be carved out of the source
btw : we have been really surprised by the numbers of interfaces been
generated and digging deep to find out to which extent they are
necessary and to what use
No organised site to store the documentation to ?
regards
3zl(Reinhard)
3 Feb
3 Feb
3:51 p.m.
New subject: Please put the subject next time
On Tuesday, February 03, 2015 06:37:24 PM 3zl Trizonelabs wrote:
1.is there any "override" mechanism to
stop lime-config touching
original config files or params within ?
Do you meana specific confg file ora you wanna prevent that lime-config edit
config files in general ?
2. overall view of the design
"/usr/bin/lime-config" ( lua script
with no "lua" extension ?)
It just call all lime modules clean() and then configure() method
3. list of keywords used in
"/usr/bin/lime-config" and respective
scripts / files
What you mean by keywords ?
4. there is some "mingle" between lime and
lime-defaults - whats the
meaning of "missing" compared to what.
Next halt : Parsing of lime / lime-defauls and the respective list of
keywords with their actions have to be carved out of the source
For example the option lime.network.protocols is a necessary option so if the
user do not specify it in /etc/config/lime then the one from /etc/config/lime-
defaults (that the user must not touch) is taken
btw : we have been really surprised by the numbers of
interfaces been
generated and digging deep to find out to which extent they are
necessary and to what use
Abstraction always come with a price, lime is a metafirmware so you can change
it's behavior dramatically just editing a couple of options, to have such a
level of abstraction we opted to use tagged vlans, mac vlan and some other
technique that have the "virtual draw back" of creating a lot of interfaces
No organised site to store the documentation to ?
http://libre-mesh.org/
We are mostly volunteers we document libre-mesh in our spare time, if you have
some resource to dedicate to us we will be happy to spend some more works
hours on developing/documenting lime, we also accept patches or if you wanna
write some docs you are welcome too
5 Feb
5 Feb
8:39 a.m.
New subject: Please put the subject next time
By the way, this wiki page explains the network architecture of libre-mesh:
http://libre-mesh.org/projects/libre-mesh/wiki/Network_Architecture
It might be useful to understand the internals of the basic system.
On 03/02/15 16:51, Gioacchino Mazzurco wrote:
On Tuesday, February 03, 2015 06:37:24 PM 3zl
Trizonelabs wrote:
--
./p4u
1.is there any "override" mechanism
to stop lime-config touching
original config files or params within ?
Do you meana specific confg file ora you wanna prevent that lime-config edit
config files in general ?
2. overall view of the design
"/usr/bin/lime-config" ( lua script
with no "lua" extension ?)
It just call all lime modules clean() and then configure() method
3. list of keywords used in
"/usr/bin/lime-config" and respective
scripts / files
What you mean by keywords ?
4. there is some "mingle" between
lime and lime-defaults - whats the
meaning of "missing" compared to what.
Next halt : Parsing of lime / lime-defauls and the respective list of
keywords with their actions have to be carved out of the source
For example the option lime.network.protocols is a necessary option so if the
user do not specify it in /etc/config/lime then the one from /etc/config/lime-
defaults (that the user must not touch) is taken
btw : we have been really surprised by the
numbers of interfaces been
generated and digging deep to find out to which extent they are
necessary and to what use
Abstraction always come with a price, lime is a metafirmware so you can change
it's behavior dramatically just editing a couple of options, to have such a
level of abstraction we opted to use tagged vlans, mac vlan and some other
technique that have the "virtual draw back" of creating a lot of interfaces
No organised site to store the documentation to ?
http://libre-mesh.org/
We are mostly volunteers we document libre-mesh in our spare time, if you have
some resource to dedicate to us we will be happy to spend some more works
hours on developing/documenting lime, we also accept patches or if you wanna
write some docs you are welcome too
_______________________________________________
Dev mailing list
Dev(a)lists.libre-mesh.org
https://lists.libre-mesh.org/mailman/listinfo/dev
3607
days inactive
3609
days old
2 comments
3 participants
participants (3)
-
3zl Trizonelabs -
Gioacchino Mazzurco -
Pau