From: Maged Mokhtar <mmokhtar-6jkX1og9WkpAfugRpC6u6w@public.gmane.org>
To: Alfredo Deza <adeza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ceph-disk is now deprecated
Date: Tue, 28 Nov 2017 14:20:33 +0200 [thread overview]
Message-ID: <58d2cc9068a226ef269faac3597a19d3@petasan.org> (raw)
In-Reply-To: <CAC-Np1zfMoqtW2M75ZAys1_NTEkns6MJ6HimuRR3nFhbMVzjPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2672 bytes --]
I tend to agree with Wido. May of us still reply on ceph-disk and hope
to see it live a little longer.
Maged
On 2017-11-28 13:54, Alfredo Deza wrote:
> On Tue, Nov 28, 2017 at 3:12 AM, Wido den Hollander <wido-fspyXLx8qC4@public.gmane.org> wrote:
> Op 27 november 2017 om 14:36 schreef Alfredo Deza <adeza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>:
>
> For the upcoming Luminous release (12.2.2), ceph-disk will be
> officially in 'deprecated' mode (bug fixes only). A large banner with
> deprecation information has been added, which will try to raise
> awareness.
>
> As much as I like ceph-volume and the work being done, is it really a good idea to use a minor release to deprecate a tool?
>
> Can't we just introduce ceph-volume and deprecate ceph-disk at the release of M? Because when you upgrade to 12.2.2 suddenly existing integrations will have deprecation warnings being thrown at them while they haven't upgraded to a new major version.
ceph-volume has been present since the very first release of Luminous,
the deprecation warning in ceph-disk is the only "new" thing
introduced for 12.2.2.
> As ceph-deploy doesn't support ceph-disk either I don't think it's a good idea to deprecate it right now.
ceph-deploy work is being done to support ceph-volume exclusively
(ceph-disk support is dropped fully), which will mean a change in its
API in a non-backwards compatible
way. A major version change in ceph-deploy, documentation, and a bunch
of documentation is being worked on to allow users to transition to
it.
> How do others feel about this?
>
> Wido
>
>> We are strongly suggesting using ceph-volume for new (and old) OSD
>> deployments. The only current exceptions to this are encrypted OSDs
>> and FreeBSD systems
>>
>> Encryption support is planned and will be coming soon to ceph-volume.
>>
>> A few items to consider:
>>
>> * ceph-disk is expected to be fully removed by the Mimic release
>> * Existing OSDs are supported by ceph-volume. They can be "taken over" [0 [1]]
>> * ceph-ansible already fully supports ceph-volume and will soon default to it
>> * ceph-deploy support is planned and should be fully implemented soon
>>
>> [0] http://docs.ceph.com/docs/master/ceph-volume/simple/
>> _______________________________________________
>> ceph-users mailing list
>> ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
Links:
------
[1] http://docs.ceph.com/docs/master/ceph-volume/simple/
[-- Attachment #1.2: Type: text/html, Size: 4569 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
next prev parent reply other threads:[~2017-11-28 12:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 13:36 ceph-disk is now deprecated Alfredo Deza
2017-11-27 20:07 ` Nathan Cutler
2017-11-28 8:24 ` Fabian Grünbichler
[not found] ` <CALWuvY9mX0Pdr4aMwPi=Dqw0qng959Z5bg5hs5dOxTfSZ+QH4Q@mail.gmail.com>
2017-11-28 12:00 ` Alfredo Deza
2017-11-28 6:56 ` Andreas Calminder
2017-11-28 11:47 ` Alfredo Deza
[not found] ` <CAC-Np1wp1M=qapRO0sCr1HMLpZ2zgLoh-GVv3p01k2DqjxqaOw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 12:22 ` Andreas Calminder
2017-11-28 12:37 ` Alfredo Deza
[not found] ` <CAC-Np1xqg2-wAguu8AO6LSbj41uOGSBZTgdgL45OAi5M080grw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 13:14 ` Andreas Calminder
[not found] ` <CAC-Np1z7OJNxUeso+FEB8g+7RUABkvKF58_mmXDHt4SeOTHSDw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 8:12 ` Wido den Hollander
2017-11-28 8:39 ` [ceph-users] " Piotr Dałek
[not found] ` <4c4b5589-b1ae-3f8b-e900-af0f2895fbc9-Rm6v+N6rxxBWk0Htik3J/w@public.gmane.org>
2017-11-28 12:32 ` Alfredo Deza
[not found] ` <CAC-Np1zsf+uqFi+ZdR7K3=re5ODpJvWFrTX-JU_8DkkyVGOz7A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 14:26 ` Willem Jan Withagen
[not found] ` <d548c5a8-c0dc-0737-66f4-e3fc04f900d7-dOtk1Lsa4IaEVqv0pETR8A@public.gmane.org>
2017-11-28 17:22 ` David Turner
[not found] ` <CAN-Gep+RmSB6gW5GRVsT8T7j60EAzGnfbgeqDjwCNDWocpgp3g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 18:39 ` Vasu Kulkarni
2017-11-30 11:31 ` [ceph-users] " Fabian Grünbichler
2017-11-30 12:04 ` Alfredo Deza
[not found] ` <CAC-Np1wo_j5MBXTzm5kp-MjWiV=vkL+5Xt88SS617MJ4qmh5UQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-30 13:04 ` Fabian Grünbichler
[not found] ` <1821337488.5487.1511856776936-4q+tAGQs9zLCXE5Mi8V/gA@public.gmane.org>
2017-11-28 11:54 ` Alfredo Deza
[not found] ` <CAC-Np1zfMoqtW2M75ZAys1_NTEkns6MJ6HimuRR3nFhbMVzjPg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 12:20 ` Maged Mokhtar [this message]
2017-11-28 12:27 ` Wido den Hollander
2017-11-28 12:38 ` Joao Eduardo Luis
[not found] ` <1db3fa50-d022-bf37-eb4b-098882ea0984-l3A5Bk7waGM@public.gmane.org>
2017-11-28 12:52 ` Alfredo Deza
[not found] ` <CAC-Np1ynRyeOChGK2k_oBAx0A7XcAFkMDMrxVHZhN-pjGXfAJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-28 14:17 ` Joao Eduardo Luis
2017-11-29 12:51 ` Yoann Moulin
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=58d2cc9068a226ef269faac3597a19d3@petasan.org \
--to=mmokhtar-6jkx1og9wkpafugrpc6u6w@public.gmane.org \
--cc=adeza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ceph-users-idqoXFIVOFJgJs9I8MT0rw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox