I've noted that the package signing feature has been busted for a while. This was in part because solving the harder problem - incremental update and rollback of the firmware - was still in progress. Pieces of that have begun to land...
---------- Forwarded message ---------- From: John Crispin <[email protected]> Date: Sat, Mar 29, 2014 at 10:05 AM Subject: [Battlemesh] BattleMeshV7: testing incremental fw upgrade feature To: [email protected], [email protected], Felix Fietkau <[email protected]> Hi everyone, recently we moved from mount_root to our new fstools feed https://dev.openwrt.org/changeset/39895/ One of the not so obvious features of fs-tools is a new overlay strategy mode which we call snapshoting. I am still working on a asciidoc to describe this feature, but in a nutshell it allows incremental and rollback-able rootfs/opkg upgrades. I would like to run a test at the wbm, a mesh of 5-10 routers, where we deploy a "new version of the routing daemon in use" and then after 30 minutes or so, rollback to the older version without actually touching the routers manually/individually. OpenWrt also has a new "config apply without save and rollback after X minutes" feature. The test case for this would be a mesh with X nodes, where we push a rpc/uci sequence to for example upgrade used ip ranges in the mesh and see if the apply and rollback after X minutes works. I am however a n00b at meshing and will need some help with the testbed :) Any volunteers that would like to help me work on this ? ideally we get organized before the event as not to loose too much time on site setting things up, but can get straight to the actual testing. John _______________________________________________ Battlemesh mailing list [email protected] http://ml.ninux.org/mailman/listinfo/battlemesh -- Dave Täht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html _______________________________________________ Cerowrt-devel mailing list [email protected] https://lists.bufferbloat.net/listinfo/cerowrt-devel
