Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
FFS Gluon
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
firmware
FFS Gluon
Commits
3fd0ca77
Unverified
Commit
3fd0ca77
authored
8 years ago
by
Matthias Schiffer
Browse files
Options
Downloads
Patches
Plain Diff
docs: feature/roles: update outdates site config docs
parent
2a101ddd
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
docs/features/roles.rst
+10
-6
10 additions, 6 deletions
docs/features/roles.rst
docs/user/site.rst
+3
-3
3 additions, 3 deletions
docs/user/site.rst
with
13 additions
and
9 deletions
docs/features/roles.rst
+
10
−
6
View file @
3fd0ca77
...
@@ -2,7 +2,7 @@ Roles
...
@@ -2,7 +2,7 @@ Roles
=====
=====
It is possible to define a set of roles you want to distinguish at backend side. One node can own one
It is possible to define a set of roles you want to distinguish at backend side. One node can own one
role which it will announce via alfred inside the mesh. This will make it easier to differentiate
role which it will announce via alfred inside the mesh. This will make it easier to differentiate
nodes when parsing alfred data. E.g to count only **normal** nodes and not the gateways
nodes when parsing alfred data. E.g to count only **normal** nodes and not the gateways
or servers (nodemap). A lot of things are possible.
or servers (nodemap). A lot of things are possible.
...
@@ -11,17 +11,21 @@ For this the section ``roles`` in ``site.conf`` is needed::
...
@@ -11,17 +11,21 @@ For this the section ``roles`` in ``site.conf`` is needed::
roles = {
roles = {
default = 'node',
default = 'node',
list = {
list = {
n
ode = 'Normal N
ode',
'
node',
test
= 'Test Node
',
'
test',
b
ackbone = 'B
ackbone
Node
',
'
backbone',
service
= 'Service Node
',
'
service',
},
},
},
},
The strings to display in the LuCI interface are configured per language in the
``i18n/en.po``, ``i18n/de.po``, etc. files of the site repository using message IDs like
``gluon-luci-node-role:role:node`` and ``gluon-luci-node-role:role:backbone``.
The value of ``default`` is the role every node will initially own. This value should be part of ``list`` as well.
The value of ``default`` is the role every node will initially own. This value should be part of ``list`` as well.
If you want node owners to change the defined roles via config-mode you can add the package
If you want node owners to change the defined roles via config-mode you can add the package
``gluon-luci-node-role`` to your ``site.mk``. Then, you can select one of the defined roles from a dropdown list
``gluon-luci-node-role`` to your ``site.mk``. Then, you can select one of the defined roles from a dropdown list
where the right-handed value is the one which is displayed and the left-handed key the one which is configured into
where the right-handed value is the one which is displayed and the left-handed key the one which is configured into
the system.
the system.
The role is saved in ``gluon-node-info.system.role``. To change the role using command line do::
The role is saved in ``gluon-node-info.system.role``. To change the role using command line do::
...
...
This diff is collapsed.
Click to expand it.
docs/user/site.rst
+
3
−
3
View file @
3fd0ca77
...
@@ -183,7 +183,7 @@ fastd_mesh_vpn
...
@@ -183,7 +183,7 @@ fastd_mesh_vpn
In any case, the ``null`` method should always be the first method in the list
In any case, the ``null`` method should always be the first method in the list
if it is supported at all. You should only set `configurable` to `true` if the
if it is supported at all. You should only set `configurable` to `true` if the
configured peers support both the ``null`` method and methods with encryption.
configured peers support both the ``null`` method and methods with encryption.
You can set syslog_level from verbose (default) to warn to reduce syslog output.
You can set syslog_level from verbose (default) to warn to reduce syslog output.
::
::
...
@@ -286,7 +286,7 @@ roles \: optional
...
@@ -286,7 +286,7 @@ roles \: optional
part of ``list``. If you want node owners to change the role via config mode add
part of ``list``. If you want node owners to change the role via config mode add
the package ``gluon-luci-node-role`` to ``site.mk``.
the package ``gluon-luci-node-role`` to ``site.mk``.
The strings to display in the LuCI interface
can b
e configured per language in the
The strings to display in the LuCI interface
ar
e configured per language in the
``i18n/en.po``, ``i18n/de.po``, etc. files of the site repository using message IDs like
``i18n/en.po``, ``i18n/de.po``, etc. files of the site repository using message IDs like
``gluon-luci-node-role:role:node`` and ``gluon-luci-node-role:role:backbone``.
``gluon-luci-node-role:role:node`` and ``gluon-luci-node-role:role:backbone``.
::
::
...
@@ -366,7 +366,7 @@ gluon-config-mode:pubkey
...
@@ -366,7 +366,7 @@ gluon-config-mode:pubkey
gluon-config-mode:altitude-label
gluon-config-mode:altitude-label
Label for the ``altitude`` field
Label for the ``altitude`` field
gluon-config-mode:altitude-help
gluon-config-mode:altitude-help
Description for the usage of the ``altitude`` field
Description for the usage of the ``altitude`` field
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment