firefly timing

firefly timing

[Sage Weil]

The original firefly freeze date was Jan 17, but I added another sprint 
because there were several things that weren't quite ready yet (the cache 
tier code and erasure coding).  Two weeks later we are much closer, but 
the EC functionality still needs a bit more time.  I would like to push 
out the freeze by one more sprint so that all of the code can land.  In 
particular, I would rather use the next sprint to get EC ready and shift 
other development focus to stability early, instead of pulling last-minute 
stuff in after the freeze date.

This bends/breaks the 'train model' schedule we are aiming for, but my 
assumption is that people are more interested in seeing the new 
functionality in place than in the exact timing.

The only time dependency that I am aware of is the looming 14.04 freeze 
date.  I'm hoping that we can (worst case) put an -rc release in place and 
update as the code stabilizes over the next several weeks.  James, will 
this be problematic?

Does anybody else have questions or concerns about adding in another 
sprint before we freeze for firefly?

Thanks- 
sage

Re: firefly timing

[Loic Dachary]

[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]

Hi Sage,

I'm both happy and stressed out to have more time to work on erasure code :-) If I'm not mistaken, the Firefly freeze is now set to Friday 14th, 2014. During this time I plan to focus on implementing whatever is required for Erasure Code to work with the default jerasure plugin ( I'm thinking https://github.com/ceph/ceph/pull/1144 , https://github.com/ceph/ceph/pull/1177 etc. ). If there is enough time, it would also be nice to have the pyramid plugin https://github.com/ceph/ceph/pull/1142 merged in, but this is not mandatory.

Is there a better use of my time during this sprint ?

Cheers

On 03/02/2014 17:21, Sage Weil wrote:
> The original firefly freeze date was Jan 17, but I added another sprint 
> because there were several things that weren't quite ready yet (the cache 
> tier code and erasure coding).  Two weeks later we are much closer, but 
> the EC functionality still needs a bit more time.  I would like to push 
> out the freeze by one more sprint so that all of the code can land.  In 
> particular, I would rather use the next sprint to get EC ready and shift 
> other development focus to stability early, instead of pulling last-minute 
> stuff in after the freeze date.
> 
> This bends/breaks the 'train model' schedule we are aiming for, but my 
> assumption is that people are more interested in seeing the new 
> functionality in place than in the exact timing.
> 
> The only time dependency that I am aware of is the looming 14.04 freeze 
> date.  I'm hoping that we can (worst case) put an -rc release in place and 
> update as the code stabilizes over the next several weeks.  James, will 
> this be problematic?
> 
> Does anybody else have questions or concerns about adding in another 
> sprint before we freeze for firefly?
> 
> Thanks- 
> sage
> 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: firefly timing

[James Page]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/02/14 18:21, Sage Weil wrote:
> The only time dependency that I am aware of is the looming 14.04
> freeze date.  I'm hoping that we can (worst case) put an -rc
> release in place and update as the code stabilizes over the next
> several weeks.  James, will this be problematic?

Pushing in an RC is a good approach; what's the likely date for the
firefly release?  I can raise the Freeze Exception now which gives our
release team *lots* of notice :-)  FWIW I don't think this will be a
problem - we have a good track record with ceph in Ubuntu now.

Cheers

James


- -- 
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS8IU1AAoJEL/srsug59jDEQkP/Ak1DvMqDsLwtdWNJCZ6Y4qM
/+GhBuJHCEDhx7+2mM4l9kiFdEVRNY4uarRIaCNYtgMhKWZ0c1MzFD4nVicqmg85
72gfdc97opDU3Mus3GXk6TI51jex6YBaRR4kUDWcT5l2N39yPN9iaxiSftfYnI4C
3sK5W2GdLCaYjWsjgdOum0UDyN9ZSZmK1qBfMHmZZ74OsMPmGK+D9hiTKnH5sEF8
57Nmoa4G4wfmBUf/vxkKnmI51hQrXnp0zqeI5i+xDvDGelNUDtofrcxQrp0yfnff
FAf50KvYeniyjvtgqQMvu9vrb4gvN0lTFUZygLXICq5mX45JitGjQ0NS7T4pVhbE
fdW+2BN4I91CkIVY/qPTRqWv/RIZJM4dj/2w3DBMhoMnIl1laFd+uMd5b2mxrWD9
RHXOOXgE9fq0gBuB5N2w8Q50Bm4+gDqxM7mfQi8lvSjXyUVPdvdnIuYd/L5beIGX
9EbYLLoaXRHIN84DQwHY/6Ni57rPGcG0VNjOBcgNXr/8DXJi4b8ztxIpCT7rhpG0
UeCVEuRsrM5wggvQFODaxQ1BzNvuQbUryj+FK2fsGfwnHESp1J5arKbRJUUHCkT7
tzhHlqx9jWDp6sMyc6jMVotSOgQv/AGq+kt/gBLEz6ymLB4MsZkQQRpMXXID+RkH
tmFj4DUwOn7LRSS1/Ag8
=kovj
-----END PGP SIGNATURE-----

