On 05/05/2012 04:51 PM, Sage Weil wrote:
The second set of patches restructure the way the cache itself is managed.
One goal is to be able to control cache behavior on a per-image basis
(this one write-thru, this was write-back, etc.). Another goal is to
share a single pool of memory for
On Mon, 7 May 2012, Vladimir Bashkirtsev wrote:
On 20/04/12 14:41, Sage Weil wrote:
On Fri, 20 Apr 2012, Vladimir Bashkirtsev wrote:
Dear devs,
First of all I would like to bow my head at your great effort! Even if
ceph
did not reach prime time status yet it is already extremely
On Mon, 7 May 2012, Josh Durgin wrote:
On 05/05/2012 04:51 PM, Sage Weil wrote:
The second set of patches restructure the way the cache itself is managed.
One goal is to be able to control cache behavior on a per-image basis
(this one write-thru, this was write-back, etc.). Another goal is
Hi. I've been working on easy deployability and manageability of Ceph.
This work is intended to be a complete replacement for mkcephfs, and
integrate new product features instead of just automating the
previous, clumsier, administration mechanisms. I'm using Chef to
create and expand the cluster,
The new site is great! I like the Ceph documentation, however I found
a couple of typos. Is this the best place address them? (Some of the
apparent typos may be my not understanding what is going on.)
http://ceph.com/docs/master/config-cluster/ceph-conf/
The Hardware Recommendations link
On Mon, May 7, 2012 at 3:58 PM, Tommi Virtanen t...@inktank.com wrote:
The current work is in a branch called ceph-1, and will be improved
upon, but it is now at a stage where others should start looking at
it.
Make that chef-1.
--
To unsubscribe from this list: send the line unsubscribe
