v0.52 released

v0.52 released

[Sage Weil]

After several weeks of testing v0.52 is ready! This is a big release for 
RBD and radosgw users. Highlights include:

 * librbd: fully functional and documented image cloning
 * librbd: image (advisory) locking
 * librbd: 'protect'/'unprotect' commands to prevent clone parent from 
   being deleted
 * librbd: 'flatten' command to sever clone parent relationship
 * librbd: a few fixes to 'discard' support
 * osd: several out of order reply bug fixes
 * msgr: improved failure handling code
 * auth: expanded authentication settings for greater flexibility
 * mon: 'report' command for dumping detailed cluster status
 * mon: throttle client messages (limit memory consumption)
 * mon: more informative info about stuck PGs in 'health detail'
 * osd, mon: use feature bits to lock out clients lacking CRUSH tunables 
   when they are in use
 * radosgw: support for swift manifest objects
 * radosgw: support for multi-object deletes
 * radosgw: improved garbage collection framework
 * rados: bench command now cleans up after itself
 * ceph.spec: misc packaging fixes

The big news in this release is that the new RBD cloning functionality is 
fully in place. This includes the ability to take a base image (snapshot) 
and instantly 'clone' it to other images. The typical use case is cloning 
a base OS install image for each VM, allowing you to immediately boot them 
up without waiting for any data to copy. RBD also got advisory locking 
support, which allows users to (cooperatively) control who is using each 
image and avoid situations where multiple hosts write to the same image 
and corrupt the file system. There is additional integration work on the 
roadmap that will make this easier to use, but all of the pieces are in 
place for users to starting taking advantage of it now.

This release also includes several improvements to the radosgw. On the 
user-facing API side this includes support for Swift 'manifest' objects 
(large objects uploaded in pieces) and support for multi-object delete. On 
the administrative side, there is a new garbage collection framework that 
makes the cleanup of deleted objects transparent, automatic, and 
efficient. (Currently a radosgw-admin command run from something like cron 
is necessary to clear out old data.)

On the release side, this is also the first release for which we are 
building RPMs. Hooray! We're starting with just CentOS6/RHEL6 and Fedora 
17 on x86_64, but will be adding additional distributions for v0.53, 
including OpenSUSE and Fedora 18. If there is a particular RPM-based 
distro that you'd like to see us build packages for, please let us know!

You can get v0.52 from:
 * Git at git://github.com/ceph/ceph.git
 * Tarball athttp://ceph.com/download/ceph-0.52.tar.gz
 * For Debian/Ubuntu packages, see http://ceph.com/docs/master/install/debian
 * For RPMs, see http://ceph.com/docs/master/install/rpm

Re: v0.52 released

[Smart Weblications GmbH - Florian Wiessner]

Am 27.09.2012 22:07, schrieb Sage Weil:
> After several weeks of testing v0.52 is ready! This is a big release for 
> RBD and radosgw users. Highlights include:

Is this a stable release to replace 0.48.2 ?


-- 

Mit freundlichen Grüßen,

Florian Wiessner

Smart Weblications GmbH
Martinsberger Str. 1
D-95119 Naila

fon.: +49 9282 9638 200
fax.: +49 9282 9638 205
24/7: +49 900 144 000 00 - 0,99 EUR/Min*
http://www.smart-weblications.de

--
Sitz der Gesellschaft: Naila
Geschäftsführer: Florian Wiessner
HRB-Nr.: HRB 3840 Amtsgericht Hof
*aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz
--
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: v0.52 released

[Sage Weil]

On Thu, 27 Sep 2012, Smart Weblications GmbH - Florian Wiessner wrote:
> Am 27.09.2012 22:07, schrieb Sage Weil:
> > After several weeks of testing v0.52 is ready! This is a big release for 
> > RBD and radosgw users. Highlights include:
> 
> Is this a stable release to replace 0.48.2 ?

No, this is a normal development release.  It goes through several weeks 
of testing before release, so it should be pretty stable, but it's not a 
long-term type release.  The next stable release will be bobtail, and will 
most likely be based on 0.54.  0.53 was just frozen.

sage

> 
> 
> -- 
> 
> Mit freundlichen Gr??en,
> 
> Florian Wiessner
> 
> Smart Weblications GmbH
> Martinsberger Str. 1
> D-95119 Naila
> 
> fon.: +49 9282 9638 200
> fax.: +49 9282 9638 205
> 24/7: +49 900 144 000 00 - 0,99 EUR/Min*
> http://www.smart-weblications.de
> 
> --
> Sitz der Gesellschaft: Naila
> Gesch?ftsf?hrer: Florian Wiessner
> HRB-Nr.: HRB 3840 Amtsgericht Hof
> *aus dem dt. Festnetz, ggf. abweichende Preise aus dem Mobilfunknetz
> 
> 

Re: v0.52 released

[Tommi Virtanen]

On Thu, Sep 27, 2012 at 1:57 PM, Sage Weil <sage@inktank.com> wrote:
>> Is this a stable release to replace 0.48.2 ?
> No, this is a normal development release.  It goes through several weeks
> of testing before release, so it should be pretty stable, but it's not a
> long-term type release.  The next stable release will be bobtail, and will
> most likely be based on 0.54.  0.53 was just frozen.

