For NetOrk/netork#2615: a package upgrade on OpenWrt writes the new package to the overlay while the old one stays in the read-only image, so the overlay only fills. A sysupgrade to the newest release of the device's own line brings those packages, and every package installed since, in the new image.
get_firmware_offer() (FirmwareOfferMixin): reads /etc/openwrt_release, the sysupgrade server the device is set to (attendedsysupgrade.@server[0].url, else the public one; http(s) only) and whether owut is installed, in one round trip. The release line is looked up in the server's /json/v1/overview.json, fetched by the caller at most once a day per server and process (a failed fetch is not retried for an hour). latest_version is the newest release of the device's line that builds its target (release candidates only where the line has no release), latest_major_version the newest later line, installable whether owut is there (left out before 24.10). A snapshot or a target the line no longer builds has no offer.
start_firmware_upgrade(version) (FirmwareUpgradeMixin): owut upgrade --version-to <version> as root, detached from the session and deaf to its hang-up, output in /tmp/owut-upgrade.log; refuses while one runs or owut is missing, and anything but a release version.
get_update_progress(): that log, running until owut prints "Installing … and rebooting" (done; sysupgrade then stops every process) or ends without it (failed).
Needs napalm-device-types 4.41.0. Release 0.8.0 (version and CHANGELOG).
Tests: tests/unit/test_firmware.py (26, the overview's real shape cut down); full suite, ruff and strict mypy for the new module green locally. All four APs on the netOrk test server already have owut.
For NetOrk/netork#2615: a package upgrade on OpenWrt writes the new package to the overlay while the old one stays in the read-only image, so the overlay only fills. A sysupgrade to the newest release of the device's own line brings those packages, and every package installed since, in the new image.
- `get_firmware_offer()` (`FirmwareOfferMixin`): reads `/etc/openwrt_release`, the sysupgrade server the device is set to (`attendedsysupgrade.@server[0].url`, else the public one; http(s) only) and whether owut is installed, in one round trip. The release line is looked up in the server's `/json/v1/overview.json`, fetched by the caller at most once a day per server and process (a failed fetch is not retried for an hour). `latest_version` is the newest release of the device's line that builds its target (release candidates only where the line has no release), `latest_major_version` the newest later line, `installable` whether owut is there (left out before 24.10). A snapshot or a target the line no longer builds has no offer.
- `start_firmware_upgrade(version)` (`FirmwareUpgradeMixin`): `owut upgrade --version-to <version>` as root, detached from the session and deaf to its hang-up, output in `/tmp/owut-upgrade.log`; refuses while one runs or owut is missing, and anything but a release version.
- `get_update_progress()`: that log, `running` until owut prints "Installing … and rebooting" (`done`; sysupgrade then stops every process) or ends without it (`failed`).
- Needs napalm-device-types 4.41.0. Release 0.8.0 (version and CHANGELOG).
Tests: `tests/unit/test_firmware.py` (26, the overview's real shape cut down); full suite, ruff and strict mypy for the new module green locally. All four APs on the netOrk test server already have owut.
get_firmware_offer() looks the device's release line up in the attended
sysupgrade server's overview.json, fetched at most once a day per server.
start_firmware_upgrade() runs owut upgrade detached from the session, and
get_update_progress() follows its log until owut hands the image to sysupgrade.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For NetOrk/netork#2615: a package upgrade on OpenWrt writes the new package to the overlay while the old one stays in the read-only image, so the overlay only fills. A sysupgrade to the newest release of the device's own line brings those packages, and every package installed since, in the new image.
get_firmware_offer()(FirmwareOfferMixin): reads/etc/openwrt_release, the sysupgrade server the device is set to (attendedsysupgrade.@server[0].url, else the public one; http(s) only) and whether owut is installed, in one round trip. The release line is looked up in the server's/json/v1/overview.json, fetched by the caller at most once a day per server and process (a failed fetch is not retried for an hour).latest_versionis the newest release of the device's line that builds its target (release candidates only where the line has no release),latest_major_versionthe newest later line,installablewhether owut is there (left out before 24.10). A snapshot or a target the line no longer builds has no offer.start_firmware_upgrade(version)(FirmwareUpgradeMixin):owut upgrade --version-to <version>as root, detached from the session and deaf to its hang-up, output in/tmp/owut-upgrade.log; refuses while one runs or owut is missing, and anything but a release version.get_update_progress(): that log,runninguntil owut prints "Installing … and rebooting" (done; sysupgrade then stops every process) or ends without it (failed).Tests:
tests/unit/test_firmware.py(26, the overview's real shape cut down); full suite, ruff and strict mypy for the new module green locally. All four APs on the netOrk test server already have owut.