All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
To: Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>,
	ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ceph-users-Qp0mS5GaXlQ@public.gmane.org
Subject: Re: firefly timing
Date: Tue, 18 Mar 2014 08:07:19 +0100	[thread overview]
Message-ID: <5327F0A7.8010105@profihost.ag> (raw)
In-Reply-To: <alpine.DEB.2.00.1403172115140.24236-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>

Hi Sage,

i really would like to test the tiering. Is there any detailed
documentation about it and how it works?

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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  parent reply	other threads:[~2014-03-18  7:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18  4:45 firefly timing Sage Weil
     [not found] ` <alpine.DEB.2.00.1403172115140.24236-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18  7:07   ` Stefan Priebe - Profihost AG [this message]
     [not found]     ` <5327F0A7.8010105-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2014-03-18  7:13       ` Ирек Фасихов
     [not found]         ` <CAF-rypyVjvuddtaj=cW_yJowzGzCq0m7LgW6S=2zK1aAvsfrTA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18  7:54           ` Karan Singh
2014-03-18 10:00       ` Alexandre DERUMIER
2014-03-18 16:06     ` Sage Weil
     [not found]       ` <alpine.DEB.2.00.1403180905500.316-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 16:20         ` Stefan Priebe - Profihost AG
2014-03-18 16:38       ` Milosz Tanski
     [not found]         ` <CANP1eJEDccw7doegUSoNKceQUgoNOfpHW1_y1Oz1fk54WDdb4w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-18 17:17           ` Sage Weil
     [not found]             ` <alpine.DEB.2.00.1403181014410.5823-vIokxiIdD2AQNTJnQDzGJqxOck334EZe@public.gmane.org>
2014-03-18 20:12               ` Sage Weil
2014-03-18 22:32                 ` Milosz Tanski
  -- strict thread matches above, loose matches on Subject: below --
2014-02-03 16:21 Sage Weil
2014-02-03 17:29 ` Loic Dachary
2014-02-04  6:14 ` James Page
2014-02-04  6:20   ` Sage Weil
2014-02-04  6:33     ` James Page

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=5327F0A7.8010105@profihost.ag \
    --to=s.priebe-2lf/h1ldwehr5kwtpvns9a@public.gmane.org \
    --cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ceph-users-Qp0mS5GaXlQ@public.gmane.org \
    --cc=sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.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.