CEPH filesystem development
 help / color / mirror / Atom feed
From: Abhishek Lekshmanan <abhishek@suse.com>
To: ceph-devel@vger.kernel.org, ceph-users@ceph.com,
	ceph-maintainers@ceph.com, ceph-announce@ceph.com
Subject: v12.0.1 Luminous (dev) released
Date: Wed, 29 Mar 2017 07:49:30 +0200	[thread overview]
Message-ID: <58DB4AEA.6040402@suse.com> (raw)

This is the second development checkpoint release of Luminous, the next
long term stable release.

Major changes from 12.0.0
-------------------------
* The original librados rados_objects_list_open (C) and objects_begin
   (C++) object listing API, deprecated in Hammer, has finally been
   removed.  Users of this interface must update their software to use
   either the rados_nobjects_list_open (C) and nobjects_begin (C++) API or
   the new rados_object_list_begin (C) and object_list_begin (C++) API
   before updating the client-side librados library to Luminous.

   Object enumeration (via any API) with the latest librados version
   and pre-Hammer OSDs is no longer supported.  Note that no in-tree
   Ceph services rely on object enumeration via the deprecated APIs, so
   only external librados users might be affected.

   The newest (and recommended) rados_object_list_begin (C) and
   object_list_begin (C++) API is only usable on clusters with the
   SORTBITWISE flag enabled (Jewel and later).  (Note that this flag is
   required to be set before upgrading beyond Jewel.)

* CephFS clients without the 'p' flag in their authentication capability
   string will no longer be able to set quotas or any layout fields.  This
   flag previously only restricted modification of the pool and namespace
   fields in layouts.

* The rados copy-get-classic operation has been removed since it has not 
been
   used by the OSD since before hammer.  It is unlikely any librados user is
   using this operation explicitly since there is also the more modern 
copy-get.

* The RGW api for getting object torrent has changed its params from 
'get_torrent'
   to 'torrent' so that it can be compatible with Amazon S3. Now the 
request for
   object torrent is like 'GET /ObjectName?torrent'.

See http://ceph.com/releases/v12-0-1-luminous-dev-released/ for a more
detailed changelog on this release, and thank you everyone for
contributing.

While we're fixing a few issues in the build system, the arm64 packages
for centos7 are, unfortunately, not available for this dev release.

Getting Ceph
------------

* Git at git://github.com/ceph/ceph.git
* Tarball at http://download.ceph.com/tarballs/ceph-12.0.1.tar.gz
* For packages, see http://docs.ceph.com/docs/master/install/get-packages/
* For ceph-deploy, see 
http://docs.ceph.com/docs/master/install/install-ceph-deploy
* Release sha1: 5456408827a1a31690514342624a4ff9b66be1d5

--
Abhishek Lekshmanan
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, 
HRB 21284 (AG Nürnberg)



                 reply	other threads:[~2017-03-29  5:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=58DB4AEA.6040402@suse.com \
    --to=abhishek@suse.com \
    --cc=ceph-announce@ceph.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=ceph-maintainers@ceph.com \
    --cc=ceph-users@ceph.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox