From owner-freebsd-geom@FreeBSD.ORG Fri Nov 10 23:10:28 2006 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B2AFB16A407; Fri, 10 Nov 2006 23:10:28 +0000 (UTC) (envelope-from sia@seagull.nest.org) Received: from seagull.nest.org (seagull.nest.org [216.218.215.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2C0743D79; Fri, 10 Nov 2006 23:10:14 +0000 (GMT) (envelope-from sia@seagull.nest.org) Received: (from sia@localhost) by seagull.nest.org (8.8.8/8.8.8/KOLO.NET-SINK-20030423-CHECK-19990919) id PAA23196; Fri, 10 Nov 2006 15:09:57 -0800 (PST) (envelope-from sia) Date: Fri, 10 Nov 2006 15:09:57 -0800 From: Igor Sviridov To: freebsd-geom@freebsd.org Message-ID: <20061110150957.A14717@seagull.nest.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Precedence: special-delivery X-IM-Skype: isviridov X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . Cc: pjd@freebsd.org Subject: geom s3 class (gs3?) X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Nov 2006 23:10:28 -0000 hi, I guess most people here heard about Amazon S3 storage service: http://aws.amazon.com/s3 I would love to have a Geom class which would use S3 as a back-end. While S3 api is good one for Web applications, using filesystem is often simpler and sometimes the only way. Obviously mapping filesystem calls to S3 API may be too slow for many applications but this can be mitigated by adding local write cache/queue on another geom provider (disk), or modifying gmirror to return write calls once they're committed to local mirror component (and using it as queue for remote mirror component stored on S3). There is in fact Linux prototype implementation of similar idea, though on slightly different level - "s3fs" filesystem via FUSE: http://dev.extensibleforge.net/wiki/s3/fuse and closed-source open-spec JungleDisk: http://www.jungledisk.com/ --igor