Perhaps it's worth saying this explicitly: stable releases will have a
version number like

<major>.<minor>[.<patch>]<codename>

It'll be a stable release when you see the next cute codename show up.
I expect we'll make more noise at that time, too ;)

Codenames will increment alphabetically: argonaut, bobtail ...

Re: v0.52 released

[Denis Fondras]

Hello all,

Is it possible/recommended to mix versions ? ie. OSD with 0.48 and MON 
with 0.52 or some OSD with 0.48 and some with 0.52 ?

Denis

Re: v0.52 released

[Sage Weil]

On Fri, 28 Sep 2012, Denis Fondras wrote:
> Hello all,
> 
> Is it possible/recommended to mix versions ? ie. OSD with 0.48 and MON with
> 0.52 or some OSD with 0.48 and some with 0.52 ?

Yes, that is supported.  We haven't done heavy-duty testing yet mixing 
0.48 with 0.52+ and osd thrashing, but we will be shortly.

sage

Re: v0.52 released

[Jimmy Tang]

Hi Sage,

On 27 Sep 2012, at 21:07, Sage Weil wrote:

> 
> On the release side, this is also the first release for which we are 
> building RPMs. Hooray! We're starting with just CentOS6/RHEL6 and Fedora 
> 17 on x86_64, but will be adding additional distributions for v0.53, 
> including OpenSUSE and Fedora 18. If there is a particular RPM-based 
> distro that you'd like to see us build packages for, please let us know!
> 
> You can get v0.52 from:
> * Git at git://github.com/ceph/ceph.git
> * Tarball athttp://ceph.com/download/ceph-0.52.tar.gz
> * For Debian/Ubuntu packages, see http://ceph.com/docs/master/install/debian
> * For RPMs, see http://ceph.com/docs/master/install/rpm

Scientific Linux 6 is something that we use here at our site, it's binary compatible with RHEL6 and Centos6. Since there is a 'stable' series of releases and a series of 'testing and development' releases would it be better to setup a repo with only stable releases and a testing repo for all development builds (and nighty builds)? It would make it easier for anyone who wants to deploy ceph  in production to just point to a stable repo and not get a development builds. It would be similar to how epel might structure their repos with a stable and a testing repo.

Regards,
Jimmy Tang

--
Senior Software Engineer, Digital Repository of Ireland (DRI)
Trinity Centre for High Performance Computing,
Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
http://www.tchpc.tcd.ie/

Re: v0.52 released

[Sage Weil]

Hi,

On Fri, 28 Sep 2012, Jimmy Tang wrote:
> Hi Sage,
> 
> On 27 Sep 2012, at 21:07, Sage Weil wrote:
> 
> > 
> > On the release side, this is also the first release for which we are 
> > building RPMs. Hooray! We're starting with just CentOS6/RHEL6 and Fedora 
> > 17 on x86_64, but will be adding additional distributions for v0.53, 
> > including OpenSUSE and Fedora 18. If there is a particular RPM-based 
> > distro that you'd like to see us build packages for, please let us know!
> > 
> > You can get v0.52 from:
> > * Git at git://github.com/ceph/ceph.git
> > * Tarball athttp://ceph.com/download/ceph-0.52.tar.gz
> > * For Debian/Ubuntu packages, see http://ceph.com/docs/master/install/debian
> > * For RPMs, see http://ceph.com/docs/master/install/rpm
> 
> Scientific Linux 6 is something that we use here at our site, it's binary compatible with RHEL6 and Centos6. Since there is a 'stable' series of releases and a series of 'testing and development' releases would it be better to setup a repo with only stable releases and a testing repo for all development builds (and nighty builds)? It would make it easier for anyone who wants to deploy ceph  in production to just point to a stable repo and not get a development builds. It would be similar to how epel might structure their repos with a stable and a testing repo.

Ah, good point.  You can do that today with the debian repos, but we 
lumped all the rpms into ceph.com/rpms.  Currently

debian			symlink to debian-argonaut (latest stable)
debian-argonaut		stable argonaut releases
debian-testing		dev releases

We can do the same with the rpms...

rpm
rpm-argonaut
rpm-testing

?
sage


> Regards,
> Jimmy Tang
> 
> --
> Senior Software Engineer, Digital Repository of Ireland (DRI)
> Trinity Centre for High Performance Computing,
> Lloyd Building, Trinity College Dublin, Dublin 2, Ireland.
> http://www.tchpc.tcd.ie/
> 
> --
> 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: v0.52 released

[Jimmy Tang]

Hi Sage,

On 28 Sep 2012, at 16:16, Sage Weil wrote:

> 
> Ah, good point.  You can do that today with the debian repos, but we 
> lumped all the rpms into ceph.com/rpms.  Currently
> 
> debian			symlink to debian-argonaut (latest stable)
> debian-argonaut		stable argonaut releases
> debian-testing		dev releases
> 
> We can do the same with the rpms...
> 
> rpm
> rpm-argonaut
> rpm-testing
> 
> ?

That sounds reasonable to do ;) +1 for something similar to what you are proposing.

Jimmy.