Re: firefly timing

[Sage Weil]

On Tue, 4 Feb 2014, James Page wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> On 03/02/14 18:21, Sage Weil wrote:
> > The only time dependency that I am aware of is the looming 14.04
> > freeze date.  I'm hoping that we can (worst case) put an -rc
> > release in place and update as the code stabilizes over the next
> > several weeks.  James, will this be problematic?
> 
> Pushing in an RC is a good approach; what's the likely date for the
> firefly release?  I can raise the Freeze Exception now which gives our
> release team *lots* of notice :-)  FWIW I don't think this will be a
> problem - we have a good track record with ceph in Ubuntu now.

If we take the usual 4 weeks, it will be the second week of March, and an 
-rc will come out in the last week of February.  The freeze will come 
before the trusty freeze, but an early -rc at that point will be 
relatively raw.  I assume it will be worth building, though, to minimize 
the number of hoops to jump through.  There are also several users who 
have expressed interest in an early build with EC support to star their 
testing.

sage

Re: firefly timing

[James Page]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 04/02/14 08:20, Sage Weil wrote:
> On Tue, 4 Feb 2014, James Page wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>> 
>> On 03/02/14 18:21, Sage Weil wrote:
>>> The only time dependency that I am aware of is the looming
>>> 14.04 freeze date.  I'm hoping that we can (worst case) put an
>>> -rc release in place and update as the code stabilizes over the
>>> next several weeks.  James, will this be problematic?
>> 
>> Pushing in an RC is a good approach; what's the likely date for
>> the firefly release?  I can raise the Freeze Exception now which
>> gives our release team *lots* of notice :-)  FWIW I don't think
>> this will be a problem - we have a good track record with ceph in
>> Ubuntu now.
> 
> If we take the usual 4 weeks, it will be the second week of March,
> and an -rc will come out in the last week of February.  The freeze
> will come before the trusty freeze, but an early -rc at that point
> will be relatively raw.  I assume it will be worth building,
> though, to minimize the number of hoops to jump through.  There are
> also several users who have expressed interest in an early build
> with EC support to star their testing.

That should be OK - I'll tee things up with the release team now

Thanks

- -- 
James Page
Ubuntu and Debian Developer
james.page@ubuntu.com
jamespage@debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS8ImdAAoJEL/srsug59jD02UP+wUSz9xt2z2hyDVmkW9h2pBg
jDYAe+prKehdm1t1yulCBWABRxPwE2aV52LXn4X/8QivHQcqQzYP3wUfwCbsT/4F
qewImdizrXU1vDVUaRJ1/eQ3V3zkH51DzgmhGzk7OdXa3HWXBrCG0U1IPnbRSzpq
qo19uWdHNInzzv8a1w83YI1Gse+PrLNcotdmuKy8zk+o0/0N+naMKHgs+jx5fvfY
doWwtbyB/h9ef4C7s57eOcyoxW69/DxUO8xXV9aL2JMHmvTdiCejKFxSlwo8Tkke
5HKWHRU166ZJgCOkuA6qHsI/Nhli/FPd3TQCdfCmK78ClfCYvZrsyPCStIvYyPCF
NAtlkNGmzU7DCNgIsylCeVVBwUZ2BnHUFyOdrUzkSL7a1KJbG/BihzgbYaOD6fMD
7IlIvm6x6ltzk634TEy/bHwGJkVy8zkB+w2zPOVeYubNTXxofkPJJ+0YRXdodEHF
/ATovYrhQbxYHTGlQUDbLJp9yoaLdTfL1clfBtaIqknpRBsSBRHH7ikobSN7hqn4
wLlj7hoFm35nOpAf/3fmMbIHF0ntRKlL9LMEwGeZjLMWVx1/6K8jsxHY1qzUzmOD
OkWDR4bWQNcpwTmfeBo6FsXOW7+sO5r4LwhvOOvkhYEwWI41Nsb0MLYXv7Q+SFZG
2TPFLdOxR2R4LqHg+Nse
=p3Oi
-----END PGP SIGNATURE-----

