From: Constantinos Venetsanopoulos <cven@grnet.gr>
To: Loic Dachary <loic@dachary.org>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Distributed Deduplication in a Cloud-based Object Storage System
Date: Tue, 23 Apr 2013 13:06:59 +0300 [thread overview]
Message-ID: <51765D43.5040207@grnet.gr> (raw)
In-Reply-To: <51763308.6010704@dachary.org>
Hello Loic,
On 04/23/2013 10:06 AM, Loic Dachary wrote:
> Hi,
>
> For later reference. Who knows ... ;)
>
> http://paulormg.files.wordpress.com/2012/08/thesis-paulo.pdf
>
that is very interesting! That was exactly what we were talking
about during the Ceph meeting @ FOSDEM'13.
We have been running a similar design in production for over
1.5 year now, with Synnefo [1], first over NFS and now over
RADOS. Specifically, the Storage Service of Synnefo, called
Pithos, stores content-addressable objects on the underlying
storage, allowing us to do file syncing with native clients, not
only for files but for VM Images, too.
We even have an extension for the OpenStack Object Storage
API (which is what we expose to the users), to allow us for
these advanced operations, the same way Paulo proposes.
If anyone is interested towards that direction, which we believe
allows for very interesting things to be done, please take a
look at the Pithos design and the corresponding OpenStack
API:
http://www.synnefo.org/docs/synnefo/latest/pithos.html#pithos-design
http://www.synnefo.org/docs/synnefo/latest/pithos-api-guide.html#the-pithos-api
The first document is somewhat outdated (sorry for that :)), but
the concepts are there and have been tested in production.
Again, we are very happy to see other people exploring those
paths in the cloud context too.
Kind Regards,
Constantinos
[1] http://www.synnefo.org
prev parent reply other threads:[~2013-04-23 10:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 7:06 Distributed Deduplication in a Cloud-based Object Storage System Loic Dachary
2013-04-23 10:06 ` Constantinos Venetsanopoulos [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51765D43.5040207@grnet.gr \
--to=cven@grnet.gr \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.