From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id C60CC21F19C for ; Sat, 29 Mar 2014 10:58:31 -0700 (PDT) Received: by mail-wg0-f44.google.com with SMTP id m15so4580326wgh.27 for ; Sat, 29 Mar 2014 10:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=HrogWfAEPQUTRvUjh9vK8WmGoyxLna+m0i5488TkZ74=; b=oVLqZmrRCfGH7VWiEnjJQmlBslbggGuRobuhlg8LQQGotVJ3/ioEFVEtxxbGedANo3 wjneqF9TKmqw6hxHT125kt170hmqEyWaPygHma3fvR1+Yn2vzO4clzR/4HGeMlf5VTZ5 wRPx2nUXEvklGkaIqD6zH0jIoQfP7F+mxCdw2cHttEwRjH947Fn+iM02TVId+0HuE9lT /RXUi9mH8kcmhkcnRA+v9M5g5eG4HrLiaoCDkHPlGvGSXdEHFAq+QcnBWK6fVlZRHxRc 3EDrXfjnzJEKABxElmez07rGUkUm9hbvjsuVNnj3vdhqmzxpLxUvPuGrGQcV/WC4jkKw pzvw== MIME-Version: 1.0 X-Received: by 10.194.81.164 with SMTP id b4mr4285535wjy.2.1396115909388; Sat, 29 Mar 2014 10:58:29 -0700 (PDT) Received: by 10.216.8.1 with HTTP; Sat, 29 Mar 2014 10:58:29 -0700 (PDT) In-Reply-To: <5336FD70.1000202@phrozen.org> References: <5336FD70.1000202@phrozen.org> Date: Sat, 29 Mar 2014 10:58:29 -0700 Message-ID: From: Dave Taht To: "cerowrt-devel@lists.bufferbloat.net" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: [Cerowrt-devel] Fwd: [Battlemesh] BattleMeshV7: testing incremental fw upgrade feature X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2014 17:58:32 -0000 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 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 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 --=20 Dave T=E4ht Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.= html