Hi all
I would like to add these points to discuss in the next libremesh meetings.
Maybe today or the 4th of october, if there is any free time left, we
can look to some of these (i.e. the first):
In general, I am willing to carry out the tasks listed below.
1. Do maintenance on the repo server
2. Use the repo server as endpoint to add a minimal telemetry of libremesh
3. Add to repo server a minimal public stats of downloads (may be a
simple grafana dashboard that read a prometheus-nginx)
4. Add a dns entry for firmware-selector.libremesh.org
5. Install an openwisp server on top of the repo server to experiment
with libremesh-openwisp
6. Create imagebuilders with a reduced kernel and let's see how far the
devices 8/64 go (kernel config SMALL_FLASH suggested by Javier [0])
7. Rework lime-docs asciidoc inclusion and packaging and substitute the
actual jekyll with a more modern vitepress or docusaurus
1. Do maintenance on the repo server
The server runs Debian 10 but with a very old kernel let's upgrade both
2. Use the repo server as endpoint to add a minimal telemetry of libremesh.
the repo server has 2G ram 140GB disk
Currently is used as download server: (up to release
2024.1-rc1-ow23.05.3-default)
The last release, the libremesh-2024.1-ow23.05.5 weight 52GB with a
reduced list of targets.
It hasn't be uploaded to the repo server and remains faster to
downloads, also for the firmware-selector, from
https://firmware-libremesh.antennine.org
Some usable tools could be
- prometheus pushgateway
- prometheus pushprox (i.e.
https://github.com/alex-pnzv/pushprox-client)
- others? (collectd, victoriametrics)
The telemetry could be something like, creating an adhoc package (so
easy to remove or to not-include) i.e. `lime-telemetry`
- opt-out the device do a curl every day/every week (i.e. prometheus
pushgateway)
- opt-in the device shares the position (gps coordinates)
This could be useful as a minimal monitoring system (uptime) for those
who need it and haven't set up anything more complex.
3. Add to repo server a minimal public stats of downloads (may be a
simple grafana dashboard that read a prometheus-nginx)
We are using something similar for firmware-libremesh.antennine.org. I
will provide a public link to Grafana in the near future.
4. The last setup of firmware-selector for libremesh is currently
deployed by github actions following this scheme:
-
https://github.com/a-gave/firmware-selector deploys using github pages
to
https://a-gave.github.io/firmware-selector
-
https://repo.libremesh.org/selector has an apache proxypass to
https://a-gave.github.io/firmware-selector
It could be nice to make it more official it seems enough used/useful.
- let's move the code of firmware-selector under the github's libremesh
organization
- ask someone of the project with access to the dns of libremesh to add
a firmware-selector.libremesh.org that points to github
5. Install an openwisp server on top of the repo server to experiment
with libremesh-openwisp
It could be nice to have for experimenting, to check if doable on the
repo server
6. Create a set of imagebuilders with a reduced kernel and let's see how
far the devices 8/64 go (kernel config SMALL_FLASH suggested by Javier [0])
And add an option in the firmware-selector to choose to use the
imagebuilders with a reduced kernel
With openwrt-24.10.3 8/64 are still usable by adopting some measures to
save space and RAM.
Generally speaking routers are easier to replace than outdoor devices
(installation, roof access, and affordability).
7. Rework lime-docs asciidoc inclusion and packaging and substitute the
actual jekyll with a more modern vitepress or docusaurus
The actual
https://libremesh.org was a readaptation of
https://github.com/vsoch/mkdocs-jekyll
It is a bit better than the previous theme, which had two half menus and
was a bit distracting, and you were never sure you had read all the
documentation.
Lets evaluate to use some ci to do the conversion of asciidoc (copied to
devices for offline-docs) to markdown
and start using a more modern and convenient to use like vitepress or
docusaurus.
[0]
https://github.com/libremesh/lime-packages/pull/1139#issuecomment-2566088066
--
gothos
PGP Key ID: 0x6406B32F2CEC0008
PGP Key server:
https://keys.openpgp.org/
