On 03/18/2014 02:07 AM, Stefan Priebe - Profihost AG wrote:
Hi Sage,
i really would like to test the tiering. Is there any detailed
documentation about it and how it works?
Just for a simple test, you can start out with something approximately like:
# Create the pools (might want to do something more sophisticated)
ceph osd pool create cache 1024
ceph osd pool create base 1024
ceph osd pool set cache size 2
ceph osd pool set base size 3
# Add cache pool to base pool
ceph osd tier add base cache
ceph osd tier cache-mode cache writeback
ceph osd tier set-overlay base cache
# Set various tunables
ceph osd pool set cache hit_set_type bloom
ceph osd pool set cache hit_set_count 8
ceph osd pool set cache hit_set_period 60
ceph osd pool set cache target_max_objects 102400
Greets,
Stefan
Am 18.03.2014 05:45, schrieb Sage Weil:
Hi everyone,
It's taken longer than expected, but the tests for v0.78 are calming down
and it looks like we'll be able to get the release out this week.
However, we've decided NOT to make this release firefly. It will be a
normal development release. This will be the first release that includes
some key new functionality (erasure coding and cache tiering) and although
it is passing our tests we'd like to have some operational experience with
it in more users' hands before we commit to supporting it long term.
The tentative plan is to freeze and then release v0.79 after a normal two
week cycle. This will serve as a 'release candidate' that shaves off a
few rough edges from the pending release (including some improvements with
the API for setting up erasure coded pools). It is possible that 0.79
will turn into firefly, but more likely that we will opt for another two
weeks of hardening and make 0.80 the release we name firefly and maintain
for the long term.
Long story short: 0.78 will be out soon, and you should test it! It is
will vary from the final firefly in a few subtle ways, but any feedback or
usability and bug reports at this point will be very helpful in shaping
things.
Thanks!
sage
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