firefly timing

[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

Re: firefly timing

[Stefan Priebe - Profihost AG]

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
> 

Re: firefly timing

[Ирек Фасихов]

[-- Attachment #1.1: Type: text/plain, Size: 2242 bytes --]

I'm ready to test the tiering.


2014-03-18 11:07 GMT+04:00 Stefan Priebe - Profihost AG <
s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@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
> >
> _______________________________________________
> ceph-users mailing list
> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>



-- 
С уважением, Фасихов Ирек Нургаязович
Моб.: +79229045757

[-- Attachment #1.2: Type: text/html, Size: 3245 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: firefly timing

[Karan Singh]

[-- Attachment #1.1: Type: text/plain, Size: 3035 bytes --]

Hello Everyone

I am looking forward to test new features of 0.78 , it would be nice if erasure coding and tiering implementation notes available in ceph documentation.

Ceph documentation is in a good shape and its always nice to follow.

A humble request to add erasure coding and tiering in documentation if its not already in your pipeline. 


Karan Singh
CSC - IT Center for Science Ltd.
P.O. Box 405, FI-02101 Espoo, FINLAND
http://www.csc.fi/ | +358 (0) 503 812758

On 18 Mar 2014, at 09:13, Ирек Фасихов <malmyzh-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> I'm ready to test the tiering.
> 
> 
> 2014-03-18 11:07 GMT+04:00 Stefan Priebe - Profihost AG <s.priebe-2Lf/h1ldwEHR5kwTpVNS9A@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
> >
> _______________________________________________
> ceph-users mailing list
> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 
> 
> 
> -- 
> С уважением, Фасихов Ирек Нургаязович
> Моб.: +79229045757
> _______________________________________________
> ceph-users mailing list
> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


[-- Attachment #1.2: Type: text/html, Size: 4913 bytes --]

[-- Attachment #2: Type: text/plain, Size: 178 bytes --]

_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: firefly timing

[Alexandre DERUMIER]

Hi Stefan, 

http://ceph.com/docs/master/dev/cache-pool/ 




----- Mail original -----

De: "Stefan Priebe - Profihost AG" <s.priebe@profihost.ag> 
À: "Sage Weil" <sage@inktank.com>, ceph-devel@vger.kernel.org 
Cc: ceph-users@ceph.com 
Envoyé: Mardi 18 Mars 2014 08:07:19 
Objet: Re: [ceph-users] firefly timing 

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@vger.kernel.org 
> More majordomo info at http://vger.kernel.org/majordomo-info.html 
> 
_______________________________________________ 
ceph-users mailing list 
ceph-users@lists.ceph.com 
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com 
_______________________________________________
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: firefly timing

[Sage Weil]

On Tue, 18 Mar 2014, 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?

Great!  Here is a quick synopiss on how to set it up:

	http://ceph.com/docs/master/dev/cache-pool/

sage



> 
> 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@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 

Re: firefly timing

[Stefan Priebe - Profihost AG]

> Am 18.03.2014 um 17:06 schrieb Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org>:
> 
>> On Tue, 18 Mar 2014, 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?
> 
> Great!  Here is a quick synopiss on how to set it up:
> 
>    http://ceph.com/docs/master/dev/cache-pool/

What I'm missing is a documentation about the cache settings?

> 
> sage
> 
> 
> 
>> 
>> 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
>> --
>> 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
>> 
>> 

Re: firefly timing

[Milosz Tanski]

Is this statement in the documentation still valid: "Stale data is
expired from the cache pools based on some as-yet undetermined
policy." As that sounds a bit scary.

- Milosz

On Tue, Mar 18, 2014 at 12:06 PM, Sage Weil <sage@inktank.com> wrote:
> On Tue, 18 Mar 2014, 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?
>
> Great!  Here is a quick synopiss on how to set it up:
>
>         http://ceph.com/docs/master/dev/cache-pool/
>
> sage
>
>
>
>>
>> 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@vger.kernel.org
>> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> >
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Milosz Tanski
CTO
10 East 53rd Street, 37th floor
New York, NY 10022

p: 646-253-9055
e: milosz@adfin.com

Re: firefly timing

[Sage Weil]

On Tue, 18 Mar 2014, Milosz Tanski wrote:
> Is this statement in the documentation still valid: "Stale data is
> expired from the cache pools based on some as-yet undetermined
> policy." As that sounds a bit scary.

I'll update the docs :).  The policy is pretty simply but not described 
anywhere yet.

sage


> 
> - Milosz
> 
> On Tue, Mar 18, 2014 at 12:06 PM, Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org> wrote:
> > On Tue, 18 Mar 2014, 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?
> >
> > Great!  Here is a quick synopiss on how to set it up:
> >
> >         http://ceph.com/docs/master/dev/cache-pool/
> >
> > sage
> >
> >
> >
> >>
> >> 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
> >> >
> >> --
> >> 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
> >>
> >>
> > --
> > 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
> 
> 
> 
> -- 
> Milosz Tanski
> CTO
> 10 East 53rd Street, 37th floor
> New York, NY 10022
> 
> p: 646-253-9055
> e: milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org
> 
> 

Re: firefly timing

[Sage Weil]

On Tue, 18 Mar 2014, Sage Weil wrote:
> On Tue, 18 Mar 2014, Milosz Tanski wrote:
> > Is this statement in the documentation still valid: "Stale data is
> > expired from the cache pools based on some as-yet undetermined
> > policy." As that sounds a bit scary.
> 
> I'll update the docs :).  The policy is pretty simply but not described 
> anywhere yet.

I've updated the doc; please let me know what is/isn't clear so we can 
make sure the final doc is useful.

John, we need to figure out where this is going to fit in the overall 
IA...

sage



> 
> sage
> 
> 
> > 
> > - Milosz
> > 
> > On Tue, Mar 18, 2014 at 12:06 PM, Sage Weil <sage-4GqslpFJ+cxBDgjK7y7TUQ@public.gmane.org> wrote:
> > > On Tue, 18 Mar 2014, 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?
> > >
> > > Great!  Here is a quick synopiss on how to set it up:
> > >
> > >         http://ceph.com/docs/master/dev/cache-pool/
> > >
> > > sage
> > >
> > >
> > >
> > >>
> > >> 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
> > >> >
> > >> --
> > >> 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
> > >>
> > >>
> > > --
> > > 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
> > 
> > 
> > 
> > -- 
> > Milosz Tanski
> > CTO
> > 10 East 53rd Street, 37th floor
> > New York, NY 10022
> > 
> > p: 646-253-9055
> > e: milosz-B5zB6C1i6pkAvxtiuMwx3w@public.gmane.org
> > 
> > 
> --
> 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
> 
> 

Re: firefly timing

[Milosz Tanski]

I think it's good now, explicit (and detailed).

On Tue, Mar 18, 2014 at 4:12 PM, Sage Weil <sage@inktank.com> wrote:
> On Tue, 18 Mar 2014, Sage Weil wrote:
>> On Tue, 18 Mar 2014, Milosz Tanski wrote:
>> > Is this statement in the documentation still valid: "Stale data is
>> > expired from the cache pools based on some as-yet undetermined
>> > policy." As that sounds a bit scary.
>>
>> I'll update the docs :).  The policy is pretty simply but not described
>> anywhere yet.
>
> I've updated the doc; please let me know what is/isn't clear so we can
> make sure the final doc is useful.
>
> John, we need to figure out where this is going to fit in the overall
> IA...
>
> sage
>
>
>
>>
>> sage
>>
>>
>> >
>> > - Milosz
>> >
>> > On Tue, Mar 18, 2014 at 12:06 PM, Sage Weil <sage@inktank.com> wrote:
>> > > On Tue, 18 Mar 2014, 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?
>> > >
>> > > Great!  Here is a quick synopiss on how to set it up:
>> > >
>> > >         http://ceph.com/docs/master/dev/cache-pool/
>> > >
>> > > sage
>> > >
>> > >
>> > >
>> > >>
>> > >> 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@vger.kernel.org
>> > >> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> > >> >
>> > >> --
>> > >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> > >> the body of a message to majordomo@vger.kernel.org
>> > >> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> > >>
>> > >>
>> > > --
>> > > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> > > the body of a message to majordomo@vger.kernel.org
>> > > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> >
>> >
>> >
>> > --
>> > Milosz Tanski
>> > CTO
>> > 10 East 53rd Street, 37th floor
>> > New York, NY 10022
>> >
>> > p: 646-253-9055
>> > e: milosz@adfin.com
>> >
>> >
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>



-- 
Milosz Tanski
CTO
10 East 53rd Street, 37th floor
New York, NY 10022

p: 646-253-9055
e: milosz@adfin.com