From: Stefan Kooman <stefan-68+x73Hep80@public.gmane.org>
To: Alfredo Deza <adeza-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
ceph-users <ceph-users-idqoXFIVOFJgJs9I8MT0rw@public.gmane.org>,
ceph-devel <ceph-devel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ceph-disk removal roadmap (was ceph-disk is now deprecated)
Date: Fri, 1 Dec 2017 09:28:10 +0100 [thread overview]
Message-ID: <20171201082810.GH30636@shell.dmz.bit.nl> (raw)
In-Reply-To: <20171201081757.qwfo2lrhpmg77jgd-aVfaTQcAavps8ZkLLAvlZtBPR1lH4CV8@public.gmane.org>
Quoting Fabian Grünbichler (f.gruenbichler-YTcQvvOqK21BDgjK7y7TUQ@public.gmane.org):
> I think the above roadmap is a good compromise for all involved parties,
> and I hope we can use the remainder of Luminous to prepare for a
> seam- and painless transition to ceph-volume in time for the Mimic
> release, and then finally retire ceph-disk for good!
Will the upcoming 12.2.2 release ship with a ceph-volume capable of
doing bluestore on top of LVM? Eager to use ceph-volume for that, and
skip entirely over ceph-disk and our manual osd prepare process ...
Gr. Stefan
--
| BIT BV http://www.bit.nl/ Kamer van Koophandel 09090351
| GPG: 0xD14839C6 +31 318 648 688 / info-68+x73Hep80@public.gmane.org
next prev parent reply other threads:[~2017-12-01 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 16:25 ceph-disk removal roadmap (was ceph-disk is now deprecated) Alfredo Deza
[not found] ` <CAC-Np1zdwLALBE_eheCJ+bR_A4-Gway6fpv6smcQNjt-4=9RxA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-30 16:35 ` Peter Woodman
2017-11-30 16:36 ` [ceph-users] " Peter Woodman
2017-12-01 8:17 ` Fabian Grünbichler
[not found] ` <20171201081757.qwfo2lrhpmg77jgd-aVfaTQcAavps8ZkLLAvlZtBPR1lH4CV8@public.gmane.org>
2017-12-01 8:28 ` Stefan Kooman [this message]
2017-12-01 12:45 ` [ceph-users] " Alfredo Deza
2017-12-01 17:28 ` Alfredo Deza
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=20171201082810.GH30636@shell.dmz.bit.nl \
--to=stefan-68+x73hep80@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 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.