Implement mesh upgrade package #1109
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
also Adds the following methods: start_node_download(url) state() change_state()
…ages into feature/mesh-upgrade
…ges into feature/mesh-upgrade
…ges into feature/mesh-upgrade
adds new methods to eupgrade like "is_meshupgrade_enabled" and "set_custom_api_url" fixes some reduntant methods call
…ages into feature/mesh-upgrade
G10h4ck
reviewed
Jun 20, 2024
| option retry_count '0' | ||
| option safeupgrade_start_mark '0' | ||
| option su_start_time_out '0' | ||
|
|
There was a problem hiding this comment.
missing new line.
I am not sure if we should use a config file per se, or this should end up into /etc/config/lime-* with the other configurations.
There was a problem hiding this comment.
this config file main reason to exist is to keep the settings and status of the current upgrade. This is to be keep across, operating system process, reboots and sysupgrades. It is a backend mesh-upgrade state and config persistence.
packages/lime-mesh-upgrade/files/usr/lib/lua/lime-mesh-upgrade.lua
Outdated
Show resolved
Hide resolved
...d-state-mesh_wide_upgrade/files/usr/share/shared-state/hooks/mesh_wide_upgrade/start_upgrade
Outdated
Show resolved
Hide resolved
selankon
requested changes
Aug 12, 2024
|
Will this work on non-LibreRouter routers? |
|
This package requires safe-upgrade, so far only lr1 is able to use it.
Luciano is working to implement it in lr2 but also documenting the process
to be able to add more routers.
Any router with more than 16mb of flash wold be able to use safe upgrade.
…On Tue, Nov 12, 2024, 06:49 Ilario Gelmetti ***@***.***> wrote:
Will this work on non-LibreRouter routers?
—
Reply to this email directly, view it on GitHub
<#1109 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABE2I2A4AZJ7R6PUDIS4LQD2AHFL3AVCNFSM6AAAAABHQ5QLIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGA3DSOJWGM>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mesh upgrade
This package can help you upgrade the firmware of all the routers in a network from a single node.
Description and steps
1- A node must become main node, the main node will fetch the firmware for all the others. And expose it in the local network.
2- The main node announces the new firmware over shared-state-async
3- Other nodes with this package will get the news and try to download the firmware.
4- Once all the nodes have the firmware in their tmp folder the main node user will be able to schedule the safe upgrade of all the nodes (this last step is done synchronously).
5- After the specified time (60s default) all the nodes will start the safe upgrade process and the nodes will reboot.
6- The nodes will report that the new firmware has to be confirmed.
7- The main node user will verify that everything is in place an press the confirm button.
8- If the firmware is not confirmed after 600 seconds the routers will go back to the previous firmware.