[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Freedombox-discuss] How to deal with uptime and connectivity issues

On Tue, Mar 01, 2011 at 08:20:37AM +0000, Matt Willsher wrote:
> On 1 March 2011 07:52, Felipe Sanches <juca at members.fsf.org> wrote:
> > SaaS users usually benefit from high availability provided by professional
> > datacenters. Data is often stored redundantly.
> >
> > How will we deal with those issues in the scenario of a single plug per user
> > tied to a power outlet? Are we expecting people to have multiple
> > freedomboxes kept in sync? I foresee people unplugging someone else's boxes
> > in order to use the power outlet.

You'll be using a distributed, redundant cryptographic filestore,
e.g. Tahoe-LAFS, or something equivalent. I don't think there's much
point in failover configrations in a home setting, but it can
be done, in principle.
> If someone unplugs the plug computer then it just needs to plugged in
> again. This isn't much different from any always on device - clocks
> especially spring to mind.
> Some form of clustering perhaps? heartbeat, corosync and on top of
> that, pacemaker.  are reasonable forms of such although there needs to
> be two channels of communication (heartbeat + data) and STONITH which
> may be a tricky problem to solve. Storage can be made resilient
> cheaply with DRBD.
> If containers (vserver, openvz) are able to be used they could be
> synced via DRBD and switched on failure. Proxmox VE implements such a
> form and might be worth further investigation.

Eugen* Leitl <a href="http://leitl.org";>leitl</a> http://leitl.org
ICBM: 48.07100, 11.36820 http://www.ativel.com http://postbiota.org
8B29F6BE: 099D 78BA 2FD3 B014 B08A  7779 75B0 2443 8B29 F6BE

Reply to: