From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Battlemesh] BattleMeshV7: testing incremental fw upgrade feature
Date: Sat, 29 Mar 2014 10:58:29 -0700 [thread overview]
Message-ID: <CAA93jw6qPaiVqkEz1dcqmUcuUuAEb0DtKXniXV9tT2+PXfEmTw@mail.gmail.com> (raw)
In-Reply-To: <5336FD70.1000202@phrozen.org>
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 <john@phrozen.org>
Date: Sat, Mar 29, 2014 at 10:05 AM
Subject: [Battlemesh] BattleMeshV7: testing incremental fw upgrade feature
To: battlemesh@ml.ninux.org, onelektra@gmx.net, Felix Fietkau <nbd@nbd.name>
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
Battlemesh@ml.ninux.org
http://ml.ninux.org/mailman/listinfo/battlemesh
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
parent reply other threads:[~2014-03-29 17:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <5336FD70.1000202@phrozen.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6qPaiVqkEz1dcqmUcuUuAEb0DtKXniXV9tT2+PXfEmTw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox